Hosting 20 Client Websites on One VPS: The Agency Infrastructure Stack

Running twenty client websites across separate shared hosting accounts means twenty control panels, twenty monthly invoices, and twenty points of failure. The management overhead scales linearly while your margins shrink. A single VPS with sufficient RAM and dedicated cores can host 20 small WordPress client sites with proper user isolation, per-site PHP-FPM pools, and automated updates. This article lays out the exact server architecture for consolidating those sites onto one properly configured VPS. It also explains when building this stack yourself is worth the effort and when white-label reseller hosting is the smarter business move.

The hidden cost of fragmentation

Most agencies start by parking client sites on cheap shared hosting. The bill looks small per site. Add ten or fifteen clients and you are spending hours each week logging into different control panels, tracking different renewal dates, and explaining to clients why their site is slow because someone else on the same shared server is running a cryptocurrency miner. The real cost is not the hosting fees. It is the time you spend acting as a human bridge between your clients and their hosting providers. That time does not scale.

What proper isolation looks like on a single VPS

Throwing twenty sites onto one server without isolation is a malpractice lawsuit waiting to happen. One compromised WordPress plugin should not give an attacker read access to every other client's database. The architecture starts with separate Linux users per client. Each user owns their web root, their PHP-FPM pool, and their log files. The PHP-FPM pool configuration enforces hard limits:

[client1]
user = client1
group = client1
listen = /run/php/php8.3-fpm-client1.sock
pm.max_children = 5
php_admin_value[memory_limit] = 128M
php_admin_value[open_basedir] = /var/www/client1:/tmp
php_admin_flag[allow_url_fopen] = off

This means client1's PHP workers run as user client1, can only access files in their own directory, and are capped at five concurrent processes. If a plugin goes into an infinite loop or a brute-force attack hits the login page, the damage stays inside that cage. NGINX server blocks route each domain to its own Unix socket, so there is no shared PHP pool where one site's traffic spike starves the others.

Where the architecture starts to creak

Disk I/O is the first bottleneck most agencies ignore. Twenty WordPress sites with their own media libraries, plugin sets, and database tables will saturate a single NVMe drive during backup windows. The ServerSpan ct.Go plan offers 80 GB of storage. That is four gigabytes per client if you split it evenly, which is unrealistic for any site with more than a few dozen images. You will need to monitor per-client disk usage aggressively or accept that some clients need to be moved to their own server.

RAM contention is the second failure point. Eight gigabytes sounds like enough until five clients install WooCommerce and Elementor simultaneously. Each PHP-FPM pool needs a minimum footprint, and MariaDB buffer pools do not shrink gracefully under pressure. The server will not crash immediately. It will slow down, and your clients will notice page load times creeping from two seconds to eight seconds before anyone checks the monitoring dashboard.

The automation layer that makes this manageable

Manual updates across twenty sites is a part-time job. The stack needs a WP-CLI loop that runs nightly across all client directories, applying security updates and plugin patches. Each site should back up independently to its own restic repository before the update runs. Uptime Kuma should check every client domain every sixty seconds and alert you before the client calls asking why their site is down. Without this layer, you have simply moved the management fragmentation from twenty hosting accounts to one server with twenty manual maintenance tasks. The automation is what makes consolidation actually reduce your workload.

When this stack is the wrong choice

Some clients need PCI compliance, HIPAA alignment, or simply generate enough traffic that they deserve their own dedicated resources. Those clients should not live on your shared agency VPS. The same applies if your clients expect cPanel or Plesk familiarity. Building a custom VPS stack means you are the support desk for every hosting question. If you bill hourly for development work, every minute spent debugging a client's email delivery issue is a minute you are not billing. Reseller hosting with DirectAdmin offloads that support to the hosting provider while you keep the margin.

Cost comparison

Twenty client sites on individual budget shared hosting plans typically run between five and fifteen euros per site per month. That is one hundred to three hundred euros monthly in raw hosting cost, plus your time managing the accounts. A single ServerSpan VPS costs a fraction of that. The math looks obvious on paper. The hidden variable is your sysadmin time. If you spend three hours per month patching, monitoring, and troubleshooting the VPS, and your billable rate is eighty euros per hour, the true cost is two hundred forty euros plus the server fee. The VPS only wins if the automation is solid enough that your monthly touch time drops under thirty minutes.

Setup	Monthly hosting cost	Management time	True cost at €80/hour
Individual shared hosting (20 sites)	€100-300	5-10 hours	€500-1100
Self-managed agency VPS	€15-30	3-5 hours	€255-430
ServerSpan reseller hosting	€20-40	1-2 hours	€100-200

The reseller option sits in the middle because DirectAdmin handles user isolation, automated backups, and SSL provisioning out of the box. You create an account per client, set your own pricing, and let ServerSpan handle the infrastructure. ServerSpan reseller plans start at €6.99 monthly for ten accounts and scale to seventy-five accounts on the r.Three plan.

The decision framework

If you have the Linux skills to configure PHP-FPM pools, write backup scripts, and respond to 3 AM alerts, the self-managed VPS gives you maximum control and the lowest raw hosting cost. If you would rather focus on building websites than tuning MariaDB buffer pools, reseller hosting converts hosting from a cost center into a recurring revenue stream with your branding. For agencies that want the VPS control without the sysadmin burden, ServerSpan's Linux administration service can manage the server while you manage the client relationships. And if you need the DirectAdmin control panel with expert management behind it, DirectAdmin server management covers security updates, performance tuning, and monitoring.

Frequently asked questions

Can I start with a smaller VPS and migrate up?

Yes, but migrating twenty live sites without downtime requires planning. Start with enough RAM that you are not forced into an emergency migration during a client traffic spike.

What happens if one client gets a traffic spike?

With per-client PHP-FPM pools, the spike affects only that client's allocated workers. If the spike is sustained, you can temporarily raise their process limit or move them to a dedicated VPS.

Is email hosting included in this stack?

Running mail servers for twenty clients on the same VPS is a reputation management nightmare. Use a third-party mail provider or ServerSpan's reseller hosting which includes managed email infrastructure.

Do clients know they are on a shared server?

With proper Linux user isolation and separate PHP-FPM pools, clients have no visibility into other sites. Their file permissions prevent cross-site access.

How do backups work with twenty sites?

Each client directory backs up to its own restic repository with individual encryption keys. One client's backup corruption does not affect the others.