Keep MainWP.See your whole agency.

Don’t replace MainWP — plug it in

MainWP keeps doing the work, on your server. Burrow becomes where you look.

MainWP is the self-hosted WordPress management dashboard trusted by tens of thousands of site owners. Open source, privacy-first, unlimited sites, your infrastructure. You chose it for control — and connecting Burrow doesn’t take any of that back. You create a read-only key yourself, scoped how you want, revocable whenever you want.

Burrow is where the owner looks when the question isn’t “are the child sites updated?” but “which clients are healthy, profitable, and actually delivered this quarter?”

What imports — and what stays in MainWP

We’d rather be precise than impressive. Here’s exactly what the integration covers:

Your MainWP monitors are a real strength — they show up in Burrow with incident history, so the WordPress fleet doesn’t need a separate uptime service.

Optional: go deeper with the Burrow plugin

The connection installs nothing on child sites. The plugin is there when you want more.

Some signals no maintenance platform API can see: whether the contact form actually delivered a lead, whether the WooCommerce checkout completed. For sites where that matters, the Burrow WordPress plugin captures form submissions from Gravity Forms, Fluent Forms, Ninja Forms, and Contact Form 7, plus WooCommerce order and checkout events — with history backfill on install.

It’s entirely optional and separate from the MainWP connection. Connect the API today with zero installs; add the plugin later, per site, only where form and commerce visibility earns its keep.

Self-hosted stays self-hosted

You create the key. You scope it. You can kill it.

Most SaaS integrations ask for account-level tokens on their terms. MainWP is different, and we lean into that: you generate a Read-only key in API Access yourself. Burrow never has write access because the key you created can’t grant it.

One honest requirement: your dashboard must be reachable from Burrow’s servers over HTTPS. Most setups connect out of the box; dashboards behind VPNs or strict allowlists need a firewall rule, and our reachability doc covers the cases — including the ones where it won’t work. We’d rather tell you that here than in a support ticket.

The rest of your portfolio, finally in the same view

Almost no agency is purely WordPress. Your maintenance dashboard will never show the headless build or the Shopify store.

Burrow puts your WordPress portfolio (imported from MainWP) next to Craft sites, Next.js apps, Shopify stores, GitHub activity, analytics, and invoices — organized by client, not by site. A client with a marketing site, a store, and a staging environment is three rows in MainWP. In Burrow it’s one client, with billing and repos attached. Because MainWP exposes client records via API, that structure imports automatically.

Know which clients are worth keeping

Site health is half the picture. Here’s the other half.

MainWP tells you a site is behind on updates. Burrow tells you that same client is also behind on invoices, logged 30 hours against a 10-hour retainer, and hasn’t had a deploy in two months.

Invoicing from Harvest, FreshBooks, or Tillage; code activity from GitHub; traffic from Plausible, Fathom, or GA — all joined against the client record you already keep in MainWP. That’s owner-level value, and the owner signs the subscription.

Reports that justify the whole retainer

Maintenance reports prove maintenance. Your retainer is bigger than that.

MainWP reports show updates applied and site health — and they’re good at it. Burrow reports add what shipped (commits and pull requests), how traffic moved, and what was billed. When a client asks “what am I paying you for?”, you answer with the whole engagement — not just the care plan.

Before and after

Before Burrow: MainWP shows 60 child sites green and every monitor quiet. But a third of your work isn’t WordPress — the Next.js app, two Shopify stores, a Craft build — and for those clients you’re back to five open tabs. Quarterly reviews mean assembling MainWP reports, GitHub logs, and Harvest exports into a document by hand, every time, for every client.

After Burrow: The same 60 sites import via a read-only key, monitors and incident history included. The non-WordPress projects live in the same client cards. The quarterly report generates from the timeline — updates from MainWP, deploys from GitHub, hours and invoices from Harvest — and assembling it drops from an afternoon to a review pass.

How Burrow fits with MainWP

Run both. Use MainWP for fleet management on your server. Use Burrow for the unified client view, profitability visibility, and retainer-grade reporting.

Compare Burrow vs MainWP | Maintenance reporting | All integrations