A dataset, not a changelog
CostMon has catalogued 30 cloud, AI, and SaaS price changes from 10 providers, announced between 2023 and 2026. Each entry carries one primary source that a person fetched and read.
Original research
The Cloud & AI Price Change Index
CostMon tracks every cloud and AI price change it can find a primary source for. This page turns that catalogue into findings, recomputed every time it ships.
30changes catalogued
10providers
12price cuts
5plain increases
2023–2026date range
Findings
What 30 catalogued price changes show
Cuts outnumber plain increases
Of the 30 changes CostMon has catalogued, 12 were price cuts, 7 restructured the pricing model, 5 raised a price outright, 3 added a new charge, and 3 added a free tier or allowance.
Cloud and AI move in different ways
Of the 13 cloud changes CostMon has catalogued, 3 added a new charge and 4 raised a price outright, against 4 cuts. Of the 11 AI changes, 5 cut a price, 5 restructured it, and 0 added a new charge. AI unit prices tend to fall while the billing model shifts. Cloud unit prices hold steadier, and new meters appear instead.
A price rise is rarely a price rise
Only 5 of the 30 changes CostMon has catalogued were a plain price increase. 10 more changed the bill a different way: a new charge, or a restructured pricing model.
The effective date is usually unstated
Only 9 of the 30 sources CostMon has catalogued state an effective date separate from the announcement date. Among those 9, the gap ran 0 to 337 days, median 60 (n=9). A missing effective date means the source does not print a separate date. It does not mean the provider gave no notice.
How many changes land each year
By announcement year, across the 30 changes CostMon has catalogued: 2023: 4, 2024: 6, 2025: 15, 2026: 5 (partial year). 2026 is not over yet, so its count is a partial-year total, not a fall in activity.
Figure 1
How each provider group moves
Counts of the 30 catalogued changes, split by provider group and by direction. The bar is decoration; the number in every cell is the real count.
| Provider group | Cut | Restructure | Increase | New charge | Free tier | Total |
|---|---|---|---|---|---|---|
| Cloud | 13 | |||||
| AI | 11 | |||||
| SaaS | 6 |
Figure 2
Price changes catalogued by year
Announcement year of every catalogued change. The current year is still open, so its count is a partial-year total, not a fall in activity.
| Year | Changes announced |
|---|---|
| 2023 | |
| 2024 | |
| 2025 | |
| 2026partial year |
Methodology
How this index is built
Every row starts from data/priceChanges.ts, the same catalogue that drives the price change log at /price-changes. One primary source, the provider's own blog post, What's New announcement, changelog, or pricing page, backs every entry. No third-party recaps, no aggregators.
Each entry gets one direction: cut, increase, new charge, restructure, or free tier. A change that both restructures a model and raises a bill for most users is filed as a restructure, since the billing mechanism is what actually changed. This index counts directions, providers, and dates, and reports the result. It adds no inference of its own about a provider's intent.
Every number on this page is computed from the catalogue at build time. There is no hand-typed count anywhere in this copy. Add or correct an entry in the catalogue, and the next build moves every figure that entry touches.
Limits
What this index is not
This is a curated catalogue, not an exhaustive record of every price change a provider ever shipped. It covers the providers CostMon monitors, and only the changes a person found a working, provider-owned source for. A figure on this page describes the catalogue, not the cloud or AI market as a whole.
A missing effective date is a fact about the source, not about the provider. When a source doesn't separately state when a change actually hits a bill, this index records that as "no stated effective date," not as "no notice given."
This index makes no promise about what any of this saves you. It reports what changed, and how often, so a reader can bring that fact into their own decision.
Cite this
Reference this page
CostMon. "The Cloud & AI Price Change Index." 2026-08-04. 30 price changes, 10 providers. https://costmon.com/price-change-index
What to do about it
A catalogue only helps if you act on it
Catch the next one before the invoice
Set a spend anomaly alert so a new charge or a repriced meter shows up the day it hits usage, not weeks later on a bill.
Model what a new rate does to your bill
Run your own token volumes against current model pricing before you move production traffic onto a repriced tier.
Read every entry behind this index
The full, dated log: what changed, who it hits, and what to do about it, one entry at a time.
FAQ
Common questions about this index
How is this different from the price change log at /price-changes?
The log at /price-changes lists each price change as its own dated entry, newest first, built to read and to subscribe to. This index takes the same catalogue and reports findings across all of it: how the corpus splits by direction, by provider group, and by year.
Why only a few dozen entries? Is that really enough to draw conclusions from?
The corpus is curated, not exhaustive: one primary, provider-owned source per entry, fetched and read before it ships. Every figure on this page states its own n. Read a small-n finding as a description of this catalogue, not a claim about the whole cloud and AI market.
What does "no stated effective date" mean?
It means the source CostMon read for that entry didn't print a separate date for when the change starts hitting bills. It does not mean the provider gave customers no notice at all. Some providers announce a change well ahead of the date printed on the source; this index only records what the source itself states.
How was each change assigned a direction: cut, increase, new charge, restructure, or free tier?
By what the source itself describes as changing. A rate that dropped is a cut. A previously-free thing that started billing is a new charge. A change to the pricing mechanism itself, tiers, units, or model, is a restructure, even where it also raises or lowers a typical bill.
Can I get the raw data?
Yes. The full catalogue is published as JSON at /price-changes.json and as CSV at /price-changes.csv, both licensed CC BY 4.0 with attribution to CostMon. Every row carries its own source URL.
A provider changed something you haven't catalogued yet. Can I tell you?
Yes. Send the announcement and its source link through the contact page. If it's a real, provider-sourced price change, it gets added to the catalogue behind both this index and the price change log.
A rate you looked up will change again.
Provider pricing pages change without notice. CostMon tracks the bill that pays for it.