How many activities fit on one UAE licence

An activity is not a description of your business. It is a row in a licensing authority's register, with a code and a name that the authority wrote, and your licence lists the rows you are permitted to carry out. That is the whole mechanism, and almost every problem in this area comes from forgetting it.

The practical consequence is narrow: you can invoice for what is listed. Work that falls outside every listed row is work your licence does not cover, however reasonable it sounds in conversation and however close it is to something that is listed, which is crucial when deciding between compare free-zone and mainland routes options.

Codes are not decoration either. Where an authority organises its register by code — and several do — the code decides which rows count as neighbours, and therefore which rows combine cheaply, which combine expensively, and which cannot combine at all. That is treated in detail below.

Across the eight UAE registers we currently capture, our snapshot holds 14,594 activity rows carrying 7,479 distinct names. Of those names, 3,393 appear in more than one register and 785 appear in four or more — the registers overlap heavily without being copies of one another. The same business idea is a differently coded, differently named, differently grouped row in each one.

Most registers do not present a flat list. They group activities into licence families, and the family carries real consequences: which licence you apply for, which rows may sit beside each other, and in some registers what a change costs later, especially when considering licensing an operation to trade onshore.

The family names below are published by each authority and reproduced verbatim from our register capture of 25 August 2026 — the same snapshot the zone directory pages on this site are built from, except that the table lists every family we captured rather than only the ones large enough to earn a directory page. That is deliberate: the columns are meant to add up to the register total, and several registers publish a family holding a single row. They are examples of how published structure looks, not a comparison, and nothing here says one structure serves you better than another. The counts are what our capture found on that date; registers change.

Five of the eight registers we capture publish a family-style grouping against each activity row. Four of them label it as a licence family — Ajman Free Zone, DMCC, IFZA and RAKEZ, the four in the table above. Meydan publishes one too, under the heading Category rather than family, against all 2,230 of its rows: Trading, Professional, Administrative, ICT, HealthCare and twelve more. The remaining three — Dubai mainland, Shams and SPC Free Zone — do not expose a grouping in the source we read, which means it either sits somewhere the public list does not show, or is applied when the application is assessed rather than when the list is published.

The distinction between those two situations matters, and it is easy to get backwards. A grouping we did not find is a fact about the list we read, not a finding that the authority has no grouping — the same trap the companion guide treats at length in its section on blank fields. Meydan is the illustration: had we looked only for a field called licence family, we would have recorded a register of 2,230 ungrouped rows, and the register would have been fully grouped the whole time under another name.

This matters when you are comparing. Where a register publishes families, you can see in advance which rows are neighbours. Where it does not, the grouping still exists — it is simply not visible to you until someone at the authority applies it to your file. In that case the answer to 'how many activities' cannot be researched. It has to be asked.

DMCC publishes its rule on its public schedule of charges, and it is worth reading in full because it shows the shape of the answer at any authority that has one — even where the wording and the amounts are entirely different.

The structure DMCC publishes is by activity code group. A licence covers up to six activities that share the same first two digits of the code. Beyond six in that same two-digit division, further activities are added for a per-activity annual fee. Adding activities from a division sharing the same first digit carries an annual fee and admits up to six activities from that new division. Adding activities from a completely different two-digit division carries a higher annual fee and likewise admits up to six from that division. Activities belonging to a different licence type — Service, Trading or Industrial — require a new licence rather than an addition. And the schedule notes that some activities, giving single-family office, real estate and DGCX as its examples, are standalone: they cannot be carried out alongside any other activity even within the same licence category.

Read that back as a general lesson rather than as a fee table. 'How many activities' is not one question. It is four: how many within the group you are already in, how far the group extends, what it costs to open a second group, and which rows refuse to share a licence at all. An authority that has not answered all four has not answered the question.

The approximate bands below are rounded from that published schedule as we captured it on 15 August 2026. They are authority costs, they carry no markup, they are not our fee, and DMCC states its fees are subject to change without prior notice — so treat them as the shape of the tiering rather than as a price.

Three separate things vary between authorities, and they vary independently, which is why no cross-zone rule survives contact with a real file.

