- When you licence software rather than buy the underlying code, you typically don't have access to the source code, only the compiled, ready-to-run version.
- A software escrow arrangement is typically a tripartite agreement — three parties, three roles: 1.
- - The vendor becomes insolvent, is placed into bankruptcy, or ceases business operations - The vendor discontinues the software and stops providing support or maintenance - The vendor…
If your business runs mission-critical operations on software licensed from a vendor — rather than software you own outright — you're taking on a quiet risk: what happens if that vendor disappears? A software escrow agreement is the tool businesses use to manage exactly that risk.
The Problem Escrow Solves
When you licence software rather than buy the underlying code, you typically don't have access to the source code, only the compiled, ready-to-run version. That's normal and usually fine, as long as the vendor is around to maintain, update, and support the product. But if the vendor goes out of business, gets acquired and discontinues the product, or simply stops honouring its support obligations, you can be left running critical software with no way to fix, update, or maintain it — and no legal right to the source code you'd need to do so.
Software escrow addresses this by having the vendor deposit a current copy of the source code with a neutral third party, to be released to you only if specific, pre-agreed trigger events occur.
How a Software Escrow Arrangement Works
A software escrow arrangement is typically a tripartite agreement — three parties, three roles:
- The vendor deposits the source code, and often related materials like build instructions and documentation, with the escrow agent.
- The escrow agent — an independent third party in the business of holding these deposits securely — verifies and retains the deposit, releasing it only if a defined trigger event occurs.
- The licensee (you) has a contractual right to receive the deposited materials if a trigger event happens, along with a pre-existing licence to actually use the source code once released.
Common Release Trigger Events
- The vendor becomes insolvent, is placed into bankruptcy, or ceases business operations
- The vendor discontinues the software and stops providing support or maintenance
- The vendor materially breaches its ongoing support or maintenance obligations and fails to cure the breach within an agreed period
- Other specific events the parties negotiate into the agreement
What Escrow Does Not Automatically Give You
- A guarantee the code is usable. Source code deposited long ago and never updated may not reflect the current version you're actually running. Look for a verification and update obligation requiring the vendor to periodically deposit current code and confirm it will actually build.
- The right to use the code without a licence. Escrow release gets you the code; it doesn't by itself grant you rights to use it. Your underlying software licence agreement needs a clause confirming your right to use released escrow materials for the purposes the escrow was meant to cover.
- The ability to maintain it yourself. Even with working source code in hand, maintaining unfamiliar software takes real technical capability. Escrow is a safety net, not a guarantee of a smooth transition.
Who Typically Needs Escrow
Escrow is most commonly used when a business depends heavily on software from a smaller, newer, or single-vendor provider, where the risk of the vendor disappearing is real — as opposed to software from a large, well-established vendor, where that risk is lower though not zero. It's a reasonable request to make part of negotiating any significant software licence for business-critical systems, and a reasonable vendor should be willing to discuss it.
Frequently asked questions
Who pays for a software escrow arrangement?
This is negotiated between the parties — sometimes the licensee bears the cost as the party requesting the protection, sometimes it's shared, and larger vendors sometimes offer escrow as a standard part of enterprise licensing. Costs vary by escrow agent and are not set by any government fee schedule, so get a quote directly.
Can I request escrow for any software licence, or only large enterprise deals?
You can ask for it in any negotiation, though a vendor's willingness — and the leverage you have to insist on it — usually depends on the size and importance of the deal. It's worth raising for any software your business genuinely couldn't operate without.
What happens to the escrowed code if the vendor is acquired rather than going out of business?
This depends on how the trigger events are drafted. A straightforward acquisition where the acquirer continues supporting the product usually wouldn't trigger release; discontinuation of the product after an acquisition typically would, if drafted as a trigger event.
Is escrow the same as owning the source code?
No. Escrow gives you a contingency right to receive the code if something goes wrong. It doesn't transfer ownership, and your rights to actually use released code depend on what your licence agreement says.
This is a corporate question
Start a file online — flat, published fees, reviewed by a licensed Ontario lawyer before a dollar is owed.