Offrampcloud exit calculator

Free · no sign-up · nine destinations

What would your cloud bill cost on Hetzner?

Net of the engineer time to run it, on Hetzner or eight other providers. Drop in one month of an AWS, Google Cloud, Azure or Oracle Cloud cost export.

What would your cloud bill cost on Hetzner?

  • Your workload priced on Hetzner · every instance mapped to a real server, storage and traffic included
  • A net number · whole servers, standbys, backups and the hours to run it, with a range
  • Every service graded · Easy, Moderate or Hard, with a replacement and the one-off cost
Nothing leaves your browser. How that works

The export is read on your machine by DuckDB-WASM; there is no upload and no server-side parsing. We record that a report was run, nothing about its contents. If you ask for the PDF, we receive your email and company name and nothing else. Your last report is kept in this browser’s storage so you can come back to it; a copied link carries the report inside the link itself, so share it as you would the export. Hetzner list prices of 17 Oct 2026, linked to their source. No affiliate or referral relationship with any provider.

1 min
to a verdict

Run your numbers

One month of any supported cost export is enough.

Drop one month of a cost export here

CSV, CSV.gz or Parquet · AWS, Google Cloud, Azure or Oracle Cloud · several files are merged

Stays in this tab
or open a sample report

No export to hand? Start from your monthly bill.

Drag the slider: the figure comes from the closest of three modelled accounts, scaled to your bill and run through the same estimator as a real report.

You'd keep about

$95,043 a year

40% less than today on Hetzner, after 74 hours a month of engineer time.

Today
$20,000
Hetzner
$12,079
Modelled on a typical “scale-up on Kubernetes” mix, not your data, ±30%. Upload an export for the real number.

Nine destinations, nine different trade-offs

Pick one and every number on the page follows. Hetzner is the cheapest; the others trade price for managed services, locations or jurisdiction. Compare all nine.

How it works

  1. 1Export one month

    A cost export from AWS, Google Cloud, Azure or Oracle Cloud; FOCUS files work too.

  2. 2Every line is mapped

    Instances become Hetzner servers, storage becomes Hetzner Volumes and Hetzner Object Storage, traffic is set against the allowance.

  3. 3Engineer time is added

    Hours by effort grade and per server, at a rate you can change. The part most calculators leave out.

  4. 4You get a net number

    Every service graded Easy, Moderate or Hard with a replacement, on Hetzner list prices of 17 Oct 2026.

Questions we get asked

Who is this for?

Teams spending roughly five figures a month or more on AWS, Google Cloud or Azure, with a workload that is mostly servers, databases and storage, and someone who can own infrastructure. Also founders and finance leads who want a defensible number before the conversation with engineering.

Who is it not for?

Teams whose bill is mostly serverless, proprietary managed services or AI APIs; workloads that need multi-region failover by contract; and bills so small that an hour of engineer time outweighs the saving. The report will tell you if that is you.

What file do I upload?

One month of a cost export: an AWS Cost and Usage Report (CUR 2.0 or legacy, CSV or Parquet) or a Cost Explorer CSV, a Google Cloud BigQuery billing export saved as CSV, or an Azure Cost Management export. “Where do I get this file?” next to the upload box has the exact clicks for each.

Is my data uploaded?

No. The file is read inside this browser tab by DuckDB-WASM and never leaves it; you can watch the network tab while it runs. The only thing we ever receive is the address you type if you email yourself the link, plus anonymous counts of what was used.

How accurate is this?

Servers, storage and traffic are priced from your actual usage at list prices, so that part is as good as the price list. Managed services without a usage model (queues, search, analytics) are priced by a ratio from our service map and carry ±50%. Engineer time is an assumption you can edit. The report shows what share of the figure is priced from usage and gives a likely range rather than a single number. A Cost Explorer CSV has service totals only, so hosts are estimated from spend, roughly ±25%.

Can I move only part of it?

Yes, and that is often the right first step. Storage and egress-heavy workloads move easily and save the most per hour of effort; a managed database or a serverless stack can stay where it is. Filter the services table by grade to see what moves cleanly.

What about compliance and latency?

Every destination publishes GDPR documentation and most hold ISO 27001; SOC 2 reports and HIPAA agreements are rarer, so check that provider’s trust page before planning. On latency: for European users, moving from an EU hyperscaler region to Falkenstein, Gravelines, Paris or Amsterdam changes little; for US users choose a US location. A CDN in front stays as it is; the report prices it separately.

Why is Hetzner so much cheaper?

It sells servers, not a platform. It owns its data centres and hardware, runs a short catalogue in a handful of locations, includes traffic instead of billing per GB, and offers almost no managed services, so there is no managed-service margin in the price. You take on the work the hyperscaler was doing: patching, backups, failover, on-call. That is why this calculator adds engineer time on top and shows the net figure.

Ready when you are.

One month of a cost export is enough, and it never leaves this tab. No export to hand? Open a sample and change the assumptions to match your team.

Getting the export

Where do I get this file?

One month is enough. The file is read in this tab and never uploaded. Open this guide as a page

Cost and Usage Report (CUR 2.0)

~10 MIN, ONE TIME · THEN UP TO 24 H

Recommended: every server is mapped exactly

  1. Open Billing and Cost Management → Data Exports and choose Create. A FOCUS 1.0 export works as well as CUR 2.0; both are read to the same depth.
  2. Standard data export, table CUR 2.0. Leave “Include resource IDs” off (not used here, and it makes the file several times larger). Not FOCUS 1.0: this tool cannot read it yet.
  3. Format Parquet or CSV gzip, delivered to an S3 bucket. The first delivery takes up to 24 hours.
  4. Download one month. If the month arrived as several files, drop in the largest one.

Gives instance types and hours, so every host is priced from a real server match. Parquet is smaller and faster to parse.

Cost Explorer CSV

~60 SEC
  1. Open Cost Explorer. If it has never been opened, enabling it takes up to 24 hours.
  2. Granularity Monthly, group by Service, last 3 months. Under Advanced options choose Net amortized costs, so commitments are spread the way the full report does.
  3. Download CSV and drop it here.

Service totals only: servers are estimated from spend and every service is priced by ratio, so the figure is rougher. Good for a first look.

What the file needs to contain

Download a sample to compare

Column names are matched case-insensitively; extra columns are ignored.

  • line_item_product_code
  • line_item_usage_type
  • line_item_usage_amount
  • line_item_unblended_cost
  • line_item_usage_start_date
  • product_instance_type
  • line_item_line_item_type

Legacy CUR headers (lineItem/ProductCode …) work too; net and reservation effective-cost columns are used when present. A Cost Explorer CSV needs a Service column plus one column per month.

Not your login?

Send this to whoever owns the billing account. It says what to export and that nothing is uploaded.

CSV, CSV.gz and Parquet up to a few hundred MB parse in the browser; above that, use Parquet. UTF-16 files (Excel “Unicode text”) need saving as UTF-8 first.