CourtChain

A record that cannot be quietly rewritten.

Behind every sealed bundle is CourtChain: a write-once evidence record kept in your own storage. Once a record is written, it cannot be edited or deleted, and any attempt to alter it shows.

How the record holds

Written once. Readable always. Rewritable never.

STEP 1The bundle is sealedThe finding, its checks and its custody path are closed into one file.
STEP 2A fingerprint is takenA SHA-256 hash: change one character in the file, and the fingerprint no longer matches.
STEP 3It is written onceStored in your write-once storage. From that moment it can be read, never edited or deleted.
Your bucket, your keysStored in your own object storage. We can append. We cannot delete. Your auditors can read.
Signed twiceEd25519 and ML-DSA-65 on every record. Both must verify.
Dated by a strangerAn independent RFC 3161 time authority stamps the seal, so the date is not ours to claim.
Held for the look-backObject Lock in compliance mode is recommended, aligned to the CMS audit look-back period.
Verify a record

Don't take our word for it. That is the point.

Paste a sealed bundle and check it yourself. The verifier runs entirely in your browser, makes no network calls, and needs no login or key. Save the page, and it still works years from now, offline.

  • 1Classical signature, Ed25519
  • 2Post-quantum signature, ML-DSA-65
  • 3Independent timestamp anchor
Ed25519waiting
ML-DSA-65waiting
RFC 3161 timestampwaiting
What you paste stays on this page. Public keys can check a signature; they cannot create one.

Evidence that legal can defend and procurement can approve.

Organized for FRE 902(14) self-authentication. Admissibility is always the court's decision.

Talk to our team