Can I get more information about Contabo's server portfolio?
TABLE OF CONTENTS
- 1. Core VPS
- 2. Performance VPS
- 3. Max performance VPS (formerly VDS)
- 4. Dedicated Servers
- Choosing the Right Product
- Upgrade Recommendations
Available tiers:
1. Core VPS
This portfolio is designed for standard workloads where cost, RAM, and storage are the priority.
It is recommended for everyday workloads, web hosting, CMS, private email servers, dev/test environments, backup and storage.
| Cloud VPS 4 | Cloud VPS 6 | Cloud VPS 8 | Cloud VPS 12 | Cloud VPS 16 | Cloud VPS 18 | |
| vCores | 4 | 6 | 8 | 12 | 16 | 18 |
| RAM (GB) | 8 | 12 | 24 | 48 | 64 | 96 |
| Storage (SSD) | 100 | 200 | 300 | 400 | 500 | 600 |
| Storage with storage extension | 200 | 400 | 600 | 800 | 1000 | 1200 |
| Port | 200 Mbit/s | 300 Mbit/s | 600 Mbit/s | 800 Mbit/s | 1 Gbit/s | 1 Gbit/s |
| Snapshots | 1 | 2 | 3 | 3 | 3 | 3 |
2. Performance VPS
The Performance VPS is a high-performance AI-ready portfolio recommended for modern workloads.
It is specifically designed for AI tooling and other performance-sensitive applications; therefore it is recommended for databases, Kubernetes clusters, CI/CD pipelines, API-based apps, N8N, Openclaw.
Performance VPS is the right choice when storage speed, CPU throughput, or connecting to an AI/LLM are the primary requirement.
| Cloud VPS Plus 4 | Cloud VPS Plus 6 | Cloud VPS Plus 8 | Cloud VPS Plus 12 | Cloud VPS Plus 16 | Cloud VPS Plus 18 | |
| Cores | 4 | 6 | 8 | 12 | 16 | 18 |
| RAM (GB) | 8 | 12 | 24 | 48 | 64 | 96 |
| Storage (NVMe) | 150 | 300 | 450 | 600 | 750 | 900 |
| Storage with storage extension | 300 | 600 | 900 | 1200 | 1500 | 1800 |
| Port | 500 Mbit/s | 500 Mbit/s | 1 Gbit/s | 1 Gbit/s | 1 Gbit/s | 1 Gbit/s |
| Snapshots | 5 | 5 | 5 | 5 | 5 | 5 |
3. Max performance VPS (formerly VDS)
Max Performance VPS is the right choice when you need a full physical server for your production applications with strict SLA requirements, high-traffic and customer-facing platforms, SaaS, multi-tenant applications, real-time processing, and basic AI inference.
| Cloud VDS S | Cloud VDS M | Cloud VDS L | Cloud VDS XL | Cloud VDS XXL | |
| vCores | 6 | 8 | 12 | 16 | 24 |
| RAM (GB) | 24 | 32 | 48 | 64 | 96 |
| Storage (NVMe) | 180 | 240 | 360 | 480 | 720 |
| Port | 250 Mbit/s | 500 Mbit/s | 750 Mbit/s | 1 Gbit/s | 1 Gbit/s |
| Snapshots | - | - | - | - | - |
4. Dedicated Servers
A physical server that is exclusively yours – no shared infrastructure. It is best for workloads requiring physical hardware, maximum I/O, full hardware control, compliance isolation, or microsecond latency with no virtualization overhead.
Choosing the Right Product
| Customer Need | Core VPS | Performance VPS | Max Performance VPS | Dedicated Server |
| Cost-efficient dev, test, or staging environments | Great fit | |||
| Keeping costs low is a primary requirement | Great fit | Potential fit | Potential fit | |
| Backup or archive storage, no processing | Great fit | Potential fit | Potential fit | |
| Guaranteed consistent performance without overspending | Potential fit | Great fit | ||
| Reliable simple server, no compute overhead | Potential fit | Great fit | Potential fit | |
| Strict SLA requirements | Potential fit | Great fit | Great fit | |
| Parallel compute — AI inference, rendering, data pipelines | Potential fit | Great fit | Great fit | |
| Storage-heavy workloads | Great fit | Great fit | Great fit | |
| RAM is the main bottleneck | Great fit | Great fit | Great fit | |
| CPU speed bottleneck, users notice slowdowns | Great fit | Great fit | Great fit | |
| API response times climbing under load | Great fit | Great fit | Great fit | |
| Build times are slowing the team down | Great fit | Great fit | Great fit | |
| High traffic, APIs, or heavy database loads | Great fit | Great fit | Great fit | |
| Performance varies by time of day or under concurrent load | Great fit | Great fit | Great fit | |
| Maximum disk I/O or sustained high bandwidth | Great fit | Great fit | ||
| Running own hypervisor or hosting customer VMs | Great fit | Great fit | ||
| Compliance or strict data isolation requirements | Great fit | Great fit | ||
| Microsecond latency, no virtualization overhead | Great fit |
Upgrade Recommendations
| Current product | Issue experienced | Recommended upgrade |
| Core VPS | Slow response times or a high CPU usage during peak traffic | Performance VPS |
| Core VPS | Performance varies depending on the time of the day | Max Performance VPS |
| Core VPS | Need dedicated resources without a full server | Max Performance VPS |
| Performance VPS | Performance spikes or inconsistency under variable load | Max Performance VPS |
| Performance VPS | Need physical hardware, maximum I/O, or full control | Dedicated Server |
| Max Performance VPS | Need latest-gen CPU performance without dedicated CPU overhead | Performance VPS |
| Max Performance VPS | Need physical hardware, maximum I/O, or compliance isolation | Dedicated Server |
Was this article helpful?
That’s Great!
Thank you for your feedback
Sorry! We couldn't be helpful
Thank you for your feedback
Feedback sent
We appreciate your effort and will try to fix the article