MKB Juristen drafts custom legal documents
It is best not to cobble together or copy important contracts, terms and conditions, and other legal documents yourself. We help entrepreneurs on a budget with customized legal solutions, clear costs upfront, and practical explanations.
- Custom contracts, terms and conditions, and legal documents
- Budget-friendly and clear about the costs upfront
- Request a free consultation or a no-obligation quote
What is a source code escrow agreement? It is an agreement between three parties (the software supplier, the customer, and an independent escrow agent) whereby the source code of software is deposited with a neutral custodian, so that the customer receives that code under pre-agreed conditions if the supplier ceases operations. Normally, the customer purchases only a right to use the working software, not the underlying source code. Escrow bridges that risk: if the supplier goes bankrupt or ceases maintenance, the deposited code is released and the customer can continue the software themselves.
The short answer
- A source code escrow agreement places the source code with an independent custodian (escrow agent).
- The customer simply uses the software; the source code remains protected until an agreed event.
- That event (release trigger) is usually bankruptcy or the cessation of maintenance by the supplier.
- Only then does the customer gain access to the code, with a right of use to maintain the software.
- The goal is continuity: the customer is not left with unusable software.
What exactly is a source code escrow agreement?
With standard software, the customer receives a license for the compiled, working version. The source code (the readable programming instructions used to build and modify the software) remains with the supplier. This is logical: that source code is the software supplier's business capital and is protected by copyright as a work within the meaning of Article 10, paragraph 1, sub 12 of the Copyright Act. As long as the supplier continues to exist and provides maintenance, the customer does not need that source code.
The problem arises when the supplier goes bankrupt. Without source code, no one else can repair the software, patch security vulnerabilities, or adapt it to new legislation. For business-critical software (such as a planning system, an accounting package, or an operating system in a machine), this is a real business risk. The source code escrow agreement solves this by storing the code with a third party, with a clear arrangement regarding when and how it is released.
The three parties and their role
- The supplier remains the owner of the copyright to the source code and deposits a current version with the escrow agent, with updates in new releases.
- The customer. Pays (often) for the escrow arrangement and receives assurance that he can continue in the event of a disaster. He may only use the code after a valid release.
- The escrow agent. An independent custodian who securely stores the code, verifies that the deposits are complete, and checks the release conditions before releasing anything.
The independence of the agent is the core. If the supplier were to retain the code themselves, the buyer would have nothing in the event of bankruptcy: the bankruptcy trustee would manage the estate, and the buyer would be at the back of the queue.
When will the source code be released?
The release is linked to a release trigger that you clearly define in advance. Common triggers are:
- Bankruptcy or suspension of payments of the supplier.
- The cessation of business activities or dissolution of the supplier.
- The systematic failure to comply with maintenance obligations, despite a notice of default.
In the event of bankruptcy, timing is legally crucial. Pursuant to Article 37 of the Bankruptcy Act, the trustee determines whether ongoing reciprocal agreements are to be fulfilled; consequently, maintenance and support may cease. Furthermore, for long-term agreements such as licenses, there is an option for early termination comparable to the tenancy provision of Article 39 of the Bankruptcy Act. Precisely for this reason, the escrow agreement must be drafted in such a way that the right to use the released source code holds up against the trustee. A well-drafted arrangement ensures that the purchaser is permitted to continue with maintenance after the release, without the trustee being able to reclaim the code.
A practical example
A logistics SME relies entirely on a route planner from a small software supplier. That supplier goes bankrupt. Without escrow, the company would grind to a halt: the software still works, but no one can modify it if an error arises or if a connection with a carrier changes. Because there was a source code escrow agreement, the escrow agent releases the source code after verifying the bankruptcy. The company engages another software firm that takes over the code and continues maintenance. Business operations continue.
What does escrow not handle?
Escrow is no guarantee that the software is error-free and is no substitute for clear agreements regarding maintenance and security. It ensures continuity in the event of emergencies, not quality. Furthermore, the recipient does not automatically grant all rights with the released source code: they receive a right of use to maintain and modify the software for their own use, not the full copyright to sell the software commercially. You must explicitly define this scope. Additionally, ensure that the deposits remain up-to-date; outdated source code is of little value at the time of a release.
Honest recommendation
You do not always need a lawyer. If your company runs on general standard software from a major vendor (where multiple parties can take over maintenance or simple alternatives exist), escrow is often unnecessary. Similarly, with cheap, easily replaceable software, the effort does not outweigh the risk. For those situations, a standard arrangement from the vendor or no escrow is perfectly fine.
It is advisable to seek legal assistance as soon as the software is truly business-critical, custom-built, or unavailable elsewhere. In such cases, your continuity hinges on a watertight release trigger, a right of use that survives bankruptcy, and the assurance that the deposited code is complete and up-to-date. Have the agreement reviewed in those instances before signing.
Want to know more? Read how to record the agreements in drafting a source code escrow agreement and what outsourcing costs in having a source code escrow agreement drafted. Need an arrangement immediately? View our source code escrow agreement.
Frequently Asked Questions
A tripartite agreement whereby the source code of software is deposited with an independent custodian. The customer uses the software normally but gains access to the source code if the supplier ceases to exist, for example due to bankruptcy or the cessation of maintenance.
The source code is the supplier's business capital and is protected by copyright pursuant to Article 10, paragraph 1, sub 12 of the Copyright Act. You are purchasing a right of use to the working software, not the code itself. Escrow bridges the risk of being left with unusable software.
In the event of a predefined release trigger, usually bankruptcy, suspension of payments, business closure, or structural failure to comply with maintenance. The escrow agent verifies whether the trigger has actually occurred before releasing the code.
You need to arrange that properly. The trustee determines, pursuant to Article 37 of the Bankruptcy Act, whether agreements are performed, and for long-term agreements, there is a termination option comparable to Article 39 of the Bankruptcy Act. A watertight agreement ensures that the right to use the released code also holds up against the trustee.
No. You receive a right of use to maintain and modify the software for your own use, not the full copyright to sell the software. You define the scope of that right in the escrow agreement.
Especially for business-critical or custom-built software from a single vendor for which no easy alternative exists. For general standard software from major vendors, escrow is usually unnecessary.
An independent escrow agent, not the supplier themselves. That independence is essential: in the event of bankruptcy, code would fall into the supplier's bankruptcy estate and is not guaranteed to end up with you.
