The file does not travel
Sovereignty is an architecture, not a contract clause. If a design requires trusting us with the document, we do not ship it.
Company
We build for the firms that cannot send data away
Sanctum Lex exists because the institutions with the most valuable documents are the ones least able to upload them. We took the constraint as the design brief rather than an obstacle to negotiate.
What we are building
A system that earns the file it is trusted with
Professional work turns on documents that cannot be shared: a privilege log, a sealed agreement, a client memorandum that has never left the firm. The current generation of legal AI asks those documents to move somewhere else first. That is a reasonable engineering shortcut and an unreasonable thing to ask a general counsel.
We build the other way around. The model, the index, and the corpus share one boundary that the firm controls, and the work product stays inside it from ingest to export. What comes out is an answer with its sources attached, produced by a system your own auditors can inspect.
How we work
Show the work
An answer without a source is a liability. Every output names what it was drawn from and what it could not find.
Built with practitioners
Litigators, deal lawyers, and compliance officers sit in the design reviews. Features that survive contact with a real matter are the ones we keep.
Boring where it counts
Deployment, upgrades, and key handling should be uneventful. We spend novelty on retrieval quality, not on operations.
Timeline
Where we have got to
2024
Founded
Started by infrastructure engineers and a former practice technology lead, after one too many pilots died in security review.
2025
First sealed node
An international firm ran live discovery work inside an air gapped enclave with no external inference calls.
2025
Agent operations
Long running agents shipped, writing reconciliation and authority checks back to the matter they came from.
2026
Financial services
The same enclave model extended to regulated institutions, with obligations mapped across portfolios.
- 2024
- Founded
- 3
- Regions with sealed deployments
- 100%
- Of engineering time spent on software that runs on customer hardware
- 0
- Customer documents held by us
Careers
Open roles
Small team, long deployments, and customers who will tell you exactly when something is wrong. If that sounds good, we would like to hear from you.
Come and see what a sealed deployment looks like.
Whether you are evaluating the platform or thinking about joining, the fastest way in is a live session on real documents.