Local-first AI for legal teams. Your matters never leave your machine.
Lex reviews, drafts, compares and reasons across your matters directly on-device. No cloud routing. No third-party exposure. Your work remains where privilege demands.
Matter processing designed to stay inside the local Vaultr environment.
How this worksFindings carry the passage they came from, and a record of what was decided.
See the demonstrationAGPL-3.0. Read the source, run the boundary test, check the register.
VerificationGrounded in the sources you already cite
Principles
Your junior counsel, already briefed — before the 8 a.m. call.
Interactive sample. Explore a prepared example using sample documents. This demonstration does not run AI on your device and does not accept your files.
Compare the termination rights across the supply agreements and flag any conflict with Annex C.
Ready — no result shown
Choose a matter and a task, then show the prepared result. You can open each source passage, record an example decision and download the sample artefact.
Every pleading, annex and exhibit across the matter — indexed with page, line and clause before you open the file.
First-pass letters, chronologies and submissions grounded in your own precedents, not the open internet.
Span-level citations you can verify in one click. If Lex cannot point to it, Lex does not say it.
Runs on your Mac. In local mode no matter data is sent, and the security brief sets out how to verify that for a given build.
Prepared example — no AI runs, nothing is uploaded · supervised by you — Lex proposes, counsel disposes.
Three deliberate steps, one local loop. Every decision stays with counsel, and every finding carries the page it came from.
PDF, DOCX, TXT or scanned OCR. Lex parses layout, headings and defined terms on-device, builds a clause index and keeps the source set on your disk. No upload dialog to a server, no queue, no third party.
Lex grades each clause against your playbook, flags high risk and medium risk, and attaches the exact span it relied on — § 14.2 assignment carve-out, page 47, lines 12–19 — linked back to the original document.
Lex proposes the redline, then stops. You accept, edit or reject, clause by clause. Export as tracked-change DOCX, PDF or ledger JSON with the proof trail attached to the document.
Inference happens on Apple silicon, in your process, against files that never leave the disk. In local mode, matter processing is designed to require no outbound connection — the boundary is enforced by architecture, not by a policy page.
Each read, draft and approval is written to an append-only ledger you can export with the matter.
Lex writes in your house style, grounded in your own bundle rather than the open internet.
Span-level references you can verify in one click. No span, no claim — Lex says not found.
Swap the local model per matter, or point sensitive work at the smallest model that holds up.
Install on the machine, work offline on a plane, no account, no seat provisioning, no admin console.
AGPL-3.0-licensed source your own security team can read line by line before it touches a matter.
Phi-4, Qwen3, Gemma or any local model, one hundred percent offline with zero data retention. The runtime boundary stays under your control, from a laptop to a firm-managed device.
Fast hosted inference when speed matters, Google models through your own key, or any OpenAI-compatible endpoint including custom deployments. The provider is selected by counsel — never by us.
Three paths. Each one states where the files sit, where inference happens and what leaves the device.
Matter processing stays in the Vaultr process on your supported device.
The active mode is shown beside the run action in the application. A hosted mode is never selected for you.
Vaultr preserves the relationship between the task, the supporting material and the reviewer's decision. The record stays with the matter and exports with it.
Integrity metadata detects alteration of the record's own entries. It does not establish that a legal conclusion is correct.
Not a trust page full of promises — a set of claims you can check against the code itself, in your own environment, on your own terms.
In local mode, matter content is designed never to reach our servers — because there are no servers in the path. Check it yourself with the published procedure.
Verification methodologyEvery line of code is public. Inspect the runtime, read the network calls, run the tests yourself.
Repository and licenceNo personal data is processed outside your machine in local mode. Regulatory fit is a scoped legal question, not a badge — the privacy notice says exactly what is and is not claimed.
Privacy noticeLicence compliance is a managed programme, self-certified against OpenChain ISO/IEC 5230 — an officially supported conformance path, stated with its exact scope. The badge and statement live in the trust center.
Compliance programmeSelf-attested — full verification procedure in the security brief
Read the full security briefNowhere. Retrieval, indexing and reasoning happen on the firm-managed device. In local runtime mode outbound traffic is denied — zero bytes leave your perimeter, and you can watch the network calls return zero yourself.
Vaultr is in assisted evaluation: we install it with you on one firm-managed device, you run your own bundle, and you decide. No public download, no free trial, and any charge agreed in writing first.