The sovereignty tier: running local inference for banking and government briefs

Some matters cannot leave the building. A regulator-facing brief, a bank's customer file, a ministry's procurement papers. For these, the question is whether the text crosses a network boundary at all, not which model is best.

LexCore Sovereign is the same product as the managed cloud, installed on hardware you own or rent. Documents, matters, the database and user accounts stay inside your network. There is no phone-home and no remote access, by design. That also means no vendor-side telemetry telling you it is healthy. That is the trade.

What you receive, and what you provide

• Container images from a private registry with a read-only token for your organisation. Not source code.
• A licence file: your signed entitlement, with seat count and expiry.
• An install package: compose file, interactive installer, deployment runbook.

The latency conversation, honestly

A local model on a 24 GB card will not match a frontier model on a provider's fleet, on either speed or headroom. What it does instead is remove an entire class of question from the procurement review, and for the matters that qualify, that is worth more than the difference in tokens per second. The failure is choosing the sovereign lane for everything and then watching review times push people back to email.

Set the lane per matter

Model routing exists precisely so a firm does not have to make one choice for all work. Route confidential matters local and let routine agreements use the faster lanes. Deciding the routing rule in advance, by matter type, is what makes the policy hold under deadline pressure. A rule you re-argue on every upload is only a suggestion.

The install path, hardware sizing and the licensing model are documented in full under Deployment & Sovereignty.