Cloud Providers

Hetzner Cloud: Price-to-Performance, Regions and the Real Constraints

Hetzner offers more compute per euro than almost anyone. Understanding where that value comes from — and what it costs you elsewhere — is how you decide whether it fits.

Hetzner Cloud: Price-to-Performance, Regions and the Real Constraints — RunCloudMarket cloud infrastructure guide illustration

Hetzner's price-to-performance is not a marketing claim; it is an outlier. A dedicated-core cloud server in Germany or Finland routinely costs a fraction of the equivalent at a hyperscaler, and the hardware is modern.

Understanding where that value comes from, and what you give up in exchange, is the whole decision.

Where the value comes from

Hetzner owns and operates its own data centres in Germany and Finland, buys hardware at scale, and offers a deliberately narrow product catalogue. There is no sprawling managed-service estate to subsidise. Energy costs in Finland are low, and the company has been building this way since the 1990s.

The result is genuine engineering efficiency rather than an introductory discount. Prices are steady rather than promotional.

The product range

Product What it is Suits
Cloud Servers (CX/CPX/CAX/CCX) Virtual machines, hourly billed, capped monthly Most workloads
Dedicated Servers Physical machines, monthly Sustained heavy load, large storage
Storage Box Managed storage over SMB/FTP/SSH Backups, archives
Object Storage S3-compatible Assets, backups
Load Balancers Managed, with health checks Multi-server deployments

Within cloud servers, the letters matter: CX is Intel shared, CPX is AMD shared, CAX is Arm64 (Ampere), and CCX is dedicated vCPU. The Arm64 CAX line is particularly good value where your stack supports it — which, for most modern Linux software, it now does.

Bandwidth: generous, but metered

Each cloud server includes a substantial monthly outbound traffic allowance, typically far larger than comparable providers include. Traffic beyond the allowance is billed per terabyte at a low rate.

Inbound is free. Private network traffic is free. For bandwidth-heavy workloads such as media delivery, this allowance alone can justify the platform.

Server count and what limits mean

New accounts start with a conservative limit on the number of simultaneous servers and on total resources. The limit rises with account history and payment record.

This is why environments are frequently described by server count: it reflects a real, account-level ceiling, not an arbitrary label. An environment rated for ten servers can run ten concurrently; one rated for five cannot, regardless of size.

When evaluating a Hetzner account, the server limit, the available regions and whether outbound port 25 is open are the three details that determine what you can actually deploy.

Regions and latency

Hetzner operates in Falkenstein and Nuremberg (Germany), Helsinki (Finland), Ashburn (US East), Hillsboro (US West) and Singapore. The European sites have the deepest capacity and the widest product range.

For a European audience the latency is excellent. For a global audience you will want a CDN in front, because Hetzner's own edge presence is not comparable to a hyperscaler's — a gap covered in the guide to regions and latency.

What you are giving up

Honesty about the trade-offs matters more than the price:

  • Managed services are minimal. No managed Kubernetes control plane of the depth GKE or EKS offers, no managed relational database service, no serverless functions. You run these yourself.
  • Support is efficient rather than consultative. Tickets are answered competently; there is no solutions architect.
  • Compliance breadth is narrower. ISO 27001 certification exists, but the attestation catalogue is nothing like a hyperscaler's. For workloads with specific regulatory requirements, check carefully.
  • Account verification is deliberate. Hetzner screens signups, which is why the platform stays clean and why getting started can take longer than elsewhere.

Those are reasonable trade-offs for a team that is comfortable administering Linux and wants the maximum compute per unit of spend. They are poor trade-offs for a team that needs managed everything.

Where it excels

Build farms and CI runners, where cost per core dominates. Self-hosted application stacks. Game and media servers where bandwidth is the constraint. Development and staging fleets where you want many machines cheaply. Any European workload with data-residency preferences.

Compared directly with OVHcloud, Hetzner generally wins on raw price and simplicity while OVHcloud offers a broader catalogue and more regions — a comparison drawn out in the Hetzner and OVHcloud article.

Frequently asked questions

Is Hetzner suitable for production? Yes, for teams comfortable operating their own stack. Uptime and hardware quality are strong. What you are choosing against is managed convenience, not reliability.

Are Arm64 servers worth using? If your dependencies build for Arm64 — and most modern Linux software does — the price-to-performance is the best in the catalogue. Verify your container images have Arm64 variants first.

Does the traffic allowance pool across servers? Allowances are per server on cloud instances. Check current terms, as the model has been adjusted over time.

Can I mix cloud and dedicated servers on a private network? Yes, via vSwitch, which is one of the platform's more useful features for hybrid setups.

The Buy Hetzner Account listing shows current server limits and port configurations.

Keep reading

Related guides

Talk to us first

Questions about a specific configuration?

Send us the workload profile — vCPU, memory, region, open ports — and we will confirm which listings actually support it before you buy.

Telegram