Regions
Akua-managed machines currently provision in Falkenstein (
fsn1). The
other locations are available when you use your own Hetzner Cloud account.
Instance types
The tables show the instance types each plan is eligible to request. Hetzner capacity changes, so a listed type may be temporarily unavailable when you create a machine.Free tier
These types are available to the account’s one-time Akua-managed VM trial — not a renewable free-tier slot.Pro tier
Pro-tier managed machines are eligible to request all Hetzner Cloud server types, including:ARM64 types (
cax*) offer the best price-to-performance ratio. Use them unless your workloads require x86.BYOM (bring your own cloud key)
Your Hetzner Cloud account can request any server type, with no Akua plan restriction.Billing model
Hetzner bills per hour, rounded up. Servers are billed as long as they exist, even when powered off. Akua’s machine lifecycle model uses snapshots and server deletion for suspend flows rather than simply stopping the server.Snapshot pricing
Hetzner charges €0.01 per GB per month for snapshots. Snapshots are compressed; you pay for actual used space, not total disk capacity.How Akua provisions machines on Hetzner
- Akua creates a server via the Hetzner Cloud API with a cloud-init script.
- The cloud-init script installs Kubernetes, configures the worker, and joins your cluster.
- The machine appears in your dashboard within approximately 2 minutes.
- Akua monitors the machine and handles its full lifecycle: scaling, suspend, and deletion.
Add your own Hetzner account (BYOM)
1
Create an API token
In the Hetzner Cloud Console, create an API token with Read and Write permissions.
2
Add the credential in Akua
Go to Compute in the Akua dashboard, click Add Credential, and paste your token. Akua validates it immediately.
3
Create a compute config
Click Create Config, select your credential, and choose a region.
Your API token is stored securely in an external secrets manager. Akua re-validates all tokens hourly and notifies you if a token becomes invalid (for example, if it was revoked or expired in the Hetzner Console).
Suspend and IP volatility
When you suspend a machine on Hetzner, Akua snapshots the disk and deletes the cloud server. On resume, a brand-new server is provisioned from the snapshot. This means the public IP address changes on every resume. Hetzner has no stop state that preserves the IP and instance. If you need a stable public IP across suspend and resume cycles, use a floating IP, short-TTL DNS, or a load balancer in front of the machine.Limitations
- No Hetzner Volume attachment on suspend and resume: Hetzner Volumes use server IDs for attachment. If you use Hetzner CSI Volumes (not local storage or LINSTOR), additional steps may be needed on resume. Local storage and LINSTOR volumes work without issues.
- Powered-off servers still bill: Unlike AWS and GCP, stopping a Hetzner server does not reduce costs. Use Akua’s suspend feature instead.
- IPv6 only on some instances: The most affordable Hetzner plans may include IPv6 only. Akua handles this through the cluster’s internal networking.
Related topics
Machine lifecycle
Full machine lifecycle including provisioning, suspension, and deletion.
Compute overview
Akua-managed machines, BYOM keys, and manual worker paths.
Plans and pricing
Compare plans and understand instance type access.