How SaaS prices change over time
No SaaS price change was recorded between Oct 13, 2026 and Oct 18, 2026 (6 observation date(s), 130 tracked plan and billing combinations). Caliper Press SaaS Price Change Watch: first value after 30 days of observations. Methodology · All software price records.
What counts as a price change
A price change is a new price of the same plan and billing period that appears in two successful checks in a row and differs from the last confirmed price by 1% or more. Only records with a measured value are compared. A price seen once, a move under 1% and a value that flips back within a week are kept in the plan's data file (data.json), not in this list; each listed change has the same ID as the row in the plan's history. A day without a recorded price neither creates nor hides a change.
Prices are stored in USD per month, but the comparison uses the price in the page's own currency. When a plan is priced in EUR or CHF, the USD figure moves with the exchange rate even if the provider changed nothing; such moves are never counted as price changes.
Two indices, two questions
Caliper Press SaaS Price Change Watch: the first 30-day value appears after 30 days of observations. Fraction of eligible plans with an observed source-price change over the stated window.
Caliper Press SaaS Price Inflation Watch: 100 (based on 115; ). Chained SaaS price level (first observed date = 100): each day's link is the geometric mean of page-price ratios for plans measured on both dates, in the page's own currency and billing period, so exchange-rate moves are excluded.
The first index answers "how many plans changed price in the window". The second answers "how much the price level of the same plans moved". They can disagree: a few large increases move the level without changing the share much, and many small changes can do the opposite.
The window index needs observations near both ends of the window, within one day. With history starting on Oct 13, 2026, the 30-day share appears after 30 days of observations and the 90-day share after 90. Until then it is shown as unknown, not as zero changes.
Recorded changes
Changes appear here once a new price is confirmed by two checks in a row. 123 plans currently have measurements on two or more dates, which is the minimum needed to detect a change.
Why observed changes are a lower bound
We read each pricing page once a day. A price that went up and back down between two reads is not seen. A provider that changes the plan structure (renames a plan, moves a feature to another tier) can change what a customer pays without changing any single published number. The plan record keeps the quote, making a changed structure visible in the text. A change to the plan structure is not counted as a price change unless the plan-bound number changes.
Some providers raise prices only for new customers and keep existing customers on old prices for a period. Our measurement is the public list price for a new customer; it says nothing about grandfathered contracts or negotiated discounts.
Using the history
Every plan page has a history of measured values with dates, and the section page lists changes from the last seven days. For a one-off comparison of billing periods, see monthly vs annual billing. All records are available as JSON and CSV next to each plan page; see how to use this data.