Flowise announced on July 29 that it's winding down. The GitHub repo gets archived on August 10, npm packages and Docker images are being deprecated, and August 31 is end of life. The code stays Apache 2.0, and the team's guidance is to fork and maintain it yourself.
If you're running Flowise chatflows in production, that leaves you with two real options: become the maintainer of your own fork (security patches, dependency upgrades, model API churn, all of it) or move to a platform that's actively maintained.
The stated reason, and why I read it differently
The Flowise team's stated reason for shutting down is that "rigid workflow low code approach quickly hits the limit when it comes to complexity." I'd frame it differently: visual workflow builders aren't the problem. Abandoned ones are. Most teams using a tool like Flowise chose it precisely because they don't want to hand-maintain orchestration code. That need didn't go away last week.
What migration actually looks like
I build LLMGraph, a hosted visual LLM workflow builder, and the concepts map over directly:
- Chatflows map to Graphs. Same node-and-edge mental model: models, prompts, logic, and data sources wired together on a canvas.
- Deployment is built in. A finished graph deploys as a public invoke API or an embeddable chat widget in one click. No Docker, no reverse proxy, no self-hosting.
- Hosted and maintained. Model providers, infra, and security patches are our problem, not yours.
Before August 31
If you want to move a Flowise setup over before end of life, every LLMGraph tier starts with a 14-day trial, and I'm happy to personally help port your chatflows. Email founders@llmgraph.ai or ping me in the comments.
Top comments (0)