I managed 180 WordPress sites at the same time. Not all on the same screen at once, thankfully. But still. And the question that comes up constantly in that situation: multisite or separate installs?
Honest answer: both are painful. Just not in the same way.
180 separate sites — what that actually means
It means 180 independent WordPress installations. Each with its own database, its own plugins, its own updates, its own backups. Running through a centralized management tool — the kind of dashboard that aggregates everything and gives you the illusion of control.
The illusion holds. Until the day a plugin update breaks 47 installations at once. Then you stare at your screen, count the incoming tickets, and wonder whether it’s you or WordPress that’s the problem.
It’s not you. It’s the architecture.
The advantage of this setup: isolation. One site going down doesn’t take the other 179 with it. A security breach on one site stays on that site. For different clients with different contexts, it’s often the only sensible choice. And when a migration goes sideways, you’re dealing with one disaster at a time, not 180.
The downside: maintenance is a full-time job. Every plugin exists in 180 copies. Every WordPress update needs to be tested, deployed, checked. If you do this manually, that’s all you do.
Multisite is not the miracle solution
WordPress Multisite is a single installation hosting multiple sites. Same core, same database, same server. In theory, you update once and everyone benefits.
In practice, that’s true. Until it isn’t.
Multisite is like an apartment building. Easy to manage when things go well. When the boiler breaks down, everyone freezes at the same time. An update that breaks the core doesn’t take down 1 site — it takes down all your sites simultaneously. A database issue? Same thing.
And network plugins are a whole topic on their own. Some aren’t compatible with multisite. Others are, but behave differently across subsites. You’ll spend hours debugging behavior you’ve never seen on standard installs.
The tools that make a difference on separate sites
To manage a fleet of WordPress sites without losing your mind, a centralized management tool is non-negotiable. Three solid options:
MainWP is self-hosted, open source, and free for the core features. You keep full control over your clients’ data — not a small thing from a GDPR perspective. Best fit for agencies managing third-party sites.
ManageWP (acquired by GoDaddy) is cloud-based, easier to get started with, and runs on a per-feature freemium model. Convenient to start, less sovereign on data.
WP Umbrella is the rising option for small to mid-size fleets. Less well-known, clean interface, solid value under 100 sites.
The choice between them depends as much on your volume as on how you feel about data sovereignty. At 180 client sites, the GDPR question is not trivial.
So which one is the least bad
It depends on what you’re managing.
If your sites belong to different clients, stick with separate installs. Data and failure isolation is non-negotiable. Invest in a solid centralized management tool and automate updates for low-risk plugins.
If your sites share the same context, same branding, same plugins — and especially the same owner — multisite starts to make sense. That’s the case for editorial networks, regional franchise sites, or corporate sub-brands.
With 180 separate client sites, multisite would have been a disaster. But for 10 sites from the same group with the same stack, it’s coherent.
What the management tool doesn’t solve
The centralized tool creates a false sense of control. It aggregates, notifies, automates. It doesn’t replace an actual maintenance strategy.
What really saves you: staging environments, daily off-server automated backups, and an update policy that includes testing before going live. Not glamorous. Effective. And if you also want to monitor the SEO performance and visibility of your fleet, management tools alone won’t cut it. That’s a different project.
The real lesson
There’s no right architecture. There’s the one that fits your context, and the one that blows up in your face because you picked it for the wrong reasons.
180 separate sites managed properly with the right tools — that’s workable. 180 sites in multisite to “simplify things” — that’s a time bomb.
When things break in either case, it’s hell. But with separate sites, the hell is contained. With multisite, it’s open to everyone.