Cloud and AI prices
Know the day a price
quietly changes.
Cloud providers change their prices without telling anyone, and none of them publish what a price used to be. We read the price lists every day, keep a permanent record, and email you when something you use moves.
These are published list priceThe price a vendor publishes — not the price you actually pay.Everything on this site is list price. Your invoice may be lower because of committed-use discounts, an enterprise agreement, sustained-use discounts or credits. What list price tells you is the direction the vendor is moving, and it is the only figure that is public and comparable across customers.All terms →What this does not cover → — what the vendor advertises, not what your account is billed after discounts.
Most recent moves
Snapshot of 16 Aug 2026
- RepricedDomain Label Detection Operations
GCPIntegrationCloud Vision APIglobal
unchanged —— — /count
- RepricedNetwork Inter Zone Data Transfer Out in Sao Paulo
GCPComputeCompute Enginesouthamerica-east1
unchanged —— — /GiBy
- RepricedPrivate Offer Medium (5 year)
GCPIntegrationStackRox Security Platformglobal
unchanged —— — /mo
How it works
Three steps, and the middle one is the whole product.
- Step 1
We read the price lists, every day
Google, Amazon and the AI providers all publish their prices. Once a day we copy the whole list — every region, every size, every discount shape — and keep it.
- Step 2
We compare today against yesterday
Anything that moved is a change. We compare the whole price structure, not just the headline number, because the quiet changes are the ones that reach a bill first.
- Step 3
We tell the people it affects
Pick the things you actually use. You get an email when those move, and nothing at all when they do not. Everything else stays in the public record.
Start with something you use
Every price belongs to a service you already have a name for. Pick one and see what it has been doing.
By service
- Amazon Elastic Compute CloudAWS2,973,899 pricesno change
- Amazon Relational Database ServiceAWS206,762 pricesno change
- Compute EngineGCP32,243 pricesno change
- Amazon SageMakerAWS25,294 pricesno change
- Amazon ElastiCacheAWS22,420 pricesno change
- Cloud SQLGCP20,258 pricesno change
- Amazon Elastic Container Service for KubernetesAWS11,554 pricesno change
- AWS LambdaAWS5,962 pricesno change
One archive, several catalogues
The machinery — snapshot, diff, rank, compare, alert — does not care what is being priced. Cloud came first because its prices move most and its buyers notice least. Anything else with a published price list is the same problem.
What moved in the last 30 days
Ranked by list-price change. Up costs you money; down is a refund you have to notice to collect.
▲ Rising
Largest list-price increases, by money per unit
Nothing rose in this window.
▼ Falling
Largest list-price decreases, by money per unit
Nothing fell in this window.
Where the movement is
Mean net change by service, last 30 days
No service moved over the last 30 days.
Why this exists
When Google doubled egress rates, no single source owned the story.
Coverage scattered across small blogs, finance aggregators and a GitHub thread. There was no canonical page for a journalist to link, no history for a FinOps lead to cite, and no alert for the teams whose bills moved.
Current-price comparison sites are everywhere. Vantage, DoiT and others will all tell you what a machine type costs today. Not one of them can tell you what it cost in March — because nobody was keeping the archive.
Every day we snapshot is a day of history that cannot be backfilled. That is the entire moat, and it starts the day the collector runs.
Biggest of the latest moves
Largest percentage change among the 3 most recent
Questions people ask first
- What is a SKU?
- One priced line item — a specific thing, in a specific place, sold by a specific unit. “An n2-standard-4 core-hour in us-central1” is one SKUOne priced line item — a specific thing, in a specific region, sold by a specific unit.“An n2-standard-4 core-hour in us-central1” is one SKU. “An m5.xlarge instance hour in eu-west-1” is another. A single cloud has roughly a hundred thousand of them, which is why a price change can matter enormously and still go unannounced.All terms →. A single cloud has around a hundred thousand of them, which is how a price can change without anyone announcing it.
- Is this my price, or the published one?
- The published one. Everything here is list price, so your invoice may well be lower — committed-use discounts, an enterprise agreement and credits all sit on top. What list price tells you is which way the vendor is moving, and it is the only figure that is public and comparable between customers.
- Where does the data come from?
- Each vendor’s own public pricing API — Google’s Cloud Billing Catalog, the AWS Price List, and the published rate cards for AI models. No scraping, no estimates, and the raw response is kept so a number can always be traced back.
- How often does it update?
- Once a day. That cadence is the product: a snapshotOne complete copy of a vendor’s published price list, taken on one day.A job reads each vendor’s public pricing API once a day and archives the whole catalogue. The archive is the point: price history cannot be backfilled, so a day without a snapshot is a day gone for good.All terms →How a snapshot works → missed is a day of history that can never be recovered, because no vendor publishes what their prices used to be.
Tell me when my prices change.
Follow one price, a whole service, or a search you have saved. One email when something you follow moves, and nothing at all when it does not.