Skip to content
LibreChat Alternative
ReferenceLibreChat Alternative
Domainlibrechatalternative.com
Updated2026-10-15

Compare LibreChat, Open WebUI, Onyx and Kortix

An open-source LibreChat alternative your team owns end to end

If you want more than LibreChat's self-hosted chat UI, Kortix is the open-source system your team owns end to end. Agents, skills, company memory and connectors live in one git repo you own. Self-host it free, in your VPC, or on-prem.

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

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

§ 01

LibreChat, Open WebUI, Onyx and Kortix, side by side

Four ways to run AI you control, compared on what each one is for.

Our pickSelected

Kortix

Open source
Yes. Read it, fork it, audit it.
What it is
Open-source AI Operating System: agents, skills, memory, connectors in one git repo
Self-hosting
Self-host free, VPC, or on-prem
Models
Any model, your keys
Agent work
Agents run on cloud computers. Work lands as a reviewed change request.

LibreChat

Open source
Yes
What it is
Self-hosted multi-provider chat UI
Self-hosting
Docker, npm, or Helm chart
Models
OpenAI, Anthropic, Google, Azure, AWS
Agent work
Chat UI with agents and presets

Open WebUI

Open source
Yes
What it is
Self-hosted AI chat platform with tools and knowledge
Self-hosting
Docker, Kubernetes, pip, or desktop
Models
Ollama, OpenAI, Anthropic, Google, Bedrock
Agent work
Tools, MCP, sub-agents and scheduled automations

Onyx

Open source
Yes
What it is
Enterprise search and AI assistant over company knowledge
Self-hosting
Yes, self-hosted
Models
Multi-model chat
Agent work
Search and answers across company knowledge

LibreChat, Open WebUI and Onyx details from each project's own site, October 2026.

§ 02

What you own with Kortix, layer by layer

Every layer an AI Operating System needs is a file in the repo you own.

  1. § 01Repo

    One git repo is the company

    Your agents, the skills they share, your company memory, and every connector live in one git repo you own.

    the project repo
    acme-co      your whole company, as filesagents/      who does the workskills/      how your company does a jobmemory/      what it has learned so farkortix.yaml  what each agent may touch
    Source: https://kortix.com
  2. § 02Connectors

    Wire each tool once

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

    connector policy
    Set each tool to Allow, Ask or Block, down to the arguments of each call.Connector credentials are brokered server-side and never enter the machine.
    Source: https://github.com/kortix-ai/suna
  3. § 03Models

    Any model, your keys

    Any model provider with your own keys. Or the ChatGPT plan you already pay for.

    models
    Runs any modelBring your own API key from any major provider, or use oursOr sign in with the ChatGPT subscription you already pay for
    Source: https://kortix.com
  4. § 04Sessions

    One cloud computer per session

    Each session has its own isolated machine and branch.

    sessions
    Each session gets its own isolated sandbox and its own branch.Run thousands of sandboxes in parallel on the same config, each fully isolated.
    Source: https://github.com/kortix-ai/suna
  5. § 05Review

    Work lands as a change request

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

    change requests
    $ kortix cr ls# review what the agents propose
    Source: https://github.com/kortix-ai/suna
§ 03

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

GitHub stars

§ 04

Questions before you switch

Self-host is free. 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.

Yes. Slack and Microsoft Teams are live. Email is experimental, per project.

One Docker Compose stack. The stack has no Redis and no separate worker.

Run your company from one repo you own.

Open source, self-hostable, and yours to audit.

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