Guide
Setting Up an AI Agent Platform for Regulated Industries in the UAE
The short answer
Whether a UAE AI-agent platform needs a licence turns on what the agent is authorised to do, not on the word "AI" in its marketing. If it initiates payments, extends credit, executes trades or settles virtual-asset transactions, the regulator with jurisdiction over that underlying activity decides what authorisation applies. That regulator is the Central Bank of the UAE (CBUAE), the Capital Market Authority (CMA, the federal onshore markets regulator reconstituted from the former Securities and Commodities Authority on 1 January 2026), the Dubai Financial Services Authority (DFSA) in the DIFC, the Financial Services Regulatory Authority (FSRA) in the ADGM, or the Virtual Assets Regulatory Authority (VARA) in Dubai. If the agent only drafts, flags or recommends for a person to approve, the operating company still carries UAE data-protection and cyber-security duties, just not a financial or virtual-asset licence. The fact that most often decides the route is whether a human signs off before the agent's action takes effect.
Which regulator decides, and on what test
The test is the activity the agent is authorised to carry out, not the sector it is sold into. An agent that drafts a credit memo for a loan officer to sign is different from one that approves the loan; an agent that flags a suspicious trade is different from one that places it. Once the agent crosses from support into execution of a licensed activity, the regulator for that activity decides the route: the CBUAE for banking, lending and payment activities; the CMA for onshore securities and commodities business; the DFSA for financial services conducted from the DIFC; the FSRA for financial services conducted from the ADGM; and VARA for virtual-asset activities carried out in Dubai outside the DIFC. A platform that serves several of these clients at once (a bank in the mainland, a fund in the DIFC, an exchange under VARA) usually answers to more than one regulator, not one licence that covers all of them. Founders building for virtual-asset clients should treat the VARA setup route as a separate track from a conventional fintech build, because the two regulators test different things. For automated investment advice, the robo adviser guide explains the test between advice and discretion.
What the data-protection and cyber-security rules already require, licence or not
Two duties apply before any sector regulator is in scope. Federal Decree Law No. 45 of 2021 Regarding the Protection of Personal Data, in force since 2 January 2022, prohibits processing personal data without the owner's consent except in limited cases, and that applies to whatever the agent collects, stores or shares, even if the platform never needs a financial or virtual-asset licence. The UAE Data Office acts as the federal data regulator. Separately, the UAE Cyber Security Council sets the national cyber-security posture expected of systems handling sensitive or critical data, which an agent with standing access to customer records, health files or payment rails is likely to be treated as. Both duties attach to what the system actually touches, not to its licence category or to a description of the product as "just software". For a structure that originates or holds loans through an SPV, the private credit and securitisation guide explains which regulator authorises each function.
How banks and regulated customers read the agent's permissions
A bank opening an account, or a regulated customer onboarding the platform, is underwriting the agent's permissions, not its pitch. Before that conversation starts, be ready to show a tool-permission matrix (what the agent can call, and under what condition), a data-flow and retention map, the human-approval threshold for each action class, and how errors are detected and reversed. Bank account readiness for this kind of platform turns on whether those four documents are consistent with each other and with the customer contract, not on the size of the pitch deck. A mismatch between what the sales material claims the agent does and what the permission matrix actually allows is the fastest way to stall both a bank review and a regulated customer's procurement.
Ownership, substance and the roles the business needs to fill
The entity that signs the customer contract should be the one that holds the compliance function, not a lightly staffed shell with the real work sitting elsewhere in the group. Where the underlying activity is regulated, the regulator will expect a named, fit-and-proper person responsible for compliance before it authorises the business: the specific role and test vary by regulator and are confirmed against the live application, not published here as a fixed list. Groups serving both DIFC- or ADGM-regulated clients and onshore clients typically need separate entities for each, because DFSA, FSRA and onshore UAE company rules are not interchangeable. This is the point at which a regulated or complex ownership structure is usually worth setting up properly rather than bolted on after the first regulated customer asks for it.
What commonly goes wrong with regulated AI-agent platforms
- Describing an autonomous decision system as "only software" to avoid the regulatory conversation.
- Giving the agent standing credentials across every system it might need, instead of scoping access action by action.
- Not preserving a durable log of what the agent did and who approved it, which is the first thing a regulator or bank asks for after an incident.
- Marketing a compliance or professional outcome ("regulator-approved," "bank-grade") that the licence held does not actually confer.
- Treating human sign-off as a checkbox rather than a real control, so the record shows approval without anyone having reviewed the action.
Cost is built in layers rather than one headline figure (entity, any sector authorisation, and the compliance roles above each carry their own cost) and the Velarozone service fee for putting that together is itemised in the engagement letter; see how Velarozone works.
How the entity, visas and tax fit around the licence decision
Once the regulator and the operating model are settled, formation follows rather than leads: a DIFC or ADGM entity if the activity sits inside that financial centre's perimeter, a mainland or free-zone entity if it does not. Federal Tax Authority (FTA) corporate tax registration and filing obligations apply to the operating entity regardless of which route is chosen, and licence renewals, visa quotas and any sector authorisation typically renew on separate annual cycles that need tracking together, not as an afterthought once the business is live. For the formation mechanics themselves, see UAE business formation step by step.

