Shared hosting is a fine place to start: cheap, simple, and managed for you. But as sites grow, the limits of sharing a server with hundreds of other accounts start to show. A VPS gives you dedicated resources and full control. Here’s how to tell when it’s time, and how to make the move without drama.
Signs you’ve outgrown shared hosting
- “Resource limit reached”, 508 errors, or CPU/entry process throttling during traffic peaks.
- Slow pages, especially uncached ones (admin, checkout, search), even after optimizing.
- Inconsistent performance caused by other accounts on the same server.
- You need software the host doesn’t allow: specific PHP versions or extensions, Redis, Node.js, Python apps, Docker, custom cron intervals, or long-running processes.
- Security worries: a neighbour’s hacked site, or no isolation you can control.
- Email deliverability problems from a shared IP with a poor reputation.
- You run several sites or a store, and want staging environments and proper backups.
What changes with a VPS
| Shared hosting | VPS | |
|---|---|---|
| Resources | Shared, with hidden limits | Allocated vCPU, RAM, storage |
| Control | Control panel only | Root access, any software |
| Isolation | Account-level | Your own virtual machine |
| Maintenance | Done by the host | Your job (or a managed service / panel) |
| IP address | Shared | Your own |
The main trade-off: more power and control, but more responsibility.
Managed, panel, or self-managed?
- Self-managed VPS: cheapest, most flexible. You handle updates, security and backups. Good if you’re comfortable with Linux, or want to learn.
- VPS + control panel (free panels like HestiaCP or CloudPanel, or paid ones like cPanel/Plesk): a familiar interface for sites, databases, email and SSL. See cPanel alternatives.
- Managed VPS: a provider or agency manages the server for you, at a higher cost. See managed vs unmanaged VPS.
Sizing your first VPS
| Current situation | Starting VPS |
|---|---|
| A few small sites hitting shared limits | 2 vCPU, 2–4 GB RAM |
| Busy WordPress site or small store | 2–4 vCPU, 4–8 GB RAM |
| Several client sites or a growing store | 4 vCPU, 8 GB RAM |
You can upgrade later. On VPS.DO, plan upgrades are handled through a support ticket. See how much RAM a VPS needs and when to upgrade your VPS.
Skills checklist (self-managed)
You’ll be more comfortable if you can:
- connect with SSH and use basic Linux commands. See SSH keys;
- install and configure a web stack (Nginx or Apache, PHP, MySQL);
- set up HTTPS with Let’s Encrypt;
- configure a firewall, and keep the system updated;
- set up and test backups.
Not there yet? Start with a control panel, which handles much of this through a web interface.
Step-by-step upgrade plan
- Pick the location closest to your visitors. See choosing a VPS location.
- Set up the server: OS, security basics, web stack (or panel).
- Migrate one site first, test it with a hosts-file override, then switch DNS. See move a website to a VPS and migrate WordPress to a VPS.
- Set up email properly: keep email with a dedicated provider, or configure SMTP for site mail. See WordPress email and SMTP.
- Add backups and monitoring before migrating the rest.
- Migrate the remaining sites, then cancel shared hosting after a safe overlap period.
Try it with low risk
Test performance and network routes before committing fully. VPS.DO offers a 7-day refund (once per customer per data centre), and lists network test IPs on each region’s VPS page. See USA VPS, Hong Kong VPS and Japan VPS.
Quick reference
| Sign | Meaning |
|---|---|
| Resource limit errors | You need dedicated resources |
| Need Redis, Node.js, Docker | You need root access |
| Slow uncached pages | More CPU/RAM + your own caching stack |
| Shared IP email issues | Your own IP + proper SMTP setup |
Related: VPS hosting costs and what is a VPS.