How to choose a VPS in 2026 (without overpaying)

Updated August 2026

A VPS — a virtual private server — is a slice of someone else's machine with root access and a public IP: the standard way to put a Linux box on the internet for a few pounds a month. The market ranges from superb value to quietly terrible, and the spec sheets are written to stop you telling which is which. Here's what actually matters.

Size the box honestly

RAM is the binding constraint for most small workloads — it determines what you can run at all. 1GB runs a static site, a small app or a WireGuard endpoint; 2–4GB is the sweet spot for a typical mix (web server + database + a few containers); go 8GB+ when you're consolidating many services or anything Java-shaped.
vCPU counts are marketing — a "vCPU" is a share of a core of unstated age and contention. Two vCPUs from a good provider beat four from an oversold one. Benchmarks from real users (the lowendtalk/serverfault crowd) tell you more than the number.
Storage: NVMe or nothing. Any modern VPS should be on NVMe SSD. The number to watch is size — databases and Docker images eat disk faster than you expect. Check whether snapshots/backups cost extra (they usually do; pay it).
Bandwidth: most workloads never touch a 1TB allowance. It only matters if you're serving media or big files — in which case check the overage price, which is where cheap plans stop being cheap.

Things the spec sheet won't tell you

Oversubscription. The difference between a £4 VPS that's fine and a £4 VPS that's misery is how many neighbours share your host. Signals of a careful provider: consistent community benchmarks, published fair-use policies, no "unlimited everything" promises.
Network location. Latency to you (for admin) and to your users (for serving). UK/EU users → London, Amsterdam, Frankfurt or Falkenstein-class locations. Ping the provider's test IPs before buying.
IPv4 reality. Public IPv4 addresses cost providers real money now; some cheap plans are IPv6-only with NAT'd IPv4. Fine for many uses, a nasty surprise for others — read the small print.
Snapshot & rescue tooling. One-click snapshots before risky changes, and a web rescue console for when you firewall yourself out (see step 4 of our hardening guide for how that happens), are worth more than an extra vCPU.
Support model. Budget VPS = unmanaged: they keep the host alive, everything inside is your job. That's the deal that makes it cheap — if you want someone to fix your WordPress, you want managed hosting instead (see shared vs VPS).

What should it cost?

Rough 2026 street prices for unmanaged Linux VPS with NVMe storage: solid European value providers charge around £4–6/month for 2vCPU/4GB class boxes; the big-name US developer clouds (DigitalOcean, Linode/Akamai, Vultr) run 2–3× that for equivalent specs, buying you slicker tooling, better docs and a bigger managed-services menu; hyperscalers (AWS/Azure/GCP) cost more again and are the wrong tool for "I want a Linux box" — their value is the surrounding ecosystem, and their billing can ambush you. Below ~£3/month, assume heavy oversubscription and plan accordingly.

The renewal-price trick: hosting marketing leans hard on first-term discounts with steep renewal jumps. VPS providers are generally better than shared hosts here, but always check the renewal price, not the banner price — and prefer monthly billing until a provider has earned a year's commitment.

A sensible buying process

Write down what you'll actually run and its RAM total, +50% headroom.
Shortlist two or three providers with a location near your users.
Buy one month of the smallest plan that fits. Run it for real: benchmark disk (fio), check steal time under load (top's st column — sustained values above a few percent mean crowded hosts), ping it from home at peak evening hours.
Happy? Scale up or commit longer. Not happy? You're out a few pounds and an hour — this is the entire advantage of monthly billing.

Once the box is yours, the first ten minutes are already written up: secure it, then put something on it.