Skip to content
QuickshipTechnologies

SoftwareUAE7 min read

Software Development Contract UAE: Key Clauses to Include

What a software development contract UAE buyers should check: IP assignment, source code, acceptance testing and support clauses, with a worked example.

By · Published

Looking for the software itself? See our custom software development Dubai.

A software development contract in the UAE should say, in writing, who owns the code, what you receive, how you accept the work and who fixes problems after go-live. If your contract is silent on any of these four, you are relying on guesswork and on the developer's goodwill.

This post is a practical checklist for business owners who buy custom software, such as a freight system, a courier dashboard or an order tool. It is not legal advice. Have a UAE lawyer review the final contract.

What should a software development contract in the UAE cover?

It should cover scope, deliverables, intellectual property, source code, acceptance testing, payment, support, data protection, confidentiality, termination and disputes. Most disputes we hear about come from vague scope and unclear handover, not from bad code.

Here is a quick map of the clauses and what each one protects.

Clause What it should say What goes wrong without it
Scope and deliverables Features, integrations, screens, reports, documents "We thought that was included"
IP assignment Who owns the custom work, in writing You pay for the build but only hold a licence
Source code What you receive, when, in what form You cannot move to another developer
Acceptance Test cases, pass marks, fix rounds Payment is demanded for work that does not run your process
Support and warranty Fix period, response times, cost after warranty Bugs after launch become paid extras
Data Who holds it, where it is hosted, what happens at exit Customer data stuck on the developer's server
Change requests How new asks are priced and approved Scope creep and surprise invoices
Termination Exit rights, handover, final payment A stalled project you cannot leave

Who owns the code under UAE law?

The honest answer is that sources disagree on the default rule, so you should not rely on it. Write an explicit assignment instead.

The law that matters is Federal Decree-Law No. 38 of 2021 on Copyright and Neighbouring Rights. It lists software, smart applications and databases as protected works (Article 2, see the full text). The Ministry of Economy hosted translation also has wording that a work made "for the benefit of another person" belongs to that person.

Here is where it gets unclear:

  • Some commentators read that wording as meaning a commissioned work belongs to the buyer unless agreed otherwise.
  • Legal 500's UAE guide says that for an independent contractor, ownership stays with the developer unless there is a written assignment. The buyer then has at best an implied licence.
  • Skimbox says a transfer of economic rights should be in writing and should specify the right, the purpose, the duration and the place of use. It also says the commissioned-work wording is ambiguous in translation and that it found no official interpretation for external suppliers.

So don't bet on the default. Put this in the contract:

  1. A present assignment of all IP rights in the custom deliverables from the developer to you. Fakher & Co recommends this for custom development.
  2. The specific rights, the purpose, the duration and the territory (for example, all rights, all business purposes, perpetual, worldwide).
  3. A separate licence for the developer's pre-existing code or tools, if any. It should be perpetual and should survive termination.
  4. A list of third-party and open-source components, with their licence types.

Why the third-party list matters

Using software without authorisation can carry a fine of AED 30,000 to AED 100,000 per software, application or database under Article 41 of the copyright law. If your developer pulls in a library with the wrong licence, that risk lands on the business running the system. Fakher & Co also flags open-source compliance as a clause topic. Ask the developer to warrant that the code does not breach any third-party rights and to list the open-source licences used.

What source code clause do you need?

You need a clause that says what code you get, when you get it and in what form. Ownership on paper is not much use if you cannot read or build the code.

Ask for these items:

  • The full source code of the custom work, in a repository you control, delivered at each milestone and at final acceptance.
  • Build and deployment instructions, so another developer can run it.
  • Database schema, API documentation and environment settings (not the passwords, which should be handed over securely).
  • Admin access to hosting, domains, app store accounts and cloud services in your company's name.

A common mistake is letting the developer register the domain, the Apple developer account or the cloud tenant under their own name. Years later, the business cannot move without their permission. Keep every account under your trade licence.

If the developer insists on keeping the code, ask for a source code escrow or a release clause. It should trigger if they close, stop support or breach the contract.

How should acceptance testing work?

Acceptance testing should be a written list of test cases with pass marks, agreed before the build starts. "The client is satisfied" is not a test.

Fakher & Co advises stating what happens if the software fails: the developer must fix it, the payment is reduced, or you can terminate. Spell out which one applies and how many fix rounds are allowed.

A worked example (hypothetical)

