Table of Contents

Frequently Asked Questions

Do UAE software companies have to publish their source code if they use open source libraries?

Not by default. Permissive licenses such as MIT, BSD and Apache 2.0 do not require you to publish your own source code. Strong copyleft licenses such as GPL can require disclosure when you distribute software that incorporates the licensed code. The trigger depends on the license terms and on how you combine and distribute the code.

Which open source licenses are safest for commercial software?

Permissive licenses carry the lowest commercial risk. MIT, BSD and Apache 2.0 mainly require attribution and a copy of the license text. Apache 2.0 also includes an express patent grant. They suit closed-source products far better than GPL or AGPL.

Does using a GPL library in a SaaS product trigger source disclosure?

Usually not under standard GPL, because hosting software for users is generally not distribution. AGPL is different. It extends the disclosure duty to software offered over a network, so a SaaS product using AGPL code may need to release its corresponding source. Check each component's exact license before launch.

What is a software bill of materials and who asks for it?

A software bill of materials is a record of every component in your software, with versions, sources and licenses. Enterprise buyers, banks and investors commonly request one during procurement or due diligence. Generating it from your build pipeline at each release keeps it accurate.

Who is responsible for open source compliance in a small software team?

One named person should own it, usually the CTO or lead engineer. That owner maintains the approved license list, reviews flagged components and checks each release. The company remains legally responsible for the code it ships, whoever performs the checks.

Can a company lose the right to use open source code after a breach?

Yes. Many open source licenses terminate automatically if you breach their conditions. Continued use after that point can expose the company to copyright infringement claims from the rights holder. Some licenses allow the right to be reinstated if you correct the breach within a stated period.

How often should a software company scan its code for open source licenses?

Scan at every release, and ideally on every build through your pipeline. New or updated dependencies can introduce different licenses without any visible change to your own code. Frequent scanning also keeps your software bill of materials current for client and investor requests.

Do clients in the UAE ask for proof of open source compliance in contracts?

Often, yes. Banks, corporates and government-linked buyers may ask for a component list in procurement questionnaires. Contracts can also include warranties that the software contains no restricted code. Keeping a software bill of materials and a notices file ready lets you answer quickly.

Topic Summary

  1. Why Open Source License Compliance Matters in the UAE

    Open source license compliance matters because every component carries legal conditions. Breaching them can force disclosure of proprietary code, trigger damages or cost you enterprise contracts. For UAE software companies selling to banks, government entities and corporates, proof of compliance shapes procurement and investment decisions.

  2. What Open Source License Compliance Means for UAE Software Companies

    Open source license compliance is the practice of identifying every open source component in your software, understanding its license, and meeting its conditions. These cover attribution, notice files, source disclosure and limits on how you combine or distribute the code.

  3. Permissive and Copyleft Licenses Compared

    Permissive licenses such as MIT and Apache 2.0 allow commercial use with minimal conditions, mainly attribution. Copyleft licenses such as GPL and AGPL require derivative works to carry the same terms. That is where copyleft license risk begins.

  4. Legal and Commercial Risks of Open Source License Compliance Failures

    Non-compliance can lead to infringement claims, injunctions, forced disclosure, contract termination and failed due diligence. In the UAE, the commercial damage often arrives first: clients and investors withdraw before any dispute reaches a court.

  5. Steps to Build an Open Source License Compliance Process

    Build the process in four stages: inventory every component, classify risk, produce notices and a software bill of materials (SBOM), and assign an owner who checks each release.

  6. How Open Source License Compliance Fits a Meydan Free Zone Software Company

    Open source license compliance is a contractual and intellectual property matter, not a free zone licensing requirement. A Meydan Free Zone software company still needs the right activities on one license, clear client contracts and internal records.

  7. Practical Decisions for Founders Before Release

    Before release, decide which licenses are acceptable, who owns compliance, how components are tracked and when to call counsel. Replacing a restricted library after launch costs more than choosing a compatible one early.

  8. Conclusion

    Open source license compliance is a routine task, not a one-off check. It’s won through inventories, a clear policy and an owner who checks every release. Audit your dependencies, set an approved license list, and align your license activities with how you distribute software before applying for your business license with Meydan Free Zone.

Open Source Licence Compliance for UAE Software Companies

Most founders in the UAE assume open source code is free to use however they like. It isn't. Open source license compliance is now a routine subject of review by banks, enterprise buyers and investors. This guide explains what it involves, where the real risk sits, and how to set up a process before applying for your business license with Meydan Free Zone.

Why Open Source License Compliance Matters in the UAE

Open source license compliance matters because every component carries legal conditions. Breaching them can force disclosure of proprietary code, trigger damages or cost you enterprise contracts. For UAE software companies selling to banks, government entities and corporates, proof of compliance shapes procurement and investment decisions.

The Common Founder Misconception

Free to download does not mean free of conditions. Say a two-person SaaS team in Dubai ships a mobile app bundling a strong copyleft library. During a client audit, they’re asked to disclose source code if the applicable license requires it. Small teams also inherit dozens of transitive dependencies without noticing.

Where Compliance Questions Arise Commercially

Procurement questionnaires, investor due diligence and app store reviews all raise the issue. A UAE fintech, for instance, may be asked by a bank client to list every third-party component and its license before signing. 

What Open Source License Compliance Means for UAE Software Companies

Infographic: Open Source Licence Compliance for UAE Software Companies

Open source license compliance is the practice of identifying every open source component in your software, understanding its license, and meeting its conditions. These cover attribution, notice files, source disclosure and limits on how you combine or distribute the code.

