How to Host Multiple Websites on One VPS

Hosting multiple websites on one VPS is like moving from a cramped studio apartment to a spacious house. You get more room, better control, and way better value per square foot.

Why Host Multiple Websites on One VPS?

Here's the math: shared hosting costs $8-15/month per site. Five websites? You're looking at $40-75/month. A single VPS at CutVPS runs $20/month for our Starter plan (2 vCPUs, 4GB RAM, 80GB NVMe).

The difference isn't just financial. You get root access (actual root — not the "root but we've disabled half the commands" version), better performance, and the ability to configure things exactly how you want them.

Most hosting companies are selling you a margin, not a service. They'll charge you $12/month per site when the underlying server costs them pennies per site to maintain.

Is This Even Right for You?

Before we dive in, let's be honest about when you DON'T need a VPS for multiple sites.

Skip this if:

Your sites get less than 1,000 visits/month each
You're running basic WordPress blogs with no custom functionality
You've never touched a command line and aren't interested in learning
Your combined sites use less than 1GB storage total

Stick with shared hosting or static site generators like Netlify. A customer once asked about VPS for three personal blogs (200 visits/day combined). I told them Netlify's free tier was better. They came back six months later when they actually needed the power.

You DO need this if:

Your shared hosting is slow or unreliable
You want to test staging environments
You're running different tech stacks (WordPress, Laravel, static sites)
You need more than basic PHP/MySQL setups

Setting Up Your Multi-Site VPS

Step 1: Choose Your Web Server Stack

You've got two main options: Apache with virtual hosts or Nginx with server blocks. Nginx handles more concurrent connections with less memory (crucial when you're running multiple sites).

For beginners, I recommend a LEMP stack: Linux, Nginx, MySQL, PHP. It's efficient and well-documented.

Step 2: Configure Virtual Hosts/Server Blocks

Each website needs its own configuration file. With Nginx, you'll create separate files in /etc/nginx/sites-available/ for each domain.

Here's what a basic server block looks like:


server {
    listen 80;
    server_name yoursite.com www.yoursite.com;
    root /var/www/yoursite.com;
    index index.php index.html;
    
    location / {
        try_files $uri $uri/ =404;
    }
}

Step 3: Manage Your Databases

Don't put all sites in one database. Create separate databases for each site. It's cleaner, more secure, and easier to backup/restore individual sites.

MySQL command to create a new database and user:


CREATE DATABASE site1_db;
CREATE USER 'site1_user'@'localhost' IDENTIFIED BY 'strong_password';
GRANT ALL PRIVILEGES ON site1_db.* TO 'site1_user'@'localhost';

Step 4: SSL Certificates for All Sites

Use Let's Encrypt. It's free, automated, and trusted. Install Certbot and run:


certbot --nginx -d yoursite.com -d www.yoursite.com

It'll automatically configure SSL and set up auto-renewal.

Resource Management: Don't Let One Site Kill the Others

This is where most people mess up. One poorly optimized WordPress site with a memory leak can bring down all your sites.

Set PHP-FPM Pool Limits

Configure separate PHP-FPM pools for each site with memory limits:


[site1]
user = site1
group = site1
listen = /var/run/php/php8.2-fpm-site1.sock
pm.max_children = 10
pm.max_requests = 500
php_admin_value[memory_limit] = 256M

This prevents one runaway site from consuming all available memory.

Monitor Resource Usage

Install htop and iotop to monitor CPU, memory, and disk usage. Set up simple alerting — even a cron job that emails you when memory usage hits 80%.

A customer's production database went down at 3am. Our AI support bot caught it, diagnosed disk space (logs filling the drive), and suggested the fix within two minutes. But you should catch these issues before they become emergencies.

VPS Specs: What You Actually Need

|-------|---------------|-----------------|--------------|

These aren't theoretical specs. We monitor actual usage across thousands of servers. Most people overestimate their needs initially (the cheapest VPS is rarely the cheapest outcome if you outgrow it quickly).

Backup Strategy: When Things Go Wrong

Automate your backups. Don't rely on your VPS provider's snapshot system alone.

Set up automated database dumps:


#!/bin/bash
mysqldump -u root -p database_name > /backups/site1_$(date +%Y%m%d).sql

Use rsync to backup files to an external location. Services like Backblaze B2 cost $5/TB/month for storage.

Security: Protecting Multiple Attack Surfaces

More sites mean more potential entry points. Here's your security checklist:

Keep everything updated: Set up unattended-upgrades for system packages
Use strong, unique passwords for each database user
Install fail2ban to block brute force attempts
Regular security scans — tools like Lynis are free and effective
Isolate sites using different system users for each site

Performance Optimization

Caching Strategy

Implement multiple layers:

PHP OPcache for compiled PHP code
Redis or Memcached for object caching
Nginx caching for static content

CDN Integration

Even on a budget, use Cloudflare's free tier. It'll reduce server load and improve global performance.

Common Pitfalls and How to Avoid Them

Pitfall 1: Running out of inodes before disk space. Lots of small files (like WordPress uploads) can exhaust inodes while you still have gigabytes free.

Solution: Monitor inode usage with df -i

Pitfall 2: SSL certificate renewal failures taking down all sites.

Solution: Test renewals regularly and set up monitoring for certificate expiry.

Pitfall 3: One site's traffic spike affecting others.

Solution: Implement rate limiting and resource quotas.

FAQ

Q: How many websites can I realistically host on one VPS?

A: Depends on traffic and complexity. Our 4GB RAM plan typically handles 5-10 small WordPress sites or 15-20 static sites comfortably.

Q: What happens if one site gets hacked?

A: If properly isolated (different users, separate databases), the damage stays contained. This is why isolation matters more than raw specs.

Q: Can I mix different CMSs on one VPS?

A: Absolutely. WordPress, Drupal, custom PHP apps, static sites — they can all coexist. Just manage your PHP versions carefully.

Q: Is it hard to migrate existing sites to a VPS?

A: Not if you plan it. Start with one site, get comfortable, then migrate others. Most control panels have migration tools, or you can do it manually with rsync and database dumps.

Ready to consolidate your hosting costs? Our Starter plan at $20/month (2 vCPUs, 4GB RAM, 80GB NVMe) handles most multi-site setups perfectly. Need more power? The Pro plan at $30/month doubles your resources. Both come with full root access, NVMe storage, and our AI support bot to help when you get stuck.

Check out CutVPS plans — because paying $15/month per site when you could pay $20/month total is just bad math.