Fetching from the wire…
01
02
03
04
05
06
07
08
Public story · 2026-08-05 · high
Code freezes July 29, the repo archives August 10, and Flowise hasn't said how cloud customers export their data.
Why now: Flowise's code freeze took hold July 29, but the shutdown only spread once Hacker News picked up the sunset notice on August 4.
Flowise is shutting down, and the team says coding agents killed the need for its low-code builder, according to its sunset notice.
The core team leaves by August 31, and Flowise hasn't published a way for cloud customers to export their workflows or data before then. That leaves anyone running the tool in production, including the builders behind its 55,186 GitHub stars and 24,850 forks, to find their own way out.
Developers increasingly reach for coding agents like Claude Code and OpenAI's instead of visual builders. "The typical rigid workflow low code approach quickly hits the limit when it comes to complexity," per Flowise's sunset post.
The repo itself isn't disappearing. It stays online under its Apache-2.0 license so existing forks can keep running after the August 10 archive date.
n8n shipped version 2.34.0 in the same window, adding sub-agent tool approval propagation and closing an editor security hole. That's maintenance work from a team still building, not winding down. Aurora Mobile made the opposite bet explicit with LoopAgent, arguing in-house execution engines beat open-source orchestration outright.
Every low-code layer sitting between a user and a coding agent that can write the logic itself is now competing with a free upgrade. Flowise is the first big name to fold under that pressure.
Each link below shares sources, entities, or timing with this story.
The sunset notice is short and it doesn't hedge. Code freeze July 29. Repository archived August 10. Core team gone August 31. npm and Docker packages deprecated. Flowise has 55,186 stars and 24,850 forks under Apache-2.0, and the team wrote its own cause of death: developers...
Existing accounts keep working indefinitely, with no end-of-life date set, but AWS is pointing everyone toward AgentCore instead.
Simon Willison found 563 Rust filenames in the binary, tracing the swap to a June 17 update.
Boundary-Bench ran 12 agent harnesses through real firewall and filesystem locks, and costs climbed as much as 167 percent as those restrictions tightened.
Microsoft counted 444 packages poisoned in under four hours, and rotating stolen credentials in the wrong order trips a destructive handler.
Serverless compute, bug-fixing agents, retrieval models and moderation APIs each got a free replacement between August 4 and 6.
MindPattern daily
One email a day at 7 AM. Sources and a take on every story. Unsubscribe anytime.