Skip to content

Use cases

Where it fits, and where it doesn't 

Six workstreams where Vaultr is intended to be used, each with the processing mode we would run it in and the honest boundary of what it does not replace. A use-case page that hides the last row is selling; this one isn't.

6 workstreams · mode named for each

01Local

Due diligence first pass

A data-room bundle lands; the first pass over thousands of pages — change-of-control, assignment, termination, indemnities — runs against the local index with every finding carrying its citation.

  • Findings graded and span-linked, ready for counsel verification
  • Nothing about the target's documents leaves the firm's machine
  • The review memo assembles from accepted findings, with sources intact

Doesn't replace — It does not replace the judgement calls — materiality, deal context, commercial appetite stay with the deal team.

02Local

Contract review and redlining

Clause-by-clause review against your playbook. Deviations are proposed with the conflicting spans shown; counsel accepts, edits or rejects at the checkpoint.

  • Playbook-consistent proposals with page-and-line citations
  • Conflicts between clauses surfaced with both spans attached
  • Every accepted change recorded in the evidence ledger

Doesn't replace — It does not negotiate. Positions, concessions and the phone call to the other side remain human work.

03Local

Precedent-grounded drafting

First drafts — letters, clauses, summaries — assembled from the firm's own precedents and the matter bundle rather than a blank page or a public model.

  • House voice, because the corpus is yours
  • Sources panel behind every draft, same as review findings
  • Edits by counsel recorded — the draft and the human outcome are both on the ledger

Doesn't replace — It does not invent precedent. What is not in the corpus is not drawn on — which is the point.

04Local

Matter interrogation

“What terminates this without notice?” — asked in plain language against the matter, answered with the span that supports it, or a stated not-found.

  • Client calls prepared in minutes, clause references in hand
  • Refusal behaviour you can test: no span, no assertion
  • Sessions and relied-on answers can be written to the matter's ledger

Doesn't replace — It answers from the indexed documents only — outside knowledge is not smuggled in, in local mode.

05Firm endpoint

Knowledge reuse across matters

A firm's accumulated matters become queryable without any of them leaving the building — the endpoint runs on infrastructure the firm controls.

  • Prior art found by meaning, not filename
  • The boundary stays the firm's: your host, your logs, your access rules
  • Per-matter records keep reuse attributable

Doesn't replace — It requires the firm to run and govern the endpoint — Vaultr operates no server for this mode by design.

06External provider, explicit

Sensitive matters needing frontier capability

When a matter genuinely needs a larger model than the device can run, the external mode names the provider, shows what will be transmitted, and waits for explicit opt-in.

  • A decision about disclosure made visibly, once, per matter
  • The provider you name — not a silent default
  • Local-first discipline intact everywhere else

Doesn't replace — It is the one mode where material leaves the device. If that is unacceptable for a matter, the mode is not for that matter.

07

See it before you believe it