Kinsta WordPress Multisite Hosting: Features, Limits & Use Cases
WordPress multisite is one of those features that sounds like the obvious solution right up until you start using it. One installation, one dashboard, one place to push updates across a network of sites. The appeal is obvious. The reality is a bit more complicated, and whether it works well for you depends heavily on what you’re trying to run and how your hosting handles the added complexity.
This article covers how Kinsta handles WordPress multisite specifically: what’s supported, what’s restricted, where the resource model gets interesting, and which types of projects it actually suits.
Get 2 months of Kinsta hosting free →
What WordPress Multisite Actually Is (and Isn’t)
Multisite is a built-in WordPress feature, not a plugin. It converts a single WordPress installation into a network of sites that share the same core files, database, plugins, and themes. Each site in the network can have its own content, domain, and settings, but everything runs under one install.
That last part matters. It’s not multiple WordPress sites sitting side-by-side. It’s one WordPress install with multiple sites nested within it. From a hosting perspective, that means one set of files, one database, one set of PHP workers serving the whole network.
There are three URL structures you can use:
- Subdirectories (example.com/site-a, example.com/site-b)
- Subdomains (site-a.example.com, site-b.example.com)
- Mapped custom domains (site-a.com, site-b.com as separate domains pointing to subsites)
Kinsta supports all three. Domain mapping in particular tends to be where things get fiddly on other platforms. On Kinsta, custom domain setups for subsites are handled through their domain management tools, with Nginx Reverse Proxy available for more complex configurations.
How Kinsta Handles Multisite
Plan Eligibility
Multisite is available on all Kinsta plans except the entry-level Single 35k visits plan and the Single 20GB bandwidth plan. Every other plan, from the WP 2 tier upward, supports multisite configurations.
That’s worth knowing before you start. If you’re on the cheapest Kinsta plan and want to run multisite, you’ll need to upgrade.
Resources: Shared, Not Dedicated Per Subsite
This is the part people sometimes underestimate. When you run a multisite network on Kinsta, the main site and all subsites draw from the same pool of resources: the same CPU allocation, the same RAM, the same PHP threads, and the same disk space included in your plan.
So if your plan includes 20GB of storage and 70,000 monthly visits, that’s the total budget across all subsites combined. A network of 10 active subsites shares those limits. It’s not 70,000 visits per subsite.
This is fine if your subsites are low-traffic or supplementary. It becomes a real constraint if you have one or two subsites that individually drive significant traffic. In those cases, separate installs on a higher-tier plan might actually be the cleaner approach.
No Fixed Subsite Limit
Kinsta doesn’t cap the number of subsites you can create within a multisite network. The practical limit is your available server resources. A network with 50 subsites all generating meaningful traffic will consume considerably more PHP threads and RAM than a network with 5 light-traffic subsites. The constraint is resource headroom, not an arbitrary number imposed by the platform.
For very large networks, Kinsta recommends contacting their sales team to configure the right plan before committing.
One Data Center Per Install
A multisite network is one WordPress install. That means it lives in one of Kinsta’s 27 global data centers, and every subsite in the network is served from that same location. You can’t place different subsites in different regions.
If your subsites serve audiences in genuinely different geographic regions and latency matters to each of them, this is a real limitation. You’d need separate WordPress installs for that, which means separate plans.
Infrastructure and Performance
Kinsta runs on Google Cloud Platform using C3D compute-optimized instances. Every install, including multisite networks, runs in an isolated LXC container with dedicated resources rather than shared server infrastructure.
What this means in practice: your multisite network isn’t competing with other customers’ sites on the same machine. It’s isolated. Plugin conflicts or resource spikes on another customer’s site won’t drag yours down.
For performance within the network itself, Kinsta provides:
- Site-level caching for each subsite, with per-subsite cache rules and manual purge controls
- Edge Caching, which can reduce page load times by serving cached content from multiple locations, enabled per subsite
- Kinsta CDN for static assets, active across the network without additional configuration
- APM (Application Performance Monitoring) at the install level, which helps identify which subsites or specific plugins are creating PHP or database bottlenecks
The APM tool is particularly useful for multisite networks, where a poorly coded plugin activated across all subsites can quietly eat through PHP workers and degrade performance across the board.
Independent benchmarks referenced by third-party reviewers have noted speed improvements after migrating multisite networks to Kinsta’s infrastructure. Testing of networks with 50+ subsites has shown managed hosting platforms like Kinsta handle the added complexity more reliably than shared hosting alternatives.
Multisite Feature Support at Kinsta
| Feature | Supported |
|---|---|
| Subdirectory subsites | Yes |
| Subdomain subsites | Yes |
| Custom domain mapping | Yes |
| Nginx Reverse Proxy | Yes (for custom domains) |
| Staging environment | Yes (at install level) |
| Free migrations | Yes |
| Edge Caching per subsite | Yes |
| APM monitoring | Yes |
| Automatic backups | Yes |
| WooCommerce on subsites | Yes |
| Redis / Elasticsearch add-ons | Yes |
| DevKinsta local development | Yes |
The staging environment covers the entire multisite install. Selective push is available, though its behaviour with multisite setups has some nuances worth checking with Kinsta support before relying on it for complex deployments.
Plugin Restrictions
Kinsta maintains a list of plugins that are blocked across all plans due to performance or security concerns. This applies to multisite networks just as it does to single installs. If your workflow depends on specific caching plugins that handle their own server-level caching, those may conflict with Kinsta’s built-in caching system.
More broadly, not all plugins behave correctly in a multisite environment regardless of host. Yoast SEO, WooCommerce, Gravity Forms, and WPML are generally well-supported. Some backup plugins and certain page builders have partial compatibility. Testing new plugins on staging before network activation is genuinely good practice.
Setup: How It Works in Practice
Kinsta’s site creation wizard includes a checkbox to enable multisite mode during initial setup. That’s the straightforward path. Enabling it on an existing site involves changes to wp-config.php and WordPress PHP files, which Kinsta documents but is more involved.
Managing domains for subsites is handled through the MyKinsta dashboard. Adding a custom domain to a subsite, configuring SSL, and pointing DNS are all manageable from the same interface you use for everything else on the platform.
Support is live chat only, but Kinsta’s support team handles multisite-specific questions directly, without routing you through tiers or generalist agents first.
Who Multisite on Kinsta Is Actually For
It’s worth being specific here, because multisite isn’t the right structure for every situation.
It works well for:
- Franchise businesses running location sites with a shared plugin stack and consistent branding
- Universities or institutions managing department sites under one install
- Publishers running a network of related editorial sites
- Businesses managing multilingual sites using domain mapping with WPML or Polylang
- Any setup where sites share users, themes, and plugins and where centralised management saves meaningful operational time
It’s less suited to:
- Agencies managing independent client sites. Separate installs per client keep things isolated, portable, and easier to hand off. Kinsta’s agency plans are designed for this via the MyKinsta dashboard and multi-user access, not multisite.
- Sites with vastly different traffic volumes. If one subsite gets 50,000 visits a month and another gets 500, they’re sharing resources in a way that may not serve either well.
- Projects where individual subsites might be extracted and moved later. Getting a single site out of a multisite network is significantly more complex than a standard migration.
- Situations where plugin stacks need to differ significantly between sites.
Kinsta’s own documentation on multisite versus separate installs is worth reading if you’re genuinely on the fence. It outlines the trade-offs plainly without pushing you in either direction.
Pricing Context
Kinsta plans start at $35/month for the WP 2 plan (the lowest tier supporting multisite). The cost scales based on the number of WordPress installs allowed, monthly visits, storage, and CDN usage.
The important thing to understand is that a multisite network counts as one install regardless of how many subsites it contains. So a WP 2 plan theoretically supports a multisite network with dozens of subsites as long as the collective resource usage fits within the plan limits.
Where costs increase:
- Storage add-ons are available at around $20 per 20GB per month if you exceed disk limits across the network
- Overage charges apply if monthly visits exceed your plan allocation. Kinsta notifies you at 80% and 100% usage, so it doesn’t catch you off-guard, but it does cost extra
- Additional staging environments beyond the included one are available as paid add-ons
For organisations running a significant multisite network, looking at Kinsta’s WP 5 or WP 10 plans is sensible. The monthly visit headroom at lower tiers fills up faster than you’d expect once a network has real traffic across multiple subsites.
For a full breakdown, the Kinsta pricing guide covers how plans scale and where costs can accumulate.
Alternatives Worth Knowing About
Kinsta isn’t the only option for managed multisite hosting. WP Engine supports multisite on their Growth plan and above. Cloudways, which takes a different approach as a cloud management layer over providers like DigitalOcean and Google Cloud, is often cited for strong multisite support with server-level caching and more flexible resource allocation.
The trade-off with Cloudways is less of a fully managed experience, meaning more responsibility for configuration, but more flexibility in how resources are allocated. For very large multisite networks where resource control matters more than convenience, that’s worth factoring in.
For more detail on how the options compare, the Cloudways vs Kinsta comparison covers the key differences.
Summary
Kinsta WordPress multisite hosting is well-suited to structured networks where sites share a plugin and theme stack, where centralised management genuinely saves time, and where resource demands are predictable across the network. The infrastructure is solid, the tooling is modern, and support handles multisite-specific issues without routing you through tiers.
The limitations are real. Shared resources across subsites, a single data center per install, and the complexity of plugin management in a network environment all need to be considered honestly before committing.
The better option depends on your site’s scale, budget, and workflow.
Frequently Asked Questions
Can I run WooCommerce on a Kinsta multisite subsite? Yes. WooCommerce is compatible with multisite and works on Kinsta’s infrastructure. Each subsite can have its own WooCommerce setup, though the plugin is installed and managed at the network level.
How many subsites can I have on Kinsta multisite? There’s no fixed limit. The practical ceiling is determined by the combined resource consumption of your subsites relative to your plan’s visit, storage, and bandwidth allocation.
Does Kinsta support custom domains for subsites? Yes. Custom domain mapping is supported, with Nginx Reverse Proxy available for more complex domain configurations.
Is multisite available on all Kinsta plans? No. It’s excluded from the Single 35k visits and Single 20GB bandwidth plans. All other WordPress hosting plans support multisite.
Does each subsite get its own staging environment? The staging environment operates at the install level, covering the entire multisite network rather than individual subsites.