WPCentrify vs MainWP: managed platform or self-hosted dashboard
This is not really a feature comparison. It is a decision about whether you want to run the management infrastructure yourself in exchange for no per-site fees and physical possession of your data.
Reviewed 26 August 2026. MainWP features and pricing re-checked quarterly.
The short version
MainWP is a self-hosted WordPress plugin. You install a dashboard site, connect child sites to it, and pay no per-site fee. Your data sits on your server. Extending it means buying extensions.
WPCentrify is a managed platform. There is no dashboard to run, monitoring happens from our infrastructure rather than your cron, and management, monitoring, reporting and agency workflows are included in a plan.
The trade is straightforward and worth stating plainly: MainWP costs less money and more time, WPCentrify costs more money and less time. Which is correct depends on the value of an hour of your team's time and how large the portfolio is.
Who should choose which
Choose WPCentrify if
- You do not want to maintain a dashboard server
- Your portfolio is past about twenty sites
- You need monitoring that survives your own hosting having a bad day
- You want tickets, time and profitability in the same tool
- Nobody on the team enjoys server maintenance
Choose MainWP if
- Data residency on your own hardware is contractual
- You have strong server skills already on staff
- You have built custom automation on MainWP hooks
- Per-site fees are the specific thing you are avoiding
- You want lifetime licensing rather than subscription
WPCentrify and MainWP compared
Checked against public product and pricing pages on 26 August 2026. Where a capability is available only on higher tiers or as a paid add-on, it is marked partial rather than yes.
| Capability | WPCentrify | MainWP |
|---|---|---|
| Deployment model | Managed SaaS | Self-hosted |
| Per-site fee | None on plan | None |
| Dashboard server you must maintain | None required | Required |
| Data stored on your own hardware | No | Yes |
| Full data export on demand | Yes | Yes |
| Bulk updates across portfolio | Yes | Yes |
| Update risk scoring | Yes | No |
| Visual regression on update | Yes | Via extension |
| Automatic rollback | Yes | No |
| Backups included | Yes | Via extension |
| Scheduled restore testing | Yes | No |
| Uptime monitoring from external infrastructure | Yes | Runs on your server |
| Vulnerability monitoring | Yes | Via extension |
| White-label client reports | Yes | Via extension |
| Support tickets and time tracking | Yes | No |
| Per-client profitability | Yes | Cost tracking extension |
| Public API and webhooks | Yes | Yes |
| Lifetime licence option | No | Yes |
The dashboard is the whole argument
Everything else in this comparison follows from one fact: MainWP's dashboard is a WordPress site that you own and operate. That gives you complete control and it gives you a second job.
The dashboard needs hosting, PHP version management, its own updates, its own security hardening and its own backups. It needs to be fast enough to render a portfolio view at your site count, which becomes a real tuning exercise somewhere north of a hundred and fifty sites. When it is down, you have no visibility into any client. When a MainWP extension conflicts with a WordPress core release, you debug it.
There is also a subtler issue with monitoring. Uptime checks that run from your own server tell you the site is up as seen from your server. If your host has a routing problem, you can get false alerts or, worse, miss real ones. External monitoring infrastructure exists specifically to avoid that class of blind spot.
None of this makes MainWP a bad product. It makes it a product with an operating cost that does not appear on the pricing page, and agencies should price that cost honestly rather than treating self-hosted as free.
Pricing structure
MainWP's core is free with paid extensions and a lifetime option, and there is no per-site fee at any scale, which is genuinely hard to beat on headline cost. WPCentrify uses portfolio tiers with everything included. The comparison that matters is MainWP licence plus extensions plus dashboard hosting plus maintenance hours, against a WPCentrify plan with no infrastructure work at all.
Model both against your own site count before deciding. Neither product is universally cheaper, and anyone who tells you otherwise has not done the arithmetic.
Where MainWP is the better product
If contractual or regulatory requirements mean client data cannot sit on third-party infrastructure, MainWP is not merely the better option, it is the only one of the two that qualifies. No amount of export tooling substitutes for physical possession when the requirement is written that way.
MainWP is also the better choice if you have already built substantial custom automation on its hooks and extension API. That work has real value, it does not port, and throwing it away to gain workflow features you may not need is a poor trade.
Finally, at genuinely large portfolios with a competent systems person already on staff, MainWP's economics are extremely strong. A thousand sites with no per-site fee is a proposition managed platforms struggle to match, and if the maintenance overhead lands on someone who is already employed and good at it, the hidden cost we describe above is much smaller than we have made it sound.
Common questions about WPCentrify and MainWP
The core plugin is free and there is no per-site fee, which is real and significant. The full picture includes paid extensions for most agency capability, hosting for the dashboard site, and staff time to maintain it. Whether that totals more or less than a managed platform depends on your site count and what your team's hours are worth.
You lose physical possession of the database. You keep full export of your account data in a machine-readable format on demand, hosting neutrality, published documentation of what we store and where, and a connector that removes cleanly from any site. If possession specifically is the requirement, MainWP is the correct answer.
Yes. The MainWP child plugin and the WPCentrify connector are independent and do not conflict. Running both during a transition is the recommended approach.
It depends on staffing. MainWP's zero per-site cost is very attractive at that scale, but dashboard performance tuning becomes a real task and a dashboard outage costs you visibility into two hundred clients simultaneously. With a systems person on staff, MainWP scales fine. Without one, the managed option removes a risk you may not want to carry.
Not in core. Some capability is available through extensions, and the ecosystem is large enough that the picture changes over time. Verify against MainWP's current extension directory rather than relying on this page, which reflects a check made on 26 August 2026.
Trying to choose between us and MainWP?
A 20-minute call, no slide deck. If your requirements point at the other product, we will say so.
Free during early access. No credit card required.