FlowiseNot rated: discontinuedDiscontinued
n8n9.5/10From $24/moFlowise vs n8n
Flowise was discontinued in 2026, so this is no longer a fair fight. Here is what each was built for, and where Flowise users can go.
Flowise is discontinued. End of life on August 31, 2026, repository archived. It is shown here for reference and is not scored.
Verdict in 30 seconds
Flowise is discontinued and not scored. n8n scores 9.5/10 on our formula.
Flowise reached end of life on August 31, 2026: its repository is archived and receives no fixes. We do not recommend starting on it.
n8n is maintained, has an AI Agent node inside a full automation tool, and offers a self-hosted Community Edition; n8n Cloud starts at $24 a month.
If you loved Flowise for being a free, open-source builder for agents and RAG, Langflow (MIT) is closer in spirit than n8n.
Flowise is for
- Existing Flowise instances with a developer who can maintain a fork
- Internal prototypes that are not exposed to the internet
n8n is for
- New projects
- Agents that must connect to business apps
- Teams that want updates and security fixes
Flowise vs n8n: side by side
Same rows as every comparison on this site. Prices checked Nov 15, 2026.
| Compared | ||
|---|---|---|
| Type | Low-code, open source (archived) | Low-code, source-available |
| Entry price | Discontinued | From $24/mo |
| Billed in | Predictions (cloud plans) | Workflow executions |
| Free plan or trial | Free self-hosted edition | Free self-hosted edition |
| Integrations announced | Not stated | 500+ |
| AI models | 100+ LLMs, embeddings and vector databases | Connect any model with your own key; Cloud plans also include AI models without API keys |
| Agents or workflows | Agents and workflows | Agents and workflows |
| Knowledge base / memory | Yes | Yes |
| Human approval | Yes | Yes |
| Self-hosting | Yes | Yes |
| API / MCP | API, SDK and embedded chat widget | Public API, CLI, webhooks, MCP server trigger |
| Built for | Teams with a running Flowise instance that need a migration plan | Technical founders and ops people who want control and a low bill at volume |
| Official page | Read the notice at Flowise | Check price at n8n |
Is Flowise still an option against n8n?
Not for a new project. On July 29, 2026 the Flowise team announced a code freeze; the notice sets the repository archive for August 10 and the end of life for August 31, 2026. GitHub shows the repository as archived on August 13. The Apache 2.0 code remains available and can be forked, but nobody upstream will patch it.

The full story, and what it means for a running instance, is in our Flowise review. The rest of this page compares what Flowise was with what n8n is, so you can judge how much of your setup carries over.
What was each tool built for?
Flowise was a builder for LLM applications: you connected models, prompts, vector stores and tools on a canvas to make a chatbot or a multi-agent system, then called it through an API or an embedded chat widget. Its two modes were Chatflow (single agents and RAG) and Agentflow (multi-agent systems).
n8n is a workflow automation tool that added agents. It connects 500+ business apps, runs on triggers and schedules, and lets you place an AI Agent node wherever a step needs judgment. If your Flowise project was "a chatbot over our documents", n8n is a wider tool than you need. If it was "an agent that must also update the CRM and send the email", n8n is the natural next step.

How do the prices compare?
n8n plans9.5/10From $24/mo · checked November 15, 2026 | Monthly billing | Annual billing, per month | Included | Notes |
|---|---|---|---|---|
| Starter (Cloud) | $24 | $20 | 2,500 workflow executions a month | 1 shared project, 5 concurrent executions, agents, MCP and AI nodes, forum support |
| Pro (Cloud) | $60 | $50 | 10,000 workflow executions a month | 3 shared projects, up to 50 concurrent executions, admin roles, workflow history |
| Business (self-hosted only) | $960 | $800 | 40,000 workflow executions a month | SSO and LDAP, multiple environments, queue mode, Git version control |
| Enterprise | On request | On request | Custom executions | Contact sales; hosted by n8n or self-hosted |
Flowise's homepage still displayed its old cloud plans on November 15, 2026 (Free, Starter at $35 a month, Pro at $65 a month) under the sunset banner. We would not subscribe to them. n8n Cloud is $24 a month for 2,500 executions on Starter and $60 for 10,000 on Pro, billed monthly, with a 1,000-execution trial. Self-hosting the n8n Community Edition has no license fee.
Open source: is n8n a like-for-like replacement?
Not on the license. Flowise was Apache 2.0, a standard open-source license. n8n uses its own Sustainable Use License, which it calls fair-code: you can self-host and modify it for internal business purposes, but you cannot offer it to others as a paid service. If you built a product on top of Flowise and sell it, read n8n's license before you migrate.
For a permissive license, look at Langflow (MIT) or the Activepieces Community Edition. Dify is source-available with its own conditions. We compare them in open source AI agents you can self-host.
AI features side by side
Flowise listed support for 100+ LLMs, embeddings and vector databases, human-in-the-loop review and execution traces. n8n lets you connect any model with your own key, lists human approval for tool calls on every Cloud plan, supports MCP as client and server, and lets you inspect each run step by step. Retrieval over your documents is built with nodes instead of a ready-made RAG template, which takes more assembly.
Video: “Build your first workflow”, from the n8n channel on YouTube.
How to move from Flowise to n8n
- Export every Flowise flow as JSON and store the files somewhere safe.
- List the model, vector store and credentials each flow uses.
- Rebuild the simplest flow in n8n first: an AI Agent node, a chat trigger, your model and your tools.
- Compare answers from both on the same real questions before you switch.
- Shut the Flowise instance off from the internet once the new flow is live.
There is no importer. Expect to rebuild, not convert.
Which one should you choose?
- New project: n8n, or another maintained builder.
- A chatbot over documents, permissive license required: Langflow.
- An agent that acts in business apps: n8n.
- A running Flowise instance: keep it internal, and plan the migration.
Keep reading
- Flowise review: plans, limits and the catch.
- n8n review: plans, limits and the catch.
- n8n alternatives: 7 tools to consider, and when to stay
- n8n pricing: Cloud plans, executions and the free self-hosted edition
- Best AI automation tools
- n8n vs Zapier
- Make vs Zapier
- n8n vs Make
- Add a third tool in the comparison tool
Flowise vs n8n: FAQ
Is Flowise discontinued?
Yes. According to the official notice, the code was frozen on July 29, 2026 and the project reached end of life on August 31, 2026. The GitHub repository is archived.
Is n8n a good Flowise alternative?
Yes if your agents need to work with business apps and you want a maintained, self-hostable tool. For a pure open-source RAG or agent builder, Langflow is closer to what Flowise was.
Is n8n open source like Flowise was?
No. Flowise used the Apache 2.0 license. n8n is source-available under its Sustainable Use License, which restricts commercial redistribution.
Can I import Flowise flows into n8n?
No. Flows have to be rebuilt as n8n workflows.