How it works

Connect once.Then it runs on its own.

Four steps, three parties, one record that none of them can rewrite.

Sixty seconds on how this works.

Why the usual sealed copy is worth less than it looks, and what a deposit looks like when somebody checks it every day.

01
Connect the repository
Vendor
The vendor grants read access to the repository. Nothing else, and nothing to upload by hand.
02
Daily deposit
Machine
Every day — or on every release tag — 42escrow takes a copy, bundles it and encrypts it with its own data key.
03
Checksum & record
Machine
Each version gets a SHA-256 and an entry in an append-only log that hashes the entry before it.
04
Release by procedure
Lawyer decides
If 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

intact

Whose move

42escrow

Evidence review for the release request.

Rule

Two-officer approval

No single person can release code.

Release procedure

Application 0041-R1

Ground: support discontinued

Objection period running

9 of 14 calendar days remaining

A bare denial is not an objection.

No step here is at the Escrow Agent's discretion.

Example — names, hashes and figures are invented.

Then only the implementation is missing. Send it over and we'll tell you what it takes.