Say a Dubai courier company commissions a dispatch dashboard. It must connect to two partner courier APIs and reconcile cash on delivery (COD) payments each week. The contract could define acceptance like this:

  1. Test set. 100 sample orders across Dubai, Sharjah and Abu Dhabi, including 20 COD orders and 10 returns.
  2. Pass mark. Every order gets the right status from each courier API. The COD report matches the finance team's manual sheet to the dirham for the test set.
  3. Review window. The company has 10 working days to test after each delivery.
  4. Fix rounds. The developer gets two rounds to fix failed cases. If the third round still fails, the company can withhold the milestone payment or terminate for that module.
  5. Sign-off. Acceptance is a written email or form signed by a named person. Silence is not acceptance.

The numbers are only an example. Your own test set should come from real orders, including the awkward ones, such as a failed delivery attempt, a partial COD collection or a customs hold on a cross-border parcel.

Pay by accepted milestone, not by calendar date. A simple pattern is a deposit, payments at accepted milestones and a holdback released after go-live plus a short fix period. The split is a commercial choice, so set it per project.

What support and warranty terms should you ask for?

Ask for a warranty period after go-live, a defined support service and clear rates for anything outside it. Bugs found in the first weeks are normal. The contract decides whether you pay for them.

Cover these points:

  • Warranty. A fixed number of days after go-live when the developer fixes defects in the agreed scope at no charge.
  • Severity levels. For example, "system down" versus "a report column is wrong", each with a response time and a fix target.
  • Support hours. UAE working days and hours, and whether the developer is reachable on weekends and during Ramadan hours.
  • Third-party changes. Courier, marketplace and messaging APIs change. Say who updates the integration and at whose cost.
  • Hosting and security updates. Who patches, who monitors and who pays.
  • Maintenance pricing. A monthly rate or an hourly rate card, fixed for a stated period.

What about data, confidentiality and exit?

Your system will hold customer names, phone numbers, delivery addresses and payment records. The contract should say who owns that data, where it is hosted and how you get it back at exit.

Include:

  • A confidentiality clause covering your pricing, customer lists and processes.
  • A data protection clause naming who decides how personal data is used and who only processes it for you. Ask your lawyer to check your duties under the UAE PDPL.
  • Hosting location, backups and a breach notice time.
  • On termination, a full export of your data in a standard format within a set number of days, then deletion by the developer.
  • Handover help: a set number of hours for knowledge transfer if you move to another supplier.

Add a change request process too. Every new ask gets a written estimate and your approval before work starts.

Checklist before you sign

  1. Is the scope written down with named features, integrations and reports?
  2. Is there a written IP assignment with rights, purpose, duration and territory?
  3. Is the developer's pre-existing code covered by a perpetual licence?
  4. Is there a list of third-party and open-source components?
  5. Will you receive the source code, documentation and account access in your company's name?
  6. Are acceptance tests, pass marks and fix rounds written in?
  7. Are payments tied to accepted milestones, with a holdback?
  8. Are warranty, support hours and response times stated?
  9. Can you export and delete your data at exit?
  10. Are governing law, language and the dispute forum stated and checked by a UAE lawyer?

If you are scoping a custom build, such as a freight or courier workflow, Quickship does custom software development on a quote basis. Whoever you pick, ask for these clauses.

Frequently asked questions

Do I need to register the copyright to own the software?

Protection under the UAE copyright law is automatic, and registration is optional. According to [Legal 500](https://www.legal500.com/guides/chapter/uae-tmt/), registration mainly helps as evidence. What matters more for a buyer is a signed written assignment, because it proves the rights moved to you.

Can I get the source code if the developer keeps ownership of a reusable core?

Yes, if the contract says so. Ask for a licence to the developer's pre-existing code that is perpetual, covers your business use and survives termination. Also ask for the source code of your custom parts, and for a list of any third-party components, so you can run the system without the developer.

Should the contract be in English or Arabic?

Many UAE software contracts are signed in English, but the language of the contract and which version prevails if there is a dispute should be stated in the text. Have a UAE lawyer confirm how the governing law and the dispute forum work for your case. This is especially important if the developer is based outside the UAE.

What is a fair way to split payments on a custom build?

Tie payments to delivered and accepted milestones, not to dates alone. A common pattern is a deposit, payments at accepted milestones and a final holdback released after go-live and a short fix period. The exact split is a commercial decision, so agree it per project.

Sources

  1. Federal Decree-Law No. 38 of 2021 on Copyright and Neighbouring Rights (UAE Legislation portal)
  2. Federal Decree-Law 38 of 2021, full text (Polaris)
  3. Legal 500: UAE TMT guide
  4. Skimbox: Who owns your code in the UAE
  5. Fakher & Co: Technology contracts and licensing in the UAE

Rules and fees in the UAE and Saudi Arabia change. This guide reflects the sources above on 21 November 2026. Check the official source before acting on it.

Software Development

Custom software for the processes off the shelf tools do not fit.

Get a quote

Related guides

Instant quote