How to Set Up an AI Data Centre Company in the UAE

No single regulator licenses an AI data centre end to end. The operating company's commercial and technology activities are licensed by the mainland economic department where it is based, or by the relevant free zone authority if it sits in a free zone — but that licence does not cover land use, construction, power or connectivity.

Telecommunications and connectivity sit with TDRA, which registers and approves telecom equipment suppliers, handles customs release permits for telecom equipment, and licenses trust service providers. A data centre importing networking or power-management hardware, or selling connectivity as part of its service, works through TDRA's supplier and equipment approvals rather than assuming the commercial licence covers it.

Personal data processed on the facility's systems falls under Federal Decree-Law No. 45 of 2021, the Personal Data Protection Law, in force since 2 January 2022 and overseen by the UAE Data Office, the federal regulator attached to the Cabinet. It governs data processed electronically inside or outside the country, requires consent before processing subject to limited exceptions, sets cross-border transfer conditions, and gives data subjects rights to correct or restrict use of their data. A facility hosting third-party workloads should map which tenants bring personal data into scope — that obligation sits with the data controller, not automatically with the host.

Land, construction, civil-defence and utility approvals come from the municipality, civil-defence authority and utility or grid operator for the site, each on its own timeline, outside any single regulator's remit — and have to be confirmed site by site before a jurisdiction or activity code is picked.

The UAE's current reference point for scale is Stargate UAE, the cluster G42 is building within the UAE–US AI Campus in Abu Dhabi, to be operated by OpenAI and Oracle with Nvidia, SoftBank and Cisco also involved: 1 gigawatt of capacity inside a wider 5-gigawatt, roughly ten-square-mile campus, powered by nuclear, solar and natural gas, with a first 200-megawatt phase expected live in 2026. Most developers build at a smaller scale, but utilities, lenders and anchor customers now use that project as the reference for what a build can power, by when, and from what source.

Fix these before any entity decision:

Cost in this sector is built in layers — land or shell, power and cooling, hardware, people, and recurring obligations — rather than one headline figure; the Velarozone fee for this work is itemised in the engagement letter, and how Velarozone works sets out how those layers are priced.

If more than one function applies — owning the site, operating it, financing it, contracting with end customers — expect a group rather than a single company: an asset owner, an operator, sometimes a separate customer-contracting entity. Infrastructure lenders and anchor tenants often require that separation before they will sign; one company holding land, debt, hardware and customer risk at once is harder to finance, not easier.

The entity that signs customer contracts should hold the people, premises, systems and risk needed to deliver them. An asset-owning special purpose vehicle, an IP company or an overseas parent can sit elsewhere in the group, but each needs a genuine role tied to financing or liability, not a lower headline setup cost — a structure built to look cheap on a formation invoice usually resurfaces as transfer-pricing questions, bank queries and renewal cost once hardware is racked and contracts are signed. Group structures with more than one shareholder class or jurisdiction layer benefit from being tested against regulated and complex ownership setup before incorporation.

A facility of this kind needs an engineering and operations lead, a security and cybersecurity function, and someone accountable for compliance and finance before a bank, lender or anchor customer will engage seriously — these roles, and the visas behind them, are part of the setup decision, not something fixed after the licence is issued.

Banks, lenders and anchor customers underwrite the project, not the licence. Before onboarding begins, be ready to show evidence of site and power discussions, capex and procurement assumptions, anchor-customer or pipeline evidence, network and cybersecurity architecture, and an experienced development and operations team. A plan that reconciles the site story, the funding story and the customer story across the deck, the financial model and the contracts removes avoidable questions; Velarozone's work on business plans and documentation and corporate bank account readiness sits alongside that stage.

Funds raised or held for the project sit in segregated client accounts with licensed institutions under regulator oversight, the same as any other corporate account. Where capital comes from several investors or an overseas parent, document the source of those funds early — see source of wealth and funds for what a bank typically asks for. None of this guarantees an account, financing or approval; it removes the questions that stall one.