mainland versus free zone for a software company

Document what the software does, who uses it, how customers access it and whether it enters a regulated sector.

Separate subscriptions, licences, implementation, customisation, support, training, resale and hardware income.

Identify where management, development, customer support, sales and implementation teams will work.

Choose accurate software, consultancy, portal, cloud, trading or technical activities.

Confirm whether financial, healthcare, educational, telecommunications or other sector approval is needed.

Review lisensi scope, customer access, office, visas, banking, tax, investor expectations and annual cost.

Complete trade-name approval, incorporation documents, licensing, office arrangements and establishment registration.

Execute founder, employee and contractor agreements ensuring the company owns or validly licenses the software.

Register for Pajak badan, assess PPN (VAT), create subscription accounting and establish IP-expenditure tracking.

Prepare customer terms, privacy notices, data-processing agreements, acceptable-use rules and security procedures.

Apply for a business account and suitable recurring-payment facilities with complete commercial documentation.

Costs vary significantly between jurisdictions and packages. Fixed prices should not be quoted without confirming the activities, pemegang saham, office and visa requirements.

A straightforward non-regulated software company may be incorporated relatively quickly when its documents and activities are clear.

Banking, payment processing and regulated-sector approvals should not be represented as guaranteed within a fixed timeframe.

A low-cost lisensi may not cover the complete business model.

Technology supporting payments, healthcare or investments may still be regulated.

SaaS and IP income require detailed Pajak badan analysis.

Unclear ownership can create serious problems during investment, banking, customer due diligence or sale of the company.

The answer changes if the company combines software subscriptions with implementation, hardware, regulated financial technology, healthcare data or customer-site services.

A SaaS company generally gives customers online access to software hosted or managed by the provider. Customers normally pay a monthly, annual, usage-based or user-based fee rather than acquiring the underlying source code.

The lisensi activity must match what the company actually does. "Software development," "IT consultancy," "portal operation," "cloud services" and "software trading" can represent different regulatory and commercial functions.

Before choosing mainland or free zone, the founder should separate each expected revenue stream.

The correct activities and tax treatment can differ across these streams.

For example, a business developing its own subscription platform is not identical to a reseller purchasing licences from an overseas vendor. A company that installs servers and network equipment may need trading and technical activities in addition to software consultancy.

A mainland company is licensed by the economic department of the emirate in which it is established. In Dubai, the relevant economic licensing functions are administered through the Departemen Ekonomi dan Pariwisata and its associated channels.

A mainland software or IT company may generally conduct its approved activities throughout the local market, subject to any sector-specific restrictions.

The company remains limited to the activities stated on its lisensi. A general software activity does not authorise regulated financial, healthcare, telecommunications or cybersecurity services where separate approvals are required.

A free zone software company is incorporated and licensed by a specific free zone authority.

Different free zones offer different activity lists, office solutions, visa allocations, ownership rules and technology communities. Some provide startup programmes, incubators, co-working facilities, investor networks and access to specialist service providers.

The company must comply with its free zone's rules and should confirm how its proposed activities may be conducted outside the zone.

A free zone software company can enter contracts with customers di UEA, but the legality and appropriate licensing structure depend on the nature and location of the activity.

Is the service delivered entirely online?

A remote subscription accessed by a customer is operationally different from a team permanently stationed at the customer's Dubai office.

Where the activity creates a mainland operating presence or requires mainland authorisation, the company may need a branch, permit or separate mainland entity.

Dubai Executive Council Resolution No. 11 of 2025 established a framework under which eligible Dubai free zone establishments may conduct approved activities outside their free zones and within Dubai.

A branch licensed to conduct mainland activity while operating from the free zone

Dubai subsequently introduced the Free Zone Mainland Operating Permit for eligible companies holding a Dubai Unified Lisensi. The initial phase includes non-regulated fields such as technology, consultancy, design, professional services and certain trading activities.

A temporary permit may be useful for an eligible technology company performing a time-limited mainland project. A branch route may be more appropriate for recurring local operations.

Eligibility must be checked using the current activity list and procedures. A software-related description on a free zone lisensi does not automatically qualify for every mainland technology activity.

A mainland company provides a clear structure for recurring work with UEA businesses.

Full foreign ownership is also available for many mainland activities, so foreign ownership alone should not determine the choice.

A Qualifying Free Zone Person can benefit from a 0% Pajak badan rate on Qualifying Income if every statutory condition is met.

For a software company, this analysis can be valuable—but it is also technically complex.

Some free zones offer legal frameworks, documentation and ecosystems commonly used by venture-funded companies. The precise suitability depends on the investor, investment round and exit plan.

The company may need additional authorisation if it maintains mainland premises, deploys staff permanently outside the zone or performs activities requiring mainland licensing.

Some public-sector tenders or supplier-registration processes may prefer or require a mainland-licensed entity.

The company cannot assume that all SaaS subscription or software-licensing income is subject to 0% Pajak badan.

A Qualifying Free Zone Person must maintain adequate substance. A lisensi and flexi-desk without appropriate people, assets and activity may not support the desired treatment.

The free zone's available activity descriptions may not cover every element of the proposed business.

Software development generally involves creating, coding, testing, modifying or maintaining software.

IT consultancy generally involves advising customers on technology systems, architecture, implementation, security, transformation or process improvement.

A company may perform both, but it should obtain both activities where required.

A free zone company is within the UEA Pajak badan regime. It does not receive an automatic exemption.

To be treated as a Qualifying Free Zone Person, the company must satisfy requirements including:

The customer's location alone does not provide a complete answer.

The Federal Tax Authority's Free Zone Persons Guide identifies copyrighted software as a form of Qualifying Intellectual Property.

However, this does not mean every dirham of SaaS revenue automatically benefits from a 0% Pajak badan rate.

The rules use a nexus approach. The qualifying amount is connected to the research-and-development expenditure incurred to develop the relevant IP.

Income exceeding the amount determined under the applicable formula, and income from non-qualifying intellectual property, may be subject to 9% Pajak badan.

Trademarks and other marketing-related intellectual property are not treated as Qualifying Intellectual Property merely because they are owned by a free zone company.