Software escrow is an arrangement where a software vendor deposits its source code and related materials with a neutral third party, called an escrow agent. The agent releases those materials to the customer only if specific events happen, such as the vendor going out of business or stopping support for the product.
It is a form of insurance. The customer gets a way to keep critical software running if the vendor disappears. The vendor keeps control of its code in every other situation.
Software escrow is sometimes called source code escrow or technology escrow. In a SaaS context, it is often referred to as SaaS escrow or cloud escrow.
Software escrow vs. transaction escrow
The word “escrow” means two very different things in software and acquisitions.
| Software escrow | Transaction escrow | |
| What is held | Source code, documentation, and deployment materials | Money (and sometimes assets) during a sale |
| Who it protects | A customer licensing software | Buyer and seller in a transaction |
| When it ends | Ongoing for the life of the license, or until a release event | At closing, once conditions are met |
| Typical use | Enterprise software contracts | Buying or selling a business, website, or domain |
If you are buying or selling a business and want to know how the purchase money is protected, you need transaction escrow, not software escrow. Acquire.com transactions can close through escrow so funds are released only when the agreed conditions are met.
The rest of this guide covers software escrow.
How software escrow works
A typical software escrow arrangement involves three parties:
- The depositor: the software vendor or developer
- The beneficiary: the customer or licensee
- The escrow agent: an independent company that holds the materials
The process usually follows five steps.
1. The parties sign a software escrow agreement
The agreement defines what will be deposited, how often it will be updated, what verification will happen, which events trigger a release, and what the beneficiary is allowed to do with the materials after a release.
Agreements can be two-party (vendor and agent, with customers added as beneficiaries) or three-party (vendor, customer, and agent negotiate one agreement).
2. The vendor makes a deposit
The deposit should include everything a competent developer would need to rebuild, run, and maintain the software, not just the code itself. That usually means:
- Source code for all relevant versions
- Build scripts, dependencies, and instructions
- Technical documentation
- Database schemas
- Third-party component and license lists
- For SaaS: deployment scripts, infrastructure configuration, and in some cases access to the hosting environment
3. The agent verifies the deposit
Verification ranges from a basic check that files are present and readable, to a full test build that confirms the code compiles and runs. Deeper verification costs more, but it is the only way to know the deposit would actually be usable.
4. The deposit is kept current
Software changes. If the deposit is not updated after new releases, the beneficiary may receive an outdated version in a release event. Agreements usually require deposits on a schedule or after major releases.
5. Release, if a trigger event happens
If a defined release condition occurs, the beneficiary requests release. The vendor typically has a short window to dispute it. If there is no valid dispute, the agent releases the materials.
Common release conditions
Release conditions vary by agreement, but common triggers include:
- The vendor files for bankruptcy or becomes insolvent
- The vendor stops doing business
- The vendor discontinues or stops supporting the product
- The vendor materially fails to meet support or maintenance obligations
- The vendor is acquired, and the new owner does not continue support (in some agreements)
Clear, objective triggers reduce disputes. Vague language like “failure to adequately support the software” is harder to enforce.
What is SaaS escrow?
Traditional source code escrow was designed for software customers installed on their own servers. If the vendor disappeared, the customer would have the code and the environment to keep it running.
SaaS is different. The customer does not run the software. The vendor hosts it. Getting the source code alone may not help if you do not have the infrastructure, data, and configuration to run it.
SaaS escrow arrangements try to close that gap. Depending on the provider and agreement, they can include:
- Regular deposits of source code and infrastructure configuration
- Backups or replication of the customer’s data
- Escrowed access credentials for the hosting environment
- A plan for keeping the service running for a transition period, sometimes funded in advance
SaaS escrow is more complex and usually more expensive than traditional escrow, but it is often the only meaningful protection for business-critical cloud software.
How much does software escrow cost?
Pricing varies by provider, the number of beneficiaries, the size and complexity of the deposit, and the level of verification. A basic arrangement with a simple deposit and minimal verification is usually priced as an annual fee. Full build verification, SaaS continuity services, and multiple beneficiaries add cost.
Who pays is negotiable. Customers often pay when they are the ones requesting escrow. Some vendors absorb the cost and offer escrow as a standard feature for enterprise customers.
When comparing providers, ask about:
- Annual fees and setup fees
- What each verification level includes
- Fees for deposit updates and release requests
- How SaaS environments are handled
- Where deposits are stored and how they are secured
Who needs software escrow?
Customers licensing critical software
Escrow makes the most sense when the software is hard to replace, central to daily operations, and supplied by a smaller vendor whose long-term stability is uncertain.
Software vendors selling to larger customers
Enterprise customers often require escrow as a condition of signing. Offering it proactively can shorten sales cycles and reassure risk-averse buyers.
Startups being asked for escrow
Early-stage vendors sometimes hesitate because escrow involves sharing source code with a third party. In practice, the agent does not release code without a valid trigger, and the deposit is stored securely. The bigger questions are cost and the operational burden of keeping deposits current.
Software escrow in a business acquisition
Software escrow comes up in acquisitions in a few ways.
Escrow agreements are a diligence item. If you are buying a SaaS or software business, ask whether it has escrow agreements with any customers. Review the release conditions carefully. A change of control or a change in support could, in some agreements, give customers rights to the code. Our guide to technical due diligence on a SaaS startup covers how to review code and contracts.
Existing agreements usually transfer. In an asset sale, customer contracts and any escrow agreements typically need to be assigned to the buyer. Both the escrow agent and the customer may need to consent. Plan for this in the asset transfer checklist.
Escrow can support a sale. A business with well-documented, buildable code is easier to diligence and easier to hand over. Keeping an escrow-quality deposit, even if no customer requires one, can make technical diligence smoother.
It is not a substitute for transaction escrow. The purchase price itself should move through transaction escrow. For how escrow protects the deal itself, see how escrow protects your startup acquisition.
Common software escrow mistakes
- Never verifying the deposit. Unverified deposits are often incomplete.
- Letting deposits go stale. An outdated deposit may not help in a release event.
- Vague release conditions. Ambiguity leads to disputes at exactly the wrong time.
- Escrowing code but not the environment. For SaaS, source code alone is rarely enough.
- Ignoring license rights after release. The agreement should say what the beneficiary can legally do with the materials, such as maintain and modify them for internal use.
- Forgetting escrow during an acquisition. Review change-of-control and assignment terms early.
Buying or selling a software business?
On Acquire.com, buyers can browse SaaS businesses for sale, review verified metrics after signing an NDA, and close through escrow. Sellers can list their SaaS business and prepare documentation, including any customer escrow agreements, before diligence begins.
Frequently asked questions
What is software escrow?
Software escrow is an arrangement where a software vendor deposits its source code and related materials with a neutral escrow agent. The agent releases them to the customer only if specific events occur, such as the vendor going out of business or ending support.
What is a software escrow agreement?
A software escrow agreement is the contract between the vendor, the escrow agent, and usually the customer. It defines what is deposited, how often deposits are updated, how they are verified, what triggers a release, and what the customer can do with the materials afterward.
What is the difference between software escrow and regular escrow?
Software escrow holds source code and technical materials to protect a software customer over time. Regular transaction escrow holds money during a sale and releases it once agreed conditions are met, usually at closing.
What is SaaS escrow?
SaaS escrow extends software escrow to cloud-hosted software. In addition to source code, it can include infrastructure configuration, data backups, hosting access, and continuity services to keep the application running if the vendor fails.
How much does software escrow cost?
Costs depend on the provider, number of beneficiaries, deposit complexity, and verification level. Basic arrangements are usually priced as an annual fee, while full build verification and SaaS continuity services cost more.
Who pays for software escrow?
It is negotiable. Customers often pay when they request escrow, but some vendors include it as a standard feature for enterprise contracts.
Do I need software escrow when buying a SaaS business?
Not usually for the purchase itself, since the buyer receives the code and assets at closing. But buyers should review any existing customer escrow agreements during diligence, because they may need to be assigned and may include change-of-control terms.














