Skip to content

The End of Cheap Bare Metal: Hetzner's Price Realignment

Hetzner's massive June 2026 price hikes force developers to rethink legacy infrastructure, hardware segmentation, and multi-cloud abstraction.

Emeka Okafor
Emeka Okafor
Security Editor · Jun 21, 2026 · 5 min read
The End of Cheap Bare Metal: Hetzner's Price Realignment

For years, Hetzner was the quiet harbor for developers fleeing the eye-watering margins of AWS, GCP, and Azure. If you could manage your own Linux boxes, configure your own firewalls, and orchestrate your own backups, you got raw, high-performance compute at a fraction of hyperscaler costs. It was the ultimate weapon against the "cloud tax."

That era of ultra-cheap bare metal and VPS hosting has officially ended.

On June 15, 2026, Hetzner instituted a massive price adjustment across its entire cloud and dedicated server portfolio. With some virtual private server (VPS) tiers seeing monthly price hikes of up to 3.1x, the German hosting giant is forcing developers to re-evaluate their infrastructure economics. This is not a minor inflation adjustment; it is a structural realignment driven by hardware procurement realities and a deliberate push toward hardware-tier segmentation. For developers, the days of treating Hetzner as a default, un-managed "dumb pipe" of cheap compute are over.

The Anatomy of the June 2026 Hike

The price adjustment, which took effect on June 15, 2026, at 8:00 AM CEST, targets new orders and cloud instance rescales. While Hetzner's previous 2026 price adjustments (such as the April 1 round) were broad and hit existing customers, this June update surgically protects existing active contracts—at least for now.

However, any new deployment or modification of existing infrastructure will face a drastically different cost profile. The CCX (dedicated AMD vCPU) and CPX (shared AMD vCPU) instances bore the brunt of the increases in the Germany, Finland, and US regions:

  • CCX Tiers (Dedicated AMD vCPU): The entry-level CCX13 instance in Germany/Finland surged from €15.99 to €42.99 per month (a 2.69x increase). The high-end CCX63 jumped from €374.49 to €853.49 per month.
  • CPX Tiers (Shared AMD vCPU): The CPX22 instance rose from €7.99 to €19.49 per month (a 2.44x increase), while the CPX52 skyrocketed from €36.49 to €100.49 per month (a 2.75x increase).
  • CX and CAX Tiers (Shared Intel/AMD and Arm): In contrast, the shared Intel/AMD (CX) and Arm-based Ampere (CAX) instances saw much milder increases of roughly 1.3x to 1.4x. For example, the CX23 rose from €3.99 to €5.49, and the CAX11 rose from €4.49 to €5.99.
xychart-beta
    title "Hetzner Cloud Monthly Price Comparison (Germany/Finland)"
    x-axis [CX23, CAX11, CPX22, CCX13, CCX23]
    y-axis "Price in € (excl. VAT)" 0 --> 100
    bar [3.99, 4.49, 7.99, 15.99, 31.49]
    bar [5.49, 5.99, 19.49, 42.99, 85.99]

Standardization and the "Limited" Tier Strategy

Alongside the price hikes, Hetzner is standardizing its dedicated server lineup. Going forward, dedicated models will be based on clearly defined server types with supplementary product designations of "-1", "-2", and "-3". This eliminates individual RAM and storage configurations, simplifying Hetzner's provisioning pipeline but reducing the granular customization developers previously enjoyed.

To address the "massive increase in procurement costs" without completely alienating budget-sensitive users, Hetzner has introduced a new "-1-Ltd" (Limited) tier. These servers are built using hardware components sourced at lower costs—typically refurbished hardware, older models, or hardware freed up by customer cancellations.

This creates a stark, structural market split. For example, a standard AX102-1 dedicated server now costs €452.30/month (with a €224.00 setup fee). Meanwhile, the AX102-1-LTD is priced at €157.30/month (with a €39.00 setup fee).

