For litigation practices
Your case files never
leave the building.
An AI case team that runs on hardware your firm owns — and a verification step that refuses to approve a document until every claim points to a real page in your own file.
Software for licensed attorneys — not a law firm, not legal advice.
Pre-release overview. Some capabilities described here are in active development — ask us what is running today.
The practical difference
What changes on your desk
Think of it as staff, not software: tireless, literal, fast — and supervised, with everything it touches staying inside the office.
The demand package
- 15–25 hours to assemble a demand package from a scanned record set
- Paralegal time spent transcribing dates and bills into a chronology
- Citations checked by hand, if there is time
- The record sits in whatever tool was convenient
The same package
- A few hours of attorney review on a drafted package
- The chronology is built from the pages and linked back to them
- Every claim is machine-checked against the source before you read it
- The record sits in an encrypted container, one per matter
And must not
- You select the matters, set the fees and make every legal judgement
- You read the draft and you sign it
- Nothing leaves your office without a decision you made, and that was recorded
- The AI never speaks to a client and never gives legal advice
Who does what
Your digital staff — seven roles
The third column is the point. Each role is deliberately narrow, because a narrow assistant is one you can actually supervise.
| Role | What it does | What it never does |
|---|---|---|
| 1. Intake | Structures the facts from the file; flags limitation periods | Advise the client, or decide whether to take the matter |
| 2. Documents / OCR | Reads scanned records page by page, preserving layout and tables | Discard the original — the source page is always kept |
| 3. Medical timeline | Builds a dated treatment chronology, every entry tied to a page | Infer a treatment that is not written on a page |
| 4. Research | Searches the case file and applicable law | Cite anything it did not actually find |
| 5. Drafting | Demands, disclosures, briefs — citing located sources only | Invent a supporting quotation |
| 6. Verification | Re-checks every claim against the source it cites | Take the drafting agent’s word for anything |
| 7. Attorney review | You: review, judgement, signature | Be skipped, in any mode |
How a matter moves through
Nothing is lost, nothing is silent
Each step hands the matter on through a durable work queue; a failed step is retried rather than dropped, and the failure is visible. Every hand-off writes a line in that matter’s audit log in the same database transaction — so a matter cannot advance without its log entry.
The last step waits for a person
Verification loops back on itself for up to three passes while any flag remains, and will not release a document while one is open. Attorney review is the only stage with no queue behind it: nothing downstream happens until a person acts.
Verification
Every claim, traced back to a page
The draft is broken into atomic claims — one checkable fact each, like separately numbered paragraphs in a pleading. For each one, the verifier reopens the actual file and page in your case container and looks for the supporting words. It never checks the draft against the draft.
A verbatim quotation, or a flag
A claim is accepted only with a verbatim supporting quotation. That is what catches a “citation-shaped” hallucination: a plausible-looking cite to a real document that does not in fact support the sentence. Anything else is flagged [VERIFY] and sent back for up to three passes.
The rule lives in the database
One unresolved flag and the document cannot be marked approved — a constraint enforced by the database itself, so it cannot be clicked past in the interface. And because this runs on your own hardware, checking is free: no per-query cost pushes anyone to check less thoroughly.
What you see: the weakest points, first
Flagged claims sort to the top. The weakest sentence in the document is the first one you read — not the one hidden in the middle of polished prose.
Illustrative screen on a fictitious matter. Note the first row: the system caught our own side’s overstatement — a $3,800 gift to the defence, flagged before it left the office.
Confidentiality
Where your data goes — you choose, per matter
The mode is chosen per matter and recorded in that matter’s log: a deliberate decision by a lawyer, on the record, not a default inherited from somebody’s terms of service. Every mode keeps the same protections — verification, your signature, per-matter encryption, and a gateway that blocks by default rather than warns.
| Mode | Where the work runs | What leaves your office | Typical use |
|---|---|---|---|
| A. Fully local | Everything on your office device | Nothing. There is no route out. | Highest-sensitivity matters; clients who require zero transfer; active litigation under a protective order |
| B. Hybrid | Protected data stays local; language polish by an outside model through the de-identification layer | Pseudonymised text only, under a signed BAA with zero data retention | Complex matters where the best available drafting quality materially helps |
| C. Outside review | Draft built locally; an independent outside model gives a second opinion on citations | Pseudonymised text only | High-stakes documents you want double-checked |
If you choose hybrid: what actually crosses
Before it leaves
- Names, dates of birth and addresses are replaced with stable placeholders: [PATIENT_1], [DOB], [ADDRESS_1]
- The table mapping placeholders back to real people never leaves the office
- One person keeps the same placeholder throughout, so cross-references still work
At the gateway
- A second, independently built detector re-scans the text just before it goes out
- A match blocks the transfer and writes a log line — it does not warn and proceed
- If the gateway, the key registry or the audit log is unavailable, nothing is sent: the matter falls back to fully local
When it returns
- Real names are substituted back inside your office, after the answer arrives
- The outside model saw [PATIENT_1] and never learned who that was
- The exchange is recorded in the matter’s audit log either way
Stated honestly: pseudonymisation lowers risk; it does not make data anonymous. That is exactly why fully local mode exists, and why it is the default posture for sensitive matters.
How your files are held
Security, in plain terms
One encrypted container per matter
Each case is its own sealed evidence box: mount it to work, unmount it to seal it. A lost or stolen drive is unreadable ciphertext.
Keys your database never sees
The key that opens a matter is itself wrapped by a key held in the machine’s security chip, released by your hardware security key.
An append-only audit log
Per matter: what was processed, when, by which model version. It cannot be edited afterwards — enforced by the database, not by an application setting.
Backups that are rehearsed
Encrypted, on the 3-2-1 pattern, with restores tested before you rely on them. The key that unwraps your matters is never inside the backup, so a stolen copy is inert.
Evidence you can hand over
The question “can you show this file never went anywhere?” has a one-page answer here — and the answer does not depend on trusting the software vendor.
Per-matter report
- States the confidentiality mode, the number of logged events, and any outbound transfers
- For a fully local matter, the answer is that no route out existed
- Printed and signed, it is the document you produce when the question is asked
The audit chain
- Each log entry is chained by hash to the one before it, computed by the database itself
- The application can add entries. It cannot alter or delete them.
- Removing or editing a past entry breaks the chain visibly
The anchor sheet
- A short sheet carrying the chain values as of that date, kept with the file
- It ties today’s report to a record made weeks earlier
- Without it, any log proves only that it agrees with itself
Practical requirements
What you need to run it
No data-centre, no cloud account, no per-seat licence to a service that holds your files. The equipment is yours, and you can unplug it.
| What | Detail | Note |
|---|---|---|
| The hub device | A desktop AI machine with 128 GB of unified memory | Sits in a locked room. Full solo-practice kit: under $8,000. |
| A room and a lock | Physical control of the device | Physical security is part of the design, not an afterthought |
| Office network only | Workstations reach the hub over your own network | In fully local mode no internet connection is required at all |
| Attorney workstations | Any current PC to start with | Purpose-built review workstations are announced but not yet shipping |
| A hardware security key | Per attorney, to unlock matters | Standard FIDO2 key |
| Installation | We install, verify and hand over | Including a rehearsed restore before you rely on it |
Getting started
We install the device in your locked room, verify it, rehearse a restore, and seal the key envelope with you present.
We run one of your closed matters through the pipeline end to end, so you can compare the output against work you already trust.
You open live matters, choosing the confidentiality mode for each one. We stay on support.
The one thing to test before you commit: ask us to run a matter you already know the answer to.
Limits, stated plainly
What LexVault does not do
- It does not practise law. It gives no legal advice, to you or to a client, and makes no judgement about a case. It is software, not a law firm, and creates no attorney–client relationship.
- It does not file, serve or send anything. There is no outbound path from the pipeline to a court system or a mail server.
- Verification is not infallible. It confirms a claim is supported by a verbatim quotation on a cited page; it cannot tell you the quotation is the whole story. Your review is the control, not a formality — and no outcome is guaranteed.
- OCR quality depends on the scan. A page a person cannot read is a page the system flags rather than guesses at.
- A local model is not always the strongest writer. That is precisely why hybrid mode exists — and why choosing it is your decision, per matter.
- Hybrid mode is not made safe by declaration. Pseudonymised data is still regulated data, and we say so on the section where we describe it.
A tool that claims no limits is telling you it has not looked for them. These are ours, in writing, before you buy. Use is subject to our Terms of Use and Privacy Policy.
Book a demo
Run a matter you already know
The strongest test we can offer is a falsifiable one: give us a closed matter where you already know the right answer, and compare.
- See the verification screen catch a planted error
- Walk the audit chain and the per-matter report
- Talk deployment in your own locked room
Prefer email? Write to hello@lexvault.associates. Raising or investing? See the investor overview.
Request ready
Thanks — we’ll be in touch to lock a time.