Skip to content
Open WebUI Alternative

How do I move off Open WebUI? A migration to the open-source Kortix

Moving off Open WebUI is a move from a chat instance to an agent platform, so the order matters: bring the models, then the configuration, then the work. Kortix is the open-source AI Operating System you migrate onto, with everything in one git repo you own.

Try Kortix
01

Four commands, from install to a change request

Every step is a git operation on the repo that becomes your company.

terminal
$ curl -fsSL https://kortix.com/install | bash$ kortix login
Read the docs

What moves, and in what order

A migration off Open WebUI moves three things: the models you connect, the configuration that shapes the assistant, and the work people hand to it. Move them in that order so each step can be tested on its own.

  1. Bring the models first. Open WebUI points at Ollama or an OpenAI-compatible API, and Kortix accepts any model provider with your own keys, the ChatGPT plan you already pay for, or an OpenCode Console account (Read the docs). Connect your provider in the app and confirm a session can reach it.
  2. Turn the configuration into files. Open WebUI keeps its settings and environment variables in the running instance. Kortix keeps them in a git repo: agents are agents/<name>.md, and kortix.yaml declares the machine image, connectors and triggers, and the secret names and grants.
  3. Define the agents and their reach. Each agent is a markdown file plus an agents.<name> block in kortix.yaml, and its connectors decide which tools it may touch. Set each tool to Allow, Ask or Block down to the arguments of each call.
  4. Connect where people work. Kortix is reachable from the web, desktop and mobile apps, the CLI and TUI, and Slack and Microsoft Teams. A trigger can also start a session on a cron schedule or a signed webhook, with no person present.
  5. Run one job and review it. Start a session, let the agent work on its own isolated sandbox and branch, and read the change request it opens before anything merges.

What does not move

Some things are Open WebUI features rather than data, so they have no file to copy across: its plugin and pipeline setup, and its community prompt presets. Rebuild the handful you actually use as agent skills or connectors in the repo, and leave the rest behind.

Start with one project, then let the repo grow

A project is a git repo with a kortix.yaml at its root, and Kortix hosts it or connects to the one you have. Create one, run one real job end to end, and let the repo grow from there (Read the docs). Run it on Kortix Cloud, in your VPC, or on-prem, with self-host free. Self-hosting Kortix is the operator path if the migration ends on your own box.

03

Migration questions

  1. 01

    How do I move off Open WebUI?

    Move the models first, then turn the instance settings into files in a git repo, then run one real job end to end. Kortix keeps agents, skills, memory and connectors in one repo you own, so each step is a diff you can review before it lands.

  2. 02

    Do I have to rebuild my Open WebUI plugins?

    Only the ones you use. Plugin and pipeline setup and community prompt presets do not carry across as files, so rebuild the handful that matter as agent skills or connectors, and leave the rest behind.

  3. 03

    Can Kortix run where Open WebUI ran?

    Yes. Kortix runs on Kortix Cloud, in your VPC, or on your own on-prem network, and self-hosting runs as one Docker Compose stack on a Linux server you control. Self-host is free.

  4. 04

    How much work is the switch?

    The install is a single command, then kortix init and kortix ship. The real work is deciding which Open WebUI workflows are worth keeping and rebuilding them as agents and connectors, one reviewed change at a time.

Move one workflow first, then let the repo grow

Start free on the cloud, or self-host on your own box.

Try Kortix