LexCore Sovereign: run it on your own servers
The self-hosted edition: what you receive, what you provide, and what it costs to run.
LexCore Sovereign is the same product as the managed cloud, installed on hardware you own or rent. Your documents, matters, database and user accounts stay inside your network. LexCore never connects to it. There is no phone-home and no remote access, by design.
What you receive
- Container images from a private registry, with a read-only access token for your organisation. You are not sent source code.
- A licence file. Your signed entitlement, with your seat count and expiry.
- An install package. The compose file, an interactive installer and the deployment runbook.
What you provide
| Minimum | Recommended | |
|---|---|---|
| CPU / RAM | 8 vCPU / 32 GB | 16 vCPU / 64 GB |
| Disk | 200 GB SSD | 500 GB SSD |
| GPU | None (demo only) | 24 GB VRAM; 48 GB for the larger models |
| OS | Ubuntu 22.04 LTS + Docker Engine 24+ |
A GPU is not optional for real work
On CPU alone, document review is slow enough that people stop using it, which is worse than not installing it at all. Plan for a GPU, or use the managed cloud.
Installation
One interactive script. It asks for your domain, generates every secret, configures the identity provider for your URLs and starts the stack. Before it reports success, it checks that authentication actually rejects an invalid token.
tar -xzf lexcore-sovereign-v1.0.0.tar.gz
cd lexcore-sovereign-v1.0.0
./scripts/setup-sovereign.shLicensing
Your licence is verified offline, against a key built into the software. It works on a machine with no internet connection at all, and no usage data is ever sent back to LexCore. Renewal is a new file.
Your licence covers a number of seats. Adding a user beyond that count asks you to free up a seat or extend the licence. It never locks out people who are already working, and deactivating someone who has left returns their seat immediately.
Sovereign is licensed, not metered
There is no credit wallet and no per-review charge on a self-hosted install. You pay a licence fee and your own infrastructure costs. AI usage is limited by your hardware, not by a balance.
Upgrades are a docker compose pull against a version tag you choose. Your install is pinned to the release you were shipped, so it never changes underneath you. See Deployment modes and Data sovereignty.
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.
Sign in with your own identity provider
LexCore authenticates against any OIDC provider, including one running inside your own network.
Whitelabel: your firm's brand, not ours
Put your firm's name, colours and logo on the application, its emails, and the files it produces.