Software escrow exists to answer a reasonable fear: the supplier who built and runs your critical system goes out of business, and you are left with something you depend on and cannot maintain. An escrow agreement puts the source code with a third party who releases it to you if that happens.

The fear is legitimate. The instrument is frequently misunderstood, and the gap between the two produces agreements that cost money every year and would not help on the day they were needed.

The uncomfortable question to ask before signing: if the code were released to you tomorrow, could anybody actually run it? A deposit of source code with no build instructions, no infrastructure definition, no credentials for the third-party services it calls and no data is not a continuity plan. It is a folder. Escrow agreements that have never been verified routinely release exactly that.

What Software Escrow Covers

A three-way agreement between you, the supplier and an escrow agent. The supplier deposits material with the agent, the agent holds it, and defined release conditions determine when you receive it.

Release conditions are the part worth negotiating. Insolvency is the obvious one and the easiest to evidence. Others matter more in practice: the supplier ceasing to maintain the product, failing to meet support obligations, or being acquired by a competitor of yours. A narrow trigger list means the agent will refuse to release in exactly the ambiguous situations where you most want the material.

The deposit itself should be more than source. At minimum: build instructions specific enough to produce a running system, the dependency versions, the infrastructure configuration, documentation of external services and where credentials live, and a named technical contact. Without those, the source is close to worthless.

And the deposit must be updated. A copy taken at signature and never refreshed is an accurate record of software nobody runs any more.

Why Most Escrow Fails on Release

Because nobody checked.

The standard agreement is a legal document that assumes the technical content is fine. Escrow agents offer verification services that range from confirming the media is readable up to compiling the deposit and running it in a clean environment. The cheap end proves almost nothing. The expensive end is the only version that answers the question you are actually asking.

Common findings when a deposit is verified properly: it does not build without a tool nobody documented, it depends on a private package repository that will not exist after the supplier does, it requires credentials for services that were never listed, or it is simply an older version than the one running in production.

If you are going to pay for escrow, pay for verification. An unverified agreement transfers the feeling of risk without transferring the risk, and the cost difference is smaller than the cost of finding out at the worst moment.

The SaaS Problem

Traditional escrow assumes you would run the software yourself. For hosted software, that assumption usually does not hold.

Receiving the source code for a platform you accessed over the internet leaves you needing infrastructure, deployment tooling, operational knowledge and your own data, most of which is not in the deposit. Even with a complete package, standing it up takes weeks that a business dependent on the system rarely has.

Which is why the useful protections for hosted software are different. Data extraction rights matter more than code: a contractual right to a complete export in a documented format, exercised regularly rather than promised. A continuity commitment, where the supplier agrees to run the service for a defined notice period after termination, buys the migration time that code alone does not. A verified export you have actually tested is worth more than any deposit you have not.

For most hosted software, an escrow agreement is the wrong instrument bought out of habit, and the money is better spent on regular exports you have proven you can read.

What It Costs and Who It Suits

Escrow is an annual cost, typically running from a few hundred to a few thousand pounds a year depending on deposit size, number of beneficiaries and level of verification. Verification is charged separately and is where the meaningful spend sits.

It genuinely suits: systems where an interruption would materially damage the business, suppliers small enough that failure is a real possibility, on-premise or self-hostable software where you could plausibly run it, and situations where a regulator or a customer contract requires it.

It suits less well: hosted software where you would not run the code anyway, commodity systems with straightforward replacements, and small suppliers where the annual cost is a noticeable fraction of the contract value.

The alternative worth considering first is simply owning the code. If the work is bespoke and you commissioned it, negotiate assignment of the intellectual property and a copy of the repository at each release. That removes the need for an agent, and the technical due diligence points in our technical due diligence guide are the same ones that make such a handover usable.

Making It Work If You Do Buy It

Negotiate the release triggers rather than accepting the standard list, and include supplier abandonment as well as insolvency.

Specify the deposit contents in the agreement, not in a schedule nobody reads. Build instructions, infrastructure definition, dependency manifest, external service inventory, and a named contact.

Require updates at a defined interval or on each major release, and require evidence that they happened.

Pay for verification at the level where the agent builds and runs it, and read the report. A verification that found problems is doing its job.

And test your own readiness. If the material arrived tomorrow, who on your side would receive it, and what would they do first? An escrow agreement with no internal owner is an invoice, not a plan. The recovery thinking in our disaster recovery guide applies directly.

Mecanik has both deposited into escrow and helped clients assess whether they needed it, as part of our software development work. More often than not the honest answer is that the money buys more protection when spent on verified backups and clear IP ownership.

Frequently Asked Questions

What is software escrow? A three-way agreement between a customer, a software supplier and an escrow agent. The supplier deposits source code and supporting material with the agent, who releases it to the customer if defined conditions are met, most commonly the supplier becoming insolvent or ceasing to maintain the product.

Why do escrow agreements fail when released? Because the deposit was never verified. Common findings are material that will not build without an undocumented tool, dependencies on a private package repository that disappears with the supplier, missing credentials for external services, or a version older than what runs in production. Verification that compiles and runs the deposit is the only check that answers the real question.

Does software escrow work for SaaS? Poorly. Receiving source code for a hosted platform still leaves you needing infrastructure, deployment tooling, operational knowledge and your data, and standing it up takes weeks. Data extraction rights, a contractual continuity period after termination, and regularly tested exports protect a hosted service far better than a code deposit.

How much does software escrow cost? Typically a few hundred to a few thousand pounds a year depending on deposit size, number of beneficiaries and verification level, with verification charged separately. The verification is where the meaningful spend sits, and an agreement without it transfers the feeling of risk rather than the risk.

Is there an alternative to escrow? For bespoke work you commissioned, negotiating assignment of the intellectual property plus a copy of the repository at each release removes the need for an agent entirely. For hosted software, a documented export you have actually tested reading is usually worth more than any deposit you have not.