Flowise Alternatives After the Archive: 5 Options in 2026
The short answer
Flowise is gone; Langflow is the closest replacement, Dify the most complete platform, and n8n the best if your “agents” are really workflows. The Flowise team froze the code on July 29, 2026, archived the repository on August 13 and ended support on August 31, citing the shift toward coding agents. Your existing flows still run, but nothing will be patched.
Versions, licences and stars read from GitHub on November 19, 2026:
| Alternative | Licence · version | Stars | Closest Flowise feature | Self-host | Hosted price | Best for |
|---|---|---|---|---|---|---|
| Langflow | MIT · v1.13.3 (Nov 17, 2026) | ~157,000 | Visual flow builder for agents and RAG, Python components | ✅ | Self-host; DataStax/IBM-hosted options | Like-for-like migration |
| Dify | Dify Open Source License (Apache-2.0 + conditions) · 1.20.0 (Nov 18, 2026) | ~161,000 | Agent workflows, RAG knowledge bases, app publishing | ✅ (no multi-tenant without permission) | Professional $590/workspace/yr; Team $1,590/yr | All-in-one LLM apps |
| n8n | Sustainable Use License (fair-code) · 2.48.6 (Nov 19, 2026) | ~211,000 | AI agent nodes inside 400+ integrations | ✅ Community Edition | Starter €20/mo (2,500 executions), Pro €50/mo (10,000), annual | Agents that automate business systems |
| Sim | Apache-2.0 · v0.9.63 (Nov 19, 2026) | ~30,000 | Visual agent workflows, knowledge bases, tables | ✅ (Docker, Kubernetes) | Sim Cloud plans | Teams wanting an MCP-controllable workspace |
| Activepieces | MIT (community) + commercial EE · 0.93.0 (Nov 8, 2026) | ~25,600 | Flows, agents, tables, ~400 MCP servers | ✅ | Free (1,000 credits/mo), Plus $20/mo, Team $200/mo | Permissive, simpler automation |
1. Langflow — the closest replacement
Langflow is a drag-and-drop builder for agents, RAG pipelines and multi-agent flows, with components you can open and edit in Python and every flow exposed as an API. If you used Flowise to prototype chatflows and serve them behind an endpoint, Langflow maps most directly. The MIT licence means no restrictions on hosting it for customers. Flowise flows don’t import automatically; rebuild them, which usually takes minutes per flow.
2. Dify — the most complete platform
Dify bundles workflow building, agents, RAG knowledge bases with document processing, model management and app publishing in one workspace. It is the best choice when non-developers will build and maintain apps. Read the licence first: you may not run Dify as a multi-tenant service (one workspace per tenant) without written permission, and you may not remove its logo from the console. Dify Cloud Professional costs $590 per workspace per year with 5,000 message credits a month; Team costs $1,590.
3. n8n — when the agent is a workflow
n8n is an automation platform with AI agent, MCP and model nodes. If your Flowise agents mostly read a ticket, call two APIs and update a CRM, n8n’s integrations do more of the work. Cloud pricing counts workflow executions, not steps: Starter €20 a month for 2,500 executions, Pro €50 for 10,000 (billed annually). The self-hosted Community Edition is free, but the Sustainable Use License restricts it to internal business use.
4. Sim — the agent workspace
Sim combines visual workflows with tables, files and knowledge bases, and exposes the whole workspace over MCP, so Claude Code or Codex can build and run workflows for you. Apache-2.0, self-hostable with Docker or Kubernetes; SSO, SCIM and audit logs sit on the Enterprise plan.
5. Activepieces — permissive and simple
Activepieces’ community edition is MIT and includes flows, agents, tables and about 400 MCP servers. The cloud has a free plan with 1,000 credits a month, Plus at $20 and Team at $200 (25 users, SSO).
How to migrate in a week
- Export every chatflow and agentflow from Flowise and list the models, vector stores and tools each uses.
- Pick by the table above; most teams land on Langflow (builders) or n8n (automation).
- Rebuild the three most-used flows first and run them side by side with Flowise on real inputs.
- Move secrets into the new platform’s credential store, then rotate the keys Flowise held.
- Shut down the Flowise instance; an unpatched, internet-facing install with stored API keys is the real risk.
If you want to drop visual builders entirely, as Flowise’s own announcement suggests many teams are doing, see how to choose an AI agent framework.
Last verified: November 19, 2026.