In short. A VPS shares physical CPU cores across multiple customers on the same host; a VDS (virtual dedicated server) gives you exclusive access to your own cores, so performance stays consistent whether or not other tenants on the same hardware are busy. Most projects start on a VPS for the lower cost, then move to a VDS once workloads need guaranteed, unshared resources — the good news is that move is usually a resize, not a rebuild.
VPS vs VDS: What Actually Changes When You Scale
The core difference is resource allocation, not features — both run the same software, both give you full root access, and both scale up or down as needs change.
| Cloud VPS | Cloud VDS | |
|---|---|---|
| CPU allocation | Shared vCPU cores across tenants | Dedicated physical cores, exclusive to you |
| Performance consistency | Can vary with neighboring tenant load | Consistent regardless of other customers |
| Typical use case | Websites, dev environments, light apps | Production databases, high-traffic apps, CPU-intensive workloads |
| Relative cost | Lower | Higher, for guaranteed resources |
| Software compatibility | Identical — same OS, same stack | Identical — same OS, same stack |
Nothing about what you can run changes between the two — a VDS isn’t a different platform, it’s the same virtualization model with the CPU-sharing removed.
Between the two sits Contabo’s Performance VPS — still built on shared vCPU cores like Cloud VPS, but running the latest AMD EPYC generations with NVMe storage and higher bandwidth as standard, so sustained CPU-bound workloads hold their throughput instead of tapering off under load. It’s worth trying before committing to a full VDS: if a project has outgrown a budget Cloud VPS but doesn’t yet need fully dedicated cores, Performance VPS closes that gap without the bigger jump in cost.
| Cloud Core VPS | Performance VPS | Cloud VDS | |
|---|---|---|---|
| CPU allocation | Shared vCPU cores across tenants | Guaranteed vCPU cores per plan, though the host is still shared | Dedicated physical cores, exclusive to you |
| Performance consistency | Can vary with neighboring tenant load | More consistent than Core VPS — resources are guaranteed by spec even on a shared host | Consistent regardless of other customers |
| Storage & bandwidth | NVMe or SSD, standard bandwidth | Latest-generation NVMe standard, up to 1 Gbit/s bandwidth | NVMe standard, up to 1 Gbit/s bandwidth |
| Typical use case | Websites, dev environments, light apps | Databases, CI/CD, Kubernetes, and CPU-based AI workloads that need sustained throughput | Production databases, high-traffic apps, CPU-intensive workloads |
| Relative cost | Lower | Mid-tier — priced for sustained performance, not the cheapest option | Higher, for guaranteed resources |
| Software compatibility | Identical — same OS, same stack | Identical — same OS, same stack | Identical — same OS, same stack |
Signs You’ve Outgrown a Shared-Core VPS for a VDS
A few patterns tend to show up before a VPS becomes the bottleneck:
- Performance that varies through the day even though your own traffic hasn’t changed — a sign neighboring tenants are contending for the same physical cores.
- Sustained high CPU load from your own workload, not spikes — databases, real-time analytics, or CI/CD pipelines that keep cores busy continuously rather than in bursts.
- A production workload where inconsistent response times are a real cost, not just an inconvenience.
- Growing concurrent-user counts on an application that’s starting to feel the ceiling of shared resources.
How to Migrate from VPS to VDS Without Downtime
- Snapshot or back up your current VPS — treat this as a standard precaution, not a sign the migration is risky.
- Provision the new VDS instance alongside the existing VPS, rather than reinstalling in place.
- Move your application, database, and configuration over, and test on the VDS’s IP before cutting over.
- Update DNS to point to the new VDS once you’ve confirmed everything runs correctly.
- Keep the old VPS running briefly after cutover in case DNS propagation takes time, then decommission it.
Why Contabo’s VPS-to-VDS Path Is Built for This
Contabo’s Cloud VPS line runs on the same account structure as its Cloud VDS (Max Performance) line, so moving from one to the other is a plan change, not a new provider relationship. The Core VPS line leads on RAM-per-Euro for projects that are still finding their resource needs; the VDS line hands you dedicated AMD EPYC cores and guaranteed RAM once consistent performance under load becomes the priority, with NVMe storage standard across both. Both lines share the same Customer Control Panel, DDoS protection, and firewall tooling, so the operational side of the upgrade is minimal — the main work is the migration itself, not learning a new system.
FAQ: Scaling from VPS to VDS
A VPS shares its host’s physical CPU cores across multiple customers, while a VDS gives you exclusive access to dedicated cores. Both are virtualized, both offer full root access, and both run identical software — the difference is whether your compute resources are shared or guaranteed.
Upgrade when consistent, predictable performance matters more than cost — typically for production databases, high-traffic applications, or CPU-intensive workloads where variance from shared-tenant contention becomes a real problem rather than a minor annoyance.
