How it works

Connect once.Then it runs on its own.

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

  1. 01

    Connect the repository

    Vendor

    The vendor grants read access to the repository. Nothing else, and nothing to upload by hand.

  2. 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.

  3. 03

    Checksum & record

    Machine

    Each version gets a SHA-256 and an entry in an append-only log that hashes the entry before it.

  4. 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
  1. Deposit #412 sealed · a3f91c2Machine
  2. SHA-256 recorded · 9f2b…4e92Machine
  3. Log entry chained to #2,113Machine
  4. Licensee recomputed hash — matchLicensee
  5. Release request — evidence under reviewLawyer decides
  6. Next depositMachine

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