Pre-release design-partner program for litigation firms
Turn one case file into a chronology your lawyer can verify
A supervised, page-pinned chronology inside an environment your firm controls.
Under Seal is in validation. It registers an authorized PDF set, makes coverage gaps visible, and keeps every proposed event in a human review queue. It does not provide legal advice or replace lawyer review.
The three facts under all of this
- The firm procures and owns compatible hardware; Under Seal never takes title to it.
- The current pilot boundary is one authorized matter, local PDF intake, page-level coverage, supervised chronology review, receipts, and attorney-gated export.
- Roadmap desks, customer outcomes, certified hardware, and universal compliance claims are not part of the current offer.
Synthetic demonstration — not a client matter or customer result
This illustrates the review record. Each operator-entered example line identifies its asserted source page. Configured failures remain visible and block export until a person resolves them. Structured model-generated chronology proposals are not a released workflow.
“Unit 12 departed scene 1652 hrs with one patient, restrained, complaining of neck and lower back pain.”
“On duty 0600. Off duty 1710. Total on duty this period: 11:10.”
This is one of the citations ChatGPT invented in Mata v. Avianca, the filing that drew $5,000 in sanctions. It is in our test set on purpose.
Illustrative export state: blocked. One claim is unsupported, so this synthetic draft would remain blocked until a person resolves it. Signing does not override the configured failure.
What we can prove today
15,045,616
Real citations it checks against. Our own count, 8 August 2026.
0
Real cases wrongly flagged in that run. We have not measured the other direction: it can confirm a citation exists, but cannot always prove one does not.
0
Customers. That is why there are no logos on this page.
Our own measurement, not a third party’s. Version one does not check whether a case is still good law. Everything above is what we can show today, including the parts that do not flatter us.
Local by design, verified at deployment
We don’t want your files. We won’t even sell you the computer.
The firm owns the environment. Under Seal supplies software, installation, training, verification, and support for the approved configuration.
The hardware purchase stays with the firm
The firm will buy supported hardware directly from the manufacturer or through its IT provider after the release candidate has a measured, approved specification. Under Seal never takes title, marks it up, or finances it.
Your paralegal signs off, not the software
A proposed chronology enters the matter file only after review. Export requires configured checks and named-human approval.
Local does not mean automatically secure or compliant
Identity, disk encryption, physical access, backups, updates, support, retention, incident response, and firm-specific legal review still have to be configured and verified before a pilot.
Three things, in this order
The architecture, the evidence, and the commercial boundary. Each one has a corresponding verification step in the Reference Center.
The firm controls the environment
Core matter processing runs on firm-controlled hardware through a loopback-only inference client.
There is no hosted-model fallback or product telemetry path in the core workflow. Backup, support, updates, remote access, and physical security are separately reviewed at deployment. Local is the boundary; the deployment receipt is the proof.
It shows its work
Every proposed factual line identifies the source document and page a reviewer must inspect.
A receipt records the document version, source locator, checks performed, coverage gaps, review decision, and export state. It does not declare the source true or the legal conclusion correct. The lawyer still verifies the work.
The ownership boundary is written down
The firm buys and owns the machine. Under Seal licenses the software and supports a documented configuration.
The pilot agreement defines the license, pricing, support, export, cancellation, and removal procedures. Under Seal does not sell, finance, mark up, or take title to the firm's hardware.
The questions we get
The practical questions a firm should resolve before considering a pre-release local-software pilot. If yours is not here, it reaches a person.
Ordinary email only. Do not include client, matter, medical, document, or privileged information.
See whether one matter is ready for a controlled pilot.
Start with firm-level facts only. We will identify the missing approvals, supported environment, evaluation packet, and stop conditions before any client material is discussed.
Request a pilot readiness reviewDo not submit a client name, matter detail, medical fact, document, or other confidential information through this website.