Hetzner vs Contabo
Compare these providers side by side, then jump into workload pages where the same pair overlaps on Docker, WordPress, databases, and other specific use cases.
| Feature |  |  |
|---|---|---|
| Starting Price | $4.51/month Best Price | $5.50/month |
| Entry Plan Specs | 2 vCPU 4GB RAM 40GB NVME | 4 vCPU 8GB RAM 50GB NVME |
| CPU Score (Single) | 1,245 Fastest | 980 |
| Disk Read Speed | 1,850MB/s Fastest | 420MB/s |
| Network Throughput | 9,800Mbps Fastest | 2,800Mbps |
| Boot Time | 18.5seconds Quickest | 55.2seconds |
| Datacenter Regions | 4 locations | 6 locations |
| Hourly Billing | ||
| Support | ticket email phone | ticket email |
| Get Started | Visit Hetzner | Visit Contabo |
Compare These Providers by Workload
Hetzner vs Contabo for Game Servers
Low-latency VPS with good network performance for hosting game servers.
Open comparison
Hetzner vs Contabo for Self-Hosting
VPS providers ideal for self-hosting apps like Nextcloud, n8n, and other services.
Open comparison
Hetzner vs Contabo for Jellyfin
VPS providers with good transcoding performance and storage for running Jellyfin media server.
Open comparison
Hetzner vs Contabo for Nextcloud
VPS providers with ample storage and good I/O for running Nextcloud.
Open comparison
Hetzner vs Contabo for Plex
VPS with good CPU power for transcoding and bandwidth for Plex media streaming.
Open comparison
Analysis
Hetzner
German hosting provider known for exceptional price-to-performance ratio. Popular choice among developers and self-hosters for their reliable infrastructure and transparent pricing.
Starting plan: $4.51/mo
CPU score: 1245
Disk read: 1850 MB/s
Contabo
German provider offering the most storage and RAM for the lowest prices. Ideal for storage-heavy workloads and users who prioritize capacity over performance.
Starting plan: $5.50/mo
CPU score: 980
Disk read: 420 MB/s
Related Comparisons
FAQ
Which provider is cheaper: Hetzner or Contabo?
Use the comparison table to check the cheapest entry plans first, then move to the workload-specific pages if you need minimum RAM, CPU, or storage filters.
Should I use the generic comparison or a workload comparison?
Use the generic comparison when you are still narrowing providers down broadly. Use the workload pages once you know the app or use case you care about.
Are these comparisons based on live benchmark data?
They are based on the current repository dataset, with the latest benchmark snapshot dated Mar 2, 2026.