The register varies. A row that exists at one authority may have no equivalent at another, or may exist under a name you would not search for. The grouping varies: the same work can be filed under a Services family in one register and a Professional family in another, and the family decides which neighbours it has. And the combination rule varies: some authorities publish it, some apply it case by case, and some treat it as a commercial term that moves with the season.

One consequence catches people out repeatedly, and it is a jurisdiction question wearing a naming question's clothes. RAKEZ administers both a free zone and Ras Al Khaimah's non-free-zone licensing, and it publishes the same activity separately under each, with a different code and a different family. Corporate Services Provider (CSP) is filed twice: 70100-06, whose scope reads 'Zone: RAKEZ free zone | Licence type: Services', and 7010006, whose scope reads 'Zone: RAK non-free zone (via RAKEZ) | Licence type: Professional'. Tax Consultancy is filed the same way, as 69200-02 and 6920002. These are not two options a free-zone applicant chooses between — the row you want is decided by which of the two jurisdictions you are applying into, and reading the scope text tells you which row is which.

Zones compete on this line. 'Up to N activities included' is one of the most common promotional terms in UAE formation marketing, and it is exactly the kind of term that is true when written and quietly different a quarter later.

Our own catalogue records the structural fact — whether an authority combines multiple activities on one licence, and whether it combines across categories — and records nothing about how many are included in whatever package is running. That is a deliberate rule for the catalogue and it is a deliberate rule for this page: a transient commercial term recorded as data becomes a fact that outlives its truth.

So confirm the number with the zone directly, in writing, for the licence you are actually applying for, and confirm what happens at renewal. An allowance that applies at first issue is not automatically the allowance that applies in year two, and the fee for exceeding it is separate from the fee for holding it.

Where an authority publishes no combination rule at all, absence of a published rule is not permission. It means the rule is applied at assessment, and the only way to know it is to ask before you pay.

The useful question is not 'how many can I fit', it is 'which rows describe the work a client will actually ask me to do'. Activities you list because they were free are activities you will renew, and in registers that price by code group they can be the rows that push you into a second group.

A worked example, using rows that genuinely exist in the registers we capture. A corporate services firm typically finds its clients asking for adjacent things: the accounts, then the tax filing, then the corporate housekeeping, then something legal-adjacent. Those needs map onto real register rows — Accounting & Bookkeeping, Tax Consultant or Tax Consultancy depending on the register's wording, Corporate Services Provider (CSP), and a legal advisory row. The first three sit in the same service-side family at the registers we capture, which is what makes them plausible neighbours on one licence. The fourth is where the example turns, because the row a corporate services client asks for most naturally is the one an authority may refuse to let you hold at all: DMCC files Legal Consultants as 7411-02 in its Service family, and states in the row itself that 'Legal Consultancy activity is a standalone activity and cannot be conducted with other activities as informed by The Government of Dubai Legal Affairs Department'. Commercially obvious, structurally forbidden — at that authority, on that row.

The same register makes the point twice, and the second time it makes it against the code. Auditing of Accounts and Accounting & Bookkeeping are as adjacent as two rows get at DMCC: consecutive codes, 7412-01 and 7412-02, sharing the 7412 prefix that DMCC's own combination rule uses to decide what groups cheaply. They still may not be held together. The auditing row states 'Branch of local companies only. Not allowed to conduct the activities ‘’7412-02-Accounting & Bookkeeping’’ and ‘’7412-01-Auditing of Accounts’’ together at the same time.' — a restriction on the pairing and a restriction on who may hold the row at all, both published in the row a reader would have skimmed past. So the lesson is not that approvals make combining harder. It is that code adjacency is not permission to combine: the code tells you what the fee table does, and the restriction text tells you what the authority allows, and only the second one is the answer.

The approvals are the third layer, on top of both. DMCC and IFZA each record the auditing row as requiring Ministry of Economy approval, and IFZA states the timing — before the licence is issued, which puts a second regulator's queue on the critical path of your formation rather than on a to-do list afterwards. Adding a row like that is not a bigger version of the same application; it introduces a decision-maker who was not previously in your file.

That is the whole lens, and it invents no rule: work out what your clients will ask for, find the rows in your register that describe it, and then check each row for the approval it drags in behind it. What is common in a market is not evidence of what an authority permits, and this page does not claim otherwise.

Every question below has a specific answer at every authority. A provider who answers them with a number and no source has answered a different question.