A four-model technical reference for selection, comparison, and routine operation. 2026 edition.
This manual describes four units in active service in 2026 for the centralised management of multiple WordPress installations. All four perform a similar high-level function — connecting many WordPress sites to one console for routine operations such as updates, backups, monitoring and reporting — but differ substantially in hosting model, pricing structure, data residency, and maintenance burden.
This document is a comparison reference, not a sales document. No model is presented as universally superior. Selection should be made on the basis of the operating profile in §4 and the matrix in Appendix A.
A cloud-hosted dashboard, founded in 2012 and operated under GoDaddy ownership since 2016. The console is provided as a service: the user installs a small worker plugin on each WordPress site and connects it to a central account. The vendor handles dashboard hosting, security and updates.
The free tier covers an unlimited number of connected sites with monthly cloud backups and basic update tooling. Premium features (more frequent backups, security checks, uptime monitoring, white-label client reports, and similar) are sold as add-ons priced per-site, per-month. A flat-fee Bundle option is available for portfolios of up to roughly 100 sites.
A self-hosted, open-source dashboard distributed under the GPL. The user installs MainWP itself on a WordPress site they control, then connects child sites to it via a companion plugin. No data passes through a third-party service — all credentials and site information remain inside the operator's own environment.
The core dashboard is free. Premium extension bundles are sold on an annual subscription (commonly cited around $199/year) that covers an unlimited number of connected sites, regardless of portfolio size. Maintenance of the dashboard itself — server upkeep, SSL, updates, scaling — is the operator's responsibility.
A newer cloud-hosted SaaS, originating in France and hosting exclusively in the European Economic Area. Marketed as an all-inclusive monitoring and management platform: features such as security scanning, uptime monitoring, performance tracking, PHP error capture and white-label client reports are bundled into a single per-site subscription rather than sold individually.
Pricing has been published at approximately €1.99 per site per month. Trial access is offered; there is no permanent free tier in the manner of Units A or B. The all-inclusive structure makes total cost predictable for portfolios where most sites need the full feature set.
A long-running platform from Revmakx, available in two configurations: a free self-hosted core that the operator installs on their own server, and a separate paid cloud version operated by the vendor. Premium add-ons cover scheduled backups, client reports, security tooling, migrations and similar — purchased individually rather than as a single bundle.
The dual-mode approach allows operators to start with a free local installation and migrate to the cloud later, or vice versa. As with Unit B, the self-hosted mode places dashboard reliability on the operator.
All four units share a common topology: a central console (1) communicating with a worker / connector plugin (3) installed on each managed WordPress site (2). The location and ownership of the central console is the chief architectural difference between models.
The console (1) is what differs across units: cloud-hosted by the vendor in Units A and C, self-hosted by the operator in Unit B and the free configuration of Unit D, and either-or in Unit D's paid mode.
Use the following decision flow as a starting point. The recommendations are general guidance, not absolute rules — operating profile, team skill, and client requirements may shift the choice.
Underlined entries indicate a notable strength of that unit relative to the others. The matrix is for orientation; verify current pricing and feature sets directly with each vendor before deployment.
| Specification | Unit A · ManageWP | Unit B · MainWP | Unit C · WP Umbrella | Unit D · InfiniteWP |
|---|---|---|---|---|
| Hosting model | Vendor cloud | Self-host | Vendor cloud (EU) | Self-host or cloud |
| Free tier | Yes · unlimited | Open-source core | Trial only | Yes (self-host) |
| Pricing model | Per add-on / site | Yearly bundle | Per site flat | Per add-on / site |
| Bulk updates | Yes | Yes | Yes | Yes |
| Cloud backup | Built-in (free monthly) | Extension | Included | Add-on |
| Security scan | Add-on | Extension | Included | Add-on |
| Uptime monitor | Add-on | Extension | Included | Add-on |
| White-label reports | Yes (add-on) | Extension | Built-in | Add-on |
| Data residency | US (GoDaddy) | Operator's server | EU only (GDPR) | Operator's choice |
| Dashboard upkeep | Vendor | Operator | Vendor | Depends on mode |
| Setup difficulty | Low | Medium–high | Low | Medium |
| Best fit | Agencies of any size | Privacy-first / large | Small & mid agencies | Devs · flexible teams |
Concluding note. No single unit serves every operating profile. A common pattern in 2026 is to keep one as the primary console for routine work and pair it with a second tool for a specialised task (a third-party backup service, for instance, or a dedicated security scanner). Selection should follow the operating profile, not a ranking.