# The open source alternatives to Flowise, compared

> Flowise is archived, so the choice now is between a handful of open source tools. This page compares the field, Kortix first: Kortix is open source, and every competitor fact here comes from that project’s own repository or site.

URL: https://flowisealternative.com/flowise-alternatives

## Flowise alternatives, compared cell by cell

Every rival fact comes from that project's own repository or site, checked in October 2026.

| | Kortix (recommended) | Langflow | Dify | n8n |
| --- | --- | --- | --- | --- |
| Open source | Yes. Read it, fork it, audit it. | Yes. Its docs call it open-source. | Source is public; self-hosted Community Edition. | Fair-code, with the source visible. |
| Self-host / where it runs | Kortix Cloud, your VPC, or on-prem. | Python package or Docker; deploy to clouds. | Docker Compose Community Edition, or Dify Cloud. | Self-host on your infrastructure, or n8n Cloud. |
| Config ownership | Files in a git repo you own. | Flows exported as JSON, with Python components. | Apps and workflows inside the Dify instance. | Workflows inside the n8n instance, versionable with git. |
| What it is for | Open-ended work an agent does on its own computer. | Visual flows and agents on a drag-and-drop canvas. | Visual workflows, RAG pipelines, and agents. | Visual workflows and multi-step agents. |
| Pricing shape | Free self-host and a free tier; paid seats. | Free self-host; optional cloud. | Free Community Edition; paid Cloud plans. | Free self-host; paid Cloud and enterprise plans. |
| Best for the Flowise refugee | Teams replacing flows with agents that return finished work. | Builders who want to stay on a visual canvas. | Teams building self-hosted RAG apps and workflows. | Fixed step-by-step automations with a code escape hatch. |

## What to pick now that Flowise is archived

Flowise's repository is archived, and the project's own announcement says the team decided to wind down its operations: the code froze on 29 July 2026, the repository moved to public archive on 13 August 2026, and end of life followed on 31 August 2026 ([the Flowise announcement](https://github.com/FlowiseAI/Flowise/discussions/6727)). The repository README now opens by saying the project has been archived ([Flowise's GitHub repository](https://github.com/FlowiseAI/Flowise)). An install that already runs keeps running, but the npm package and the Docker image are marked deprecated, so the project ships no further fixes.

## Kortix, the recommended replacement

Kortix is the open-source AI Operating System: your agents, their skills, your company memory, and every connector in one git repo you own, with the agents working on real cloud computers ([Kortix docs](https://kortix.com/docs)). One isolated sandbox per session. Each session has its own isolated machine and branch. Session work reaches `main` through a change request. Merge is default-deny for agents.

Run it on Kortix Cloud, in your VPC, or on your own on-prem network. Self-host is free. Any model provider with your own keys. Or the ChatGPT plan you already pay for. Kortix is open source. Read it, fork it, audit it.

Free is $0 with 200 credits per month and 1 project. The team plan is $40 per seat per month with 2,500 credits per month per seat, pooled ([Kortix pricing](https://kortix.com/pricing)).

## Langflow

Langflow is an open-source, Python-based framework for building AI applications, with a drag-and-drop canvas and a Python escape hatch ([the Langflow documentation](https://docs.langflow.org/)). Flows export as JSON, and a flow can be served as an API or as an MCP server. Self-host it with a Python package or the official Docker image, or deploy it to a cloud. Its own repository notes that official images now require authentication by default ([the Langflow repository](https://github.com/langflow-ai/langflow)).

## Dify

Dify describes itself as an open-source LLM app development platform, combining a visual workflow canvas, RAG pipelines, and agents in one workspace ([the Dify repository](https://github.com/langgenius/dify)). Self-hosting is a Docker Compose start of the Community Edition; the managed Dify Cloud is billed per workspace per year, with message credits and document quotas ([Dify pricing](https://dify.ai/pricing)). Dify's repository states that additional conditions sit on top of its open source base, so read those before you commit.

## n8n

n8n calls itself a fair-code platform to build and deploy AI agents and workflows, with a visual canvas, custom JavaScript and Python, and a run that is self-hosted or cloud ([the n8n repository](https://github.com/n8n-io/n8n)). Its repository labels it fair-code, with the source visible and self-hostable, and paid Cloud and enterprise plans add features and support ([n8n pricing](https://n8n.io/pricing/)). n8n suits a job whose steps are fixed and known in advance; Kortix's own README recommends it for exactly that shape of work ([Kortix on GitHub](https://github.com/kortix-ai/suna)).

## If you are leaving Flowise

Sort your flows by what they actually did. A flow that ran the same fixed steps on a schedule maps onto n8n or a Dify workflow. A flow that was really a chatbot over documents maps onto Langflow or Dify.

A job that needed someone to read open-ended work and fix it maps onto Kortix, where an agent runs on its own isolated machine and hands back a change you review. Plan to [reproduce each job](/migrate-from-archived-flowise) rather than port the diagram, because each tool here starts from its own canvas or repository.

## Three commands to start

The Kortix README lists the install, scaffold and ship commands ([Kortix on GitHub](https://github.com/kortix-ai/suna)).

```sh
curl -fsSL https://kortix.com/install | bash
kortix init
kortix ship
```

## Where a Kortix job lives

`kortix.yaml`

```yaml
triggers:
  - slug: daily-digest
    type: cron
    cron: '0 0 9 * * 1-5'
    prompt: Summarize yesterday's support tickets and open a change request with the digest.
```

Source: https://github.com/kortix-ai/suna

A trigger in `kortix.yaml` starts a session on a schedule, with nobody present.

## Questions a Flowise user asks

### Is Flowise still maintained?

No. The repository is archived and the project's own announcement says the team decided to wind down its operations: the code froze on 29 July 2026, archival came on 13 August 2026, and end of life on 31 August 2026. An install that already runs keeps running, but the npm package and the Docker image are deprecated, so no further fixes arrive.

### What is the closest open source alternative to Flowise?

It depends on what the flow did. A fixed sequence of steps is served by n8n or a Dify workflow. A document chatbot suits Langflow. Open-ended work that a person would otherwise pick up suits [Kortix](/kortix-vs-flowise), the open-source AI Operating System, where an agent runs on its own isolated machine and hands back a change you review.

### Can I self-host the replacement?

All four options here run on infrastructure you control. Kortix self-hosts for free as one Docker Compose stack, and also runs in your VPC or on your own on-prem network. Langflow, Dify's Community Edition, and n8n all self-host as well.

### Do I have to rebuild my flows?

Expect to reproduce them. Each tool here starts from its own canvas or repository, so you rebuild each flow's job as an agent, a workflow, or a fixed automation rather than porting the diagram. Inventory your flows first, then rebuild the ones that still earn their keep.

## Leave the archived flow behind.

Start with one job and let the agent hand back the work.

[Try Kortix](https://kortix.com)

Open source · Any model, your keys · Self-host, VPC, or on-prem