Skip to content
97.5% of teams see value from GC AI before month oneSee how
Back To All Clauses

Software Escrow Clause

Requires a software vendor to place source code with a neutral escrow agent for release after defined failure events.

Reviewed by GC AI Solutions Team•Updated August 2026

Definition

A software escrow clause, also called a source code escrow clause, requires a software vendor to deposit a current copy of its source code, build instructions, and related materials with a neutral escrow agent, and sets the conditions under which that code is released to the customer. The customer licenses object code in the ordinary course and never receives the source, so the escrow exists for one scenario: the vendor fails, and the customer still depends on the software. Release is tied to defined trigger events, typically the vendor's bankruptcy, insolvency, discontinuation of the product, or failure to meet its maintenance and support obligations. A well-drafted clause also fixes what gets deposited, how often the deposit is refreshed, who verifies that it builds, and what license the customer receives in the released code.

  • Requires the vendor to deposit source code, build scripts, and documentation with an escrow agent
  • Releases the materials to the customer only on defined trigger events
  • Ties triggers to vendor bankruptcy, insolvency, abandonment of the product, or failure to support it
  • Sets how often the deposit is refreshed and whether a third party verifies that it builds
  • Grants the customer a license to use and maintain the released source code for its own continuity

Section 365(n) of the U.S. Bankruptcy Code lets a licensee keep using licensed intellectual property even when a bankrupt vendor's trustee rejects the contract, and well-drafted escrow agreements are written as "supplementary agreements" so the release survives the bankruptcy it is meant to protect against.

What It Does

A software escrow clause answers a single question: if the vendor disappears, can you keep running the software your business depends on? You license the application, but you do not own or possess the source code, so a vendor bankruptcy can strand a system you cannot maintain, patch, or migrate. The escrow places the source code in a neutral party's hands and defines the events that release it to you. For in-house counsel, the protection lives in three places, and they have to be read together. The first is the deposit: what code, documentation, and build tools are actually held, and how often they are updated. The second is the release triggers: the precise events that hand you the code. The third is verification: whether anyone has confirmed the deposit compiles into the software you run. A practical test: if the vendor filed for bankruptcy tomorrow, trace the path from that filing to working code in your hands, and note every step where a stale deposit or a narrow trigger breaks the chain.

When You'll See It

The software escrow clause appears in enterprise software licenses, SaaS and on-premise agreements, technology development and OEM deals, and outsourced platform contracts where the customer's operations depend on software it does not control. It is most common, and most heavily negotiated, where the software is business-critical and hard to replace: ERP systems, payment and trading platforms, embedded industrial software, and core infrastructure. The larger and more dependent the customer, the more leverage it has to demand escrow, which is why enterprise vendors often carry source-code escrow obligations specifically for their largest accounts.

SaaS complicates the classic model. For cloud-hosted software, raw source code is often useless without the vendor's hosting environment, configuration, and data, so modern SaaS escrow increasingly covers a deployable copy of the running environment rather than code alone. It matters most where switching costs are high and downtime is expensive, such as a manufacturer running vendor software on a production line or a bank running a licensed core system. The deeper the dependency, the more the escrow is doing.

Examples

Symbotic LLC / GreenBox Systems LLC

Master Services, License and Equipment AgreementBankruptcy-triggered release2023
"The Parties further agree that in the event that any bankruptcy proceedings are commenced by or against Symbotic under the Bankruptcy Code, Customer shall be entitled to retain and enforce its rights under the Source Code Escrow Agreement."
Source

Serve Operating Co. / Magna New Mobility USA, Inc.

License and Services AgreementRelease triggers: uncured breach and escrow lapseMutual2024
"Serve, or its successors or assigns, materially breaches its obligations under this Agreement or the Source Code Escrow Agreement, and fails to cure such breach within sixty (60) days upon receiving notice thereof; or [...] the Source Code Escrow Agreement terminates due to breach by Serve, or its successors or assigns, and is not replaced within thirty (30) days with another escrow agreement reasonably acceptable to Magna..."
Source

E2open Parent Holdings, Inc. / WiseTech Global

Agreement and Plan of MergerSource-code escrow as a top-customer obligation2025
"Source Code Escrow Obligations relating to material Company Group Software licensed to any customer who, in the fiscal year ended February 28, 2025 was one of the ten (10) largest sources of revenues for the Company Group, taken as a whole, based on amounts paid or payable..."
Source

Negotiate

If you're the customer:

You want a release you can actually use

  • Tie release to broad, objective triggers: bankruptcy, insolvency, ceasing the business, and failure to provide contracted support or maintenance.
  • Require the deposit to be updated on a fixed schedule and at every major release, not just once at signing.
  • Insist on verification, so an independent party confirms the deposit compiles and includes build tools and documentation.
  • Secure a perpetual license to use, modify, and maintain the released code for your own continuity.
  • Draft the escrow as an agreement supplementary to the license under Section 365(n), so a bankruptcy trustee cannot strip your access.

If you're the vendor:

You want to protect your code

  • Narrow the triggers to genuine failure events and exclude ordinary disputes or alleged breaches.
  • Limit the released license to internal maintenance of the licensed version, with no right to distribute or compete.
  • Require the customer to bear the escrow agent's fees and any verification costs.
  • Resist depositing build environments or keys beyond what is needed to maintain the specific release.
  • Add a redeposit-and-return mechanism if a release event is later cured.

A software escrow is only as good as its triggers and its freshness. Code released years out of date, or never verified to build, protects nobody.

Red Flags

  • Release triggers so narrow that real vendor failure, such as quietly discontinuing support, never releases the code.

  • A deposit made once at signing and never updated, so the escrowed code no longer matches the version you run.

  • No verification, leaving you to discover at release that the deposit does not compile or is missing build tools.

  • A released license limited to “viewing” the code, with no right to modify or maintain it.

  • An escrow not structured to survive the vendor's bankruptcy, which is the event it most needs to withstand.

Software Escrow Clause FAQs

What is a software escrow clause?
A provision requiring a software vendor to deposit its source code with a neutral escrow agent, to be released to the customer only on defined failure events such as the vendor's bankruptcy or discontinuation of the product.
What is the difference between a software escrow and a source code escrow?
They describe the same arrangement. Source code escrow names what is deposited, and software escrow names the broader package, which can also include build tools, documentation, and, for SaaS, a deployable copy of the environment.
What triggers the release of source code from escrow?
The events the clause defines, most commonly the vendor's bankruptcy or insolvency, ceasing to do business, discontinuing the product, or a material, uncured failure to provide support and maintenance.
What should be deposited in a software escrow?
The current source code, plus the build scripts, compilers, configuration, and documentation needed to recreate the running software. A deposit of code alone, without build tools, is often unusable.
Is a software escrow enforceable if the vendor goes bankrupt?
Generally yes when it is drafted correctly. Section 365(n) of the U.S. Bankruptcy Code lets a licensee retain its intellectual property rights even if the trustee rejects the license, and escrow agreements are commonly written as supplementary agreements so the release survives.
Do I need a software escrow clause for SaaS?
Often, but the classic model needs adapting. For cloud-hosted software, source code alone may not let you run the service, so SaaS escrow increasingly covers a deployable instance of the environment and data, not just the code.

Related Clauses

This content is for informational purposes only and does not constitute legal advice.