Flowise is archived. Which alternative should you move to?

Flowise is archived, so if you run it today, plan a move. For a visual, open source builder that feels closest to Flowise, look at Langflow. For chatbots and retrieval over your documents with a polished interface, look at Dify. For agents that mostly connect apps, move to n8n, and if nobody on your team codes, try a hosted no-code builder such as VectorShift.

The team behind Flowise announced the wind-down in The Future of Flowise, and the FlowiseAI/Flowise repository was archived on 13 Aug 2026 and is now read-only. The code stays available under Apache 2.0, so your self-hosted instance keeps running, and it will receive no more fixes. I first published this page in January 2025 as a list of no-code alternatives, when people compared tools for features. Today the question is where to move, so this update matches each alternative to the kind of project you built.

First, secure what you are running

An archived project gets no security patches. Until you move, keep your Flowise instance behind a login and off the public internet where you can, rotate the API keys and credentials stored in it, and check the repository's security advisories for anything that affects your version. If your chatbot is embedded on a public site, put moving it at the top of the list.

The alternatives, matched to your project

Langflow: the closest match

Langflow is an open source visual builder for AI flows and agents, released under the MIT licence. You connect components on a canvas, as you did in Flowise, and publish a flow as an API. It releases often: the Langflow blog lists several releases in 2026.

Choose it when you want the same way of working and to keep self-hosting.

Dify: chatbots and knowledge bases

Dify is an open source platform for AI applications with a visual workflow editor, a retrieval pipeline, agent features and model management. It is strong for the most common Flowise use, a chatbot over company documents.

Read its licence before you deploy. It is a modified Apache 2.0 with added conditions, including a limit on running Dify as a multi-tenant service without written permission. For a single company's internal use, that is usually fine.

n8n: when the agent mostly connects apps

n8n is a workflow automation platform with AI agent steps and a large integration library. If your Flowise flow spent most of its nodes calling APIs and moving data, n8n will feel more natural. It is self-hostable under its own Sustainable Use License.

Hosted no-code builders: when nobody wants to run servers

If your team never wanted to maintain a server, a hosted builder removes that job. VectorShift builds AI pipelines, chatbots and search over your data with drag and drop. PromptOwl is a no-code agent platform that supports several AI models and adds prompt versioning and team collaboration. Rentprompts offers a visual editor for AI apps and agents.

Letta and Relevance AI: special cases

If your Flowise assistant needed memory across conversations, Letta is built around exactly that, with an open source framework under Apache 2.0. If you were building teams of agents for sales, support or operations, Relevance AI lets you build and monitor several agents in one visual platform.

A migration plan for the next month

1. List every flow in production, who uses it, and which credentials and documents it touches.
2. Export each flow from Flowise and keep the files with your notes. Its prompts and settings are what you will rebuild.
3. Pick one alternative using the table above, and rebuild your simplest flow first.
4. Write ten test questions with known good answers, and compare the old and new flows on them.
5. Switch traffic flow by flow, keeping the old one available for a week as a fallback.
6. Shut down the Flowise instance and revoke its credentials once the last flow has moved.

Rebuilding by hand sounds slow, so plan about a day for each flow and start with the simplest. It is also a good moment to delete the flows nobody uses.

Questions people ask

Is Flowise shut down?

The open source project is archived and read-only since 13 Aug 2026, with no further releases. The code remains under Apache 2.0, so existing installs keep running and anyone can fork it. Check the team's announcement for the status of Flowise Cloud.

What is the best open source alternative to Flowise?

Langflow is the closest in how it works, a visual builder you can self-host under the MIT licence. Dify is the strongest choice for chatbots and knowledge bases, with a licence that adds conditions to Apache 2.0.

Can I import Flowise flows into another tool?

Each tool uses its own format, so plan to rebuild flows rather than import them. Keep the exported Flowise files as a reference for the prompts, models and settings you used.

The AI Agents framework and No-code builder categories on AI Agents Live list more builders with their reviews.