Flowise Shuts Down as AI Coding Agents Take Over
Flowise Is Shutting Down
Flowise, a popular low-code platform for building AI applications, is winding down operations. The team cites a major shift in developer behavior: as AI models become more capable, developers increasingly rely on coding agents like Claude Code and OpenClaw for complex tasks, hitting the limits of rigid low-code workflows. The company will freeze features, archive the repository, and end support by August 31, 2026. The Apache 2.0-licensed code remains available for forking.
The typical rigid workflow low code approach quickly hits the limit when it comes to complexity.
- ashu1461
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.
- fsuts
>Over the last few months, we've noticed a significant shift in how people build. As AI models become more capable at reasoning, we've noticed that developers are increasingly relying on new coding agents such as Claude Code/OpenClaw to handle complex tasks. The typical rigid workflow low code approach quickly hits the limit when it comes to complexity.
Their front page says ‘design agents visually’ so their target market was less skilled devs/non devs.
So not sure why they are giving the reason if closer as cli related when low code and cli are different markets.
- jbdamask
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.
- mkeeter
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...
- resiros
Flowise was acquired by workday, so I'd take this with a grain of salt.
However, I agree with the reasoning. I don't see a future for visual workflow builders. They are used to define plumbings that can be defined by a 50 line python script.
A non-technical user does not need to draw this workflow. They can just ask an agent to write that code for them, to debug it, to visualize it. All workflow builders now have an AI chat where you ask the agent to build the flow for you. Why not skip the flow part?
I'm pretty biased though since that's the thesis behind what I am building.