Source code escrow is an arrangement where a neutral third party, the escrow agent, holds a copy of bespoke software's source code. The agent is contracted to release that code to the customer only if an agreed event occurs, such as the supplier going out of business or failing to meet its support obligations.
Why source code escrow exists
When you commission bespoke software, the running version you use day to day is the compiled program. The instructions a developer would need to fix bugs or make changes, the source code, are something else entirely. With most arrangements that source code sits with the supplier, not with you.
That is fine while the supplier is healthy. The risk appears if they go out of business, are bought out or simply stop supporting the product. You could be left running important software that nobody is able to maintain.
Source code escrow is the safety net for that scenario. A neutral agent holds a copy of the code so that, if the worst happens, your business can keep the software working.
How an escrow arrangement works
Escrow is a three-party arrangement. It involves you as the customer, the supplier who built the software and an independent escrow agent who holds the deposit. The terms are set out in an escrow agreement signed by all three.
The supplier deposits the source code with the agent and updates it as the software changes. The agent stores it securely and does nothing with it unless a release condition is triggered. Specialist providers such as NCC Group also offer to verify that the deposited code is complete and can actually be rebuilt, so the safety net is known to work before you ever need it.
A typical deposit is more than the code alone. It usually includes the build instructions, technical documentation and details of the tools or environment needed to turn that code back into working software.
Release events: when the code is handed over
The escrow agent only releases the code when a condition named in the agreement is met. These conditions are called release events, and they are negotiable commercial terms rather than a fixed list. Common ones include:
- Supplier insolvency: the supplier enters liquidation or administration or otherwise ceases to trade.
- Abandonment of the product: the supplier stops developing or supporting the software altogether.
- Failure to meet support obligations: the supplier materially breaches the maintenance or support commitments in the contract.
When a release event occurs, the agent verifies the claim and then hands the deposit to you. The agreement should also state what you may then do with the code: typically, a licence to maintain and fix the software for your own use, not to resell it.
Who owns the source code?
Escrow raises a question many buyers assume is already settled: who owns the code? It is a common and costly misunderstanding that paying for bespoke software automatically makes you the owner of it. In the UK, it usually does not.
Under UK copyright law the person who writes the code, the developer, is normally its first owner, even when a client has commissioned and paid for the work. The UK Intellectual Property Office's guidance on intellectual property confirms that ownership of commissioned work depends on the terms agreed in the contract.
So the contract has to say so explicitly. It should either assign the intellectual property to you outright, or grant you a clearly defined licence to use it. A statement of work or development contract that is silent on ownership is a real risk, and is exactly where escrow and IP terms belong.
When should an SME ask for escrow?
Escrow is not needed on every project. Weigh it against two things: how important the software is to your business and how much risk sits with the supplier.
It is worth asking for when the software is genuinely business-critical and the supplier owns the code rather than you. It matters most with a smaller supplier, where the chance of them ceasing to trade is a real consideration. If you own the code outright and already hold a copy, escrow may add little.
Either way, settle it early. Ownership, escrow and ongoing maintenance and support are far easier to agree before a contract is signed than after. They are commercial points to raise during scoping, alongside the pricing model for the work itself.
A good supplier will be straight with you about ownership Source-code ownership and escrow should never be a surprise late in a project. Red Eagle Tech sets out intellectual property terms plainly from the start of every bespoke software development engagement, so you know exactly where you stand. If you would like to talk through protecting an idea, the form below is the place to start.
