All use cases

Control your infrastructure costs

Make your cloud spend work harder.

Understand estimated spend, find unused capacity and price your next infrastructure decision with Ankra.

Start freeRead the guide

For engineering leaders, finance partners and infrastructure owners.

Production cluster, a month, at list price

€463to€1,051

Hetzner to Azure: a 2.3x spread for the same 24 vCPU, 96 GB memory, 250 GB storage, 500 GB egress a month.

  1. Hetzner€463
  2. OVHcloud€611
  3. UpCloud€697
  4. DigitalOcean€722
  5. Scaleway€767
  6. Google Cloud€945
  7. AWS€1,039
  8. Azure€1,051
On-demand list prices checked September 2026, before VAT. Change the cluster

Price your cluster

Your cluster, priced across providers.

Change the cluster shape and inspect the bill. Price sources, their dates and the assumptions are included in the calculator.

Memory per vCPU
CPU
Cluster
Load balancers
1

The same cluster, a month, at list price

€463 on Hetzner to €1,051 on Azure

A 2.3x spread for identical vCPUs, memory, storage and traffic.

  • Worker nodes
  • Control plane
  • Load balancers
  • Block storage
  • Network

Hetzner k3s on your own servers, Germany and Finland

€463 a month
Worker nodes3 × CCX33 (8 vCPU, 32 GB, dedicated)
€415
Control plane3 × CX33 control plane servers
€25
Load balancers1 × LB11 load balancer
€7
Block storage250 GB of block storage volumes
€14
Network20 TB of traffic included per server, then €1 per TB
€0
  • Hetzner sells no managed Kubernetes, so a highly available control plane is three servers you pay for and somebody operates.
  • Arm CAX nodes are cheaper again and are left out here, because moving to them means every image in the cluster has to be multi-architecture.

Prices read 2026-09-14 from Hetzner Cloud pricing, the 15 June 2026 price adjustment.

On-demand list prices checked September 2026, before VAT, discounts, commitments or spot. Always-on month, European regions. USD and EUR convert at the ECB rate of 2026-09-15 (1 EUR = 1.1539 USD). Ankra charges the same per vCPU on every provider, so it never changes the order.

Why it matters

You need to know what the bill is buying.

Ankra connects the resources in your clusters to estimated costs by provider, cluster and workload. Inspect usage and unused capacity, then price a different configuration or provider. Estimates include their coverage and assumptions; compare the full operational needs before making a change.

How it works

A clearer view of spend. A next move you can review.

  1. 01

    Understand the spend

    Follow estimated costs across clusters, accounts and workloads, and inspect which resources are priced.

  2. 02

    Find room to improve

    Investigate idle capacity and unused resources. Inspect usage evidence before reviewing a recommendation.

  3. 03

    Price the next move

    Explore configuration changes and provider comparisons with published sources and explicit assumptions.

  4. 04

    Review and verify

    Consider availability, performance, storage, backups and migration effort. Review the proposed change and verify its effect.

Follow the product guide

What it runs on

The resources in your clusters, connected to estimated costs.

Related use cases

Open source alternatives, other clouds and the systems you already run.

Your next chapter

You built it. Let’s get it live.

Give your application a path to production. Give your team a simpler way to run it.

Start freeTry a playground

First 30 vCPU of platform usage included. Try it without a card; a card unlocks full access and €59 of credit.

From something you built to something people use.

  • Deploy from your repository
  • Run on infrastructure you choose
  • Operate with your team and agents