Software Escrow Agreement: Template and How to Draft One (2026)

What a software escrow agreement is and when you need one A software escrow agreement is a three party contract that protects a customer who depends on software they do not own the source code for. The software vendor deposits the source code, build instructions and other materials with a neutral third party, the escrow agent. The agent holds them and releases them to the customer only if an agreed event happens, usually the vendor going out of business or failing to support the software. The reason it exists is simple. A customer buys a licence to use the software as a compiled product, but the source code, the thing you would need to keep the software running or fix it, stays with the vendor. If the vendor disappears, is acquired and shuts the product, or stops maintaining it, the customer can be left running business-critical software that no one can repair. Escrow is the safety net. There are three parties: the vendor, also called the depositor or licensor; the customer, also called the beneficiary or licensee; and the escrow agent. The agent is the point of the arrangement, because a deposit the vendor simply promises to hand over is worth little. A neutral agent holding verified materials under agreed release conditions is worth a great deal. A growing variant is SaaS escrow. When the software runs in the vendor's cloud rather than on the customer's servers, source code alone may not help. SaaS escrow can also cover deployment scripts, cloud configuration, data and sometimes a plan to stand the service up elsewhere. Note which kind you need. This template is general information, not legal advice. Insolvency law affects whether a deposit survives a vendor's bankruptcy, and it varies by country, so confirm the local position before you rely on it. ## A software escrow agreement template you can copy ```

SOFTWARE ESCROW AGREEMENT Date: [date] Parties: [Vendor name], of [address] ("Depositor") [Customer name], of [address] ("Beneficiary") [Escrow agent name], of [address] ("Escrow Agent") 1. DEPOSIT MATERIALS The Depositor will deposit with the Escrow Agent, within [number] days and on each update, the following for [software name, version]: source code, build scripts, documentation, configuration, dependency list and third party licences, and [for SaaS: deployment scripts, infrastructure config]. The full list is in Schedule 1. 2. VERIFICATION The Escrow Agent / an agreed independent tester will verify the deposit on [level: file listing / compile test / full build and run test] within [number] days of each deposit, and report to the Beneficiary. 3. UPDATES The Depositor will refresh the deposit on each new release, and at least every [number] months, and confirm in writing that the deposit is current. 4. RELEASE EVENTS The Escrow Agent will release the Deposit Materials to the Beneficiary if any of the following occurs and is verified under clause 5: (a) the Depositor enters insolvency, liquidation or equivalent; (b) the Depositor stops carrying on business in the software; (c) the Depositor materially fails to meet its support or maintenance obligations under [the licence/support agreement] and does not cure within [number] days of notice; (d) [other agreed events]. 5. RELEASE PROCEDURE The Beneficiary sends the Escrow Agent a release notice with evidence. The Escrow Agent notifies the Depositor, who has [number] days to object. If there is no valid objection, or a dispute is resolved in the Beneficiary's favour under clause 9, the Agent releases the Materials. 6. LICENCE ON RELEASE On release, the Depositor grants the Beneficiary a [non-exclusive, non-transferable] licence to use, maintain and modify the Deposit Materials solely to support the Beneficiary's own licensed use of the software, and for no other purpose. The Beneficiary keeps all confidentiality duties. 7. CONFIDENTIALITY Each party keeps the Deposit Materials and the terms confidential. The Escrow Agent will not access or disclose the Materials except as this agreement allows. 8. FEES AND TERM Fees are payable to the Escrow Agent as set out in Schedule 2. This agreement runs while the underlying licence is in force, and may be ended on [notice], subject to any release already triggered. 9. DISPUTES AND GOVERNING LAW A dispute over a release is referred to [expert / arbitration] for a quick decision. This agreement is governed by the law of [place]. SIGNED by each party: ____________ Name/Title/Date for each Schedule 1: Deposit Materials Schedule 2: Fees and verification level

- Thin deposit list. Source code without build instructions, dependencies and config often cannot be compiled or run. Deposit everything needed to rebuild.
- Stale deposits. Without an update obligation and a cadence, the deposit drifts away from the live version until it is worthless.
- Weak release triggers. If the only trigger is formal insolvency, a vendor that simply abandons the product may never trigger a release. Add a maintenance failure trigger.
- Ignoring insolvency law. In some countries an administrator or liquidator can challenge the release or the licence. The agreement should be drafted to survive the vendor's insolvency, not assume it will. ## How jurisdiction changes things In India, enforceability on a vendor's insolvency should be checked against the Insolvency and Bankruptcy Code, 2016, because a resolution professional or liquidator controls the company's assets once a process begins, and the escrow structure needs to work around that. In the United States, the treatment of software licences and escrow in bankruptcy is shaped by specific provisions of the Bankruptcy Code that can protect a licensee's rights, which is why careful drafting matters. In the UK and EU, a well structured escrow with a genuine third party agent generally holds, but the licence granted on release should be clearly separate from the deposit so an insolvency practitioner cannot easily unwind it. Wherever you are, confirm that the arrangement survives the vendor's insolvency, because that is the exact moment it is meant to work. ## Keeping escrow, licence and support terms in step A software escrow agreement never stands alone. It hangs off a licence and a support agreement, and it refers to events, cure periods and obligations that live in those other documents. If the licence changes or the support terms are amended and the escrow agreement is not updated to match, the release triggers can point at obligations that no longer exist. That ongoing work, drafting the escrow terms against the licence they depend on, checking that a release trigger still matches the support obligation it references, editing the deposit list as the software grows, and keeping every version dated and linked, is the same tracking job companies face across a stack of connected contracts. It can live in one AI workspace tuned to how your company contracts, so the licence, the support terms and the escrow sit together and a change in one is easy to carry into the others. [Adira](https://adiralaw.com) is built around that single-workspace idea. For a single escrow deal the template above is enough on its own; the point worth keeping is that an escrow agreement only protects you if it stays consistent with the contracts it is bolted to.