Hetzner adjusted cloud prices in April 2026 and again on 15 June 2026. The increases were not uniform, and the conventional wisdom about which family to pick is now wrong in at least one important way.
Rather than repeat the announcement, we pulled the live catalogue from GET /server_types and sorted by value. These are the Nuremberg figures, gross, per month.
The measured table
| Type | Cores | RAM | Disk | €/month | € per GB RAM |
|---|---|---|---|---|---|
| cx23 | 2 | 4 GB | 40 GB | 5.49 | 1.37 |
| cax11 (Arm) | 2 | 4 GB | 40 GB | 5.99 | 1.50 |
| cx33 | 4 | 8 GB | 80 GB | 8.49 | 1.06 |
| cax21 (Arm) | 4 | 8 GB | 80 GB | 10.49 | 1.31 |
| cx43 | 8 | 16 GB | 160 GB | 15.99 | 1.00 |
| cpx22 | 2 | 4 GB | 80 GB | 19.49 | 4.87 |
| ccx13 | 2 | 8 GB | 80 GB | 42.99 | 5.37 |
Three things worth noticing
1. Arm is no longer the cheap option
The received wisdom has been that CAX (Ampere Arm) is the value play. It is not any more. cx33 gives you four cores and 8 GB for €8.49; cax21 gives you the same for €10.49. CX is cheaper at every comparable tier.
That is a genuinely useful conclusion, because it also removes a pile of work: if you were considering Arm you were also signing up for arm64 build compatibility across every dependency you use. You can skip it.
2. CPX and CCX have become very expensive
cpx22 costs 3.5× what cx23 costs for identical cores and RAM. ccx13 is nearly 8× cx23. Dedicated vCPU still makes sense if you genuinely need consistent, uncontended CPU — sustained compilation, video encoding, CI runners. For a development box that is idle most of the time and bursts occasionally, it is money on fire.
3. The SKU names changed
The CX line is now cx23 / cx33 / cx43 / cx53. If you have infrastructure code referencing cx22 or cx32, it will fail — those types no longer exist. We found this the direct way, by watching a provisioning call fail.
The broader lesson: do not hardcode prices
We inherited a pricing table from an older internal project. It had been written maybe four months earlier and was already wrong enough to materially understate costs. Nothing warned us; the numbers were simply stale.
If your margins depend on infrastructure cost, read it from the provider's API and cache it for a few hours. A hardcoded rate table does not fail loudly. It quietly reports a healthier business than you have.
What we picked
For reference, we run cx33 for single-developer boxes and cx43 where a team shares one machine. Both are CX, both in Germany, both chosen from the table above rather than from habit.