Flowise Alternative
Self-host an open-source Flowise alternative
Self-hosting Flowise kept your data on your own server, and the open-source replacement we recommend for that same control, at a larger scale, is Kortix. It installs as one Docker Compose stack on a server you control, with kortix self-host init and kortix self-host start.
Self-host on a server you own
Three commands from the Kortix docs, then the repo layout where your agents, skills and memory live.
$ curl -fsSL https://kortix.com/install | bash$ kortix self-host init --domain kortix.example.com --admin-email you@example.com$ kortix self-host startkortix_version: 2default_agent: kortixagents: kortix: file: agents/kortix.md connectors: allagents/ who does the workskills/ how the company does one jobmemory/ what it has learned so farkortix.yaml rules, triggers, connectors, the machine imageWhat self-hosting Flowise meant
Flowise ran as a Node app on infrastructure you controlled. You installed it globally with npm i -g flowise and started it with npx flowise start, or built its Docker image and ran it on port 3000. Both paths are in the Flowise README, which now opens by saying the repository has been archived.
What to check before you pick the replacement
Four things decide whether a replacement fits the way you ran Flowise. Check each one against your own setup.
- Where it runs. A self-hosted app on your server, a managed cloud, or a stack you can put in either.
- Who holds the model keys. Your own provider keys, or the vendor's.
- Where the configuration lives. Files in a repo you own, or state inside the vendor's database.
- How models are chosen. Per agent, per session or per message, instead of one fixed default.
How Kortix's self-host, VPC and on-prem options read
Kortix is the open-source AI Operating System we recommend on this page. Run it on Kortix Cloud, in your VPC, or on your own on-prem network. Self-host is free.
A self-hosted Kortix is one Docker Compose stack on a Linux server you control: the web app, the API, the LLM gateway and the Supabase distribution. kortix self-host init writes the compose file, .env, a Caddyfile and updater.sh, and kortix self-host start runs it. Sessions run on a separate sandbox provider, not on that server, and the instance stays reachable from the internet so the sandboxes can call back. The full path is in the self-hosting docs.
What stays on your infrastructure
After a self-host, the things that matter are files and keys you control.
- The repo. Your agents, their skills, your company memory and every connector live in one git repo you own.
- Secrets. Secrets are encrypted at rest with a key per project.
- Connector credentials. Connector credentials are brokered server-side and never enter the machine.
- The model keys. Any model provider with your own keys.
Questions before you move off a self-hosted Flowise
- 01
Can Kortix be self-hosted?
Yes. It installs as one Docker Compose stack on a Linux server you control, with
kortix self-host initandkortix self-host start. Self-host is free. Sessions still run on a separate sandbox provider, so keep the instance reachable from the internet. - 02
Which models can I use?
Any model provider with your own keys. Or the ChatGPT plan you already pay for. Or sign in with your OpenCode Console account for OpenCode Zen and Go.
- 03
Where does my configuration live?
In a git repo you own.
kortix.yamlsits at the root and declares the agents, triggers, connectors and the machine image. Agent behavior is markdown underagents/, skills live underskills/, and what the agents have learned is files undermemory/. - 04
Is Kortix open source?
Yes. Open source. Read it, fork it, audit it. The source is at Kortix on GitHub.
Self-host your agent layer, on your own infrastructure.
Start with one job and grow from there.
Open source · Any model, your keys · Self-host, VPC, or on-prem