The price watch

When a vendor moves a price, this page says so

Every figure in our price index was read off a vendor's own page on one day and then frozen. Vendors do not freeze. So each morning a job re-reads the 43 vendor pricing pages behind the index — 42 tools, 68 published figures — and diffs what they say today against what we quoted. Anything that no longer matches is recorded below, dated, with the excerpt it was read from — and anything else on the web still citing the old figure goes into the correction queue beneath it.

3 open corrections · 0 third-party pages named · the queue

We diff the vendor's OWN published figures, the ones our briefs quote directly — never our annualised arithmetic, which no vendor page contains. The job reads HTML and declared JSON-LD, not JavaScript: where a rate card renders client-side and declares nothing, the run is recorded as "could not read its prices" rather than as a change. A withdrawal — "this figure is gone" — additionally requires the page to publish real rates in the same unit today: where it publishes none, we cannot tell a withdrawn price from a page we could not read, and we say the second. "We could not read it" and "they changed it" are different claims and this page keeps them apart. And where a vendor publishes no machine-readable rate in the unit we quote at all, that is not an unread page either: it is declared below, with every candidate page we fetched and the date, rather than left as a daily blank. Last completed pass: 2026-10-25. Runs every morning at 05:40 UTC.

3 open changes

3 records we withdrew

A monitor that quietly deletes its own mistakes is not auditable. When a record here turns out to be wrong, it comes off the list above and is named here instead, with the date and what we got wrong — and no correction is sent off the back of it.

10 rows we corrected by hand

The watch above can only see figures a vendor's page still publishes. It cannot see a figure that was never the vendor's in the first place — our own ×12 of a monthly rate, or a different product's plan price sitting in the same paragraph. Those are found by reading, and every one we find is rewritten against the vendor's live page and listed here: what the table printed before, what it prints now, the page that was read and the day it was read. The figure changes on every surface at once — the table, the CSV, the dataset descriptors and the tool page — because they all read the same corrected paragraph.

A row can appear twice. 11 rounds are listed below across 10 rows, because a figure can be wrong in more than one way and each pass is published separately rather than overwritten: Sentry Seer was corrected on 19 October for quoting the wrong line item, and again on 20 October because the rate was right but the unit was not — $40 is charged per active contributor (any user opening 2+ pull requests a month to a Seer-enabled repository, counted fresh each month), which is not a seat, so multiplying it by 20 seats stated a precision we do not have. Where we cannot state a figure in the unit we claim, the row says so and carries a band or a named ceiling instead of a number that looks firmer than it is. The site serves the newest round; the older ones stay here as the record.

3 open corrections

A moved price does not only make OUR row stale. The same figure is usually sitting in other people's pricing round-ups, and the morning the vendor moves it, every one of those pages is wrong too. So each change above opens an entry here naming the pages on record citing the old figure, the sentence each states it in, and the route we checked for reaching that publisher. Nothing is sent automatically: this is a dated work list with the vendor's own page attached as the evidence.

Observed live on 2026-10-17 by searching for each figure and reading the page back: 14 third-party pages across 5 figures. The citation rounds recorded earlier this month live in growth documents this build could not read, so nothing here is copied from them — every entry carries the URL, the sentence and the date it was read.

5 figures no rate card publishes

"Could not read its prices" is a statement about US, and on 19 October it was covering for three different things: a reader bug on our side, a page we were pointed at wrongly, and a vendor who simply does not publish the number our brief quotes. The first two are fixed in code. The third is not a failure to read anything — it is a fact about the vendor — so each one is declared here instead: the figure, every candidate rate card we fetched, what each one publishes instead, and the date it was read. These figures are no longer counted as unread pages, and they are not diffed, because there is nothing on any page to diff them against.

2 of them — Lorikeet, Sprig Analyze Agent — look like figures that may have gone stale rather than figures a vendor never published, so they are queued for a human to re-research. A declaration is not a licence to stop looking.

What is watched

One row per vendor page: 13 typed in by hand against the brief they came from, 30 derived automatically from the researched rows of the index, so a tool priced in this morning's issue is watched tomorrow morning. The figures column is what our own brief quotes from that page — the only numbers the watch compares, and the test suite fails if any of them has drifted from the sentence in the brief it was taken from.

What is not watched, and why

Not every researched row has a vendor figure to diff. Where our price comes from buyer reports or our own arithmetic on units the vendor states in prose, there is no published number on a rate card for a monitor to compare — and where no conventional rate-card URL answered at all, we say that rather than invent a page to watch. Both are named here instead of being quietly left out of the count.

How a change becomes a correction

A record here is evidence, not a rewrite. The brief behind it stays exactly as published until a human re-reads the vendor's page and rewrites it, because the paragraph carries caveats and arithmetic a diff cannot safely edit. What the record does is make the correction uncontestable: the vendor's page, the date, the old figure, the new one. Spotted something this missed? [email protected] — a dated vendor URL is all we need.

The table those figures live in is the price index, and the same rows as data are in the CSV. Both carry the figures as published; this page is where you find out which of them the vendor has since contradicted.