Skip to content
Flowise Alternative

Flowise is archived. Pick a replacement you own.

The open-source alternative to Flowise: an AI Operating System you own

Flowise is archived, so the open source replacement to pick is Kortix. It is an AI Operating System where your agents, their skills and the company memory live in one git repo you own, and each session runs on its own cloud computer.

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

The open-source AI Operating System

kortix.yaml
# kortix.yamlagents:  support-triage:    file: agents/support-triage.md # what it does, in plain markdown    connectors: all # what it may reach
Source: https://github.com/kortix-ai/suna

Session work reaches main through a change request. Merge is default-deny for agents.

How the open source replacements compare

Five questions decide it, and every rival cell comes from that project's own repository or site, checked in October 2026.

Open source
Yes. Read it, fork it, audit it.
Yes, its own README calls it completely open source.
Yes, its own README calls it an open-source platform.
Fair-code, with the source visible and self-hostable.
Where it runs / self-host
Kortix Cloud, your VPC, or on-prem; self-host is free.
A Python package or Docker, on your own machine or a cloud.
Docker Compose Community Edition, or Dify Cloud.
Self-hosted, or n8n Cloud.
Your configuration lives in
Files in a git repo you own.
The Langflow instance; a flow exports as JSON.
The Dify workspace you host.
The n8n instance you run.
Agents vs fixed flows
Agents that do finished work, reviewed by people.
A visual canvas for flows and agents.
Visual workflows, RAG pipelines and agents.
A visual canvas for fixed, step-by-step workflows.
Pricing shape
Free is $0. The team plan is $40 per seat per month.
Free to self-deploy; a free cloud account.
Self-host free; cloud from $590 per workspace per year.
Self-host free; cloud billed per execution.

What an AI Operating System ships with

Agents, skills, memory and connectors are files in one git repo you own.

  1. 01Agents and skills

    Agents and skills are markdown.

    An agent is agents/<name>.md (behavior) plus an agents.<name> block in kortix.yaml (governance).

    kortix.yaml
    # kortix.yamlagents:  support:    file: agents/support.md    connectors: [helpdesk]    skills: [kortix-cli, triage]
    Source: https://kortix.com/docs/project/agents
  2. 02Memory

    Memory is files that accumulate.

    memory/ holds what the project knows about itself: its purpose, connections, conventions and decisions.

    docs/project
    memory/ holds what the project knows about itself:its purpose, connections, conventions and decisions.memory/MEMORY.md is the index, with one line per file.
    Source: https://kortix.com/docs/project
  3. 03Connectors

    Connectors live in the repo.

    3,000+ apps in a click, plus MCP, OpenAPI, Postman, GraphQL and raw HTTP.

    kortix.yaml
    connectors:  - slug: gmail    name: Gmail    provider: composio    app: gmail
    Source: https://kortix.com/docs/connect/connectors
  4. 04Sessions

    Every session gets its own cloud computer.

    One isolated sandbox per session.

    terminal
    $ kortix sessions new -p "Fix the failing test in src/billing and open a change request" --wait$ kortix sessions stop <id>   # ends the turn and stops the sandbox
    Source: https://kortix.com/docs/work/sessions

Open source. Read it, fork it, audit it.

20,000+

GitHub stars

What a Flowise user asks

  1. 01

    Is Flowise still maintained?

    No. Its GitHub repository is archived and its own site says the team is winding the project down, so no new features or security fixes land (the Flowise announcement). The code stays up for forks.

  2. 02

    What happens to my existing flows?

    They keep running on your own infrastructure, because the code is still on GitHub, but nothing upstream updates or fixes them again. Treat the install as frozen and give it no new work.

  3. 03

    Do I have to rebuild every flow?

    Expect to reproduce them. Each replacement starts from its own canvas or repository, so a flow is rebuilt as an agent, a workflow, or a fixed automation rather than ported. Inventory your flows first, then rebuild the ones that still earn their keep.

  4. 04

    Can I self-host Kortix?

    Yes. Run it on Kortix Cloud, in your VPC, or on your own on-prem network. Self-host is free.

  5. 05

    What does it cost to switch?

    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. Current plans are on Kortix (checked October 2026). The move itself costs your time.

Run your first agent on the open-source AI Operating System.

Start with one job; the agent hands back a change you review.

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