Skip to content
Beta

Cost Ticker is under development. Features are incomplete and prices shown here may be inaccurate, stale or missing — check any figure against the vendor before you rely on it. Tell us what you need it to do.

Beta
Get alerts
Cloud

One workload, every cloud

Build an estimate

Add the pieces of a workload, say how much of each you use in a month, and see what the whole thing costs on each cloud side by side — not one at a time. Every line is priced on a unit that means the same to each of them, and every figure links the SKUs it was built from.
Why this can be totalled across vendors at all
Because nothing is added up until it has been normalised. Google prices a machine's cores and its memory separately and AWS prices the whole instance, so a 4 vCPU · 16 GB line is composed from whatever each vendor actually sells and expressed as one rate per hour. Where both already publish the same unit — a gigabyte-month of object storage — the line is direct. Line items exist only where such a unit genuinely exists, which is why the picker offers seven things and not the whole catalogue. For anything outside them, the cost impact page prices your own meters without making a cross-vendor claim.

Applies to every line — a committed rate is never totalled against an on-demand one.

Azure is not in this estimate. Its prices are in the archive and on every other page of this site, but no line item here has an Azure side yet: a comparison needs each cloud's meters matched to the same stated configuration, and that work is not finished for this one. Absent from the table, not priced at zero.

Add a line

Quantities are per month, in each line's own unit — the South America region group on spot pricing

Which cloud is cheaper for a machine of this size?

hours a month

Leave blank for one running all month (730 h).

Nothing in the estimate yet

Add a line above, or start from an ordinary small production footprint — two general-purpose machines, a managed Postgres instance, a terabyte of object storage and a terabyte of egress — and change it from there.
Try a sample workload

These are list prices

Published rates, exactly as each cloud advertises them. Enterprise agreements, committed-spend discounts, credits and free tiers are negotiated privately and appear in no public catalogue, so a real invoice will differ — usually downward, and by different amounts on different clouds.

What is not in the total

Only the lines you added. Support plans, inter-zone traffic, load balancers, IP addresses, snapshots and the long tail of small meters a real bill carries are not inferred on your behalf — a total that quietly invented line items would be a worse number than one that is honestly incomplete.

It changes when they reprice

This is priced from today's snapshot. The archive knows what each of these lines cost before, and will email you the day one of them moves — which is the difference between an estimate and a forecast.