Core Obligations Under Most Licenses

  • Keep copyright and attribution notices.
  • Ship the license text with distributed software.
  • Disclose source where the license requires it.
  • Mark any modifications you make.

A desktop application, for example, must ship a notices file listing each library and its license text.

Permissive and Copyleft Licenses at a Glance

FeaturePermissive Licenses (MIT, BSD, Apache 2.0)Copyleft Licenses (GPL, LGPL, AGPL)
Main obligationKeep attribution and license noticesRelease derivative works under the same terms
Source code disclosureNot required for your own codeRequired for derivative works when distributed (AGPL: also over a network)
Suitability for closed-source productsHigh; widely used in proprietary productsLimited; LGPL allows dynamic linking, GPL generally does not
Network use impactNoneAGPL can require source-code access when modified software is used over a network
Typical risk levelLow, if notices are maintainedMedium to high, depending on architecture

Distribution Versus Internal Use

Internal use rarely triggers disclosure. Distribution to customers usually does. A SaaS provider hosting software for clients sits in a different position from a vendor installing it on client servers, and network clauses such as AGPL can change that.

How UAE Law Frames Software Rights

Software is protected as a work under Federal Decree-Law No. 38 of 2021 on Copyright and Neighbouring Rights. Open source licenses work as contractual terms backed by that copyright. A licensor can assert rights if you use code outside the license terms. For wider context, see understanding intellectual property in the UAE.

Permissive and Copyleft Licenses Compared

Permissive licenses such as MIT and Apache 2.0 allow commercial use with minimal conditions, mainly attribution. Copyleft licenses such as GPL and AGPL require derivative works to carry the same terms. That is where copyleft license risk begins.

Apache 2.0 adds an express patent grant. A UAE e-commerce platform built on permissive frameworks must still meet the applicable attribution, notice and other license conditions.

Copyleft needs architecture review. A company embedding a GPL library in a distributed product can be asked to release its own source. If you're choosing between two libraries that do the same job, pick the permissive one for closed-source products. Bring in legal review when the alternative is GPL or AGPL.

Legal and Commercial Risks of Open Source License Compliance Failures

Non-compliance can lead to infringement claims, injunctions, forced disclosure, contract termination and failed due diligence. In the UAE, the commercial damage often arrives first: clients and investors withdraw before any dispute reaches a court.

Contract and Infringement Exposure

A breach can terminate your right to use the code, subject to the license's terms. Client contracts often add warranties that no copyleft code is included. If that proves untrue, you face indemnity claims.

Due Diligence and Funding Impact

Investors ask for component inventories. A seed-stage Dubai startup that must replace a restricted library can delay a funding round. Fixing issues afterwards costs more than preventing them. Treat licensing alongside penalties for non-compliance in the UAE and data protection duties at each annual review. Regulated clients, such as banks, tend to scrutinise vendors hardest.

Steps to Build an Open Source License Compliance Process

Build the process in four stages: inventory every component, classify risk, produce notices and a software bill of materials (SBOM), and assign an owner who checks each release.

  1. Inventory every component. Include transitive dependencies. A scan of a Node.js project often reveals hundreds of packages. Run scanners in your build pipeline and record versions.
  2. Classify by risk. Use green, amber and red categories. Approve MIT and Apache 2.0 automatically, and flag AGPL for review.
  3. Produce notices and an SBOM. Ship a notice file with each release and keep the SBOM in version control. A corporate buyer may request it during onboarding.
  4. Assign ownership. Name one owner, usually the CTO or lead engineer. Add a release checklist item that blocks deployment if an unapproved license appears. Track reviews in your company compliance calendar.

How Open Source License Compliance Fits a Meydan Free Zone Software Company

Open source license compliance is a contractual and intellectual property matter, not a free zone licensing requirement. A Meydan Free Zone software company still needs the right activities on one license, clear client contracts and internal records.

Choosing the Right Activities on One License

Match your activities to how you distribute software. A founder selling ready-made software and providing custom development services should align both activities before applying for a business license with Meydan Free Zone. The guide to start a software company in Dubai covers the options.

Records, Contracts and Digital Documents

Meydan Free Zone issues the Business License, Certificate of Formation, Share Register and Memorandum and Articles of Association digitally. Keep these beside your SBOM, notices and IP assignment agreements for employees and contractors.

Accounting and Running Costs

Scanning tools and legal review are a recurring cost, so include them in your running budget. Meydan Plus (mPlus) brings together Meydan Free Zone’s business support offerings, one of which is mAccounting, covering bookkeeping, VAT, Corporate Tax and payroll. The Meydan Free Zone Setup Cost Calculator helps you plan.

Keep tooling and legal costs on budget with mAccounting, part of Meydan Plus (mPlus).

Free Business Setup Cost Calculator

Calculate Now

Practical Decisions for Founders Before Release

Before release, decide which licenses are acceptable, who owns compliance, how components are tracked and when to call counsel. Replacing a restricted library after launch costs more than choosing a compatible one early.

Build Versus Adopt Decisions

Weigh license terms alongside features and support. For a distributed product, choose a permissive database driver over an AGPL one, and document why.

When to Involve Legal Counsel

  • Copyleft code in a distributed product.
  • Contributing company code to open source projects.
  • Acquisition or funding events.

A short legal review before a Series A data room opens is cheap insurance.

Conclusion

Open source license compliance is a routine task, not a one-off check. It's won through inventories, a clear policy and an owner who checks every release. Audit your dependencies, set an approved license list, and align your license activities with how you distribute software before applying for your business license with Meydan Free Zone.

Administrative