One workload, every cloud
Build an estimate
Why this can be totalled across vendors at all
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
Monthly, at list
Google Cloudis cheaper for this workload
$41.57 a month against $502 on AWS — 91.7% less, over the 1 line every cloud priced.
South America · Spot · list prices, USD · per calendar month
- Google CloudCheapest$41.57/month
- AWS$502/month
The estimate, line by line
What each piece costs on each cloud, per month
This whole estimate lives in the URL — copy the address bar to share it, and nothing about it is stored on our side.
Totals compare clouds on the lines all of them publish a qualifying configuration for.
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.