One inventory
A current record of every site, its WordPress version, its plugins and themes, its host, and who it belongs to. Most operational failures start with not knowing what you have.
Manage multiple sites
Manage multiple WordPress sites from one dashboard
Connect every WordPress site you are responsible for, whoever hosts it, and run updates, backups, monitoring and reporting from a single place. Built for anyone past the point where logging into each site individually still makes sense.
Free during early access. Connects to any host.
What you get
Included on every plan
- One inventory: A current record of every site, its WordPress version, its plugins and themes, its host, and who it belongs to.
- Updates in one pass: Every pending update across the portfolio, grouped by release rather than by site, with per-site exclusions and scheduling windows.
- Recovery that works: Off-site encrypted backups that are restore-tested, plus a restore point before any change.
- Continuous monitoring: Uptime, response time, Core Web Vitals, SSL expiry and vulnerability exposure, checked continuously rather than when somebody remembers.
Why managing WordPress sites individually stops working
WordPress was designed around a single site with a single administrator. Everything in wp-admin assumes you are looking after exactly one installation. That assumption holds until roughly the fifth site, at which point the work stops being manageable through the interface WordPress gives you.
The failure is not dramatic. It is a slow accumulation of small omissions: a site that has not been updated in four months because it never comes up, a backup schedule that stopped, an SSL certificate nobody was watching, a vulnerable plugin running on three sites you forgot were connected.
Being able to bulk update WordPress plugins across the whole portfolio in one pass is what stops that accumulation. Centralised management fixes this by inverting the default. Instead of remembering to check each site, you get told which sites need attention, ranked by how much it matters.
Capability
What WordPress site management software should do
Updates in one pass
Every pending update across the portfolio, grouped by release rather than by site, with per-site exclusions and scheduling windows.
Recovery that works
Off-site encrypted backups that are restore-tested, plus a restore point before any change. Untested backups are the most common false sense of security in WordPress.
Continuous monitoring
Uptime, response time, Core Web Vitals, SSL expiry and vulnerability exposure, checked continuously rather than when somebody remembers.
Access without shared passwords
Roles scoped to sites or clients, one-click login, and a record of who did what. Shared admin credentials do not survive a team of more than one.
Proof of work
A tamper-evident log and reports generated from it, so the maintenance is visible to whoever is paying for it.
Approaches
WordPress multisite management and two other approaches
WordPress multisite
- Single codebase, shared plugins and themes
- Only works for sites you control end to end
- One compromise affects every site
- Not suitable for independent client sites
Self-hosted management plugin
- No per-site subscription fee
- You maintain the dashboard server and its security
- Performance depends on your own hosting
- Cost moves from subscription to your own time
Recommended
Hosted management platform
- Works across any host, for sites you do not control
- No infrastructure for you to maintain or patch
- Monitoring runs externally, so it still works when a site is down
- Predictable per-site cost, no server to secure
Getting there
Setting up a portfolio properly
Connect everything, including the sites you forgot
Bulk connect by pasting a list of URLs. Include the abandoned campaign microsite and the staging copy nobody deleted. You cannot secure an inventory you do not have.
Group by how you actually think about them
Tag by client, by criticality, by host, by care plan tier. Grouping is what makes policy possible: stores behave differently from brochure sites.
Set policy per group, not per site
Decide what updates automatically, what needs approval, when maintenance windows open and who gets alerted. Do it once per group and let new sites inherit.
Let the exceptions come to you
After the first fortnight the dashboard becomes something you check twice a week rather than a place you work. That is the point.
Answers
Frequently asked questions
For sites that share a codebase and one owner, WordPress multisite is reasonable. For independent sites, especially client sites on different hosts, a management platform is the practical answer: it connects to each site over its REST API and gives you one dashboard for updates, backups, monitoring and reporting without changing anything about how the sites are hosted.
Yes. WPCentrify is hosting neutral and connects to any self-hosted WordPress installation on any host. A single portfolio can mix managed WordPress hosting, shared cPanel accounts and your own VPS without issue.
Manually, most people find five to eight is the ceiling before maintenance starts displacing billable work. With centralised management and automation, one person comfortably runs fifty to a hundred sites, because the work scales with exceptions rather than with site count.
No. Multisite runs many sites from one WordPress installation with a shared plugin and theme set. It is useful for sites you control entirely, but it creates a shared failure domain and is a poor fit for independent client sites. A management platform leaves each site fully independent.
No. The connector plugin does no work during front-end page loads and adds nothing to the rendered page. Monitoring requests come from outside the site.
Early access open
Stop logging into forty dashboards
Connect your first site in under two minutes. No credit card, no contract, no migration fee.
Free during early access. Keep your data, export any time.