Shared Hosting vs VPS: When It Is Time to Move
Shared hosting vs VPS: the symptoms that mean you have outgrown shared hosting, what replaces the control panel, and what the move really costs.
Shared hosting vs VPS is a question about permission, not just speed. Shared hosting gives you a slice of one big server and a control panel, and the host decides what may be installed on it. A VPS gives you your own virtual machine with root access, which is the administrator login that lets you install anything and break anything. The move usually costs an afternoon and buys you predictability, which is the thing you are short of once a site starts earning money.
What you are buying on each side#
On shared hosting, hundreds of accounts sit on one operating system. The host patches it, hands you a panel for domains, mailboxes, and databases, and enforces limits so nobody's bad afternoon takes down everyone else's. Those limits are the product: most plans cap CPU seconds, concurrent processes, and file counts, and the panel decides which PHP versions and extensions you may run.
A VPS is a virtual private server: a slice of a physical machine that runs its own copy of Linux or Windows, with memory and disk reserved for you whether you use them or not. You pick the operating system, you install what you like, and nothing you run gets killed for being long-lived. You also inherit every job the panel used to do for you, which is the honest half of this comparison and the part most upgrade guides skip.
Five signs you have outgrown shared hosting#
- The panel shows throttling at your busiest hour. Resource-limit graphs that flatten out at the top mean your traffic is being metered, not served.
- You need software the host does not offer. A newer PHP or Node runtime, Redis, a headless browser, an image processor, a queue worker.
- Something needs to run continuously. A scheduled job every minute, a live connection that stays open, a task that runs longer than the panel's process timeout.
- You want more than one environment. Staging alongside production, or three client sites that must not share a database user.
- Support answers slowdowns with an upgrade link. We have written before about the suggestion to upgrade in order to fix problems that are not yours.
None of those are performance complaints exactly. They are permission complaints. That is the real line between shared hosting and a VPS.
What a VPS takes away#
Every convenience in a shared hosting panel is a job somebody has to do. On a VPS that somebody is you, with the platform underneath handled by us. Both our VPS lines are unmanaged: we run the hardware, the network, and the virtualisation layer, and you run what is inside. Support will tell you which log to read and whether a symptom is ours or yours.
| Job | On shared hosting | On your VPS |
|---|---|---|
| Operating system updates | The host, silently | You, starting with the first hour on a new server |
| HTTPS certificates | A checkbox in the panel | Caddy or nginx with Let's Encrypt, renewing on its own |
| One-click app installs | A script library | Docker Compose, which is the same idea with a version you control |
| Sending email | Bundled mailboxes | A relay on port 587, or a reviewed exception for port 25 |
| Firewall | The host's, shared | Yours, and only yours |
| Backups | Whatever the plan includes | One free automated backup per Foundational plan, plus the restore you rehearse yourself |
Read the email row twice before you migrate. We reserve the right to filter outbound mail by default to protect the reputation of the network's addresses, so a site that quietly sent order confirmations through the shared hosting mail server wants a relay service set up before launch day, not after.
Shared hosting vs VPS: what the entry tier looks like#
These are the live Foundational (F) line plans, straight from our pricing data, so the table matches the Foundational VPS page to the cent. They run on enterprise Intel hardware with hardware RAID-10 SSD storage, one free automated backup, full root access, a web rescue console, and a credit-backed 99.9 percent network uptime SLA.
| Plan | vCPU | RAM | RAID-10 storage | Transfer | Monthly | Yearly |
|---|---|---|---|---|---|---|
| F10 | 1 | 2 GB | 24 GB | 4 TB | Annual terms | $43.20/yr |
| F20 | 2 | 3 GB | 36 GB | 6 TB | Annual terms | $64.80/yr |
| F30 | 2 | 6 GB | 72 GB | 12 TB | $12.00/mo | $129.60/yr |
| F40 | 2 | 8 GB | 96 GB | 16 TB | $16.00/mo | $172.80/yr |
| F50 | 3 | 12 GB | 144 GB | 24 TB | $24.00/mo | $259.20/yr |
| F60 | 4 | 16 GB | 192 GB | 32 TB | $32.00/mo | $345.60/yr |
| F70 | 6 | 24 GB | 288 GB | 48 TB | $48.00/mo | $518.40/yr |
Compare that against your shared hosting renewal rather than its first-year promotion. Introductory pricing on shared plans commonly jumps at renewal, which is the arithmetic we walked through in the cheap hosting trap. A VPS bill that stays flat is worth a few dollars a month on its own.
If the site is CPU-bound rather than starved of permissions, the Performance (P) line is the better landing spot: AMD EPYC 4564P processors, NVMe RAID storage, and published benchmarks you can reproduce with YABS on your own server. Either way, upgrades happen in the MyNobull portal without a reinstall, so starting small is not a trap.
FAQ#
Is a VPS faster than shared hosting?
For the same money, not always on raw single-request speed. It is far more consistent, because your CPU and memory are provisioned to you instead of shared with hundreds of accounts, and we cap how many machines share a node. Consistency is what visitors actually notice.
Do I need to know Linux to run a VPS?
You need to be willing to learn a little. If the idea of an SSH session is a hard no, stay on shared hosting or hire someone; unmanaged means nobody logs in to fix your application for you.
Can I move a WordPress site from shared hosting to a VPS?
Yes, and the pattern is boring on purpose: stand the new stack up, copy files and the database, test on the server's IP address, then move the DNS record once it works. Keep the old plan running until the new one has served real traffic for a week.
How much transfer do I actually need?
Far less than most people assume; a busy small business site rarely clears a fraction of the TB-scale allowances above. The bandwidth and overage article explains how usage is counted and what happens if you exceed it.
What if I need more than one server later?
Then the question changes from shared hosting vs VPS to how you split workloads, and the same tradeoff shows up in game hosting. Consolidating several small sites onto one larger VPS is usually cheaper than running several small ones.