Bring your own key (BYOK) and self-hosting
Use your own model provider account, or run the whole stack on your own infrastructure.
Bring your own key (BYOK)
A tenant can bring its own cloud-provider key (currently Anthropic and Cerebras). The key is encrypted at rest, your organisation is billed on its own account, and you hold the model relationship directly. BYOK works with any deployment mode.
Self-hosting
For maximum data sovereignty, the whole stack (the AI orchestrator, vector store and local models via Ollama or vLLM) can be deployed on your own private cloud or intranet using the sovereign compose configuration. It ships with automated Postgres backup and restore and a business-continuity runbook.
Related documentation
Deployment modes: cloud, sovereign and hybrid
Same code, different data boundary. You choose where AI runs, per tenant and per matter.
Data sovereignty and model routing
How the model router keeps a sovereign tenant's documents away from third-party model providers, and why where your analytics go is a separate question with its own control.
LexCore Sovereign: run it on your own servers
The self-hosted edition: what you receive, what you provide, and what it costs to run.
API overview
The service topology and the main REST endpoints for integrators.