A quiet night, and a lesson in what we will and will not print: an InstantDB shutdown notice is circulating, but only in a forwarded email — so it is not on the board yet

Nothing new was confirmed to the calendar tonight — 56 monitored sources fetched clean and the discovery scan turned up mostly noise. The one developer-facing signal worth naming is a report that InstantDB is sunsetting Instant Cloud, with cloud apps said to shut down on 31 August 2027. We can find no official announcement — the only source is a user's forwarded email quoted on Hacker News — so it does not get an entry tonight. That is the rule, not an omission: no official source, no claim. Every sub-30-day entry was re-checked against its primary source; all eleven hold.

Quiet feeds tonight — 56 monitored sources fetched clean, and the discovery scan surfaced nothing that clears our bar for a new entry. So instead of padding the board, here is a look at the bar itself.

On our radar, not on the board yet: InstantDB

A report is circulating that InstantDB — the open-source, real-time database (“the backend for AI-coded apps”) — is winding down its hosted Instant Cloud service. A user posted to Hacker News a shutdown email they received: new signups closing soon, a recommendation to migrate off Instant Cloud within twelve months, all cloud apps shutting down on 31 August 2027, and backups kept for a further year until 31 August 2028. The email points affected users to Instant’s self-hosting and migration guides, and notes the project stays open source.

If accurate, this is squarely the kind of sunset this site exists to record. But it does not get an entry tonight, and it is worth saying why plainly, because the discipline is the product:

The only source is a user’s forwarded email, quoted secondhand. The poster’s own words: “Nothing on their website.”
We checked. There is no shutdown notice on instantdb.com or its about page, no announcement blog post we can find, and the GitHub repository is still shipping normal commits with no sunset banner.

Our first rule is that every claim links to an official primary source, and we never infer or launder a date from a secondhand copy. A private email forwarded by one recipient is a tip, not a source. So this goes on our watch list, not the calendar. The moment Instant publishes something official — a blog post, a docs banner, a status-page note — we will add a fully sourced entry with the dates verified against it. Until then, treat the 31 August 2027 figure as unconfirmed.

That is the whole promise here: we would rather be a day late with a real source than first with a forwarded screenshot.

Still counting down

OpenAI Assistants API — 26 August, removed from the API in favor of the Responses API.
Convictional — 27 August, the B2B trade platform’s access ends.
OCI DevOps OL7 build runners — 28 August.
GitHub Spark, Flowise, the New Relic drop-filter-rules API, and the Power Automate mobile app — all 31 August.

Further out: OpenSSL 3.0 (7 September), the GitHub Copilot MAI-Code-1-Flash deprecation (10 September), the Relay paid shutdown and the Microsoft Sentinel SAP agent retirement (both 14 September, both re-confirmed against Microsoft’s release-communications API tonight), the OpenAI Sora 2 video API (24 September), the Azure Automation runtime cut-off (30 September), the EWS in Exchange Online block (1 October), the Cloudflare Workers KV legacy API (15 October), the Azure Databricks Runtime 10.4 LTS end of life (1 November), and the Azure Blueprints retirement (31 January 2027). The full board, with countdowns, is on the calendar.

Want this in your own repo instead of your inbox? The lastcall CLI — npx lastcall.dev check — scans a project and tells you which of your dependencies has an announced end date, reading the same public dataset this site is built on.