// hosting
VPS hosting explained: what it is and how to choose
What a VPS actually is, how it differs from shared and dedicated hosting, the criteria that matter when choosing one, and who it's the right fit for — no invented benchmarks, just the facts.
A VPS — Virtual Private Server — is one physical server partitioned into several isolated virtual machines, each with its own operating system, guaranteed resources and root access. You get most of the control of a dedicated machine at a fraction of the cost, while a hypervisor keeps your slice separate from everyone else's. This guide explains what a VPS really is, how it compares to the alternatives, and the concrete criteria to judge any provider on — so you don't have to trust a leaderboard.
What a VPS actually is
Virtualization software (the hypervisor) splits one powerful physical server into multiple virtual servers. Each VPS behaves like its own machine: it boots its own OS, has its own IP address, and is allocated a fixed amount of RAM, CPU and storage that the neighbours can't take from you. That isolation is the key difference from shared hosting — your performance no longer depends on what the site next door is doing.
Because you typically get root (administrator) access, you can install any software stack, configure the web server yourself, run background workers, containers or a database engine of your choice — things a managed shared host simply won't let you do.
VPS vs shared vs dedicated
The three common tiers sit on a spectrum of control, isolation and cost.
| Type | Resources | Control | Best for |
|---|---|---|---|
| Shared hosting | Pooled, informal limits | Low — no root, fixed stack | Small sites, blogs, brochure sites |
| VPS | Guaranteed slice (RAM/CPU/disk) | High — root access, custom stack | Growing apps, custom runtimes, side projects with real traffic |
| Dedicated server | A whole physical machine | Full — but you manage it all | Heavy, steady workloads needing maximum isolation |
A VPS is the middle ground: more power and freedom than shared hosting, far cheaper and lower-maintenance than renting an entire physical box.
Managed vs unmanaged
This is the choice that surprises people most.
- Unmanaged VPS — you get a bare OS and you're the sysadmin: you patch it, secure it, configure the web server, set up backups and fix it when it breaks. Cheaper and maximally flexible, but it assumes you're comfortable on the command line.
- Managed VPS — the provider handles OS updates, security hardening, monitoring and support, usually with a control panel. Costs more, but it buys back your time if you'd rather not run a server.
The criteria that matter when choosing
Ignore marketing superlatives and compare providers on these concrete dimensions instead.
RAM and CPU
RAM is what you'll run out of first — a database plus an application server plus a cache all want memory, and the OS needs its share too. vCPUs (virtual CPUs) handle concurrent requests and CPU-bound work like image processing or server-side rendering. Watch the difference between shared/burstable vCPUs (fine for spiky light loads) and dedicated vCPUs (consistent performance, higher price).
Storage type
Prefer NVMe or SSD over mechanical disks — disk speed shows up directly in database query times and page builds. Check the amount, too: logs, uploads and database growth add up faster than you'd expect.
Bandwidth and location
"Bandwidth" hides two numbers: the monthly data-transfer allowance and the port speed. Media-heavy sites burn through transfer quotas, so read the overage policy. And pick a datacenter region close to your audience — physical distance adds latency to every dynamic request.
Backups, scaling and support
- Backups — included snapshots or a paid add-on? Automated backups are worth paying for.
- Scaling — can you resize the plan (more RAM/CPU) without rebuilding from scratch?
- Support — response times matter most on unmanaged plans when something breaks at 2am.
Price
Compare the renewal price, not just the promotional first term, and confirm what's bundled (backups, bandwidth, an IPv4 address, a control panel). Among providers that focus on a strong resource-to-price ratio, Contabo is a well-known option for generous CPU and RAM at a low monthly cost — useful when you want headroom without paying premium rates. As always, map the spec to your real workload rather than to a sticker price.
Pros and cons of a VPS
Advantages
- Guaranteed, isolated resources — no noisy neighbours.
- Root access and a custom stack — install anything, tune everything.
- Far cheaper than a dedicated server, with similar control.
- Usually scalable on demand (resize the plan as you grow).
Trade-offs
- More responsibility — an unmanaged VPS means you handle security and maintenance.
- Overkill for a tiny static site that shared hosting or a static host would serve more cheaply.
- Requires some Linux/command-line comfort unless you pay for managed.
Who a VPS is for
A VPS is the right call when your project has outgrown shared hosting but doesn't justify a dedicated machine: a growing dynamic app, a site that needs a specific runtime version, a project running background jobs or containers, or any workload where you want control over the stack and isolation from other tenants. If you only run a small static site or a low-traffic blog, shared or static hosting is usually simpler and cheaper.
How to decide
Start from your workload, not from a "best of" list. Estimate memory first, then CPU, then storage and transfer. Require a region near your users, insist on NVMe/SSD and affordable backups, decide whether you want managed or unmanaged, and compare renewal prices on equivalent specs. Once you've judged the criteria for yourself, our companion guide on choosing the best VPS for a web project walks through sizing a plan to a real project.