Software Escrow Agreements for UAE IT Contracts

Many UAE founders assume a software license lets them keep running a system if the vendor disappears. It doesn't. A software escrow agreement is what gives you access to the source code when a vendor fails, exits the market or stops supporting the product. This guide is for founders about to sign an IT contract or apply for a business license with Meydan Free Zone, and it explains what to ask for.

What a Software Escrow Agreement Covers

A software escrow agreement is a three-party contract between a software vendor, a customer and a neutral escrow agent. The vendor deposits source code and build materials with the agent. The agent releases them to the customer only if defined events occur, such as vendor insolvency or failure to provide support.

The Three Parties and Their Roles

The vendor is the depositor, the customer is the beneficiary and the agent is the custodian. The agent doesn't judge the commercial dispute beyond the contract terms. The escrow contract sits alongside the main license or SaaS contract, not inside it.

Take a Dubai logistics SME that licenses a bespoke fleet-management platform from an overseas vendor. It names an independent agent as custodian, so the code sits outside the vendor's control.

What Goes Into the Deposit

• Source code, build scripts and third-party dependencies.
• Database schemas, documentation and deployment instructions.
• Credentials or keys needed to compile and run the software.

A deposit with code but no build instructions leaves you unable to compile a working version.

Single-Customer and Multi-Beneficiary Arrangements

Bespoke systems usually get a dedicated agreement. Off-the-shelf products often use one shared deposit with several licensees, which costs less but gives each customer less control. A publisher with several UAE clients typically chooses the shared model. See the guide to a ready-made software publishing business in Dubai if that's your model.

How UAE Law Treats a Software Escrow Agreement

UAE law has no dedicated escrow statute for software. A software escrow agreement is enforced as a commercial contract under the UAE Civil Transactions Law, now Federal Decree-Law No. 25 of 2025, while Federal Decree-Law No. 38 of 2021 on Copyright protects the vendor's rights in the code. The agreement must therefore grant clear, limited usage rights on release.

Contract Law Foundations

Courts read the text, so drafting matters. A dispute over whether "support failure" triggered release turns entirely on how that phrase was written. Choose governing law and forum deliberately. The UAE contract law clauses that free zone businesses often get wrong apply here too.

Copyright and License Scope on Release

• Source code stays the vendor's intellectual property.
• Release must carry a license to use, modify and maintain it.
• Limit use to internal support to protect the vendor.

Without modification rights, you hold code you can't legally use to fix a critical bug. For background, read understanding intellectual property in the UAE.

Data Protection and Sector Rules

Escrowed material shouldn't contain personal data. Licensed financial clients may face outsourcing and continuity expectations from the Central Bank of the UAE, so a fintech tool provider may be asked to show its arrangements. 

Release Conditions a Software Escrow Agreement Must Define

Release conditions are the events that entitle the customer to the deposit. Common triggers include vendor insolvency, cessation of business, failure to support the software within agreed service levels, and material breach. Each trigger should be measurable, with a defined notice and dispute process.

Triggers That Hold Up in Practice

• Insolvency or bankruptcy proceedings.
• Discontinued product or end of support.
• Repeated service-level failures after written notice.

Say a vendor misses a defined fix deadline three times in a quarter. That should trigger a release request.

Notice, Challenge and Release Procedure

You send a written request with evidence. The vendor gets a fixed counter-notice window. If there's no valid objection, the agent releases. If the vendor contests, the agreement should route the question to a named expert or arbitration.

Verification of the Deposit

A basic check confirms the files exist. A full build test confirms they compile into the live version. Repeat after each major release. One build test caught a missing library before it became a crisis.

How to Put a Software Escrow Agreement in Place

To set up a software escrow agreement: identify the critical system, agree the principle with the vendor, select an independent escrow agent, define deposit contents and release triggers, sign the three-party contract, make the first deposit, verify it, and schedule updates after each major release.

Step 1: Decide Which Systems Justify Escrow

Escrow bespoke, business-critical or hard-to-replace software. Skip commodity tools. A trading company might escrow its custom order-management platform but not its email service. Weigh each system against the cost of downtime.

Step 2: Negotiate Terms and Choose the Agent

Raise escrow before you sign the main IT contract. Agree who pays: fees are often split, or the customer pays in return for a lower license price. Pick an agent independent of both parties.

Step 3: Sign, Deposit and Verify

Authorised signatories sign the three-party agreement. Complete the notarisation of documents in Dubai if a counterparty requires it. Verify the first deposit within an agreed period of signing, then fix the update schedule.

Costs and Risks of a Software Escrow Agreement

Costs typically include an agent set-up fee, annual storage fees and optional verification charges. These vary by agent and service level, so treat any figure as an agent quote, not an official fee. The main risks are incomplete deposits, outdated code and vague release triggers.

Fee Components to Budget For

• No official UAE fee schedule exists.
• Request quotes from two agents and compare service levels.
• Agree in writing who bears each cost.

Where Escrow Arrangements Fail

• Deposits not updated after new releases.
• Missing build environment details.
• Release clauses you can't prove.

Escrowed code that's two versions behind production is close to worthless.

Escrow Versus Other IT Contract Protections

Escrow protects access to source code, while warranties, service-level agreements and step-in rights protect performance. A software escrow agreement works best alongside these, not instead of them. An SLA penalises downtime. Escrow lets you keep the system alive after the vendor stops operating.

SaaS and Cloud Deliveries

Code alone isn't enough for hosted services. A SaaS customer needs the code and a running environment, plus data continuity. Ask whether the vendor offers hosted-environment escrow.

What This Means for a Meydan Free Zone Founder

A Meydan Free Zone company can sign a software escrow agreement as a normal commercial contract, as customer or vendor. Developers should plan deposit obligations into client contracts. Buyers should request escrow before committing to business-critical systems. Meydan Free Zone sits under Dubai Courts jurisdiction, so name the Dubai Courts or an arbitration forum for any release dispute.

If You Buy Software

• Request escrow during procurement.
• Keep signed copies with company records.

A Meydan Free Zone e-commerce company, for example, could escrow its custom storefront platform.

If You Build or Publish Software

• Offer escrow to win enterprise clients.
• Use limited-use licenses to protect your code.
• Keep activity within your business license.

See how to start a software development business in Dubai.

Conclusion

A software escrow agreement turns a license into continuity. It won't fix a poor vendor, but it keeps a critical system maintainable if the vendor fails. Define release conditions precisely, deposit complete materials and verify them. Before signing your next IT contract, list the systems your business can't run without and request escrow terms for each.