An agency signs client number twelve and someone asks: "Can we just add them to multisite?" It sounds efficient. One WordPress install, one update button, one bill from the host. Sometimes that is the right call. Often separate installs are less painful when clients need different plugins, SSL, or an exit plan.
We host both patterns for Canadian agencies on reseller and VPS plans. The tradeoffs are operational, not ideological.
What WordPress multisite actually is
One codebase, one database with shared tables, many sites under a network. Super-admin can enable themes and plugins network-wide. Each subsite has its own content and users (with caveats).
Updates hit every site at once. That is a feature when you trust your stack. It is a disaster when one client needs an old plugin another client cannot run.
When multisite fits agencies
- Similar sites: same theme family, same plugin set, no WooCommerce edge cases
- Internal or partner microsites you control end to end
- University or franchise style: central brand, local editors, strict template lockdown
- You have runbooks for network upgrades and staging the whole network
Multisite shines when variance is low and you own every subsite's lifecycle.
When separate installs are saner
- Clients bring their own plugins, builders, or compliance requirements
- WooCommerce stores with different gateways, currencies, or ERP hooks
- Anyone who might leave and take the site to another host (export is simpler from a normal install)
- Different PHP memory limits, Redis keys, or cron load profiles
- SSL and domain mapping complexity (multisite domain mapping is workable but fiddly)
WHM/cPanel reseller hosting makes separate installs cheap operationally: isolated accounts, per-client backups, clear billing.
Security and blast radius
On multisite, a critical plugin vulnerability or a compromised super-admin account can affect every subsite. Separate installs contain incidents to one client. For agencies with mixed trust levels (you built site A, client B self-manages plugins), isolation matters.
Shared hosting "addon domains" are not multisite but still share one cPanel user. Reseller or separate accounts beat addon domains for the same reason.
Updates and staging
Multisite: one staging network that mirrors production topology, or you risk surprise. Plugin that works on nine subsites and whitescreens the tenth blocks the whole network update.
Separate installs: stage per client or per tier (all Elementor sites, all Woo sites). Slower, but failures are contained.
Performance and noisy neighbors
All subsites share one PHP-FPM pool and one database server unless you architect around it. A viral post on subsite A steals workers from subsite B. On a beefy VPS with monitoring, that may be fine. On tight resources, separate small VPS or accounts spread load.
Billing and offboarding
Clients like clear lines: "This is my hosting account." Multisite makes offboarding a export/migrate project from a shared network. A dedicated install hands over cPanel or a migration package without untangling network tables.
Canadian agencies reselling hosting often map one cPanel account per paying client for exactly this reason.
Hybrid patterns
Some teams run multisite for a template-driven product (landing page factory) and separate installs for flagship clients. Others use multisite only on a management domain for internal tools. That is valid if documented.
Questions to decide in one meeting
- Will every site share the same plugin list in two years?
- Who is super-admin, and what happens if they leave?
- Does any site need WooCommerce or custom PHP that others do not?
- How do clients exit without a emergency migration?
- Does our host backup and restore at network or account level?
Honest answers point you to multisite or separate installs quickly.
Bottom line
WordPress multisite is a consolidation tool for homogeneous sites you fully control. Separate installs are the default for client work with different stacks, commerce, and departure expectations. Agencies on Canadian reseller hosting usually get better sleep with isolation unless they have a deliberate multisite product.
Choosing architecture for a growing client list? Talk with Swift Host. We will map reseller, VPS, and backup options without pushing one WordPress pattern because it is easier for us.
