Self-host an open-source Copilot alternative
The Microsoft Copilots run in Microsoft’s cloud. Kortix is open source, and self-host is free. Three commands start it on a Linux box you control.
Three commands
$ curl -fsSL https://kortix.com/install | bash$ kortix self-host init --domain kortix.example.com$ kortix self-host startFrom the Kortix self-hosting docs. Point DNS at the box and open ports 80 and 443 first. Then check kortix self-host status, logs and doctor while the stack starts.
What you run
Kortix runs as one Docker Compose stack: the frontend, the API, the LLM gateway and the Supabase distribution. Agent sessions run on a separate sandbox provider, not on this stack.
One isolated sandbox per session. Each session has its own isolated machine and branch.
What the first run asks
The first run asks six things and no model key. GitHub connects in the dashboard (Settings → Git). Models are BYOK in the app.
- 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.
- Connector credentials are brokered server-side and never enter the machine.
What it is not
It needs the internet: kortix self-host start pulls images from docker.io, and the instance must be reachable so the sandbox can call back.
Versus the Copilots
GitHub Copilot, Copilot Studio and Microsoft 365 Copilot run in Microsoft's cloud. If a security review needs the agent layer on your own network, Kortix fits that lane. Run it on Kortix Cloud, in your VPC, or on your own on-prem network. Self-host is free.
The full guide, with the evaluation mode and backups, is in the Kortix self-hosting docs.
Run your whole company from one repo you own.
Start with one job and grow from there.
Open source · Any model, your keys · Self-host, VPC, or on-prem