Host Multiple Static & CMS Sites on One VPS
The best way to host multiple static and CMS websites on one VPS is to use Docker Compose with a reverse proxy like Caddy or Traefik. This gives you isolated environments for each site, automatic SSL, and simple updates—without the overhead of managing separate virtual machines or complex manual configs.
What to Look For
When choosing a hosting setup for multiple sites, focus on these criteria:
- Isolation: Each site should have its own dependencies and versions so one site’s update doesn’t break another.
- Resource efficiency: A VPS has limited RAM and CPU; the solution should use as little overhead as possible.
- Ease of SSL: Automatic HTTPS certificates are essential for modern sites; manual cert management is a pain.
- Update workflow: How easy is it to deploy a new version of a site or add a new site?
- Backup simplicity: You need to be able to back up each site’s files and database separately.
- Your skill level: Some solutions require more command-line comfort than others.
Option 1: Docker Compose + Caddy (Top Pick)
Strengths: Caddy automatically obtains and renews SSL certificates for each domain. You define each site as a service in a docker-compose.yml file, with its own container for the CMS (like WordPress) and a database. Static sites can be served from a simple Nginx or Apache container, or even directly from Caddy’s file server. Updates are as simple as pulling new images and restarting.
Trade-offs: Requires understanding Docker basics (volumes, networks, ports). Caddy’s config is simple but not as flexible as Nginx for complex routing rules. You need to manage Docker updates yourself.
Who it suits: Developers comfortable with the command line who want a clean, reproducible, and low-maintenance setup. Ideal for 2-10 sites with mixed static and CMS needs.
Option 2: Docker Compose + Traefik
Strengths: Traefik is designed for dynamic environments; it automatically discovers services via Docker labels and configures routing and SSL. It has a web dashboard for monitoring. It’s more feature-rich than Caddy for advanced load balancing and middleware (like rate limiting).
Trade-offs: Traefik’s configuration is more complex (using labels and dynamic config). The learning curve is steeper than Caddy. For simple setups, it’s overkill.
Who it suits: Those already familiar with Docker and wanting more control over routing, or who plan to scale to many services or microservices later.
Option 3: Nginx Reverse Proxy + Manual Virtual Hosts
Strengths: No extra layers—just Nginx serving static files and proxying to PHP-FPM or Node.js processes. You have full control over every aspect of the config. Very low memory footprint. Works well if you’re comfortable editing config files and managing processes manually.
Trade-offs: SSL certificates must be obtained and renewed manually (using certbot, which can be automated with cron). Each site’s setup is manual, so adding a new site means copying configs and creating databases. Updates to PHP or Node versions are global, which can break older sites.
Who it suits: Experienced sysadmins who want maximum control and have few sites (1-5). Good for those who prefer traditional hosting over containers.
Option 4: CloudPanel or CyberPanel (Control Panel)
Strengths: These free, open-source control panels give you a web UI to manage multiple sites, databases, SSL (via Let’s Encrypt), and email. They handle Nginx/Apache config, PHP versions per site, and even WordPress management. They are designed for exactly this use case and are much lighter than cPanel.
Trade-offs: You’re tied to the panel’s structure and updates. Some features (like staging) may be limited. Security depends on the panel’s code; you must keep it updated. They are not as flexible as Docker for custom setups.
Who it suits: Users who want a graphical interface and don’t want to write config files. Great for hosting client sites or if you’re not a full-time sysadmin.
Option 5: Virtualmin (Webmin Module)
Strengths: Virtualmin is a mature, powerful control panel that runs on top of Webmin. It supports virtual hosts, databases, SSL, and even mail. It’s free and open-source, with a large community. It can manage many sites efficiently.
Trade-offs: The interface is dated and can be overwhelming. Configuration is complex, and there’s a learning curve. Some features require paid modules (like Cloudmin for virtualization).
Who it suits: Those who want a full-featured control panel without paying for cPanel, and are willing to spend time learning it. Good for larger numbers of sites (10+).
Option 6: LAMP/LEMP Stack with Separate Users
Strengths: No extra software—just Apache/Nginx, MySQL, PHP, and perhaps Node. Each site gets its own system user, home directory, and database. This provides good isolation and is a classic approach.
Trade-offs: Manual setup for each site (creating users, databases, vhosts, SSL). PHP version is global unless you use multiple PHP-FPM versions. Security requires careful permissions. Updates can break sites.
Who it suits: Purists who want to understand every layer and have a small number of static sites or simple CMSs. Not recommended for many dynamic sites.
How to Choose
First, consider your budget. All options above are free software; the cost is your time and VPS resources. If you have a low-spec VPS (1GB RAM), a plain Nginx setup or CloudPanel will use less memory than Docker. If you have 2GB+ RAM, Docker is fine.
Next, think about your use case. For a mix of static sites and a few CMSs, Docker Compose + Caddy is the sweet spot: you get isolation, easy SSL, and simple updates. If you’re managing client sites and want a UI, CloudPanel is excellent. If you’re a developer who wants to automate everything, Traefik is powerful.
Common trade-offs: Docker adds a learning curve but saves time in the long run. Control panels are easy but can be limiting. Manual Nginx gives control but is time-consuming for many sites. Also, consider backups: Docker volumes and databases need to be backed up separately; control panels often have built-in backup tools.
Frequently Asked Questions
Can I host a static site and WordPress on the same VPS?
Yes. With Docker, you can run a static file server (like Nginx) and a WordPress container simultaneously. With a control panel, you create two virtual hosts. The reverse proxy routes requests to the correct service based on domain.
How do I get SSL certificates for multiple domains?
Use Let’s Encrypt. With Caddy or Traefik, it’s automatic. With Nginx or control panels, you use certbot or the panel’s SSL feature. All are free.
What if one site gets hacked?
With Docker, containers are isolated; a hack in one container doesn’t affect others. With control panels, sites are isolated via user permissions. Always keep software updated and use strong passwords.
Can I use a single IP address for all sites?
Yes, that’s standard. The reverse proxy or web server uses the domain name in the HTTP request to route to the correct site. You only need one IP.
How much RAM do I need for 5 sites?
For static sites, 1GB is plenty. For 5 WordPress sites, you’ll want at least 2GB, preferably 4GB, especially if using Docker (each container adds overhead). Use a lightweight PHP-FPM setup to reduce memory.
Should I use Apache or Nginx?
Nginx is generally more efficient for static files and reverse proxying. Apache is easier for beginners and has more modules. Both work; Nginx is the common choice for multi-site setups.
Bottom Line
For most people, Docker Compose with Caddy is the best balance of power, simplicity, and maintainability. It handles SSL automatically, isolates each site, and makes updates painless. If you prefer a graphical interface, CloudPanel is a strong alternative. Avoid manual Nginx unless you have few sites and love configuring servers. Start with a 2GB VPS, use Docker, and you’ll have a solid foundation that can grow.
Related
Method: the standard formula for this calculation, rounded as each result states. See how the calculators work or report an error.