Hetzner Review 2026: Cloud Pricing & Trade-offs

The advertised EUR 5.99 Cost-Optimized floor was marked unavailable when reviewed and is not used here as an orderable starting quote. A Helsinki CPX12 IPv6-only calculator example is EUR 11.49 per month, excluding VAT, with hourly billing of EUR 0.0184 and a monthly cap. The Regular Performance table gives EUR 11.99 including IPv4 for the reviewed configuration, again excluding VAT. Confirm region, resources, availability, and tax status before relying on either amount. No USD conversion rate was verified.

Transfer allowances are regional. The reviewed CPX examples show twenty terabytes in Europe, one terabyte for a US CPX11, and half a terabyte for a Singapore CPX12, with larger plans differing. The calculator's EUR 1 per additional terabyte applies to its European scenario, not every location. Budget the expected outgoing traffic against the exact regional allowance rather than importing an EU figure into a US or Singapore cost model. Vendor comparison charts can suggest questions, but they are not independent evidence that two complete application stacks cost the same to operate.

Everything included is infrastructure-shaped: stateful firewalls, private networks, snapshots and backups as products, a REST API and CLI, and documented Terraform, Ansible, and Kubernetes integrations. What is absent is equally defining: no managed application runtime, no deploy previews, no serverless functions, and a thinner managed-database story than platform rivals - the operations are the discount. Teams uncomfortable patching Linux should read this as a different product category, not a cheaper version of the same one.

The middle path is the documented one-click catalog: Coolify, Docker CE, GitLab, Nextcloud, Grafana, and more - effectively building your own PaaS on rented metal. That pattern (Hetzner + Coolify, Hetzner + n8n) is the backbone of the self-hosting movement our no-code and hosting categories keep meeting, and our cloud storage guide's Nextcloud section shows the same trade: control and cost versus operational ownership.

The provider's information-security documentation and data-protection information provide material for a procurement review. Certification statements about infrastructure do not independently certify the customer's application or settle every GDPR obligation. Select the appropriate region, review the processing agreement, and retain responsibility for the data and configuration you deploy. We did not inspect an independent audit report or benchmark uptime for this review.

The Cloud SLA describes a 99.9% commitment and service-credit remedies. That is not measured uptime, a guarantee of uninterrupted business operation, or reimbursement for every consequential loss. Confirm support and incident obligations against your own recovery requirements. The practical buying questions are whether the available region, operating model, and documented obligations fit the workload—not whether a hosting provider's marketing label makes the entire stack compliant.

Against DigitalOcean: the closest philosophical rival - DO offers more managed services (databases, app platform) with US-centric polish at higher per-compute prices; Hetzner wins raw price-performance and included traffic. Against Vercel and Netlify: platforms for frontend teams - previews, edge, zero ops - at a premium that our Vercel alternatives guide and Vercel vs Netlify comparison put in context; Hetzner is what several of those alternatives run on underneath.

Compare Railway and Render when a managed deployment workflow is valuable, and Fly.io when its regional application model matches the requirement. Our startup hosting guide covers the broader options. A platform fee buys some operational work, but neither model is universally cheapest: include the people, services, and recovery duties required by the actual application.

Write down CPU and memory needs, region, IPv4 requirement, outgoing transfer, persistent storage, backups, and expected hours before comparing hosts. Include both a normal month and a traffic spike. A vCPU count alone does not establish equal performance, and a shared instance is not interchangeable with dedicated resources. Use the actual regional plan and quote rather than a global minimum advertised in a different currency or unavailable family.

The billing FAQ prices automatic server backups at twenty percent of the server price. Snapshots and attached Volumes have their own billing; the Volume page publishes storage pricing that should be reconciled with the quote's tax basis. Add an independent backup destination if the recovery plan needs one. A stopped test instance can continue costing money, and an unused IPv4 address or retained storage can outlive it. Review resource cleanup only after data preservation has been checked. This worksheet makes a comparison with DigitalOcean, Railway, or Render more useful than comparing headline server rent.

The backup and snapshot FAQ distinguishes server disks from attached Volumes. Automatic server backups provide seven slots but do not include those Volumes. Live snapshots also do not automatically guarantee application-consistent database recovery. Identify where each database, uploaded file, and secret lives, then decide how it is backed up and restored. Replication and a snapshot are not substitutes for a tested, appropriately isolated recovery process.

Assign patching, monitoring, incident response, and restore ownership before moving a production workload. Define how much data loss and downtime are acceptable, and rehearse a restore using non-production resources and approved data. Verify the database, files, credentials, DNS, and any external integrations after recovery. Our n8n review and self-hosting discussions describe why control comes with this responsibility; a one-click application image does not remove it. Service credits under an SLA and recovering your customers' data are different problems, and the procurement plan needs to address both.

The 8.9/10 editorial assessment reflects Hetzner's documented server options, regional allowances, and infrastructure tooling, balanced against operational work, add-on costs, availability, and recovery boundaries. It is not a performance, security, or uptime benchmark. Compare the current regional net quote and applicable taxes, not an unavailable EUR advertisement presented as a USD offer.

Choose Hetzner for self-hosted stacks, staging, batch and worker fleets, and production you are equipped to operate - it is also the natural home for the n8n-and-Coolify pattern. Choose Vercel or Netlify for frontend velocity, Render or Railway for managed simplicity, and DigitalOcean as the managed-service middle ground. Then price your real workload with traffic included - on that line item, the comparison usually ends where it started: at the bottom of the bill.