Some documents cannot leave. We built for that first.
Sovereign exists for two reasons: to keep a client's files strictly confidential, and to let an organisation meet a data-localisation obligation when it has one. "Sovereign" gets used loosely in this market, usually to mean a data-centre region on a map. At LexCore it means a dedicated deployment on infrastructure you control, run on its own or alongside our hosted quality tier. This page covers both, including where each one stops.
Hybrid
A tenancy agreement does not need what a bank's financing document needs. On hybrid, the matters that require it run on a sovereign deployment, and routine work runs on the quality tier with full multi-round debate. Every review records which tier it ran on. We size both against your work on a scoping call.
Dedicated deployment
LexCore is installed in your VPC, your data centre or your rack. Documents, database, search index, models and audit trail all sit inside your network boundary, under your access control and your retention policy. Air-gapped installations are supported, and the licence is verified offline, with no callback to us.
Confidentiality, and a localisation answer that holds up
Sovereign is built for the matters where the question is not how good the analysis is, but who else was able to read the document. These are the situations it is bought for.
Some organisations must keep a category of data in a defined place, and sector regulation in financial services is the common case. A sovereign deployment puts the storage and the inference where that requirement points, and keeps them there by enforcement rather than by policy.
Outside-counsel guidelines, a parent company's data policy, or a tender condition can each require that files stay within a named boundary. Sovereign satisfies that boundary directly, and the deployment can be evidenced to the party asking.
Clients rarely ask which country a server is in. They ask who, other than you, has been able to read their document. On a sovereign review the answer is nobody, because no third-party model provider is in the document path at all.
Government agreements, dispute memos, board and investigation material, and anything under a strict privilege policy. Route those to sovereign per matter and leave the rest of the practice on the quality tier. You do not have to make one choice for everything.
How the sovereign tier actually works
LexCore routes every model call on two axes: what kind of thinking it is, and which tier the matter is on. The tier decides which models are even constructed.
"Runs on local models" and "stays in your jurisdiction" are two different claims, and only the first one is about the model tier. Jurisdiction follows where the deployment is hosted. A sovereign deployment sits wherever you put it. Our hosted quality tier is ours, and the country it sits in is whatever the sub-processor register says today. This page makes no promise about it on your behalf. If your requirement is that data never leaves your boundary, the matters it covers belong on a dedicated deployment. It is worth settling before you scope, and we will go through it with you.
Three shapes of dedicated deployment
They differ in one respect that matters more than any other: whether anything leaves your network at inference time. Which one you need depends on what your policy requires, and that is the first thing we establish in scoping.
Local models only. No cloud model backend is ever constructed. It is not configured and left idle; it is absent, so there is no credential to leak and no route to misconfigure. This is the configuration for matters under a policy that forbids third-party processing outright.
The platform runs on your infrastructure, but reasoning calls go to your own frontier-model account: your Vertex or Azure OpenAI tenancy, your contracts, your DPA, your spend. The appeal is that AI spend lands inside governance you already have.
No route out of the environment. Licence verification is offline, updates and the authority corpus arrive as signed media, and telemetry stays inside. Built for environments where the network boundary is the control.
A different open-weight model for each kind of work
No single generic model is good at every legal task, so LexCore runs several specialised open-weight models, all of them inside your boundary. No cloud telemetry, no egress and no licensing lock-in.
Reads scanned Nigerian court processes, Certified True Copies (CTCs), exhibits and complex tabular schedules natively, as images. Everything is parsed locally, with no external OCR sidecar.
Sticks closely to JSON schemas and calls tools precisely. Contract redlines, playbook rule checks and structured findings come back in the JSON schema they were asked for.
Chain-of-thought reasoning trained with reinforcement learning. It works step by step on the local lane. Statute citations are checked at section level against the indexed federal Acts from the 2004 Laws of the Federation, and each step is kept in the audit trail.
8,192-token dense text embeddings for fast semantic retrieval in PostgreSQL pgvector. High throughput, no cloud cost and no external dependency.
The licence does not phone home
An on-premise product that calls a vendor server on a timer is the first thing a bank's security review finds, and rightly so, because it defeats the point of on-premise. Ours has no such call to remove.
What sovereignty means here, precisely
Each of these is a property of the running system rather than an intention, and each is enforced somewhere you can point at. The same standard we apply on the security page, applied to this word.
Hardware-attested confidential compute. Running the platform in a confidential VM, so that what is executing can be cryptographically verified, is under active evaluation. It is not a shipped control today. If remote attestation is in your policy, raise it during scoping so we can plan the timeline around it.
How a dedicated engagement runs
Four stages. Pricing is agreed at the end of the first one, when both sides know what is actually being deployed.
Bring us your security review
The fastest way to scope a dedicated deployment is to send the questionnaire your risk team would send anyway. We answer it, show you the platform working on your own documents, and then price the engagement.