Akili

Self-HostedComing soon

Your infrastructure. Your data. Your AI.

Run the full platform — chat, agents, knowledge base, everything but the marketplace — inside your own environment. Nothing leaves your network unless you decide it does.

Talk to us about your environment

Self-hosted deployments are coming soon — early conversations start now, and they shape the rollout order.

Who this is for

Sorted by constraint, not by industry

If your data residency policy, regulatory obligations, or security review would block a shared multi-tenant cloud, self-hosted removes that question entirely. Your data stays in your PostgreSQL database, your files in your blob storage, and your provider API keys encrypted at rest — inside a network boundary you control. With the Ollama stack, even inference never leaves the building.

What the self-hosted edition includes

What's different, stated plainly: the public marketplace is a cloud-only feature today. That isn't an asterisk — the self-hosted build physically excludes the billing and marketplace plane, which is exactly what lets it keep serving chat, agents, and knowledge even when it can't reach us at all.

Three ways to run it

Docker Compose

Three stacks, from a minimal footprint to a full one — including an Ollama stack where the entire platform runs on a local LLM with zero external AI calls.

Kubernetes

Manifests with kustomize overlays for every service, including an isolated sandbox workload template for code execution.

Your own Azure tenant

Infrastructure-as-code deployment into your subscription — your PostgreSQL, your blob storage, your Key Vault, your network boundary.

Licensing is per named user — you license the software, not the tokens, because inference runs on your own keys. Deployment specifics are covered in the self-hosting guide.

Talk to us about your environment

Self-hosted deployments start with a real conversation — your constraints, your infrastructure, your identity provider — not a checkout page.

Start the conversation