Hetzner is the price-per-core leader, by a wide margin. Kamatera is servers sized by the resource rather than chosen from a menu. This page puts the two side by side — the live configurations and prices from our catalogue, then the differences that actually decide the choice.
| In our catalogue | Hetzner | Kamatera |
|---|---|---|
| Product | Buy Hetzner Account | Buy Kamatera Account |
| Configurations in stock | 3 | 2 |
| Lowest price | $55 | $30 |
| Highest price | $250 | $70 |
| Example options | 5 Server Account / 10 Server Account / Hetzner Cloud Server | Kamatera Free Trial / Kamatera Cloud Server |
| View options | View options |
Prices and configuration counts are read from the live catalogue. Specifications are listed exactly as supplied; nothing here is estimated.
Different categories, so compare the burden rather than the features
Hetzner is a European infrastructure provider; Kamatera is a per-resource cloud provider. Comparing their feature lists is misleading, because one of them expects to run things for you and the other expects you to run them.
The honest question is operational: every managed service you adopt is work you are not doing, and every raw virtual machine is work you are. If the answer to who patches this, who watches it, who gets paged is “me, in the evenings”, optimise for fewer moving parts. Managed services on a more expensive platform can be cheaper than self-managed services on a cheap one once your own time is priced in.
Where Hetzner is the stronger choice
Economics. For a given amount of CPU and RAM, Hetzner is routinely a fraction of a hyperscaler’s price, with a bandwidth allowance that makes egress a non-issue for most workloads.
Best suited to: teams that need raw compute and are happy to operate it themselves.
Regions: Germany and Finland, with a US presence — the European sites are the core of the offering.
Worth knowing: The acceptable-use rules are enforced, and the support model is efficient rather than hand-holding. It suits teams that already know what they are doing.
Where Kamatera is the stronger choice
Configurability. vCPU, RAM, storage and bandwidth are selected independently, so you pay for the shape you actually need instead of rounding up to the next tier.
Best suited to: workloads that do not fit standard instance shapes — unusual CPU-to-RAM ratios, or capacity that changes often.
Regions: An unusually wide data-centre list for a provider of this size, spanning North America, Europe, Asia and the Middle East.
Worth knowing: Flexibility invites over-provisioning. Size against measurements, not against the maximum you might one day want.
The trade-offs, stated plainly
Hetzner: Almost no managed services. You get excellent servers and a competent network; databases, queues, backups and monitoring are yours to run.
Kamatera: A smaller platform with fewer managed services, and per-resource pricing takes more thought than picking a named plan.
How to choose between them
- Choose Hetzner if your workload is Self-managed workloads, build farms, batch processing and anything where the bill is dominated by CPU hours
- Choose Kamatera if your workload is Memory-heavy or CPU-heavy outliers, short-lived capacity, and multi-region deployments needing an unusual city
- Choose neither if the shape of the work does not match either — the full catalogue has eight other platforms, and the comparison tool will hold four of them side by side.
Related reading
- Buy Hetzner Account – every Hetzner configuration in stock
- Buy Kamatera Account – every Kamatera configuration in stock
- How to choose a cloud provider – the framework behind this comparison
- How cloud billing works – why the billing model matters more than the sticker price
- Compare up to four accounts side by side
Questions
Common questions about this comparison
Is Hetzner cheaper than Kamatera?
The prices in the table above are the live catalogue prices for the accounts we stock, so you can compare those directly. Running cost is a separate question and depends on the billing model: Hetzner bills a fixed monthly figure and Kamatera bills a fixed monthly figure, which means the cheaper account is not always the cheaper month.
Can I run the same workload on both?
For ordinary Linux servers, databases and web applications, yes. The divergence starts when you adopt a platform's proprietary managed services — a specific queue, function runtime or identity model — because those are what make a migration expensive later.
Which one is better for Self-managed workloads?
That is Hetzner's stated strength, so it is the natural starting point. It is still worth checking region availability and the billing model against your own constraints before committing.
What do I actually get when I buy an account here?
The configuration named on the product page and nothing beyond it — the vCPU figure, region, account age or credit exactly as listed. Both product pages set out every option in stock with its own price.