Comparisons

Kortix vs Open WebUI: chat answers, or open-source work that lands

Open WebUI is a self-hosted chat interface for your models; Kortix is the open-source system you own, review and self-host.

The Kortix Team
Kortix··4 min read

Kortix vs Open WebUI: chat answers, or open-source work that lands

Open WebUI gives people a private interface to their own models, and it does that job properly; Kortix, the open-source CompanyOS, takes the next question: what happens to the work once an answer is written. The agents that do the work, and the memory they draw on, live in your own repo.

What Open WebUI is great at

Open WebUI started as a front end for Ollama. It grew into a platform you host yourself, running with no outside connection at all. (Open WebUI on GitHub)

  • One command to a working chat. A published image and a single docker run are enough to start, and Python and Kubernetes paths exist for larger deployments. (quick start)
  • Retrieval built in. Local RAG sits on 13 vector databases, combining BM25 with vector search and reranking. (feature list) A document enters a chat with # or from the library.
  • Search, images and notes. Dozens of search providers are wired in, several engines handle image generation and editing, and Notes and Channels run alongside the conversation.
  • Enterprise identity. LDAP, Active Directory, SSO and SCIM 2.0 provisioning are supported; the application layer stays stateless over shared databases and storage, and Redis keeps sessions together. (enterprise overview)

Where a chat interface stops

Open WebUI is designed around a conversation. Everything else in it arranges itself around that unit.

  • Memory is personal. What it learns about you stays in your own history, which is right for a chat and wrong for a company record.
  • Execution rides along. Open Terminal hands an agent a shell and a filesystem inside the chat; keeping those Terminals separate for each person takes an Enterprise license.
  • Settings live in the database. Models, tools and knowledge bases are configured through the admin panel. A change there is live state, not a file anyone can review first.
  • Nothing lands by default. An answer stops at the message, and nothing about it updates the company's systems by default. Python tools, MCP servers and OpenAPI endpoints can reach outward, so each connection a team wires is work it builds and maintains itself. (tools and MCP)

The setup is files, not settings

Kortix takes the open question Open WebUI leaves and answers it with files. The agents, their instructions and the connections to other systems are files in a repository the company holds. A change arrives as a diff. (Kortix on GitHub)

A new teammate clones it and inherits the same working setup. An agent is one agents.<name> block in kortix.yaml: prompt (inline, or prompt_file pointing at agents/<name>.md), model, permission, grants. The manifest has no version line. A prompt file holds no frontmatter; kortix.yaml and the files it names define the project. A reviewer can read the setup like documentation and review a change like code.

The work comes back for review

Session work reaches main through a change request. Merge is default-deny for agents. Thousands of agents in parallel on one config, each on its own cloud computer. Each session has its own isolated machine and branch.

The self-hosted install is a single Compose stack: a frontend, an API, an LLM gateway and Supabase. Sessions themselves run on Platinum, the compute provider every new session lands on. Install the CLI with curl -fsSL https://kortix.com/install | bash, then kortix self-host init to set the stack up, and kortix self-host start to boot it. Nothing on the first run wants a model key; it asks six questions. (self-hosting docs)

Where Open WebUI is the better pick

If the work is a conversation, Open WebUI wins outright. One Docker command gets it running. 13 vector databases handle retrieval, and dozens of search providers plug in. LDAP, SSO and SCIM wait for the day the outfit grows. Anyone who wants a private, model-agnostic place to talk to their models will be running it before Kortix is even installed.

Side by side

DimensionKortixOpen WebUI
Open sourceYes, open sourceYes, Open WebUI License, branding clause
Where state livesOne git repo you ownPer-user memory and settings
Agent executionOne isolated sandbox per sessionOpen Terminal; Terminals on Enterprise
Landing workReviewed change requestAnswers stay in the chat
Self-hostDocker Compose plus a sandbox providerOne Docker command or Kubernetes
CostFree $0 with 500 credits a month; credits from $50 a monthFree; enterprise license to rebrand

The Open WebUI License is a permissive license with a branding clause attached. The Open WebUI name has to stay visible unless a deployment covers 50 or fewer people in a 30-day window. Written permission or an enterprise license also lifts the requirement. (Open WebUI License) The code can be forked, audited and self-hosted.

When to pick which

Choose Kortix if the company's setup has to sit in one repository you control, with a sandbox per session. Nothing merges itself: work reaches main through a change request a person approves, unless an admin granted the merge capability. Free is $0 with 500 credits per month, every feature and 1 project, on the user's own provider keys or ChatGPT subscription. Run it on Kortix Cloud, in your VPC, or on your own on-prem network. Self-host is free, from a public server with a Platinum key. The paid plan is credits: you choose the monthly amount, and 5,000 credits a month costs $50 at 100 credits per dollar. Members are unlimited and free, and one credit pool is shared across the account. (Kortix pricing)

Choose Open WebUI if the work lives in conversations. It gives a team a quick, private chat surface over any model, retrieval across 13 vector databases, and enterprise identity ready when you need it.

Two more reads: how the category of open-source agents fits together, and what to weigh in running one yourself. Kortix also lines up against OpenWork.

Start free, or self-host it and pay nothing. Try Kortix.

Own your company’s AI.Start today, in our cloud or yours.

Start for free

Open source · SOC 2 Type I · SAML SSO and SCIM · Any model, your keys