Skip to content
Cross-border6 min read2026

Running one AI governance model across the Gulf and Europe

Organisations operating in Dubai, London and the EU face three regimes and one engineering budget. The reconcilable part is larger than most teams assume.

Contents

  1. 01Three regimes, one system
  2. 02Where the real divergence is
  3. 03Practical footing

Three regimes, one system

The DIFC and wider UAE frameworks, the UK's regulator-led approach and the EU AI Act differ in scope, enforcement and documentation. They agree almost entirely on what the underlying system must be able to do: explain a decision, limit an action, and prove both.

That agreement is what makes a single technical model viable across markets, even when the filings are separate.

Where the real divergence is

Data residency, notification timelines and the definition of a sensitive use case are the genuine forks. These are configuration and hosting decisions, and they are cheaper to make once, deliberately, than to retrofit per market.

Everything downstream of them, the logging, the receipts, the oversight path, can be shared.

Practical footing

We are registered in the DIFC, Dubai, and deliver into the UK and EU with the same team and the same method. For groups operating across all three, that removes a layer of translation between advisor, engineer and regulator.

“Write the control once at the strictest bar you face, then vary the paperwork by jurisdiction rather than the system.”

The thesis

The next generation of software will not wait to be asked. It will understand, decide, act, and prove what it did.

We’re building that generation from Dubai’s DIFC, for organisations that have to answer for what their systems do.