Bailment Bailment demo
What the tech does

Hashes Go Out. Files Stay In.

Demo. The crypto runs in your browser. The appliance, the registry and the chain are planned, not built.

Bailee architecture flow The client portal and the firm portal both reach the firm-owned appliance. The appliance drives the shared AI thread, the template and vault store with matter vectors, and queries the public corpus on Bailment GPUs. From the store, a blinded period root goes to the Client Communication Protocol on one shared contract, and a deliberate per-document commitment goes to Document Record on a per-matter contract. Document Record settles on Cardano level one in USDM or ADA. Client portal BROWSER Firm portal VPN OR mTLS Appliance FIRM-OWNED GPU Shared AI thread ATTRIBUTED, ADOPTED Templates + vault + MATTER VECTORS Public corpus BAILMENT GPUs Client Communication Protocol ONE SHARED CONTRACT Document Record PER-MATTER CONTRACT Cardano L1 USDM / ADA PERIOD ROOT PER DOC, DELIBERATE PLANNED — NOTHING HERE IS DEPLOYED YET
Boxes are planned. The two demos below are real code.

Hash One Document

Pick any file. See what would go out, and what stays.

Loading…

Batch a Period

Many documents, one root. The root never says how many.

Loading…

The detail is in the plan →