Skip to content

Independent marketplace for verified cloud accounts

Hetzner vs Contabo

Both are German hosts competing on low prices, and Contabo is usually the cheaper number on the page. The useful question is what you give up to get that discount.

Buy Hetzner Account
Germany, EU hardware value

Hetzner

Regions noted in source
Germany, Finland, United States, Singapore
Configurations listed
3
From$50 View account
Buy Contabo Account
Germany, low cost VPS

Contabo

Regions noted in source
Germany and global
Configurations listed
1
From$70 View account

Compare the two spec sheets and Contabo looks like it is winning. More vCPUs, more RAM, more disk, for a monthly figure that sits below what Hetzner asks for a smaller machine. If the decision were made on the listing alone it would not be a decision.

It is not made on the listing. Both companies are German, both sell cheap servers, and both are legitimate businesses with long track records. But they reached low prices by different routes, and the route determines what the server actually feels like under load. This page is about that difference, written for someone who has to run the thing afterwards.

Price is a specification, not a discount

When a provider sells more hardware for less money, something in the delivery model is paying for it. That is not an accusation, it is arithmetic. The honest questions are which variable moved and whether it is a variable your workload cares about.

Contabo’s model leans on generous resource allocation at low cost, and the resources are shared more aggressively than on premium tiers elsewhere. You get a large allocation on paper and you share the underlying host with more neighbours. For workloads that are idle most of the time, that is close to free money.

Hetzner’s model leans on operating its own facilities at high efficiency and selling on thin margin, with less aggressive oversubscription. You get less headline resource per euro than Contabo advertises, and the resource you get behaves more consistently.

What Contabo gives you more of

Be clear about the upside, because it is real.

  • Raw allocation. For memory-hungry software that spends most of its life waiting, a large cheap instance is the correct answer.
  • Disk space. Storage-heavy use cases such as backup targets, media libraries and archives are where the pricing is most compelling.
  • A wider international location list than Hetzner, which matters if you need presence outside Europe without adding a provider.
  • A low floor. If your budget is genuinely tight, Contabo lets you run something that would not otherwise exist.

None of that is a trick. Self-hosted media, personal infrastructure, lab environments, bulk storage, low-traffic sites and development boxes all run perfectly well, and paying Hetzner prices for them is paying for consistency you will never notice.

What you give up

The costs show up in four places, and all of them are about variance rather than capability.

Consistency under load is the main one. On a heavily shared host, your performance depends partly on what your neighbours are doing. Most of the time this is invisible. During the window when it is not, you cannot fix it, because the cause is outside your instance.

Storage behaviour is the second. Headline disk capacity says nothing about throughput or latency under concurrent access, and cheap bulk storage is usually optimised for capacity rather than random input and output. A database that would be comfortable on Hetzner can feel sluggish on a nominally larger Contabo instance, because the bottleneck was never the gigabytes. Reading cloud storage performance specs is worth ten minutes before you choose on disk size.

Provisioning speed is the third. Hetzner cloud instances come up in seconds, which makes automated scaling and ephemeral environments practical. Contabo provisioning has historically been slower and less immediate, which is irrelevant for a server you keep for two years and disqualifying for infrastructure you create and destroy from a pipeline.

Support responsiveness is the fourth. Neither company runs a premium support organisation, but expectations should be calibrated lower at the cheaper end. If an unanswered ticket costs you revenue per hour, that is a real cost that belongs in the comparison.

The workloads where the gap actually shows

Be specific rather than general. The difference matters when:

  • You are running a production database with latency expectations users can feel.
  • You are serving interactive traffic where tail latency is a product quality issue, not a graph.
  • Your infrastructure is created and destroyed automatically, so provisioning time is in the critical path.
  • You need performance you can predict for capacity planning rather than performance you observe and hope holds.

It does not matter much when the workload is a backup destination, a batch job that runs overnight, a staging environment, a personal service, or anything where an occasional slow hour is an inconvenience rather than an incident.

Networking, locations and what sits around the server

Hetzner’s cloud product includes the pieces you need to build a normal application topology: private networks, firewalls that are managed as resources rather than only inside the guest operating system, floating addresses, load balancers and a block storage service. You can describe all of it in Terraform and rebuild an environment from scratch. That is a cloud, in the sense that the network is programmable.

Contabo is closer to a traditional hosting product with a cloud label. You get a server with an address and you build outward from there. For a single machine running a single application, that is the whole requirement and the difference is academic. For a multi-tier environment with separate application and database tiers that should not be publicly reachable, you will be doing more of that isolation yourself, inside the instances, with firewall rules you maintain by hand. Cloud firewall rules that hold up is the reference to read if that is your situation, because host-level rules fail differently from network-level ones.

On geography, Contabo lists more locations outside Europe, which is genuinely useful if you need a presence in a region Hetzner does not serve and you do not want a third supplier. Hetzner’s footprint is tighter and its network inside that footprint is excellent. As always, the number of cities on a page is less informative than the measured round trip from the users you actually have.

Reading the two offers side by side

What you are comparing Hetzner Contabo
Headline resources per euro Good Higher
Performance consistency More predictable More variable under contention
Provisioning speed Fast enough to automate Slower, better suited to long-lived servers
Storage profile Balanced toward performance Oriented toward capacity
Best-fit workloads Production services, databases, automated fleets Bulk storage, labs, idle-heavy services

How to test instead of guessing

Both providers are cheap enough that you should not take anyone’s word for this, including ours. Rent one instance of each for a month and run your own workload on them, not a synthetic benchmark. Measure the thing your users experience: query latency at the ninety-ninth percentile, build duration, request time under your actual concurrency.

Run it across a full week, including evenings and weekends, because contention effects are time-of-day phenomena and a Tuesday morning sample will tell you nothing. If the numbers look the same, buy the cheaper one with a clear conscience. That outcome is common and it is a legitimate result.

Buying an account on either

Both providers verify new customers and both have grown more careful about payment methods and billing regions, which catches out teams in some countries entirely. If you need capacity now, the listings for Buy Hetzner Account and Buy Contabo Account set out what each one includes.

TrustCloudHub is an independent marketplace and is not affiliated with Hetzner or Contabo. If an account carries credit, that credit is the provider’s to govern: it expires, it does not apply to every service, and the remaining balance should be verified inside the provider’s console after transfer rather than taken from a listing. Our guide on how to read a cloud account listing explains which details to check before you commit.

The short version

Choose Contabo when you need volume cheaply and your workload tolerates variance. Choose Hetzner when you need the machine to behave the same way on Friday evening as it did on Tuesday morning. If you are also weighing a provider outside Germany, Hetzner vs Digital Ocean covers the same value argument against a platform that sells ecosystem rather than hardware.

Other comparisons to consider

Google Cloud vs Hetzner
vs

Google Cloud vs Hetzner

Hetzner sells compute by the unit at a low price. Google Cloud sells a platform. The comparison is really about…

Hetzner vs Digital Ocean
vs

Hetzner vs Digital Ocean

Hetzner sells hardware value from a mostly European footprint. DigitalOcean sells a developer platform with managed add-ons and deep documentation.…

AWS vs Hetzner
vs

AWS vs Hetzner

For steady always-on compute the price gap between Hetzner and AWS is wide. This comparison works out what that gap…

OVH vs Contabo
vs

OVH vs Contabo

Contabo sells generous specifications at low prices; OVHcloud sells a full infrastructure catalogue with enterprise options. The comparison is really…

Background reading

Decided which platform fits?

Both accounts are documented in the catalog, with configurations, credit balances and service limits listed before you buy.

Telegram