Software escrow (source code escrow)
Definition
Software escrow, also called source code escrow, is an arrangement where a software vendor deposits its source code with a neutral agent. The agent releases the code to a named customer if agreed events happen, such as the vendor going out of business. It protects the customer, and it is separate from payment escrow.
Software escrow, also called source code escrow, is an arrangement between three parties. A software vendor deposits its source code with a neutral agent. A customer who relies on that software is named as the beneficiary. If one of a list of agreed events happens, the agent releases the code to the customer so they can keep the software running.
Not the same as payment escrow
The word causes confusion in a sale. Escrow in a business sale means the buyer's money is held by a third party until the assets have moved. On Indiemaker that runs through Escrow.com. Domain escrow is the same idea applied to a domain name.
Software escrow holds code, not money, and it exists to protect a customer of the software, not the buyer of the business.
What software escrow means at this size
Most small online products have no escrow arrangement at all. Someone paying $15 a month for a tool does not ask for one. It comes up when a small vendor sells to a larger organisation whose procurement team worries, reasonably, about depending on a one-person company. They ask for the code to be placed in escrow as a condition of signing.
A typical agreement sets out:
- what is deposited, and how often the deposit is updated
- the release events, such as the vendor ceasing to trade or failing to maintain the software
- what the customer may do with released code, usually use and maintain it for themselves only
- who pays the agent
Terms and fees vary by provider. If you need to know them, read the provider's current agreement.
Where it bites in a sale
If you are buying a business that has an escrow agreement in place, three questions follow.
- Does the sale itself trigger a release? Some agreements treat a change of ownership or an assignment of the software as a release event, or require the customer's consent. Read the clause before the transfer, not after.
- Does the obligation come with the business? If the customer contract moves to you, the duty to keep the deposit current probably does too.
- Is the deposit real? A deposit made three years ago and never updated protects nobody, and may put the seller in breach of the customer contract already.
There is a wider point about the code. A release under escrow gives a customer a copy of the source and a limited right to use it. Check that this sits properly with the IP assignment you are relying on to own the code outright.
The reverse case also matters. If the product you are buying depends on licensed software from another vendor, ask whether the seller is a beneficiary of an escrow arrangement for it, and whether that benefit can pass to you.
Why it matters when you acquire
A software escrow agreement is a sign that at least one customer is large enough to have asked for it. That is worth knowing for its own sake, and for what it says about customer concentration. Ask in due diligence whether any customer contract requires escrow, and get the agreement itself. This is general information, not legal advice, and the clauses are worth a lawyer's reading.
Related: escrow, domain-escrow, ip-assignment, due-diligence
See what a business at this level is listed at.
Everything on sale between $50,000 and $150,000, on the same fields.