This limited tier is not a temporary promotion; it is a permanent architectural tier. However, availability is highly volatile, dependent on cancellations and supply chain cycles, meaning developers cannot reliably use the LTD tier for rapid, predictable scaling.

The Developer Playbook: Mitigation and Architecture

For engineering teams running workloads on Hetzner, this price realignment requires immediate tactical and strategic shifts.

1. Beware the "Rescale Trap"

Because Hetzner is grandfathering in existing contracts, your current active servers are your most valuable assets. Do not touch them. In the cloud console, rescaling an existing instance triggers the new pricing model. If you have a legacy CCX13 instance running at €15.99, scaling it up to a CCX23 and then back down will permanently lock you into the new €42.99 rate. If you need temporary compute, spin up separate, short-lived instances rather than modifying your legacy baseline.

2. Leverage the Setup Fee Trade-off

While monthly recurring costs have increased, Hetzner has significantly reduced one-time setup fees for most dedicated servers. This shifts the economic equation. Previously, the high upfront setup fee penalized short-term bare-metal deployments. Now, with lower setup fees, bare metal becomes highly viable for short-term, high-intensity workloads (e.g., batch processing, CI/CD runners, or database migrations) where you spin up servers for a few weeks and tear them down.

3. Decouple via BYOC and Multi-Cloud Abstraction

If you must deploy new workloads and the 3x price hike destroys your unit economics, running bare-metal or VPS configurations directly via provider-specific scripts (like custom Terraform providers or Ansible playbooks tied to Hetzner's API) becomes a liability.

To mitigate this, teams are increasingly adopting Bring Your Own Cloud (BYOC) deployment platforms like Northflank. By utilizing a BYOC platform layer, your application configurations, networking, and deployment pipelines are decoupled from the underlying infrastructure provider. If Hetzner's pricing in a specific region (like the US or Germany) becomes unviable, you can point the control plane at alternative bare-metal providers, on-premises hardware, or alternative clouds (like Civo, CoreWeave, or managed Kubernetes) and redeploy without rewriting your entire deployment stack.

4. Pivot to Arm (CAX) and the Server Auction

If your stack is architecture-agnostic, migrating workloads from AMD-based CPX/CCX instances to Arm-based CAX instances is the easiest way to blunt the price increase. The CAX family only saw a ~30% increase, making Ampere-based Arm compute highly attractive. Additionally, for non-production workloads, developers should bypass the standardized lineup entirely and utilize Hetzner's Dutch-style Server Auction, which remains unaffected by the new pricing structure and features zero setup fees.

The Reality Check

Hetzner's price adjustment is a symptom of a broader macroeconomic reality: the hardware supply chain is expensive, and running data centers is no longer a race to the bottom. While Hetzner remains cheaper than the raw on-demand compute of the big three hyperscalers, the gap has closed significantly.

For developers, the lesson is clear. Relying on a single, low-cost provider as a structural shortcut to avoid architectural optimization is a fragile strategy. Whether through migrating to Arm, leveraging the Server Auction, or implementing BYOC abstraction layers, developers must now actively architect for infrastructure agility.

Sources & further reading

  1. Hetzner increased dedicated server prices 3-4x — news.ycombinator.com
  2. Details regarding the standardization and price adjustment of our server products effective 15 June 2026 — hetzner.com
  3. Hetzner cloud server price increases in 2026: full breakdown and alternatives | Blog — Northflank — northflank.com
  4. Hetzner Price Adjustment 15 June 2026 - Hetzner Docs — docs.hetzner.com
Emeka Okafor
Written by
Emeka Okafor · Security Editor

Emeka has spent over a decade tracking threat actors, vulnerability disclosures, and the evolving landscape of application security, bringing a sharp continent-spanning perspective to his reporting. He's known for translating dense CVE advisories into clear, actionable context that developers and security teams alike actually read.

Discussion 0

Join the discussion

Sign in or create an account to comment and vote.

No comments yet

Be the first to weigh in.

Related Reading