Quick answer: One VPS can host many WordPress sites: give each site its own directory, database, DB user and web-server vhost, and add roughly 1–2 GB RAM per active site. Keep sites isolated (separate DB credentials, ideally separate PHP-FPM pools) so one compromised or overloaded site can’t take down the rest.
Overview
Consolidating sites on a single VPS cuts cost and simplifies maintenance — one server to update, one backup job, one firewall. The trade-off is shared fate: size the server for the sum of the sites and isolate them properly. This is the standard setup for freelancers and agencies (see agency best practices).
Before you start
- A VPS sized for the total load — see choosing a VPS; 4 GB RAM comfortably runs 2–4 typical sites.
- A working stack (manual) or a control panel like CloudPanel, which automates vhosts per site.
- DNS access for every domain you’re adding.
Step-by-step guide
- Create a directory per site:
/var/www/site1.com,/var/www/site2.com… - Create a separate database and DB user per site — never share one DB user across sites.
- Add a server block (vhost) per domain; with a panel this is the “add website” button.
- Optionally create one PHP-FPM pool per site with its own
pm.max_children, so a runaway site hits its own limit instead of exhausting the server:sudo cp /etc/php/8.3/fpm/pool.d/www.conf /etc/php/8.3/fpm/pool.d/site2.conf # edit: [site2], listen = /run/php/php8.3-fpm-site2.sock, pm.max_children = 10 sudo systemctl reload php8.3-fpm - Issue SSL per domain (guide) and include every site in the backup job.
Common issues
- One site slows down all of them: no per-site FPM pools — add them, and find the culprit with
topand the slow-query log. - RAM exhaustion as sites are added: each active site adds PHP workers and DB working set — watch
free -hand upgrade before swapping starts. - Cross-site infection: all sites under one Linux user with shared write access — tighten permissions or use a panel that separates site users.
When to contact support
If you’re planning to consolidate many sites and aren’t sure one VPS is enough — or whether several smaller VPS would isolate clients better — open a ticket with the site list and traffic estimates.
Frequently asked questions
How many WordPress sites fit on one VPS?
As a rule of thumb, plan 1-2 GB RAM per active site plus headroom for the database: a 4 GB VPS runs 2-4 typical sites, an 8 GB plan comfortably hosts 5-8 lean ones.
Should I use WordPress multisite or separate installs?
Separate installs are safer for unrelated sites: independent plugins, backups and failure domains. Multisite suits a network of closely related sites managed as one product.
How do I stop one site from slowing down the others?
Give each site its own PHP-FPM pool with capped workers and its own database user, then monitor with top and the MariaDB slow-query log to catch the heavy site early.
Related articles
- How to choose a VPS for WordPress
- WordPress hosting for agencies: best practices
- How to migrate multiple WordPress sites
- How to optimize PHP for WordPress
Ready to get started? Order a WordPress VPS at Cloud2Y →
