Drafting a software escrow agreement
A software escrow agreement deposits source code, build instructions, and documentation with a neutral agent. On a defined release event — typically insolvency or sustained support failure — the licensee can recover the materials to continue using the software.
This is an 8-step workflow for drafting a tripartite software escrow agreement between vendor, licensee, and escrow agent that defines release events and deliverables.
Before you start
- Executed or draft software licence agreement
- Selection of escrow agent (Iron Mountain, NCC Group, or equivalent)
- Technical inventory of the deposit materials
- Agreement on release events and verification regime
The workflow
Define the deposit materials
Specify source code, build scripts, third-party library lists, configuration files, documentation, and credentials sufficient for a competent engineer to rebuild the product.
Set the release events
Define clear release events — vendor insolvency, administration, liquidation, breach of support obligations persisting beyond a cure period, or cessation of business.
Draft the verification regime
Include an annual verification procedure — directory listing, build verification, or full end-to-end rebuild — so the licensee knows the deposit is usable.
Address ipso facto stay
The ipso facto stay means insolvency-triggered release events may be unenforceable in some scenarios. Draft release events around breach of support obligations rather than solely insolvency.
Draft the licence on release
Specify the licence granted on release — typically perpetual, non-exclusive, for internal use only, with rights to modify and maintain but not to distribute externally.
Negotiate with the escrow agent
Engage an independent escrow agent. Review the agent's standard terms for fees, notice periods, and dispute handling between vendor and licensee on release claims.
Execute and lodge the deposit
Execute the tripartite agreement. The vendor lodges the initial deposit with the agent and a confirmation receipt is issued to all parties.
Schedule updates and audits
Set a cadence for updated deposits (each major release) and annual verification. Calendar the obligations so they do not lapse.
What you will have at the end
An executed escrow agreement with deposit lodged, giving the licensee contractual and practical ability to continue using the software if a release event occurs.
Common issues
- Deposit materials that are inadequate to actually rebuild the product
- Release events drafted around insolvency only, caught by the ipso facto stay
- No verification regime, so the deposit degrades in value over time
- Licence on release that is too narrow to be practically useful
- Agent fees that escalate without a cap
Run this workflow on a real matter
Quillio drafts software escrow agreements with release events calibrated around the ipso facto stay and a practical licence on release. See /practice-areas/commercial-lawyers.
This workflow is a general guide. Escrow is a backstop, not a substitute for vendor diligence or a true multi-vendor procurement strategy.
Try this workflow with Quillio.
Quillio can run this workflow on a real matter, with citations to current AU authority on every step. The free trial requires no credit card.
Start your free trial