A VPS (Virtual Private Server) gives you a guaranteed slice of a physical server, with root access and your own operating system. It sits between shared hosting and a dedicated machine, in both capability and price. This guide covers when the upgrade is justified and how to size one sensibly.
The real difference from shared hosting
On shared hosting you get an account on a server that also hosts many other accounts. You cannot install system software, and your performance depends partly on your neighbours' behaviour.
On a VPS you get:
- Reserved RAM and CPU that no other customer can consume
- Root access — install any software, any version
- Your own operating system, usually Ubuntu, Debian, AlmaLinux or Rocky
- Your own IP address, so another site's reputation cannot affect your email deliverability
- Custom networking — open the ports you need, run services on them
Five signs you have outgrown shared hosting
- You keep hitting resource limits. Recurring "resource limit reached" errors or 508 pages during your busiest hours.
- You need software the host will not install — Redis, Elasticsearch, a specific Node.js or Python version, FFmpeg, a headless browser.
- You are running an application, not a website. Node.js, Django, Laravel queues, background workers and cron-heavy jobs all fit poorly in shared hosting.
- Email deliverability is suffering because of a shared IP's reputation.
- Compliance or client requirements demand isolation, your own firewall rules, or full audit access.
If none of these apply, stay on shared hosting. A VPS you have to administer is a genuine ongoing cost in time.
Sizing: how much do you actually need?
Most people buy too much CPU and too little RAM. RAM is the constraint that produces hard failures — when you run out, the kernel starts killing processes and your site goes down. Running short of CPU merely makes things slow.
1 vCPU / 2 GB RAM
A small WordPress or Laravel site, a staging environment, a personal project, or a lightweight API. Comfortable up to roughly 10,000 visits a month.
2 vCPU / 4 GB RAM
The practical starting point for a business site with WooCommerce, or two or three moderate sites sharing a box. Enough headroom for MySQL plus a caching layer.
4 vCPU / 8 GB RAM
A busy e-commerce site, a multi-tenant application, or a small team's production and staging together. Also the sensible size once you are running Docker containers.
8 vCPU / 16 GB RAM and above
High-traffic applications, video processing, large databases, or hosting many client sites commercially.
A useful rule: budget about 1 GB of RAM for the operating system and control panel, 1–2 GB for the database, and the remainder for your application and its cache.
Managed or unmanaged?
Unmanaged gives you a bare server and root credentials. Every security update, firewall rule, backup and web-server configuration is yours. It is the cheapest option and it is genuinely fine if you are comfortable with Linux administration.
Managed means the provider handles the operating system, security patching, monitoring and backups. You pay more and give up some freedom. For most businesses without a dedicated systems person, this is the honest recommendation.
A middle path many providers offer — including us — is an unmanaged VPS with a control panel installed, so routine work (domains, SSL, databases, backups) is point-and-click while root remains available for anything else.
The security work a VPS requires
This is the part that surprises people migrating from shared hosting. On a VPS, security is your responsibility. At minimum:
- Disable password SSH login and use key-based authentication
- Change the default SSH port and never permit direct root login
- Configure a firewall — open only 22 (or your chosen SSH port), 80 and 443
- Install fail2ban to block repeated failed logins
- Enable automatic security updates
- Take off-server backups — a snapshot stored on the same machine protects you from nothing
An unpatched VPS with password SSH enabled will be found by automated scanners within hours of coming online. This is not a hypothetical.
Frequently asked questions
Is a VPS faster than shared hosting?
For the same workload, usually yes — because the resources are guaranteed rather than contended. A badly configured VPS can easily be slower than well-run shared hosting, though. The hardware is only part of the outcome.
Can I upgrade my VPS later?
Yes. RAM, CPU and disk can normally be increased with a short reboot. Scaling down is sometimes restricted, particularly for disk, so it is better to start modestly and grow.
What happens if my VPS runs out of RAM?
The kernel's out-of-memory killer terminates the largest process — typically MySQL or PHP — and your site returns errors until the service restarts. Adding swap softens this but is not a substitute for adequate RAM.
Do I need a control panel on a VPS?
Not strictly, but it saves substantial time on SSL renewals, database creation, backups and email. Unless you specifically want to configure everything by hand, install one.
How is a VPS different from cloud hosting?
The terms overlap heavily in marketing. Broadly, a traditional VPS is a fixed slice of one physical machine, while "cloud" usually implies the instance can be moved between machines and resized more freely. In practice, judge the specification and the SLA rather than the label.
Next steps: browse VPS plans, or if you are not sure you need one yet, start with shared hosting.