There is something about agent workflow builders not gaining as much traction as they could have. Open AI also launched something in house and they are also shutting it down
OpenAI is deprecating Agent Builder. Existing users can continue using it during the transition window, and the product is scheduled to shut down on November 30, 2026. ChatKit remains available. See the deprecations page for the current timeline.
Disclosure up front: I build LLMGraph (llmgraph.ai), a hosted product in the same category, so I have a horse in this race.
The interesting part of the announcement is the stated reason: "developers are increasingly relying on new coding agents" and "rigid workflow low code approach quickly hits the limit when it comes to complexity." I think that's half right. Coding agents are clearly eating the developer end of this market. But a lot of Flowise usage was never developers; it was teams who wanted to design an LLM pipeline visually, hand it to a non-engineer to tweak prompts, and deploy it without owning infrastructure. That need didn't go away this week, and telling those users to fork and maintain a large TypeScript codebase themselves is not a real answer for them.
For anyone running Flowise in production, the practical decision is fork-and-maintain versus migrating somewhere maintained. Forking is a bigger commitment than it sounds: you own dependency updates, security patches, and model API churn indefinitely, and the contributor community that used to absorb that work is dispersing. Worth being honest with yourself about whether your team will actually do that maintenance before the first CVE forces the question.
Flowise was cool. I used to to help build an enterprise employee search tool with it a few years back. https://medium.com/better-programming/employee-search-with-o...
The fact is, there's not as much need for drag-n-drop low code tools anymore. At least I don't have much need.
There is something about agent workflow builders not gaining as much traction as they could have. Open AI also launched something in house and they are also shutting it down
https://developers.openai.com/api/docs/guides/agent-builder
OpenAI is deprecating Agent Builder. Existing users can continue using it during the transition window, and the product is scheduled to shut down on November 30, 2026. ChatKit remains available. See the deprecations page for the current timeline.
I think it's the cost (both tokens and initial setup and debugging the workflow).
It's really easy to spend a gazillion tokens by mistake and the resulting workflows are still probabilistic and open for abuse or failure.
Maybe it's too soon, we need more time to figure out what works and what doesn't.
We're still looking for the right balance for when a probabilistic solution (i.e AI) works and when we need a deterministic one (classic software).
Flowise was acquired by Workday in August 2025 [1].
At the time, they posted "Flowise isn’t going anywhere, we’re doubling down. In fact, we’re only just getting started!" [2]
I wonder if "keep the platform running for >= 1 year post-acquisition" was part of the terms! Ah well, another one for Our Incredible Journey [3]...
[1] https://newsroom.workday.com/2025-08-14-Workday-Acquires-Flo...
[2] https://www.linkedin.com/posts/flowiseai_were-thrilled-to-sh...
[3] https://ourincrediblejourney.tumblr.com/
https://github.com/flowiseai/flowise
Disclosure up front: I build LLMGraph (llmgraph.ai), a hosted product in the same category, so I have a horse in this race.
The interesting part of the announcement is the stated reason: "developers are increasingly relying on new coding agents" and "rigid workflow low code approach quickly hits the limit when it comes to complexity." I think that's half right. Coding agents are clearly eating the developer end of this market. But a lot of Flowise usage was never developers; it was teams who wanted to design an LLM pipeline visually, hand it to a non-engineer to tweak prompts, and deploy it without owning infrastructure. That need didn't go away this week, and telling those users to fork and maintain a large TypeScript codebase themselves is not a real answer for them.
For anyone running Flowise in production, the practical decision is fork-and-maintain versus migrating somewhere maintained. Forking is a bigger commitment than it sounds: you own dependency updates, security patches, and model API churn indefinitely, and the contributor community that used to absorb that work is dispersing. Worth being honest with yourself about whether your team will actually do that maintenance before the first CVE forces the question.