Private Contract Vault
Contracts you can prove were in force — version by version, seal by seal.
The problem
/ 01Contracts are high-stakes documents that get amended, superseded, and disputed. Knowing which version was in force — and proving it wasn’t altered — matters in negotiations and disputes.
What it does
/ 04Seals contractual documents with immutable audit trail.
Unseals evidence for review under NDA.
Supports chain-of-custody tracking for compliance.
Lists version history and contract IDs.
Private pilot adds
/ pilotPilot-ready: durable contract-vault store available under NDA with a /v1 API for private pilots. The public studio card runs against /demo (ephemeral).
Who it’s for
/ 03- Legal teams managing agreement lifecycles
- Finance and operations tracking executed contracts
- Organizations that need tamper-evident version history
In context
/ 01The contractual sibling of the Regulatory Evidence Locker — same sealing discipline, different document class.
Spec & limits
/ limits| Interface | Input limits | Output artifact | Failure mode | Non-claim |
|---|---|---|---|---|
Studio ephemeral /demo; pilot durable /v1 on your infrastructure. | TBD — verified in pilot acceptance | TBD — verified in pilot acceptance | TBD — verified in pilot acceptance | TBD — verified in pilot acceptance |
Related guide
/ guideSee the sealed contract storage guide for a deeper problem walkthrough and verification notes — evaluation notes for the live demo and for a private pilot. Also: try the live experiment and read the product overview.
Frequently asked questions
/ 0501 How do you prove which contract version was in force on a date?
Each version is sealed with a timestamped receipt; to prove history you replay the chain and the registry confirms the active version for any date.
02 What makes a contract "sealed" — encryption, hashing, or both?
Sealing applies an integrity hash and a signed receipt; encryption is optional and applied per policy — the guarantee is tamper-evidence, not just secrecy.
03 Can two parties exchange signed versions without a shared database?
Yes — each party seals and receipts its own copy; signature verification and the hash chain let both prove the version history independently.
04 How is version history audited after the fact?
The version chain is hash-linked; an auditor walks the chain and checks each seal + receipt without needing the originating database.
05 Is the vault itself hosted, or run on my infrastructure?
Run on your infrastructure — the vault, the registry, and verification all run under your control with no required cloud dependency.