Your customer portal crawls at 10 a.m. A database query times out mid-campaign. No shared-hosting add-on fixes that.
The real cause is usually one of three things: you’re competing for resources with other customers, you don’t have enough control over the server, or the environment was never built for a business-critical workload.
A VPS sits between shared hosting and a dedicated server. You get your own allocated CPU, RAM and disk inside a physical host — more control and isolation than shared hosting, without paying for a whole machine.
But VPS plans are not interchangeable. Here’s what to check.
1. Performance under real load
Big numbers on a spec sheet mean little. Four CPU cores can be plenty for one app and useless for another.
Match the plan to the workload:
- Company website — usually limited by PHP execution, database queries and disk latency. Fast SSD matters more than core count.
- Internal application — needs steady, predictable RAM more than raw CPU.
- Dev team running containers or CI — needs consistent CPU scheduling and fast disk I/O.
Ask what happens at peak, not just at idle.
2. Isolation: KVM or LXC?
Your provider uses virtualisation to separate you from the other customers on that host. The two common approaches behave differently:
- KVM — a fully isolated virtual machine with its own kernel. Choose it when you need real isolation, any operating system, or kernel-level control.
- LXC — lighter containers sharing the host kernel. Faster to deploy and more efficient, if you’re comfortable with a shared kernel.
Neither is better. KVM suits most business workloads; LXC suits high-density, uniform ones.
3. What’s underneath the VM
Look past the virtual machine at the building it lives in:
- Where are the servers physically located?
- Is there redundant power and redundant connectivity?
- How is the network designed — and how much bandwidth is actually included?
- Who answers at 2 a.m., and how fast?
A generous CPU allocation in a weak facility is a bad trade.
4. Backups and recovery
Ask two blunt questions:
- How often are backups taken, and where are they stored?
- How long does a full restore take?
If nobody has ever tested a restore, you don’t have backups — you have hope.
5. Room to grow
The plan you buy today should not be the ceiling. Check that you can:
- Add CPU, RAM or disk without rebuilding the server
- Move up to a dedicated server later if you outgrow virtualisation
- Keep the same IPs and setup through an upgrade
Migrating twice because the first provider had no upgrade path is expensive.
The short version
For most growing teams, a KVM VPS on SSD in a properly run European data centre — with real backups, room to scale and support you can reach — beats a bigger-sounding plan somewhere cheaper.
Internetport’s Cloud VPS runs KVM on SSD in our own Swedish data centres, with root access, 10 TB traffic included and instant provisioning. New to this? Start with what is a KVM VPS, or compare VPS hosting in Europe.