Running multiple WordPress sites on separate hosting accounts wastes money and creates management overhead. Consolidating them onto one server cuts costs and centralizes maintenance, but the approach you choose determines how much work you take on. This guide covers three ways to host multiple WordPress sites on one server: manual VPS setup, managed VPS platforms like Cloudways and ScalaHosting, and managed WordPress hosting like Kinsta. Each approach has different tradeoffs in control, cost, and time investment.
Key Takeaways
- Use separate installs, not WordPress Multisite: Multisite shares one database across all sites, making individual migrations painful and limiting plugin compatibility
- Manual VPS gives full control at the lowest cost: configure Apache or Nginx virtual hosts yourself, but you handle all security, updates, and backups
- Managed VPS platforms handle the server stack for you: Cloudways starts at $11/mo and ScalaHosting starts at $50/mo for managed VPS with its own control panel (SPanel) built for multi-site management
- Managed WordPress hosting charges per site but eliminates server work: Kinsta includes staging environments, CDN, and automatic backups per site
- A 2GB VPS handles 3-5 low-traffic sites comfortably: budget 512MB of RAM per WordPress site as a baseline, and scale up when traffic grows
WordPress Multisite vs Separate Installs
WordPress has a built-in Multisite feature that lets you run multiple sites from a single WordPress installation. Enable it by adding define( 'WP_ALLOW_MULTISITE', true ); to wp-config.php. While this sounds convenient, it introduces limitations that make it the wrong choice for most multi-site setups.
Multisite shares one database across every site in the network. Migrating a single site out of the network later is significantly harder than moving a standalone WordPress install. Some plugins don’t work reliably in Multisite environments. And a security issue in one site can affect the entire network since they share the same codebase.
Separate installations give each site its own database, its own plugins, and its own wp-config. You can migrate, update, or delete any site without touching the others. The tradeoff is managing multiple dashboards instead of one, but that’s a smaller problem than the migration headaches Multisite creates down the line.
Use Multisite only when you need subsites under one domain (like blog.example.com and shop.example.com) with shared users and themes. For independent sites with their own domains, separate installs are the right call.
Three Approaches Compared
| Approach | Cost | Control | Server Work | Good For |
|---|---|---|---|---|
| Manual VPS | $5-20/mo | Full root access | You do everything | Developers who want total control |
| Managed VPS | $11-50/mo | Application-level | Platform handles server stack | Developers who skip sysadmin work |
| Managed WordPress | $35+/mo per site | WordPress-level only | Zero server management | Agencies and non-technical site owners |
Approach 1: Manual VPS Setup
Rent a VPS from any provider (DigitalOcean, Vultr, Hetzner), install your web server, and configure virtual hosts for each domain. This gives you full root access and the lowest monthly cost, but you’re responsible for security patches, SSL certificates, backups, and firewall configuration.
How It Works
Each WordPress site gets its own directory, its own database, and its own Nginx or Apache server block. The web server routes incoming requests to the correct directory based on the domain name in the request header.
# Nginx server block for site one
server {
listen 80;
server_name siteone.com www.siteone.com;
root /var/www/siteone;
index index.php;
# ... PHP and WordPress rules
}
# Nginx server block for site two
server {
listen 80;
server_name sitetwo.com www.sitetwo.com;
root /var/www/sitetwo;
index index.php;
# ... PHP and WordPress rules
}Each site needs its own MySQL database and user. Create them separately and point each wp-config.php to its own database. Set directory ownership to www-data (or your web server’s user) and file permissions to 644 for files, 755 for directories.
Resource Planning
Budget 512MB of RAM per WordPress site as a baseline. A 2GB VPS handles 3-5 low-traffic sites comfortably. Once any site starts getting consistent traffic (1,000+ daily visitors), monitor your RAM and CPU usage and scale up. PHP-FPM process limits and MySQL query caching are the two biggest levers for squeezing more out of limited resources.
If you’re comfortable with Linux server administration and want to keep costs under $20/month for multiple sites, this is the most economical path. For a step-by-step walkthrough of setting up WordPress on a VPS, see our WordPress server setup guide. For automating deploys after setup, check our GitHub Actions deployment guide.
Approach 2: Managed VPS
Managed VPS platforms sit between raw servers and fully managed hosting. You pick a cloud provider and plan size, and the platform handles the server stack: web server configuration, PHP versions, SSL certificates, firewalls, and OS updates. You manage WordPress itself.
Cloudways
Cloudways lets you deploy WordPress on DigitalOcean, Vultr, Linode, AWS, or Google Cloud through a visual dashboard. Adding a new site takes a few clicks: pick the server, choose WordPress, and Cloudways handles the virtual host, database, and SSL. Plans start at $11/month on DigitalOcean (1GB RAM), and you can host unlimited applications per server.
The platform includes built-in caching (Varnish, Memcached, Redis), automated backups, staging environments, and server monitoring. You don’t get root SSH access on lower plans, but you get application-level SSH and Git integration. For a detailed breakdown of the platform, see our Cloudways review.
ScalaHosting
ScalaHosting takes a different approach with SPanel, their proprietary control panel built as a cPanel alternative. SPanel includes per-site resource isolation, a WordPress manager for automated installs and updates, and addon domain management through a familiar panel interface. Managed VPS plans start at $50/month with 2 CPU cores and 4GB RAM.
The resource isolation is the key differentiator. If one site gets a traffic spike, SPanel prevents it from starving the other sites on the same server. You also get full root access, which Cloudways restricts on lower tiers. See our ScalaHosting review for a detailed look at SPanel and the managed VPS plans.
Approach 3: Managed WordPress Hosting
Kinsta
Kinsta runs on Google Cloud Platform’s premium tier and charges per WordPress site rather than per server. Plans start at $35/month for one site. Each site gets its own staging environment, daily automatic backups, a built-in CDN, and DDoS protection. You manage WordPress through the MyKinsta dashboard and never touch a server config.
The per-site pricing means costs scale linearly with the number of sites. Five sites at $35 each is $175/month, compared to one $11-50 VPS hosting all five on Cloudways or ScalaHosting. The tradeoff is zero server management, faster support response times, and infrastructure you don’t have to think about. Agencies managing client sites often find the time savings worth the premium. For the full breakdown, see our Kinsta review.
For a direct comparison of the managed options, our Cloudways vs Kinsta comparison breaks down pricing, performance, and developer features side by side.
Which Approach to Choose
Choose Manual VPS if:
- You’re comfortable with Linux server administration
- You want full root access and custom configurations
- Budget is the top priority (under $20/mo for multiple sites)
- You run non-WordPress apps on the same server
Choose Cloudways or ScalaHosting if:
- You want VPS performance without sysadmin work
- You need built-in caching, backups, and SSL management
- You host 3-10 sites and want one dashboard for all of them
- You want per-site resource isolation (ScalaHosting’s SPanel)
Choose Kinsta if you manage client sites, need guaranteed uptime SLAs, and value support response time over cost efficiency. The per-site pricing makes sense when your time costs more than the hosting premium.
Frequently Asked Questions
How many WordPress sites can one server handle?
A 2GB VPS comfortably handles 3-5 low-traffic sites. Budget 512MB of RAM per site as a baseline. High-traffic sites (1,000+ daily visitors) need more resources. Monitor CPU and RAM usage and scale up when you see sustained high utilization.
Should I use WordPress Multisite for multiple domains?
No. Multisite shares one database, making individual site migrations difficult and limiting plugin compatibility. Use separate WordPress installations with their own databases for independent sites with different domains.
What is the cheapest way to host multiple WordPress sites?
A manual VPS from a provider like DigitalOcean or Vultr starts at $5-12/month and can host multiple sites with Nginx virtual hosts. You handle server management yourself. For managed options, Cloudways starts at $11/month with unlimited applications per server.
Can one site crashing take down the other sites on the same server?
On a manual VPS or basic managed setup, yes. A traffic spike or runaway PHP process on one site can consume all available RAM. ScalaHosting‘s SPanel includes per-site resource isolation to prevent this. On Kinsta, each site runs in its own isolated container.
Do I need a separate SSL certificate for each site?
Yes, each domain needs its own SSL certificate. On a manual VPS, use Let’s Encrypt with Certbot to generate free certificates for each domain. Managed platforms like Cloudways, ScalaHosting, and Kinsta handle SSL automatically.
Summary
Skip WordPress Multisite and use separate installations for each site. A manual VPS gives the most control and the lowest cost if you’re comfortable managing the server yourself. Cloudways and ScalaHosting handle the server stack while keeping costs reasonable for 3-10 sites on one server. Kinsta charges more per site but eliminates server management entirely. Match the approach to how much time you want to spend on infrastructure versus how much you’re willing to pay to avoid it.