[ 28 vendors watched · 50 breaks published · 4 deadlines ahead ]
OpenAI retires models in a table on a docs page.Node.js changes behaviour inside a security release.A free tier ends on a pricing page.Anthropic deprecates a model in a line of its docs. Easy to miss. Suricate keeps watch for you and raises the alarm the moment a change concerns your stack.
An alert only when it matters. The rest of the time, we keep watch quietly.
Nothing yet tonight. Most nights, it stays that way.
Put to the test · real repository
We replayed the last 366 nights of vercel/ai-chatbot with its real stack and our engine. The test is reproducible (pnpm backtest): open the repository and check for yourself.
8 / 366
emails in 366 nights · 5 breaks · about one every seven weeksEvery square is a night, 6 Oct 2025 to 6 Oct 2026.
first sightingremindernothing to say
Not a claim about our speed — the base did not exist on these dates. Every entry it matched against was written and checked in October 2026, then replayed backwards. It shows the engine picking the right things out of a real stack, not how fast we would have got there.
An alert only when it matters. The rest of the time, we keep watch quietly.
Read-only GitHub access. We read your manifests and your configuration files. Never your code.
What others miss
OPENAI · ANTHROPICnothing to subscribe to
Both publish their retirements as rows on a documentation page. We looked for a feed on either and found none (checked 5 Oct 2026), so we read the pages themselves, every night, and diff them.
Nine from OpenAI and two from Anthropic, every one with a date.
NODE.JSinside a security release
A patch release you apply without reading, and in its own words:
This release changes behavior in several networking and security-sensitive subsystems to close the fixed vulnerabilities.Nobody reads the notes of a .17.
VERCEL · CLOUDFLAREnot a version at all
A model id that stops serving once the offer closes. A free plan where going over the daily quota starts failing queries. Nothing moves in your lockfile, so nothing that reads your lockfile can see it coming.
Pricing and limits are breaking changes with an invoice instead of a version number.
How it works
From connecting your repository to the alert in your inbox.
Once · two minutes
GitHub, read-only, no write access. We read your manifests and your configuration files. Never your code. Then you tick the services a manifest can’t show.
manifests + config filessrc/ never opened
Every night · then every day
Changelogs, docs, release notes, and the commits nobody announces. About 50 new items on a typical night — and years of history at once when a vendor joins the list.
28 vendorsabout 50 a night
At the source, before anything is published: several agents cross-check every alert.
1 concerns you✓ checked at the source
It tells you what changes, what breaks for you and what to do, with the source. When it concerns a dependency’s version, it also shows where that dependency sits in your repo and the version we read there. A real one, published and still ahead:
06:001 email · or none
Subject: Clerk for Next.js: Clerk phases out CBC cipher suites Jan 18
Clerk for Next.js · deprecation ○ info
Effective 18 Jan 2027
What changes
Starting January 18, 2027, Clerk will stop supporting CBC-mode SSL/TLS cipher suites on Clerk-managed subdomains such as the Frontend API and Account Portal. The rollout happens gradually as certificates are renewed, since Clerk certificates are valid for 90 days, so all affected subdomains will be moved over within a few months of the start date.
What breaks for you
This only affects clients that cannot negotiate modern cipher suites.
What to do
Most applications will not be affected, since modern browsers, mobile OSes, and server runtimes already prefer AEAD ciphers.
Read the announcement (verified 29 Sept 2026)
We keep watch every night, and write only when something concerns you.
Then nothing until the next one. 8 emails in 366 nights on a real repository.
What lands in your inbox
Two here, because a month with two is the one worth drawing. On the repository we replayed it was 8 emails in 366 nights — most months, none.
What we don’t do
Manifests and configuration files only — the exact scope of the GitHub permission we ask for.
28 vendors today, selected one by one and listed with their freshness on the status page. If yours is not there, we will not see it. Missing yours? Suggest it from your account and we’ll look at adding it.
Our agents check each change against its source, and the email links to it so you can check too.
The replay above matched against 49 announcements, and only the ones readable from a manifest could fire: major versions, no cut-off date. A model being retired or a plan discontinued needs someone signed in to say they use it — and those are the ones carrying a date.
No replay of your history. Weeks without an alert? Good sign: nothing concerned you. And to see that the watch holds, it’s all public on /status.
Tonight
An alert only when it matters
A suricate keeps watch over your first repository, for free.