Managing Multiple WordPress Sites: When DIY Breaks Down and What to Do About It

At two or three sites, manual WordPress management is fine — a few CLI commands, a shared spreadsheet of credentials, an afternoon a month on updates. At seven sites, that system starts costing real time. At fifteen, it's a liability: a missed update cascades into a compromised site, a manual backup fails quietly, a client migration overwrites a production database. The pattern is consistent across agencies and freelancers who reach that scale without a management layer in place.

This guide covers the three paths out of that situation — the tooling options, the cost reality at 5, 10, and 25 sites, and the specific criteria that determine which option fits your portfolio.

The Three Management Models

Manual management (WP-CLI, SSH scripts, spreadsheets) works at 1–3 sites. It fails not because the tools are inadequate but because the cognitive overhead of tracking versions, credentials, backup status, and uptime across a growing portfolio scales linearly with site count. A single developer managing 10 sites manually will spend 8–12 hours per month on routine maintenance alone.

Self-hosted dashboard (MainWP) centralizes WordPress admin across unlimited sites on your own infrastructure. The dashboard runs as a WordPress instance on a dedicated VPS; child sites connect via a plugin. You update, back up, monitor, and apply security changes across all sites from one interface. Licensing is flat annual: $149/year (Personal, up to 25 sites), $249/year (Developer, up to 100 sites), $399/year (Agency, unlimited with premium extension bundle). Site count does not affect the cost.

Managed hosting with multi-site management built in (Nexcess, Kinsta) eliminates the dashboard infrastructure overhead entirely. At a per-site or tiered plan cost, the provider handles server maintenance, auto-updates, staging environments, and basic monitoring. You get a managed console rather than a self-hosted tool. The tradeoff: cost scales with site count, and operational data lives on the provider's infrastructure rather than your own.

Cost by Site Count

These numbers use realistic loaded rates, not vendor marketing figures.

Sites	Manual (labor only)	MainWP + VPS	Managed Hosting
5	~$375/mo (5hr × $75/hr)	~$62/mo ($50 VPS + $12.42 license)	~$99–$150/mo
10	~$750/mo (10hr × $75/hr)	~$137/mo ($50 VPS + $12.42 + 1hr labor)	~$190–$350/mo
25	~$1,875/mo	~$175/mo ($75 VPS + $20.83 license + 2hr labor)	~$500–$900/mo

MainWP's cost-per-site drops as you scale; manual and managed hosting costs rise. The crossover where MainWP saves more than its setup overhead occurs at roughly 5 sites over six months. Before that threshold, managed hosting or manual processes are simpler.

Full breakdown: WordPress Site Management Cost Breakdown

When Self-Managed (MainWP) Is the Right Call

Choose a self-hosted dashboard if:

You manage 5 or more sites with consistent update and backup requirements
You or your team has basic server administration skills (patching, monitoring a VPS)
Data sovereignty matters — client site access logs, backup data, and credential management cannot live on a third-party platform
You want predictable costs that don't grow as you add sites
You're already running infrastructure; the MainWP VPS is an additional workload, not a new infrastructure category

MainWP runs on a $20–50/month VPS (2 vCPU, 4GB RAM is adequate for managing up to 100 sites). The dashboard itself is a WordPress install; you maintain it like any other WP instance.

MainWP Review: What It Does Well and Where It Falls Short

Check current MainWP pricing →

When Managed Hosting Replaces the Dashboard

Choose Nexcess or Kinsta if:

You manage fewer than 10–15 sites and don't want to operate dashboard infrastructure
Your clients are on SLA-backed hosting already, and consolidating to one managed provider simplifies billing and support
Your team lacks the capacity to maintain an additional VPS
Agency-scale WooCommerce or performance-critical sites require more than self-managed hosting can deliver reliably

Nexcess targets the 5–30 site agency range with bulk pricing and managed NGINX/Redis stacks. Kinsta serves portfolios where per-site container isolation, Google Cloud C2 infrastructure, and expert support access justify the premium at 30–100 sites.

Nexcess Managed WordPress for Agencies

Kinsta for Multi-Site WordPress Portfolios

Check current Nexcess pricing →

Signs You've Already Hit the Wall

If any of these are true, manual management has already stopped working:

You've missed a WordPress core or plugin update for more than 30 days on any site
A backup has failed silently — you discovered it only when you needed to restore
Client site access requires consulting a spreadsheet or password manager for each login
An update on one site broke a plugin, and you didn't catch it for more than 24 hours
You're spending more time on maintenance than on billable work in any given week

Signs Your WordPress Management Process Is Out of Hand

The WordPress Multisite Question

WordPress Multisite consolidates multiple sites into a single WordPress installation with shared core files. For brand networks with shared themes, shared plugins, and no isolation requirements between sites, it reduces the management surface. For agencies managing independent client sites, it creates a failure blast radius: a misconfigured plugin or compromised site affects all sites on the network simultaneously.

The default is separate installs managed through a dashboard tool. Multisite is the exception, not the standard agency architecture.

WordPress Multisite vs Separate Installs: The Decision Framework

Self-Hosted Dashboard vs Managed Hosting: The Bottom Line

At 10+ sites with technical staff, MainWP on a provisioned VPS is the cost-rational choice. The operational overhead of maintaining dashboard infrastructure costs less than the per-site fee differential over 24 months in almost all scenarios.

Below that threshold, or without in-house server administration capacity, Nexcess or Kinsta eliminates the infrastructure overhead that would otherwise consume the cost savings. Neither is universally better — the right answer is determined by site count, team capability, and how much you value operational data control.

Self-Hosted Dashboard vs Managed Hosting: Which Is Right for Your Portfolio?

When Managed Hosting Replaces a Self-Hosted Dashboard