Self-hosting guide
The same platform, inside your network boundary — with the honest map of what's included and what stays in the cloud.
What the self-hosted edition is
Self-hosted Akili includes chat, agents, knowledge, memory, and integrations — plus SSO, SCIM deprovisioning, RBAC, and the audit trail. The public marketplace and the managed billing plane are cloud-only, and that's structural: the self-hosted build physically excludes those components, which is exactly why it keeps serving your team even if it can't reach us at all.
Licensing is per named user — you license the software, not the tokens. Inference runs on your own provider keys (or entirely locally with Ollama), so there's no per-token markup to anyone.
The architecture diagram shows exactly where that boundary sits — every layer below the surfaces ships in the self-hosted build.
Deployment shapes
| Shape | What it looks like | Fits when |
|---|---|---|
| Docker Compose | PostgreSQL, Redis, backend, worker, frontend — one compose file. A minimal stack exists for small footprints. | Evaluations, small teams, single-host deployments |
| Docker Compose + Ollama | The same stack plus a local Ollama container. Zero external AI calls. | Air-gapped evaluation; sovereignty requirements down to inference |
| Kubernetes | Manifests with kustomize overlays per service, including an isolated sandbox workload for code execution. | Production platform teams |
| Your Azure tenant | Infrastructure-as-code into your subscription: your database, blob storage, Key Vault, network. | Azure-standard enterprises with residency requirements |
The fastest honest evaluation
The Ollama compose stack is the strongest proof of the ownership claim — the entire platform answering from a local model, with nothing leaving the machine:
docker compose -f docker-compose.yml -f docker-compose.ollama.yml upOperational notes
- Identity: bring your IdP — SSO over SAML/OIDC with DNS-verified domains; SCIM handles deprovisioning (auto-provisioning is on the roadmap).
- Secrets: provider keys and integration credentials are encrypted at rest in your database; platform secrets live in your vault.
- Data: your PostgreSQL, your blob storage. GDPR erasure tooling and the audit trail run inside your boundary.
- Upgrades: versioned releases with migration scripts; agents move between cloud and self-hosted as portable export packages.
Still deciding?
The deployment comparison lays both modes side by side. The short version: if a shared multi-tenant cloud passes your security review, the cloud is faster to evaluate — and agents are portable if you later move.