Comparison
Shared vs VPS hosting: which do you need?
The real difference is who administers the machine. A decision guide with the four questions that settle it.
- Shared hosting means you build the site, the host runs the server. VPS hosting means you run everything, including fixing crashes at 2am.
- Ask four questions: do you need a persistent process, root access, guaranteed resources, or custom software? One yes means a VPS.
- Most slow sites just need caching, not a VPS. Fix caching before you upgrade.
- Shared hosting is the right default for personal and small business sites. Move to a VPS only when you hit a limit you cannot work around.
The question is not which tier is faster. It is who you want to be responsible for the machine.
Shared hosting means the host runs the server. You get a folder, a database, and a control panel. The host sets limits so one account cannot crash the machine for everyone else. You never touch the operating system.
VPS hosting means you rent a virtual machine. You get root access. You install the web server, the database, the firewall, the PHP version, the monitoring, and the security patches. The host provides the virtual hardware. Everything else is your job.
If you do not know what a VPS is, start with what-is-web-hosting. That page covers the basics of how hosting works. This page is about the decision between the two.
The real difference is operational
Shared hosting is for people who want to build a site and forget the server. The host handles kernel updates, DDoS mitigation, disk failure, and MySQL tuning. You handle your content. That is the trade.
VPS hosting is for people who need to control the server. You decide the software stack, the process manager, the kernel modules, and the firewall rules. You also handle the server crashing at 2am. There is no support ticket for “my VPS won’t boot” that ends with someone else fixing it. You fix it, or you rebuild.
A VPS is not a faster version of shared hosting. It is a different job.
What shared hosting actually limits
Shared hosting enforces resource ceilings per account. On CWP free hosting the limits are concrete.
| Resource | Limit |
|---|---|
| Storage | 1 GB |
| Files (inodes) | 30,000 |
| Concurrent PHP processes | 10 |
| Requests per day | 50,000 |
| CPU per account | 25% of one core |
| Memory per account | 256 MB |
| MySQL concurrent connections | 5 |
The limit that people actually hit is the 10 concurrent PHP processes. That is the ceiling that produces the 508 error page. If your site has a slow plugin or a traffic spike that keeps ten PHP workers busy, new visitors get a resource-limit page instead of your site.
Shared hosting also blocks outbound email, cron jobs, SSH, and any language runtime other than PHP. If your project needs a Python daemon or a Node.js listener, shared hosting will not work.
Four questions that decide the tier
Ask these four questions. If the answer to any of them is yes, you need a VPS.
Do you need a persistent process?
A persistent process is a program that runs continuously in the background. A chat server, a queue worker, a WebSocket listener, a game server. Shared hosting runs PHP scripts only when a request arrives. Nothing stays in memory between requests. If your application needs a long-running process, shared hosting cannot do it.
Do you need root?
Root means you can install any software, change any config file, and reboot the machine. It also means you can break the machine. If you need to install a specific PHP extension, compile a kernel module, or run a custom firewall, you need root. Shared hosting gives you a control panel, not a shell.
Do you need guaranteed resources?
Shared hosting is shared. If another account on the same machine gets a traffic spike, your site can slow down. The host caps your usage, but it does not reserve resources for you. A VPS gives you dedicated CPU cores, dedicated RAM, and dedicated disk IO. The neighbours cannot take yours.
Do you need custom software?
PHP and MySQL cover most sites. If you need PostgreSQL, Redis, Elasticsearch, RabbitMQ, or a specific version of Python, shared hosting will not provide it. A VPS lets you install whatever you want.
Most busy sites just need caching
A common mistake is to assume a slow site needs a VPS. Usually it needs caching.
A WordPress site with no cache plugin will run a PHP process and query the database on every page load. That uses one of your 10 PHP processes per visitor. Ten visitors at once and the site is down. A caching plugin serves a static HTML copy from disk. One PHP process can serve hundreds of cached pages per second.
Before you move to a VPS, fix the caching problem. If the site is still slow after caching, then look at the plan.
The short answer for your site
If you are unsure, use the hosting calculator. It asks about your traffic, your software, and your technical comfort. It gives a recommendation in one screen.
If you already know you need a VPS, read how to host a website on a VPS. That guide covers the setup steps and the ongoing maintenance you will need to do.
Shared hosting is the right default
For most personal sites, small business sites, and static projects, shared hosting is the right choice. The limits are real but they match the traffic these sites get. The operational burden is zero. You write the site, the host runs the machine.
If your project outgrows shared hosting, you will know because you will hit one of the four questions above. At that point a VPS is not an upgrade. It is a change of job title. You become the sysadmin.