What people run on it
Databases
Postgres or MySQL with an fsync that does not become the bottleneck.
CI and build runners
Cold builds, container layers and package caches, all on NVMe.
AI tooling
Vector stores, embeddings and model artefacts that need real throughput.
Every Cloud VDS, side by side
| Plan | Cores | Memory | Storage | Network | Per month | |
|---|---|---|---|---|---|---|
| Cloud VDS S | 3 dedicated cores | 24 GB | 180 GB NVMe | 1 Gbit/s · unlimited | $30.00 | Configure |
| Cloud VDS L | 4 dedicated cores | 32 GB | 240 GB NVMe | 1 Gbit/s · unlimited | $50.00 | Configure |
| Cloud VDS XXL Popular | 12 dedicated cores | 96 GB | 720 GB NVMe | 1 Gbit/s · unlimited | $180.00 | Configure |
Prices exclude VAT. Regions outside the EU carry a small monthly fee shown in the configurator. Compare every line →
Deploy next to your users
9 regions on 4 continents, every one with the same images, snapshots and firewall. Move a server between them later without a rebuild.
Latency is measured from a well-connected line in the same country and is a guide, not a promise. Nuremberg is the base region; anywhere else adds a surcharge that scales with the plan and is shown in the configurator before you pay.
Straight answers before you deploy
It is the same architecture as Cloud VPS with NVMe drives and EPYC cores instead of SSD. The difference shows up in random writes, which is where databases and builds spend their time.
Take a snapshot, deploy the Performance plan from it, then point your DNS. Your data comes across; the IP changes.
No, they are shared EPYC cores. For reserved cores choose Cloud VDS.
Ready when you are.
Configure a server now. Your account is created right before payment, with the configuration saved.