Cloud Pricing Reference
3 free tools · no login · nothing uploaded
Two maintained datasets rather than calculators. Both exist because the answer changes over time, which is exactly the kind of question a search engine or a chatbot answers badly.
The SKU dictionary translates Google Cloud billing line items into plain English. A price list will tell you that "Network Internet Egress from Americas to China" costs a certain amount per gibibyte; it will not tell you what in your architecture triggers that charge, what typical magnitude looks like, or which of the three plausible fixes actually applies. That editorial layer is the useful part, and it is the part nobody else has built for Google Cloud.
The price change tracker is the other half: a weekly, permalinked record of what moved in AWS, Google Cloud and Azure pricing, with tier-boundary changes and retirements separated from the noise of new SKUs being added. Providers announce increases rarely and quietly, and a rate that changed three months ago is still news to most teams.
Both are rebuilt from vendor APIs rather than hand-maintained, and both state when they were last synced. A page that has not been refreshed says so instead of showing a stale number, because a reference that quietly goes out of date is worse than one that admits it.
The readiness assessment sits here too. It is the one item on this site whose result is not instant — it asks for an email and sends the score back rather than showing it on screen — and it is labelled that way everywhere it appears.
3 tools in reference data
GCP Billing SKU Dictionary
What that mystery line on your Google Cloud bill actually is.
Search Google Cloud billing SKUs in plain English: what triggers the charge, what unit it bills in, what it costs by region, and how to make it smaller. The price list tells you the rate; this tells you the cause.
Cloud Pricing Change Tracker
What changed in AWS, GCP, and Azure pricing — before your bill tells you.
A weekly, permalinked digest of SKU-level price changes across the three major clouds, with tier-boundary moves and retirements called out separately from the noise of new SKUs. Subscribe by RSS.
Cloud & AI Cost Readiness Assessment
Score your FinOps practice against the four framework domains.
A 25-question self-assessment across Understand, Quantify, Optimize and Manage — the FinOps Framework's own domains — scoring each capability from "not in place" to "automated and measured". Results are emailed to you.
Other categories
Looking a charge up, or never having to.
Finitizer maps every line on your bill to the workload that caused it, so the question stops being "what is this SKU" and becomes "which service should stop doing that". It also tracks the price changes that affect your specific usage, not all of them.