Hacker News Board Hacker News, browsed like a classic message board
Live data from Hacker News

Flowise is shutting down

flowiseai.com

Post reply on HN
Print view View original

11–20 of 49 posts

Re: Flowise is shutting down

#13

Post by ashu1461 »

juancn wrote: post #7
ashu1461 wrote: post #6

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 av…

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 determi…

Correct and I think for non technical folks just creating pure ai agents is much easier than creating these workflows which can be harder to test as well.

Re: Flowise is shutting down

#14

Post by jaggederest »

llmgraph wrote: post #2

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 th…

[dead]

Re: Flowise is shutting down

#15

Post by maxdo »

as a person who spent years building flow.ai before flowise.ai, i'd say drag n drop ui was dead on arrival it works for a set of very hand picked cusomers , the rest were in a weird spot between people who can code( and think accordingly ) and don't.

Re: Flowise is shutting down

#16

Post by behnamoh »

It lacked so many features that n8n and Langflow offered, so I'm not sad about it, but it was the first visual agentic workflow builder that I tried and I wish they could make it somehow.

Re: Flowise is shutting down

#17

Post by itake »

ashu1461 wrote: post #6

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 av…

The problem that workflow engines solve (configurable code) is just better solve with agents just maintaining the code.

2 years ago (during the agentic workflow boom) prompting was annoying and tedious. Context was small, harnesses were weak. You needed to string along multiple complex prompts to get anything done.

Now, you can give an agent 50+ tasks and it will churn through them.

Re: Flowise is shutting down

#19

Post by taoh »

"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." is true when your primary users are developers. But no-code workflow is still valuable at scenarios where determinism is required.

I'm building an agentic compliance platform where every procedure needs to follow company policies and operated on the rigid plan, but the procedure itself is different for every customer. Coding agents could in principle generate the necessary workflow for each company, but they need to integrate with millions of other applications in the company, easy to review and modify.

We built our own workflow builder because every other existing solution is too complicated and doesn't meet compliance requirements. The workflow builder itself was coded by Claude, and it's working wonderfully.

So flowise's shutdown is because their business is targeting a specific sector which doesn't need it anymore, not because workflow builder itself is not useful.

Post reply on HN