How I Manage 7+ Websites Across 3 Servers

Right now, I'm running 7+ production websites across 3 servers. Two are Vultr CloudPanel instances — one in Virginia, one in Miami — and the third is an Enhance/cPanel server hosting a client's Kirby CMS site. I also have a home NAS that stores Git backups of everything. Here's how it all works without consuming my entire life.

The Setup: 3 Servers, 7+ Sites

My primary server is a Vultr VPS in Virginia running CloudPanel. It hosts the bulk of my sites: myseodesk.com (this portfolio), crawlhound.com (an SEO scanner I built), fancypetsalon.com (a 162-page bilingual dog grooming site), and several others. Each site has its own virtual host, database, and SSL certificate.

The second server is another Vultr instance in Miami, hosting a Laravel quoting tool and an Asterisk PBX for a VoIP phone system I built. Different stack, different requirements, different server.

The third server is an Enhance/cPanel box hosting a client's company website running Kirby CMS. It auto-deploys from a Git hook on my office NAS — push to the repo, and it's live within seconds.

Why Multiple Servers Instead of One Big One

Isolation. If one site gets hit with traffic or has an issue, it doesn't take down everything else. My SEO scanner can spike to 100% CPU during a crawl without affecting the dog grooming site. The Asterisk PBX needs real-time audio processing that can't share resources with web applications.

Different stacks. CloudPanel handles PHP and Node.js sites beautifully. But the quoting tool runs Laravel with Vite, and the PBX needs Asterisk with SIP/WebRTC configuration. Trying to jam all of that onto one server creates a maintenance nightmare.

Cost optimization. Two small VPS instances ($12/mo + $12/mo) cost the same as one larger one but give me better isolation and redundancy. If one server has a hardware issue, only half my sites go down, not all of them.

The Tools That Make It Work

• CloudPanel — Free server management panel for PHP/Node.js sites. Clean UI, Nginx-native, Let's Encrypt SSL automation.
• systemd — For Python/FastAPI applications. Each app runs as a systemd service with automatic restart on failure.
• rsync — Deployment in one command. rsync -avz over SSH, excluding .git and credential files.
• Git with dual remotes — Every project pushes to both a self-hosted Gitea instance and a home NAS. Two backups, always in sync.

Deployment: One Command, Every Time

Every deployment follows the same pattern: rsync the project to the server, fix file ownership, restart the service if needed. No CI/CD pipeline, no Docker orchestration, no Kubernetes. For 7 websites, that's overkill. A well-structured rsync command does the job in 3 seconds.

For the Kirby CMS site, deployment is even simpler: git push to the NAS remote, and a post-receive hook rsyncs to the production server automatically.

Monitoring and Backups

Every site has uptime monitoring that alerts me if it goes down. Database dumps run on a cron schedule and get stored locally on each server plus synced to the NAS. All code lives in Git with dual remotes, so even if both production servers disappeared tomorrow, I could rebuild everything from the NAS backups in an afternoon.

What This Costs

Total monthly infrastructure cost for 7+ production sites:

• Vultr Virginia (CloudPanel): $12/mo
• Vultr Miami (Laravel + Asterisk): $12/mo
• Enhance/cPanel client server: $18/mo
• Home NAS backup storage: $0 (already owned)
• Cloudflare DNS + CDN: $0 (free plan)

Total: ~$42/month for 7+ production websites. That's $6 per site. A single managed hosting plan from WP Engine costs $20/month for ONE site.

Read the full case study: Managing 7 Sites Across 3 Servers.