Software escrow vs a timestamp: what’s the difference?

Flat illustration of a glowing light bulb, a patent-style drawing and a set of gears, with a teal timestamp badge

Software escrow and a timestamp do different jobs. In an escrow arrangement, a developer deposits source code (and sometimes build instructions) with a neutral third party, and the agreement says when the code can be released to a customer, for example if the developer goes out of business. A timestamp doesn’t hold or release anything. It records that your exact files existed no later than a recorded time and still match their fingerprints. This is general information, not legal advice. Escrow agreements are contracts, so take advice before you sign one.

Table of Contents

What escrow is for

Customers who rely on software they don’t control worry about what happens if the supplier fails, stops support or changes direction. An escrow agreement is a way to address that:

  • The supplier deposits the source code and related materials with an escrow agent.
  • The agreement lists release conditions: for example, insolvency or a failure to support.
  • If a release condition is met, the agent releases the materials to the customer, who may then use them under the agreement’s licence.
  • Many agreements involve verification that the deposit is complete and builds.

The terms vary a lot. Read what the agreement says about what’s deposited, how often it’s updated and what the customer may do on release.

What a timestamp is for

A timestamp is about evidence of what existed when:

  • It shows that a snapshot of your code existed no later than a recorded time.
  • It shows the snapshot hasn’t changed since.
  • It isn’t a code repository. Your browser makes the fingerprint and the files stay on your device.
  • It can’t release anything to anyone.

Side by side

Escrow Timestamp
Holds a copy of the code with a third party Yes No
Releases code on set events Yes, by agreement No
Shows what the code was on a date The agent’s records of deposits may Yes, for the exact files
Needs a contract with several parties Yes No
Typical user Customers and suppliers of business software Developers and teams wanting a dated record

Using them together

They can complement each other. A supplier might timestamp each deposit snapshot, so both sides have a separate dated record of what was deposited. A customer might also keep a record of the version they licensed. A timestamp doesn’t make a deposit complete or buildable, and it doesn’t replace a verification service.

For developers who aren’t doing escrow

If you just need a dated record of your code at delivery, handover or open-sourcing, see prove source code existed before a date, freelance code delivery before payment and timestamp code before open-sourcing. For how it compares with version control, see git commit dates as proof and source code timestamping.

A snapshot routine

  1. Tag the release in version control.
  2. Zip a clean snapshot, with build instructions.
  3. Add the zip and a release note to one TimeBind. See how to timestamp a file.
  4. Keep the certificate with the release.
  5. If you have an escrow agreement, deposit as the agreement requires.

Frequently Asked Questions

  1. Is a timestamp a substitute for escrow?

    No. Escrow is about access to code on release events. A timestamp is a dated record.

  2. Does the escrow agent need my timestamp?

    Not necessarily. Some suppliers keep one as an extra record.

  3. Does a timestamp prove my code works?

    No. It shows when the exact files existed.

  4. Does timestamping share my code?

    No. Your browser makes the fingerprint and the files stay on your device. The certificate lists file names and any Reference or Details text, so keep those neutral.

  5. What does a TimeBind cost?

    Your first Pooled TimeBind is free, with no credit card required. After that, Pooled TimeBinds start from US$5, and an ASAP TimeBind is US$15. See plans and pricing

Date the snapshot you’d deposit

Free to start. The files stay on your device and your browser makes the fingerprint.

Last fact-checked: 10 November 2026.

Date your source code snapshot

Add a zipped snapshot of your code and a note of the version to a TimeBind. Your code stays on your device.

Make your first TimeBind free → See plans and pricing

Your first Pooled TimeBind is free, with no credit card required. After that, TimeBinds start from US$5, and an ASAP TimeBind is US$15. Your browser makes the fingerprint and the file stays on your device. A TimeBind shows a file existed no later than the recorded time. It doesn’t show who made it.