How it works
Connect once.Then it runs on its own.
Four steps, three parties, one record that none of them can rewrite.
- 01
Connect the repository
VendorThe vendor grants read access to the repository. Nothing else, and nothing to upload by hand.
- 02
Daily deposit
MachineEvery day — or on every release tag — 42escrow takes a copy, bundles it and encrypts it with its own data key.
- 03
Checksum & record
MachineEach version gets a SHA-256 and an entry in an append-only log that hashes the entry before it.
- 04
Release by procedure
Lawyer decidesIf an agreed trigger event occurs, evidence is reviewed and the release approved. Only then does the licensee receive the code.
Example · deposit log
helios-core · Vendor ↔ Licensee
Daily at 02:00 UTC · retention 7 years
- Deposit #412 sealed · a3f91c2done · 02:02Machine
- SHA-256 recorded · 9f2b…4e92done · 02:02Machine
- Log entry chained to #2,113done · 02:02Machine
- Licensee recomputed hash — matchdone · 09:41Licensee
- Release request — evidence under reviewwaitingLawyer decides
- Next depositplanned · 02:00Machine
Whose move
42escrow
Evidence review for the release request.
Rule
Two-officer approval
No single person can release code.
Already have an escrow clause?
Then only the implementation is missing. Send it over and we'll tell you what it takes.
Get in touch