Flowise is winding down — repo frozen 10 August, end-of-life 31 August

After two quiet nights, one real shutdown: Flowise, the open-source low-code builder for LLM apps and agents, is winding down on a dated schedule — code freeze already in effect, GitHub repo archived 10 August, end-of-life 31 August 2026. Self-hosted instances keep running, but the project goes unmaintained; fork it before the archival if you depend on it. Nearest on the board otherwise: Resend closes new.email on 7 August.

After two short nights, the calendar has one genuine new entry — and it is one a lot of developers will feel.

Flowise is winding down. The popular open-source, low-code builder for LLM chatbots, RAG pipelines, and agents has announced it is ending — both the hosted cloud and active development of the open-source project. The schedule is unusually specific: development froze on 29 July, the GitHub repository is archived on 10 August (read-only, issues and PRs locked, npm packages and Docker images deprecated), and the project reaches end-of-life on 31 August. Nothing switches off on those dates for a self-hosted instance — it keeps running, and the Apache-2.0 code stays forkable indefinitely — but from 10 August it is frozen: no fixes, no security patches, no upstream. There is no named successor and no automated migration. If your stack leans on Flowise, the cheap move is to fork the repository before 10 August, while the full history and issue tracker are still open; the harder deadline is the cloud, where 31 August is the point to have everything exported. Full detail, dates, and options are on the entry. Surfaced via discovery, then written from the maintainers’ own wind-down notice, not the discussion thread.

The fifty monitored sources produced no new product or service shutdowns tonight (the only changes were small historical-date corrections to already-past Elasticsearch versions). Every entry with a sunset date inside 30 days was re-checked against its primary source; all are unchanged.

Still counting down

Everything below is already on the calendar and was re-verified against its source tonight. The nearest lands in two days:

Resend new.email — 7 August, export your templates first; the tool folds into Resend’s main editor.
ChatGPT Atlas browser — 9 August, export your data first.
Rails 7.2 — 9 August, end of security support.
Relay — 15 August, the app shuts down.
Google Content API for Shopping — 18 August, end-of-life.
OpenAI Assistants API — 26 August, removed from the API.
New Relic drop-filter-rules API — 31 August, the API endpoint is removed — the same day Flowise reaches end-of-life.

Further out, OpenSSL 3.0 (7 September), the OpenAI Sora 2 video API (24 September) and the Gemini 2.5 model family (from 2 October) are on the calendar too. The full list, with countdowns, lives on the calendar.