>
The Sovereign Stack : GCC Digital Sovereignty Outlook
Volge
Quarterly
Q2 2026 · The Digital Sovereignty issue
Trust Fabric
Trust as infrastructure
Foundation
The data-engineering gap
AI FAQs
101 for the board

Sovereign
Stack

Sovereign compute, Arabic models and national champions: what is truly sovereign, and what runs on imported silicon.

volge.com/quarterlyComplimentary editionISSN 2977-4404 · 05

Volge Quarterly is Volge's signature series, published every quarter for enterprise customers. Each edition takes one subject, sets out where it currently stands on the published record, and makes a set of dated, falsifiable judgements on where it is going, written to give a buyer something firmer than a forecast: every figure carries its source and its date, every judgement carries the date on which it resolves, and the following year's edition grades each one hit, missed or partial.

In 2027 Gulf sovereignty moves from mandate to architecture. Residency rules, sovereign cloud regions and national control are rebuilding the regional stack layer by layer, and national data-classification tiering is the single mechanism that connects them, deciding for every workload whether it runs in a public region, a sovereign region or an air-gap.

Figures carry their basis and their date. Where published estimates disagree, the range is given and the basis named rather than averaged away, and where a widely quoted number does not survive checking it is corrected here rather than repeated. Every chart plots a figure stated in the text, and nothing is projected beyond what a named source projects.

Contents

  1. 02The year sovereignty stops being a mandate and becomes an architecture
  2. 02The state of the sector
  3. 02The region in numbers
  4. 03The two sovereignty models, and the switch between them
  5. 03Sovereign cloud: the footprint and what it cost
  6. 04Sovereign AI & chips: the national compute programmes
  7. 05The dependence paradox: sovereignty, licensed abroad
  8. 05Saudi Arabia and the UAE: the two poles
  9. 06Qatar, Kuwait, Bahrain and Oman: the four that set the range
  10. 07The forces shaping the year
  11. 07From mandate to architecture
  12. 07The dependence paradox
  13. 07Classification is the switch
  14. 08The sovereign premium
  15. 08National models of compute
  16. 09Keys, confidential computing and air-gaps
  17. 10The buyer's ground
  18. 10The rules that bind, country by country
  19. 12Saudi Arabia: classification sets the control, and procurement sets the clock
  20. 13The UAE: the first published sovereignty taxonomy in the region
  21. 15Qatar, Bahrain, Oman and Kuwait: four regimes that are not one regime
  22. 16What has actually been built
  23. 18Sovereign AI: announced capacity against energised capacity
  24. 20What sovereignty costs
  25. 21A framework for placing a workload
  26. 22The dated calendar, 2026 to 2028
  27. 24The dependence question
  28. 25India, for contrast
  29. 27Sovereignty by sector
  30. 27Banking: the only sector where the rule is written as a place
  31. 28Healthcare: one state legislates the place, the rest legislate the permission
  32. 30Energy and utilities: a borrowed obligation, a secret perimeter, and a clause that has been deleted
  33. 31Government: the state built the sovereign cloud instead of regulating it
  34. 33Telecommunications: the only sector where the regulator licenses the host
  35. 34Aviation, logistics and ports: the sector with no rule, and why that is the risk
  36. 36The six compared, and the test for placing any workload
  37. 38The year ahead: the Calls
  38. 38The Calls: 2027, at a glance
  39. 38Calls one to three
  40. 39Calls four to six
  41. 39Calls seven and eight
  42. 39Calls nine and ten
  43. 40How the Calls are made
  44. 40By domain, and three scenarios
  45. 40Technology and markets
  46. 41Regulation and delivery
  47. 41Three scenarios for 2027
  48. 42What to watch, and the record
  49. 42The watchlist
  50. 42Regulatory crosswalk
  51. 43Sources
  52. 44Glossary and method
Volge Quarterly is Volge's signature series, published every quarter for enterprise customers.
A Volge Quarterly edition · Panache Editions · 2027
Digital SovereigntyVolge Quarterly01 •

The year sovereignty stops being a mandate and becomes an architecture

2027 is the year Gulf digital sovereignty stops being a policy mandate and becomes an engineering specification.

For most of the past dec­ade, sov­er­eignty in the Gulf was a state­ment of in­tent. A min­istry de­clared that gov­ern­ment data would stay in-coun­try; a cab­inet de­cree an­nounced a cloud-first policy; a na­tional vis­ion prom­ised an ar­ti­fi­cial-in­tel­li­gence eco­nomy. What the re­gion did not yet have was the ma­chinery to make those state­ments op­er­a­tional: the phys­ical re­gions, the cer­ti­fied op­er­at­ors, the key-man­age­ment sys­tems and, above all, a com­mon way to de­cide which data could sit where. That ma­chinery is now largely in place, and 2027 is the year it starts to bind. Sov­er­eignty ceases to be a clause in a strategy doc­u­ment and be­comes a set of choices made, work­load by work­load, in­side a pro­cure­ment.

The mech­an­ism that con­nects every part of this story is na­tional data-clas­si­fic­a­tion tier­ing. Each Gulf state has, or is com­plet­ing, a scheme that sorts data into tiers: Qatar's runs from C0 Pub­lic to C4 Top Secret [NCSA Na­tional Data Clas­si­fic­a­tion Policy v3.0, 2023]; Saudi Ar­a­bia's and Kuwait's turn on four levels with the top two loc­al­ised [CST CCRF, 2018-19; CITRA Cloud Frame­work Res 112, 2021]. The tier a data­set car­ries de­term­ines the host­ing model it is per­mit­ted: a pub­lic hy­per­scaler re­gion, a sov­er­eign re­gion op­er­ated by vet­ted na­tion­als, or, for the most sens­it­ive ma­ter­ial, an air-gapped en­clave. Clas­si­fic­a­tion is there­fore the switch. It is the single con­trol that trans­lates a polit­ical pref­er­ence for sov­er­eignty into an in­struc­tion a cloud ar­chi­tect can fol­low.

Classification is the switch: public region, sovereign region, or air-gap.

Two mod­els sit either side of that switch. The loc­al­isers (Saudi Ar­a­bia, Kuwait and Oman) hold sens­it­ive and gov­ern­ment data in­side na­tional bor­ders and per­mit ex­port only under tightly drawn con­di­tions. The open hosts (Bahrain and Qatar) in­vite for­eign data onto their soil, and in Bahrain's case guar­an­tee that it re­mains gov­erned by the cus­tomer's home law [Data Em­bassy De­cree 56/2018]. Both mod­els are an­swers to the same ques­tion, and both are being tested in 2027 by the same force: a build-out of cloud and ar­ti­fi­cial-in­tel­li­gence ca­pa­city lar­ger than any­thing the re­gion has at­temp­ted.

The Ed­it­ors, Volge Quarterly · 2027

That build-out car­ries a para­dox at its centre. The Gulf is as­sem­bling sov­er­eign com­pute at ex­traordin­ary scale (the United States has agreed to li­cense the United Arab Emir­ates up to 500,000 ad­vanced NVIDIA chips a year [US-UAE AI Ac­cel­er­a­tion Part­ner­ship, 15-16 May 2025]), yet every one of those chips, and much of the se­cur­ity op­er­at­ing the sov­er­eign clouds around them, de­pends on United States ex­port li­cences and United States-op­er­ated con­trols. What the re­gion se­cures is the sov­er­eignty of its data and its model out­puts, not the sov­er­eignty of its sup­ply chain. The chip cap is, in ef­fect, a real-time throttle held in Wash­ing­ton. Cap­ital is not the con­straint; chips, power and tal­ent are.

The Calls in this edi­tion put dates and con­fid­ence levels on how these forces re­solve through 2027. They are writ­ten to be graded a year from now. Read them as the firm's con­sidered judge­ment on a re­gion at an in­flec­tion, and as a stand­ing in­vit­a­tion to mark our home­work in 2028.

The state of the sector

A cloud and compute build-out crossing tens of billions of dollars, governed by six data-protection regimes and one shared idea: that the tier a dataset carries should decide where it is allowed to live.

The region in numbers

The reconciled basis used throughout this edition, on one page. Where credible sources differ on scope, a range is given rather than a false point estimate; every figure is sourced and year-stamped.

  • Saudi cloud mar­ket: $15.4→$27.9B, 2025→2030 [Mordor In­tel­li­gence, 2025]
  • UAE cloud mar­ket: $12.8→$56.3B, 2025→2031 [Mordor In­tel­li­gence, 2025]
  • Dis­closed hy­per­scaler com­mit­ments: >$13–15B, GCC re­gions, AWS/Or­acle/Mi­crosoft (2024–25)
  • Middle East live data-centre ca­pa­city: 1,115 MW, 2026, about 2.2 GW; 1.2 GW at end-2025 and 3.2 GW in 2027 [Knight Frank, Data Centre Atlas 2026]
  • MEA coloca­tion mar­ket: $3.3→$12.9B, 2025→2031 [Ar­izton, 2025]
  • NVIDIA chips/yr li­cens­able to the UAE: 500,000, US-UAE part­ner­ship [15–16 May 2025]

The capital behind the build

  • Saudi PIF as­sets: $1.21tn, Up from ~$925bn; funds HUMAIN [PIF, 2025]
Digital SovereigntyVolge Quarterly02 •
  • Mubadala as­sets: ~$385bn, Par­ent of MGX, whose Fund I closed at about $49bn in July 2026 against a $45bn tar­get; $100bn is an AUM am­bi­tion, not a fund size
  • The sov­er­eign premium: 15–30%, Over pub­lic cloud; ana­lyst con­sensus, dir­ec­tional [2025]

Re­con­ciled from Mordor In­tel­li­gence and Ar­izton mar­ket siz­ing, Knight Frank data-centre track­ing, the US-UAE AI Ac­cel­er­a­tion Part­ner­ship readout, and sov­er­eign-fund dis­clos­ures (2024–26). Ranges re­flect genu­ine source dis­agree­ment on scope. Cur­rent to July 2026.

The one-line read

A cap­ital-rich, power-cheap re­gion buy­ing com­pute ca­pa­city faster than it can staff or sup­ply it, where the bind­ing con­straints are chips, power and tal­ent, and the de­cis­ive vari­able is a United States ex­port li­cence, not a Gulf bal­ance sheet.

The two sovereignty models, and the switch between them

Two models of digital sovereignty have emerged in the Gulf. They are opposite answers to one question (may foreign or sensitive data leave the country), and both are operated through the same instrument: national data-classification tiering.

The first model is loc­al­isa­tion. Saudi Ar­a­bia bars the ex­port of gov­ern­ment data and re­quires its two most sens­it­ive data levels to be held in-coun­try [CST CCRF, 2018-19]; Kuwait re­quires its private-sens­it­ive (L3) and highly-sens­it­ive (L4) tiers to re­main on Kuwaiti soil, ex­empt­ing only De­fence and In­terior [CITRA Cloud Frame­work Res 112, 2021]; Oman keeps sens­it­ive cross-bor­der trans­fers sub­ject to Cyber De­fence Centre ap­proval [PDPL Royal De­cree 6/2022]. The loc­al­iser's premise is that con­trol fol­lows geo­graphy: data held on na­tional ter­rit­ory, op­er­ated by vet­ted na­tion­als, is data the state can pro­tect.

The second model is the open host. Bahrain's Data Em­bassy law is the purest ex­pres­sion of it: under De­cree 56/2018, for­eign data hos­ted on Bahraini soil re­mains gov­erned by the cus­tomer's home law, and Bahraini au­thor­it­ies are barred from ac­cess­ing it. Qatar, too, po­s­i­tions it­self as a re­gional host with a ma­ture clas­si­fic­a­tion and cloud-policy stack. The open host's premise is the in­verse of the loc­al­iser's: that a cred­ible legal guar­an­tee, not a bor­der, is what makes data sov­er­eign, and that a small state com­petes by of­fer­ing law rather than land.

Bahrain's data embassy: your servers on our soil, your law over your data.

What both mod­els share is the switch. Every re­gime sorts data into clas­si­fic­a­tion tiers, and maps each tier to a per­mit­ted host­ing model. The lower tiers may sit in a pub­lic hy­per­scaler re­gion; the middle tiers re­quire a sov­er­eign re­gion op­er­ated under na­tional con­trol; the top tier is con­fined to an air-gapped en­clave. On top of geo­graphy sit four tech­nical lay­ers that harden each rung: data res­id­ency; na­tional op­er­a­tion by vet­ted local staff; cus­tomer con­trol of en­cryp­tion keys through bring-your-own-key or hold-your-own-key schemes; and con­fid­en­tial com­put­ing (hard­ware-isol­ated ex­e­cu­tion using Intel TDX, AMD SEV-SNP or NVIDIA Con­fid­en­tial Com­put­ing) for data in use.

ModelPremiseStatesInstrument
LocaliserControl follows geographySaudi Arabia, Kuwait, OmanIn-country residency for top tiers; export controls
Open hostControl follows lawBahrain, QatarLegal guarantee over hosted foreign data
Shared switchControl follows classificationAll sixTier → permitted hosting model (public / sovereign / air-gap)

Sources: CST Cloud Com­put­ing Reg­u­lat­ory Frame­work (2018-19); CITRA Cloud Frame­work Res 112 (2021); Bahrain Data Em­bassy De­cree 56/2018; Qatar NCSA Na­tional Data Clas­si­fic­a­tion Policy v3.0 (2023). Cur­rent to July 2026.

Why it matters for 2027

The mod­els are di­ver­ging in law but con­ver­ging in mech­an­ism. Whichever premise a state ad­opts, the op­er­a­tional ques­tion a buyer faces is identical: what tier is this data­set, and which rung of the stack does that tier per­mit? That is the ques­tion 2027 pro­cure­ment is built around.

Sovereign cloud: the footprint and what it cost

The hyperscaler regions are the physical substrate of Gulf sovereignty. Their announced dates and disclosed investments are set out below; where a region is committed but not yet live, it is marked, because the gap between announcement and availability is itself a 2027 story.

Sov­er­eign cloud in the Gulf is being built along two tracks at once. The global hy­per­scalers (Amazon Web Ser­vices, Mi­crosoft, Or­acle, Google) are open­ing in-coun­try re­gions and, in­creas­ingly, ded­ic­ated sov­er­eign or air-gapped vari­ants op­er­ated to na­tional re­quire­ments. Along­side them, na­tional cham­pi­ons (Core42 in the United Arab Emir­ates, Center3 and HUMAIN in Saudi Ar­a­bia, Beyon in Bahrain, Oman Data Park) provide the sov­er­eign op­er­at­ing layer that vet­ted local staff and cus­tomer key con­trol de­mand. The table re­cords the dis­closed com­mit­ments; the cap­tion re­cords the caveats.

Sources: pro­vider an­nounce­ments and Volge track­ing (2024–26). Kuwait's Google and Mi­crosoft re­gions re­main com­mit­ted but not op­er­a­tional as of July

Digital SovereigntyVolge Quarterly03 •
ProviderLocationStatus / dateDisclosed investment
Amazon Web ServicesSaudi ArabiaAI Zone / region build-out>$5.3bn [AWS, 2024]
OracleSaudi Arabia10-year regional commitment$14bn [Oracle, 2024-25]
Amazon Web ServicesUAERegion~$5bn [AWS, 2024]
MicrosoftUAETo 2029; plus $1.5bn into G42$15.2bn [Microsoft, 2024-25]
AWS (first ME region)BahrainLive since 2019First hyperscale ME region
Google CloudKuwaitAnnounced 24 Jan 2023, not liveUndisclosed
Microsoft Azure (AI region)KuwaitAnnounced 6 Mar 2025, not liveUndisclosed

2026: the basis of Call 9. Dis­closed hy­per­scaler GCC com­mit­ments ex­ceed $13–15bn in ag­greg­ate.

Two fea­tures dis­tin­guish the Gulf build from a ma­ture mar­ket. First, the sov­er­eign vari­ant is now the de­fault ask, not a premium op­tion: Abu Dhabi's Di­gital Strategy 2025-27 com­mits AED 13bn and tar­gets a gov­ern­ment run­ning on 100% sov­er­eign cloud, AI-nat­ive by 2027 [Abu Dhabi, 2025]. Second, the eco­nom­ics still fa­vour the re­gion as a place to build (power at $0.05–0.07 per kilo­watt-hour is among the cheapest avail­able to any hy­per­scaler [ana­lyst es­tim­ates, 2025]) even as the sov­er­eign layer adds a 15–30% premium over pub­lic cloud for the buyer.

The read

The sub­strate is largely com­mit­ted; the vari­able is de­liv­ery. A re­gion an­nounced is not a re­gion live, and in 2027 the dif­fer­ence de­term­ines whether a state's sov­er­eignty runs on hy­per­scaler steel or on telco-and-NVIDIA im­pro­visa­tion.

Sovereign AI & chips: the national compute programmes

The Gulf's two largest economies are each building national artificial-intelligence platforms of a scale that has no precedent outside the United States and China. Both rest on imported silicon, and both pair the compute with a national large language model.

Saudi Ar­a­bia's vehicle is HUMAIN, a Pub­lic In­vest­ment Fund com­pany launched on 12 May 2025 and chaired by the Crown Prince, po­si­tioned as a pro­gramme of the order of $100bn [PIF, 2025]. Its com­pute com­mit­ments are ex­traordin­ary: NVIDIA an­nounced on 22 Oc­to­ber 2026 a con­crete pipeline of up to 84 MW and about 27,000 GPUs in two phases through 2027, against HUMAIN tar­gets of about 3 GW by 2030 and over 6 GW by 2034; the earlier fram­ing was an ini­tial 18,000 GB300 units and sev­eral hun­dred

thou­sand GPUs over five years across 500 MW; AMD a $10bn, 500 MW com­mit­ment; an AWS AI Zone of more than $5bn; Or­acle's $14bn; and, from Novem­ber 2025, a 500 MW xAI-HUMAIN build [com­pany an­nounce­ments, 2025]. Center3 tar­gets 1 GW by 2030. The na­tional model is ALLaM, SDAIA's Ar­abic large lan­guage model, which has powered HUMAIN Chat since Au­gust 2025.

The United Arab Emir­ates runs a par­al­lel pro­gramme through G42, chaired by Sheikh Tahnoon bin Zayed and led by Peng Xiao, which took a $1.5bn Mi­crosoft in­vest­ment and a Brad Smith board seat in April 2024 after di­vest­ing its China and Hua­wei ex­pos­ure in 2023-24. Its flag­ship is Star­gate UAE, an­nounced on 22 May 2025: a 1 GW cluster within a 5 GW Abu Dhabi AI cam­pus, first 200 MW live in 2026, backed by OpenAI, Or­acle, NVIDIA, Cisco, SoftBank and G42 and built by Khazna: a build the UAE's AI min­is­ter put above $30bn in Janu­ary 2026. The na­tional mod­els are the Tech­no­logy In­nov­a­tion In­sti­tute's Fal­con fam­ily (Fal­con-H1 and Fal­con Ar­abic, both May 2025) and Jais, from G42, In­cep­tion, MBZUAI and Cereb­ras.

HUMAIN: a $100bn bet that sovereignty and scale are the same project.

The national large language models

Four sov­er­eign Ar­abic mod­els now com­pete for gov­ern­ment ad­op­tion: ALLaM (SDAIA, Saudi Ar­a­bia), Fal­con (TII, UAE), Jais (G42 and part­ners, UAE) and Fanar (QCRI, Qatar). Fal­con-H1 is a hy­brid ar­chi­tec­ture reach­ing 34B para­met­ers with a 256K-token con­text win­dow across 18 lan­guages [TII, May 2025]. The stra­tegic point is not bench­mark lead­er­ship but proven­ance: a model trained, hos­ted and gov­erned in-re­gion is it­self a sov­er­eignty claim, and its ad­op­tion into a gov­ern­ment pro­duc­tion work­flow is the test that Call 8 sets for 2027.

The read

Two na­tional com­pute pro­grammes, four na­tional mod­els, one de­pend­ency. Every layer above the sil­icon is genu­inely sov­er­eign; the sil­icon it­self, and the se­cur­ity op­er­at­ing much of the sov­er­eign cloud around it, is li­censed abroad. That ten­sion is the sub­ject of the next page.

The para­dox is that the same ar­range­ment that un­locks the chips also en­codes the de­pend­ency. A flow that can be made li­cence-free can be made li­cence-bound again; a Coun­try Group can be re-tiered; a

Digital SovereigntyVolge Quarterly04 •

real-time en­force­ment frame­work op­er­ated to United States re­quire­ments is, by con­struc­tion, a con­trol the United States can tighten. The chip cap is there­fore best un­der­stood not as a ceil­ing but as a throttle: a vari­able held out­side the re­gion. Sen­ator War­ren's cri­ti­cism of the G42, MGX and Trump-crypto ties is a re­minder that the ar­range­ment is polit­ic­ally con­tin­gent as well as com­mer­cially struc­tured.

The dependence paradox: sovereignty, licensed abroad

The central tension of Gulf sovereign AI is that its supply chain is not sovereign. Every advanced chip in the region enters under a United States export licence, and much of the security operating the sovereign clouds runs on United States-defined controls. What is secured is the sovereignty of data and output, not of supply.

The mech­an­ism is ex­pli­cit. Under the US-UAE AI Ac­cel­er­a­tion Part­ner­ship of 15-16 May 2025, the United States agreed to li­cense up to 500,000 ad­vanced NVIDIA chips a year into the Emir­ates: roughly a fifth to G42, the re­mainder to United States hy­per­scalers op­er­at­ing there. The Biden ad­min­is­tra­tion's AI Dif­fu­sion Rule, which would have capped such flows, was res­cin­ded on 13 May 2025. First li­cences fol­lowed around 9 Oc­to­ber 2025, ini­tially for United States-op­er­ated data centres only, with G42 ex­cluded until it was cleared on 20 Novem­ber 2025. On 10-11 July 2026 the Emir­ates moved to Coun­try Group A:5. The con­ces­sion is nar­rower than it reads: G42 and Core42 hold time-lim­ited Sup­ple­ment 8 eli­gib­il­ity that ex­pires on 6 April 2027 un­less re­newed or un­less they be­come US com­pan­ies, and Saudi Ar­a­bia was not moved to A:5 and re­mains li­cence-by-li­cence. Within those lim­its the flow is li­cence-free for G42, Core42, Amazon, Apple, xAI, Google, Meta, Mi­crosoft, OpenAI and Or­acle.

500,000 NVIDIA chips a year: the sovereignty of output, licensed by Washington.
  • Ad­vanced chips/yr, li­cens­able: 500,000, ~20% to G42; rest to US hy­per­scalers [May 2025]
  • AI Dif­fu­sion Rule res­cin­ded: 13 May 2025, Cap re­moved; part­ner­ship an­nounced days later
  • UAE to Coun­try Group A:5: 10–11 Jul 2026, Li­cence-free for named op­er­at­ors

The read

The Gulf can own its data, its keys and its model weights, and it in­creas­ingly does. It can­not yet own the fab­ric­a­tion of its com­pute. Sov­er­eignty of the stack is real from the sil­icon up­ward and pro­vi­sional at the sil­icon it­self, and that single fact is the swing factor the Calls re­turn to.

Saudi Arabia and the UAE: the two poles

The Gulf stack has two centres of gravity. Saudi Arabia is the archetypal localiser at national scale; the United Arab Emirates is the region's compute hub and its most complex legal map. Between them they set the terms the smaller states adapt.

Saudi Arabia: the localiser at scale

Saudi Ar­a­bia's Per­sonal Data Pro­tec­tion Law, is­sued as Royal De­cree M/19 in 2021, amended by M/148 in 2023 and fully en­forced from 14 Septem­ber 2024, is ad­min­istered by SDAIA. It re­quires breach no­ti­fic­a­tion within 72 hours and car­ries fines to SAR 5m, doub­ling to SAR 10m for re­peat of­fences, with sens­it­ive-data mis­use pun­ish­able by up to two years and SAR 3m. The 2024 Data Trans­fer Reg­u­la­tion per­mits cross-bor­der move­ment under ad­equacy find­ings, stand­ard con­trac­tual clauses or bind­ing cor­por­ate rules: a mech­an­ism this edi­tion ex­pects to be­come the de-facto Gulf stand­ard (Call 2). Above the data law sits the CST's Cloud Com­put­ing Reg­u­lat­ory Frame­work, a four-level con­tent clas­si­fic­a­tion under which the top two levels are loc­al­ised, and a Cloud First Policy. The com­pute layer (HUMAIN, Center3, ALLaM) is ex­amined on page 05.

The United Arab Emirates: the hub with three regimes

The Emir­ates' fed­eral Per­sonal Data Pro­tec­tion Law, Fed­eral De­cree-Law 45/2021, came into force on 2 Janu­ary 2022 under the UAE Data Of­fice (Law 44/2021), whose func­tions passed to the Fed­eral Au­thor­ity for Ar­ti­fi­cial In­tel­li­gence and Data on 14 June 2026, but its ex­ec­ut­ive reg­u­la­tions re­mained un­pub­lished into mid-2026, so the com­pli­ance grace period had not been triggered and a de-facto 72-hour breach norm pre­vailed. Two fin­an­cial free zones op­er­ate in­de­pend­ently: the DIFC, under Data Pro­tec­tion Law 5/2020 with a 2025 amend­ment adding a private right of ac­tion, and the ADGM, under its 2021 reg­u­la­tions with fines to $28m and a ded­ic­ated Com­mis­sioner. Both are GDPR-aligned. The com­pute layer (G42,

Digital SovereigntyVolge Quarterly05 •

Core42, Star­gate UAE, Fal­con, Jais) and the 500,000-chip part­ner­ship make the Emir­ates the re­gion's AI centre, gov­erned by Abu Dhabi's Di­gital Strategy 2025-27 and its 100% sov­er­eign-cloud, AI-nat­ive-by-2027 tar­get.

The contrast

Saudi Ar­a­bia of­fers scale and a single, fully-en­forced na­tional re­gime; the Emir­ates of­fers the re­gion's deep­est com­pute and the most frag­men­ted legal map. A mul­tina­tional host­ing across both is man­aging one loc­al­isa­tion rule in Riy­adh and three reg­u­lat­ors in the Emir­ates: the prac­tical shape of Gulf sov­er­eignty in 2027.

Qatar, Kuwait, Bahrain and Oman: the four that set the range

The four smaller states span the full spectrum of Gulf sovereignty: the region's first data law, its most explicit localisation regime, its purest open-host guarantee, and its one hard enforcement cliff.

Qatar le­gis­lated first. Its Per­sonal Data Pri­vacy Pro­tec­tion Law 13/2016, in force from 13 Feb­ru­ary 2017, was the Gulf's earli­est, ad­min­istered by the NCSA and NCGAA with 72-hour breach no­ti­fic­a­tion and fines of QAR 1–5m. Above it sit the re­gion's most de­veloped clas­si­fic­a­tion stack: the Na­tional Data Clas­si­fic­a­tion Policy v3.0, run­ning C0 Pub­lic to C4 Top Secret with con­fid­en­ti­al­ity, in­teg­rity and avail­ab­il­ity im­pact scored 0-3; the NIA Stand­ard v2.1 (2023), a 2022 Cloud Policy Frame­work, the Fanar large lan­guage model from QCRI, and a Na­tional Data Pro­gram launched in 2025.

Kuwait has no om­ni­bus law, but CITRA's Data Pri­vacy Pro­tec­tion Reg­u­la­tion (Res 42/2021, up­dated by Res 26/2024, in force 19 Feb­ru­ary 2024) sets a 72-hour breach norm and re­quires ad­equacy for cross-bor­der trans­fers. Its Cloud Frame­work (Res 112, 2021) is the re­gion's most ex­pli­cit loc­al­iser: four tiers, with private-sens­it­ive (L3) and highly-sens­it­ive (L4) data re­quired to re­main in Kuwait, De­fence and In­terior ex­empt. With the an­nounced Google (24 Jan 2023) and Mi­crosoft (6 Mar 2025) re­gions not yet live, sov­er­eignty is being de­livered by telco and NVIDIA hard­ware: Oore­doo's first sov­er­eign AI data centre (10 Nov 2025, NVIDIA H200) and KISR's ICARUS HPC/AI plat­form (12 Aug 2025), the basis of Call 9.

Oman sets the re­gion's one hard date. Its PDPL (Royal De­cree 6/2022, in force 13 Feb­ru­ary 2023) and ex­ec­ut­ive reg­u­la­tions (Min­is­terial De­cision 34/2024) be­came fully en­force­able on 5 Feb­ru­ary 2026 and widened by Royal De­cree 68/2026 from 7 Septem­ber

2026, which adds ex­tra­ter­rit­orial reach, cuts the ex­emp­tions from ten to six and cre­ates a right to human re­view of auto­mated de­cisions after a final grace ex­ten­sion: the Gulf's only firm 2027-rel­ev­ant cliff. The MTCIT ad­min­is­ters it; sens­it­ive cross-bor­der trans­fers need Cyber De­fence Centre ap­proval, a DPO in Oman is pre­ferred, and fines reach RO 500,000. Oman Data Park provides sov­er­eign cloud and Oman­tel an­chors a sub­sea-cable hub.

Bahrain is the open host. Its PDPL (Law 30/2018, in force 1 Au­gust 2019) is ad­min­istered through the Min­istry of Justice with fines of BHD 1,000–20,000, but its sig­na­ture is the Data Em­bassy (De­cree 56/2018) and a Cloud-First policy that was the first in MENA (2017). AWS opened its first Middle East re­gion in Bahrain in 2019, and Beyon (the former Batelco) provides sov­er­eign cloud.

Oman's PDPL becomes the Gulf's one hard 2027 cliff: fully enforceable 5 February 2026.
Classification is the switch. Every Gulf regime, localiser or open host, routes the same question (what tier is this data) to the same three answers: public region, sovereign region, or air-gap.

The state of the sec­tor · Volge Quarterly 2027

The evid­ence is in the spe­cific­a­tions. Abu Dhabi's Di­gital Strategy 2025-27 does not merely prefer sov­er­eign cloud; it com­mits AED 13bn and tar­gets a gov­ern­ment run­ning en­tirely on it, AI-nat­ive, by 2027 [Abu Dhabi, 2025]. Saudi Ar­a­bia's Cloud First Policy is paired with a four-level clas­si­fic­a­tion frame­work that tells a buyer ex­actly which level may sit where [CST CCRF, 2018-19]. The move from man­date to ar­chi­tec­ture is what makes Call 1 (that clas­si­fic­a­tion-driven res­id­ency be­comes a de­fault clause in Gulf gov­ern­ment RFPs) a high-con­fid­ence judge­ment rather than a hope.

The cost of the shift is ri­gid­ity. An ar­chi­tec­ture, once spe­cified, is ex­pens­ive to change: a sov­er­eign re­gion is a phys­ical asset, a clas­si­fic­a­tion cata­logue is an in­sti­tu­tional com­mit­ment, and a key-man­age­ment re­gime binds a buyer to an op­er­ator. The Gulf is, in 2027, lock­ing in choices whose con­sequences run for a dec­ade, which is pre­cisely why the year re­wards get­ting the clas­si­fic­a­tion layer right, be­cause it is the one de­cision every later de­cision in­her­its.

Digital SovereigntyVolge Quarterly06 •

The forces shaping the year

Six through-lines that connect the region's build-out, its laws and its dependencies: from the shift out of mandate into architecture to the mechanics of keys, confidential computing and the air-gap.

From mandate to architecture

The defining shift of 2027 is that sovereignty stops being declared and starts being built. The mandate era produced policy; the architecture era produces regions, operators and clauses.

A man­date is a state­ment that cer­tain data be­longs at home. An ar­chi­tec­ture is the set of sys­tems that make the state­ment true: the in-coun­try re­gion, the vet­ted op­er­ator, the key-man­age­ment scheme, the clas­si­fic­a­tion cata­logue that tells an en­gin­eer where a given data­set may run. For most of the past dec­ade the Gulf had man­dates without ar­chi­tec­tures: Bahrain de­clared cloud-first in 2017, Kuwait set loc­al­isa­tion tiers in 2021, but the re­gions to host the data and the op­er­at­ors to run them were in­com­plete. What changes now is that the ar­chi­tec­ture is ar­riv­ing in volume, and a man­date met by an ar­chi­tec­ture be­comes a pro­cure­ment rule rather than an as­pir­a­tion.

A mandate met by an architecture becomes a procurement rule, not an aspiration.

The read

2027 is not the year sov­er­eignty is an­nounced: that happened years ago. It is the year sov­er­eignty is spe­cified, priced and signed. The through-line is the harden­ing of in­tent into in­fra­struc­ture.

The dependence paradox

The Gulf is building sovereign compute on a supply chain it does not control. The paradox is not a flaw in the strategy; it is the strategy's defining condition, and managing it is the region's central 2027 task.

Sov­er­eignty has lay­ers, and they do not all re­solve the same way. Data res­id­ency, na­tional op­er­a­tion, key con­trol and model weights can all be genu­inely sov­er­eign: held, run and owned in-re­gion. Sil­icon can­not. Every ad­vanced ac­cel­er­ator in the Gulf enters under a United States ex­port li­cence, and the real-time en­force­ment frame­works that con­di­tion those li­cences place United States-defined con­trols in­side the re­gion's most sov­er­eign fa­cil­it­ies. The 500,000-chip UAE part­ner­ship is the clearest case: it is

sim­ul­tan­eously the largest en­a­bler of Gulf sov­er­eign AI and the largest single ex­pres­sion of its de­pend­ence [US-UAE part­ner­ship, May 2025].

The de­pend­ence is dy­namic, not static. Between Janu­ary 2025 and July 2026 the gov­ern­ing re­gime moved through four states: the Dif­fu­sion Rule cap, its res­cis­sion, li­cence-by-li­cence ap­proval, and a li­cence-free Coun­try Group A:5 des­ig­na­tion. Each trans­ition changed the re­gion's ef­fect­ive com­pute ceil­ing without any change in Gulf policy or cap­ital. That is what it means for the chip cap to be a throttle: the vari­able that most de­term­ines Gulf sov­er­eign-AI ca­pa­city in 2027 sits in Wash­ing­ton, which is the sub­stance of Call 5.

The Gulf secures the sovereignty of its output, not of its supply chain.

The stra­tegic re­sponse is di­ver­si­fic­a­tion within the con­straint. AMD along­side NVIDIA; na­tional mod­els trained to run on whatever sil­icon is li­censed; sov­er­eign clouds en­gin­eered so that a change in chip sup­ply does not com­prom­ise data con­trol. None of it re­moves the de­pend­ence (fab­ric­a­tion re­mains out­side the re­gion), but it nar­rows the blast ra­dius of a li­cens­ing re­versal. The Gulf can­not make its sup­ply chain sov­er­eign in 2027; it can make its sov­er­eignty of data and out­put ro­bust to the sup­ply chain's volat­il­ity.

The read

Cap­ital is abund­ant; the con­straints are chips, power and tal­ent. Of the three, chips are the only one held abroad, and so the de­pend­ence para­dox, not the bal­ance sheet, is the ceil­ing on the year.

Classification is the switch

If a single instrument explains Gulf sovereignty, it is data classification. The tier a dataset carries decides the hosting model it is permitted, and so the classification catalogue is the control plane of the entire regional stack.

A clas­si­fic­a­tion scheme sorts data by sens­it­iv­ity and maps each tier to a per­mit­ted en­vir­on­ment. Qatar's is the re­gion's most ex­pli­cit: C0 Pub­lic through C4 Top Secret, each with con­fid­en­ti­al­ity, in­teg­rity and avail­ab­il­ity im­pact scored from 0 to 3 [NCSA v3.0, 2023]. Saudi Ar­a­bia's four con­tent levels and Kuwait's four cloud tiers do the same work: the lower tiers may sit in a pub­lic hy­per­scaler re­gion, the middle tiers re­quire a sov­er­eign re­gion under na­tional op­er­a­tion, and the top tier is con­fined to an air-gap. The scheme is

Digital SovereigntyVolge Quarterly07 •

not pa­per­work; it is the switch that con­verts a sens­it­iv­ity judge­ment into an ar­chi­tec­ture de­cision.

Be­cause the switch is shared across re­gimes, it is where prac­tical con­ver­gence is hap­pen­ing even as the stat­utes di­verge. A loc­al­iser and an open host dis­agree about whether data may leave the coun­try, but both agree that a Top Secret re­cord and a pub­lic data­set be­long in dif­fer­ent en­vir­on­ments, and both ex­press that agree­ment through a tier-to-host­ing map. For a mul­tina­tional, this is a gift: clas­si­fic­a­tion is port­able in a way that law is not, so a single in­ternal data cata­logue can be mapped onto six na­tional schemes.

The classification catalogue is the control plane of the Gulf stack.

The 2027 con­sequence is pro­ced­ural. As clas­si­fic­a­tion-driven res­id­ency be­comes a de­fault RFP clause (Call 1), the clas­si­fic­a­tion ex­er­cise moves up­stream: from a com­pli­ance af­ter­thought to the first de­cision in any Gulf cloud pro­ject. Get the tier­ing right and every down­stream choice fol­lows; get it wrong and the ar­chi­tec­ture is either over-se­cured and over-priced, or under-se­cured and non-com­pli­ant. The switch is where 2027 pro­cure­ment be­gins.

The read

Watch the clas­si­fic­a­tion cata­logues, not the head­lines. The tier-to-host­ing map is the single arte­fact that de­term­ines where Gulf data lives, and the one that quietly har­mon­ises six di­ver­gent re­gimes.

The sovereign premium

Sovereignty is not yet free. A sovereign region costs an estimated 15–30% more than public cloud, and in 2027 that premium persists: sovereignty remains a cost the Gulf pays for control, not a saving it earns.

The premium has clear sources. A sov­er­eign re­gion car­ries lower util­isa­tion than a global one, be­cause it can­not pool de­mand across the planet; it re­quires vet­ted local staff, whose sup­ply is thin; it adds con­fid­en­tial-com­put­ing and key-man­age­ment lay­ers that con­sume over­head; and it for­goes the ar­bit­rage of run­ning a work­load wherever com­pute is cheapest that hour. BCG puts the res­ult­ing mark-up at 15 to 30 per cent over pub­lic cloud, a dir­ec­tional fig­ure rather than a con­sensus [BCG, 2025]. Against it sits one struc­tural off­set: power at $0.05–0.07 per kilo­watt-hour, among the cheapest avail­able to any op­er­ator, which makes the Gulf a cheap place to run the com­pute even where the sov­er­eign layer is dear.

The premium is a buyer's cal­cu­la­tion, not a builder's. For the state host­ing the re­gion, cheap power and sov­er­eign-fund cap­ital make the eco­nom­ics work. For the en­ter­prise buy­ing sov­er­eign ca­pa­city, the 15–30% is a real line item that must be jus­ti­fied by the sens­it­iv­ity of the work­load, which is ex­actly why clas­si­fic­a­tion mat­ters com­mer­cially as well as leg­ally: it pre­vents a buyer pay­ing the sov­er­eign premium on data that never needed it.

Sovereignty stays a cost, not yet a saving; and the premium persists through 2027.

The ques­tion the year does not re­solve is whether the premium ever in­verts. It could, if sov­er­eign re­gions reach scale, if local tal­ent deep­ens, and if the al­tern­at­ive (a com­pli­ance breach or a data-trans­fer block) is priced in. But 2027 is too early: the re­gions are still filling, the tal­ent is still scarce, and the premium holds. Call 10 makes this ex­pli­cit: sov­er­eignty in 2027 is a cost of doing busi­ness in the Gulf, not yet a source of ad­vant­age.

The read

Price the premium against the tier. The dis­cip­line of the year is to pay for sov­er­eignty only where the clas­si­fic­a­tion de­mands it, and to treat the 15–30% as the cur­rent, not per­man­ent, cost of Gulf data con­trol.

National models of compute

The Gulf is not building one model of sovereign compute; it is building several. Saudi Arabia's state-scale programme, the Emirates' partnership-led hub and Kuwait's telco-delivered improvisation are three distinct answers to the same constraint.

The Saudi model is ver­tic­ally in­teg­rated and state-scale. HUMAIN, chaired by the Crown Prince and fun­ded through the Pub­lic In­vest­ment Fund, bundles chips, data centres, a na­tional model and a cloud into a single $100bn pro­gramme, with NVIDIA, AMD, AWS and Or­acle as sup­pli­ers rather than part­ners [PIF, 2025]. The premise is that sov­er­eignty and scale are the same pro­ject, pur­sued through na­tional own­er­ship.

The Emir­ates' model is part­ner­ship-led. G42 took Mi­crosoft's cap­ital and a board seat, di­vested its China ex­pos­ure, and built Star­gate UAE with OpenAI, Or­acle, NVIDIA, Cisco and SoftBank [2024-25]. The premise is that sov­er­eignty is best se­cured by bind­ing the re­gion's com­pute to the United States tech­no­logy stack: trad­ing some in­de­pend­ence for guar­an­teed ac­cess to

Digital SovereigntyVolge Quarterly08 •

the fron­tier, and for the Coun­try Group A:5 des­ig­na­tion that ac­cess earned.

Kuwait's model is de­liv­ery by im­pro­visa­tion. With its an­nounced hy­per­scaler re­gions not live, sov­er­eignty is being car­ried by Oore­doo's NVIDIA-H200 sov­er­eign data centre and KISR's ICARUS plat­form [2025]: telco and re­search in­fra­struc­ture stand­ing in for the cloud re­gions that have not ar­rived. It is the model of a state that has the man­date and the cap­ital but not yet the hy­per­scaler steel, and it is the basis of Call 9.

Three national models (state-scale, partnership-led, telco-delivered), one imported silicon.

The read

There is no single Gulf com­pute model to copy. A state's model fol­lows its en­dow­ment (Saudi scale, Emir­ati part­ner­ships, Kuwaiti telco reach), but all three con­verge on the same de­pend­ency and the same clas­si­fic­a­tion switch. Whether a Saudi-ap­proved model is re­cog­nised across other states is the test of Call 3.

Keys, confidential computing and air-gaps

Beneath residency sits a stack of technical controls that make sovereignty real for data in use, not merely data at rest. In 2027 the top of that stack (external key control and confidential computing) becomes a standard requirement for the most sensitive Gulf workloads.

Res­id­ency an­swers where data sits; it does not an­swer who can read it while it is being pro­cessed. The tech­nical lay­ers close that gap. Cus­tomer key con­trol (bring-your-own-key, and its stronger form, hold-your-own-key, where the op­er­ator never pos­sesses the key) en­sures that a cloud pro­vider can­not de­crypt cus­tomer data even on its own hard­ware. Con­fid­en­tial com­put­ing goes fur­ther, isol­at­ing data in use in­side hard­ware-en­cryp­ted en­claves using Intel TDX, AMD SEV-SNP or NVIDIA Con­fid­en­tial Com­put­ing, so that even a com­prom­ised host can­not ob­serve the work­load. For the top clas­si­fic­a­tion tier, the an­swer is starker still: an air-gap, phys­ic­ally dis­con­nec­ted from any ex­ternal net­work.

Call 6 makes the 2027 judge­ment: hold-your-own-key, ex­ternal key man­age­ment and con­fid­en­tial com­put­ing be­come stand­ard re­quire­ments for Gulf top-tier, Secret and L4 work­loads. The dir­ec­tion is clear even if the pace is un­cer­tain: as sens­it­ive work­loads move to cloud, the buy­ers who own their keys and isol­ate their

com­pute are the ones who can host at the top tier without an air-gap, and that cap­ab­il­ity be­comes a pro­cure­ment ex­pect­a­tion rather than a dif­fer­en­ti­ator.

These con­trols mat­ter be­cause they de­couple sov­er­eignty from geo­graphy. A work­load pro­tec­ted by hold-your-own-key and con­fid­en­tial com­put­ing is, in a mean­ing­ful sense, sov­er­eign even on for­eign-op­er­ated hard­ware, which is what al­lows an open host like Bahrain to guar­an­tee for­eign data on its soil, and what al­lows the Gulf to ac­cept United States-op­er­ated re­gions without con­ced­ing data ac­cess. The keys, not the co­ordin­ates, be­come the locus of con­trol.

For the top tier, the keys (not the coordinates) are the locus of control.

The read

The air-gap is the an­swer of last re­sort; the keys and the en­clave are the an­swer of scale. 2027 is the year the Gulf top tier stand­ard­ises on ex­ternal key con­trol and con­fid­en­tial com­put­ing: sov­er­eignty en­gin­eered into the sil­icon's trust bound­ary, not just the map.

500,000 NVIDIA chips a year. The Gulf's sovereign-AI ceiling is not set by its capital or its power: it is set, and can be reset, by a licence held in Washington.

The de­pend­ence para­dox · Volge Quarterly 2027

Sources: the in­stru­ments named in the table. Sev­eral un­der­ly­ing texts are pub­lished in Ar­abic only, in­clud­ing Bahrain's Res­ol­u­tions No. 42 and No. 44 of 2022. The res­ol­u­tion num­ber of the Kuwait CITRA cloud frame­work, and the exact re­gis­tra­tion cri­teria for the Saudi Qual­i­fy­ing Cat­egory and Classes A, B and C, are not pub­lic. Where a label or a fig­ure is con­tested in the sources, the con­flict is stated in the body rather than re­solved.

Digital SovereigntyVolge Quarterly09 •

The buyer's ground

What the rules require, what has actually been built, what it costs, and how a workload is placed against the region's published classification tiers.

The rules that bind, country by country

There is no Gulf localisation regime. There are six, and the distance between them is wide enough that a workload lawfully placed in one state may be unlawfully placed in the next.

The use­ful start­ing point for any buyer in the re­gion is that the six states of the Gulf Co­oper­a­tion Coun­cil do not share a data pro­tec­tion law, a clas­si­fic­a­tion scheme, a cloud li­cens­ing model or a cross-bor­der trans­fer route. They share a dir­ec­tion of travel and very little else. The table below sets out, for each state, the prin­cipal in­stru­ment, what must re­main in­side the na­tional bor­der, the route by which data may law­fully leave it, and whether a pro­vider must hold a li­cence or a re­gis­tra­tion in order to serve the mar­ket at all. It is to be noted that the dif­fer­ences are not cos­metic. Two of the six li­cence the pro­vider as well as reg­u­lat­ing the data. One of the six has no gen­eral data pro­tec­tion stat­ute. One of the six has le­gis­lated to apply a for­eign cloud con­sumer's own home law to data held in des­ig­nated fa­cil­it­ies on its ter­rit­ory.

StatePrincipal instrumentsWhat must stay in countryCross-border routeCloud licensing
Saudi ArabiaPDPL, Royal Decree M/19 of 2021, amended 2023; SDAIA enforcement commenced 14 September 2024; NCA CCC-2:2024No blanket localisation under PDPL. Localisation arises sector by sector: SAMA for financial institutions, NCA for critical national infrastructureRegulation on Personal Data Transfer Outside the Kingdom, amended version dated 1 September 2024, with the Kingdom's first Standard Contractual Clauses issued alongsideCST Cloud Computing Services Provisioning Regulations, in force 10 October 2023, replacing CITC framework v3 (effective 3 December 2020). Registration via CST portal. A Qualifying Category plus Classes A, B and C
United Arab EmiratesFederal Decree-Law No. 45 of 2021, in force 2 January 2022; National Cloud Security Policy v2.0, UAE Cyber Security CouncilNo general statutory localisation. Hosted encryption keys and their backups must be generated, stored and managed within the UAE. At the sovereign tier, all data under exclusive UAE jurisdictionArticles 22 and 23 turn on adequacy of the destination. No adequacy list has been published, so in practice standard contractual clauses, consent or Data Office approvalNo separate cloud licence identified. The Cloud Security Policy binds all providers serving UAE consumers through three sovereignty tiers
QatarLaw No. 13 of 2016 on Personal Data Privacy Protection; NCSA National Data Classification Policy V3.0, established May 2023Determined by classification tier. Five tiers, C0 to C4, for government entities, and a minimum of four tiers for non-government entitiesRestricted unless the destination ensures adequate protection, the competent authority approves, or a statutory exception appliesNo provider licence identified. MCIT Cloud First Policy, document P005 v1.0.0, published April 2024, applies to all government agencies
BahrainPersonal Data Protection Law No. 30 of 2018, in force 1 August 2019; Legislative Decree No. 56 of 2018, the Cloud LawNo general localisation identified. Article 3 of the Cloud Law instead subjects data stored in designated Bahraini data centres by overseas cloud consumers to the law of the consumer's home stateResolution No. 42 of 2022 permits direct transfer without PDPA permission to listed countries and territories. Resolution No. 44 of 2022 also governs outbound transfersNo provider licence identified. Cloud First Policy, April 2017
Digital SovereigntyVolge Quarterly10 •
StatePrincipal instrumentsWhat must stay in countryCross-border routeCloud licensing
OmanPDPL, Royal Decree No. 6/2022, published 13 February 2022; Executive Regulations by Ministerial Decision No. 34/2024, published 4 February 2024; fully enforceable from 5 February 2026Article 12 of the cloud bylaw prohibits transferring Levels 3 and 4 data, which include governmental and financial data, outside Oman without prior TRA approvalArticle 23 of the PDPL and Article 37 of the Executive Regulations. Firms read the consent requirement differently. Anonymised transfers are treated as outside itTRA Decision No. 1152/2/19/2024-20, September 2024, in force the day after Gazette publication. A licence is required to establish, operate or provide cloud or data centre services. Three-year licences
KuwaitNo single national data protection statute. CITRA Resolution No. 26 of 2024 on data privacy, superseding Resolution No. 42 of 2021, applying to CITRA-licensed telecommunications and IT service providersStorage, classification and localisation requirements for government and citizen data under the CITRA cloud frameworkNo general statutory transfer route identified in the sourcesCITRA Cloud Computing Regulatory Framework, version 2.4 cited, applying to licensed providers operating data centres in Kuwait

What the table shows

The first thing the table shows is that loc­al­isa­tion in the Gulf is rarely im­posed by the pri­vacy stat­ute it­self. The Saudi Per­sonal Data Pro­tec­tion Law, is­sued as Royal De­cree M/19 in 2021 and amended in 2023, im­poses no blanket re­quire­ment that per­sonal data be held in the King­dom: the ob­lig­a­tion arises sec­tor by sec­tor, through the Saudi Cent­ral Bank for fin­an­cial in­sti­tu­tions and through the Na­tional Cy­ber­se­cur­ity Au­thor­ity for crit­ical na­tional in­fra­struc­ture. Fed­eral De­cree-Law No. 45 of 2021 in the UAE, in force since 2 Janu­ary 2022, car­ries no gen­eral loc­al­isa­tion man­date either, and the in-coun­try ob­lig­a­tion a buyer will ac­tu­ally en­counter sits else­where, in the re­quire­ment under the Na­tional Cloud Se­cur­ity Policy v2.0 that hos­ted en­cryp­tion keys and their backups be gen­er­ated, stored and man­aged within the UAE. The con­sequence is that a com­pli­ance as­sess­ment built on the pri­vacy law alone will un­der­state the con­straint in both of the re­gion's two largest mar­kets.

The third thing the table shows is that in two of the six states the pro­vider is li­censed and not merely su­per­vised. Saudi Ar­a­bia re­quires re­gis­tra­tion under the CST Cloud Com­put­ing Ser­vices Pro­vi­sion­ing Reg­u­la­tions, and Oman re­quires a three-year li­cence under the TRA bylaw to es­tab­lish, op­er­ate or provide cloud or data centre ser­vices, with Art­icle 28 per­mit­ting ad­min­is­trat­ive pen­al­ties and the sus­pen­sion of per­mits. Kuwait's frame­work reaches li­censed pro­viders op­er­at­ing data centres in the coun­try rather than the

mar­ket at large. The com­mer­cial ef­fect is that in those jur­is­dic­tions the field of law­ful sup­pli­ers is nar­rower than the field of cap­able ones.

The second thing the table shows is that cross-bor­der routes are open in prin­ciple and nar­row in prac­tice. Saudi Ar­a­bia pub­lished the amended Reg­u­la­tion on Per­sonal Data Trans­fer Out­side the King­dom dated 1 Septem­ber 2024 and is­sued its first Stand­ard Con­trac­tual Clauses along­side it, al­though one source dates those clauses to Au­gust 2024 and the two ac­counts are un­re­con­ciled. Qatar per­mits trans­fer where the des­tin­a­tion en­sures ad­equate pro­tec­tion, where the com­pet­ent au­thor­ity ap­proves, or where a stat­utory ex­cep­tion ap­plies, with the reg­u­lator cited vari­ously as the Na­tional Cyber Se­cur­ity Agency and as the MCIT Com­pli­ance and Data Pro­tec­tion De­part­ment. The UAE po­s­i­tion is the most awk­ward of the six: Art­icles 22 and 23 turn on the ad­equacy of the des­tin­a­tion, but no ad­equacy list has been pub­lished, which leaves stand­ard con­trac­tual clauses, con­sent or Data Of­fice ap­proval as the work­ing routes. Oman's po­s­i­tion is un­settled in a dif­fer­ent way, in that firms read the con­sent re­quire­ment under Art­icle 23 of the PDPL and Art­icle 37 of the Reg­u­la­tions dif­fer­ently, with an­onymised trans­fers treated as fall­ing out­side it.

Localisation in the Gulf is seldom written in the privacy statute: it is written in the sector rule, the cloud licence and the classification tier.

The fourth thing the table shows is an out­lier that de­serves more at­ten­tion than it re­ceives. Art­icle 3 of Bahrain's Le­gis­lat­ive De­cree No. 56 of 2018, the Cloud Law, sub­jects data stored in des­ig­nated Bahraini data centres by over­seas cloud con­sumers to the law of the con­sumer's home state rather than to Bahraini law. This is the in­verse of the sov­er­eignty logic every other state in the table ap­plies: in­stead of pulling for­eign data under local jur­is­dic­tion, it pushes local host­ing under for­eign jur­is­dic­tion, by con­sent of the con­sumer. For a buyer whose prin­cipal con­cern is pre­dict­ab­il­ity of gov­ern­ing law rather than phys­ical res­id­ency, that is a sig­ni­fic­antly dif­fer­ent pro­pos­i­tion, and it is the only such pro­vi­sion in the six.

The Bahraini pro­vi­sion op­er­ates on data centres des­ig­nated by a Coun­cil of Min­is­ters res­ol­u­tion. Whether that res­ol­u­tion has been is­sued could not be con­firmed from the sources avail­able, and the pro­vi­sion should be checked against the primary text and the des­ig­na­tion in­stru­ment be­fore it is re­lied upon.

The takeaway is that a single re­gional com­pli­ance po­s­i­tion is not avail­able and should not be con­struc­ted. What the table sup­ports in­stead is a per-state, per-sec­tor mat­rix, built from the named in­stru­ments rather than from vendor sum­mar­ies, and re­freshed on the

Digital SovereigntyVolge Quarterly11 •

dates the in­stru­ments them­selves carry. Where the sources con­flict, as they do on the Saudi clauses and on the Kuwaiti no­ti­fic­a­tion period, the con­flict be­longs in the mat­rix rather than being re­solved by pref­er­ence.

The fifth thing the table shows is that the stated pen­al­ties are high and the en­force­ment re­cord is empty. Saudi Ar­a­bia provides for fines of up to SAR 5m per vi­ol­a­tion, doubled on re­pe­ti­tion, up to SAR 3m and two years' im­pris­on­ment for un­law­ful dis­clos­ure of sens­it­ive data, and up to SAR 1m for un­law­ful trans­fer abroad. Qatar's pen­al­ties are re­por­ted at QAR 1m to QAR 5m with no cus­todial ele­ment. Bahrain's are re­por­ted at up to BHD 20,000 per breach plus crim­inal sanc­tions for un­au­thor­ised cross-bor­der trans­fer. Oman's are re­por­ted from OMR 500 to OMR 500,000 for un­law­ful cross-bor­der trans­fer. Against those ceil­ings, no named pub­lished fine or en­force­ment de­cision under any of the six laws could be loc­ated. That ab­sence is it­self a find­ing, and it cuts both ways: it tells a buyer that the prob­ab­il­ity of a pub­lic pen­alty is cur­rently un­meas­ur­able, and it tells the same buyer that no body of prac­tice yet ex­ists to cla­rify how the writ­ten rules will be read.

Pen­alty fig­ures above are stat­utory or re­por­ted ceil­ings drawn from sec­ond­ary com­ment­ary, not amounts im­posed. Kuwait's breach no­ti­fic­a­tion period is re­por­ted as 24 hours by one source and 72 hours by an­other, and the two ac­counts are un­re­con­ciled. CITRA is also re­por­ted to have re­pealed its 2021 Data Clas­si­fic­a­tion Policy along­side Res­ol­u­tion No. 26 of 2024, which could not be con­firmed.

Saudi Arabia: classification sets the control, and procurement sets the clock

In the Kingdom the control level applied to a workload is decided by the data's classification rather than by the privacy statute, and the date by which a bidder must be ready is decided by procurement rather than by the regulator.

The Saudi re­gime is best read as two mech­an­isms work­ing at dif­fer­ent speeds. The slower one is clas­si­fic­a­tion: the Na­tional Data Man­age­ment Of­fice scheme sorts data into four levels, and the Na­tional Cy­ber­se­cur­ity Au­thor­ity's Cloud Cy­ber­se­cur­ity Con­trols then at­tach a con­trol level to each, so that the host­ing model fol­lows from the label rather than from the con­tract. The faster one is pro­cure­ment: from 1 April 2027 local con­tent car­ries weight in the fin­an­cial eval­u­ation of IT ser­vice con­tracts for gov­ern­ment tenders of SAR 10m or more, which is a harder date than any­thing in the pri­vacy frame­work. A buyer who pre­pares only for the Per­sonal Data Pro­tec­tion Law will be com­pli­ant and un­com­pet­it­ive.

Trans­fers out of the King­dom are gov­erned by the Reg­u­la­tion on Per­sonal Data Trans­fer Out­side the

King­dom, in the amended ver­sion dated 1 Septem­ber 2024, along­side which the King­dom's first Stand­ard Con­trac­tual Clauses were is­sued. One source dates the clauses to Au­gust 2024. The two ac­counts are un­re­con­ciled and a buyer draft­ing a trans­fer in­stru­ment should take the date from the pub­lished text rather than from com­ment­ary. The en­force­ment ceil­ings are sub­stan­tial: up to SAR 5m per vi­ol­a­tion, doubled on re­pe­ti­tion; up to SAR 3m and two years' im­pris­on­ment for un­law­ful dis­clos­ure of sens­it­ive data; and up to SAR 1m for un­law­ful trans­fer abroad. No named en­force­ment de­cision under the law has been veri­fied.

The statute, and what it does not do

The Per­sonal Data Pro­tec­tion Law was is­sued as Royal De­cree M/19 in 2021 and amended in 2023, with en­force­ment by the Saudi Data and Ar­ti­fi­cial In­tel­li­gence Au­thor­ity com­men­cing on 14 Septem­ber 2024. It is to be noted that the law im­poses no blanket loc­al­isa­tion. The ob­lig­a­tion to keep data in the King­dom is sec­toral: the Saudi Cent­ral Bank im­poses it on fin­an­cial in­sti­tu­tions, and the Na­tional Cy­ber­se­cur­ity Au­thor­ity im­poses it on crit­ical na­tional in­fra­struc­ture. The prac­tical read­ing is that the stat­ute gov­erns how per­sonal data is handled, while the ques­tion of where a work­load may run is answered by the sec­tor reg­u­lator and by the clas­si­fic­a­tion scheme.

Classification, and a conflict in the labels

The Na­tional Data Man­age­ment Of­fice op­er­ates a na­tional data clas­si­fic­a­tion scheme of four levels keyed to the sever­ity of harm that dis­clos­ure would cause. The la­bels are con­tested. Saudi­pe­dia gives Top Secret, Secret, Re­stric­ted and Pub­lic. The policy text and the vendor sum­mary pub­lished by For­tra give Highly Con­fid­en­tial, Con­fid­en­tial, Re­stric­ted and Pub­lic. Both ac­counts agree on four levels and on the harm-sever­ity basis; they dis­agree on no­men­clature, and the con­flict is not re­solved in the pub­lic sources. The sig­ni­fic­ance for a buyer is mod­est in ar­chi­tec­ture and con­sid­er­able in pa­per­work, be­cause tender re­sponses, data in­vent­or­ies and con­trac­tual sched­ules all have to name a level, and nam­ing it from the wrong source in­vites a find­ing.

The statute says how data is handled; the classification says where it may live; the procurement rule says when a bidder must be ready.
Digital SovereigntyVolge Quarterly12 •

The con­trol side is clearer. The Na­tional Cy­ber­se­cur­ity Au­thor­ity's Cloud Cy­ber­se­cur­ity Con­trols CCC-1:2020 have been su­per­seded by CCC-2:2024, which cover gov­ern­ment bod­ies and private own­ers and op­er­at­ors of crit­ical na­tional in­fra­struc­ture. The con­trols run to four levels keyed to data clas­si­fic­a­tion, with Level 1 ap­plied to top secret ma­ter­ial and Level 2 to secret ma­ter­ial. This is the two-axis model in its simplest form: the clas­si­fic­a­tion axis sets sens­it­iv­ity, and the con­trols axis sets the ob­lig­a­tions that fol­low. The two to­gether, rather than the stat­ute, de­term­ine whether a work­load can sit in a pub­lic re­gion at all.

The licence to serve the market

Pro­viders re­quire re­gis­tra­tion. The Com­mu­nic­a­tions, Space and Tech­no­logy Com­mis­sion's Cloud Com­put­ing Ser­vices Pro­vi­sion­ing Reg­u­la­tions came into force on 10 Oc­to­ber 2023, re­pla­cing the CITC frame­work ver­sion 3 that had been ef­fect­ive from 3 Decem­ber 2020. Re­gis­tra­tion runs through the CST portal, and the tiers are de­scribed as a Qual­i­fy­ing Cat­egory plus Classes A, B and C. The exact re­gis­tra­tion cri­teria for each are not pub­lic. A buyer can­not there­fore verify from pub­lished ma­ter­ial which class a given pro­vider ought to hold for a given work­load, and the po­s­i­tion is that the class must be con­firmed with the pro­vider and, where the work­load war­rants it, against the reg­u­lator.

The procurement clock

From 1 April 2027, local con­tent car­ries weight in the fin­an­cial eval­u­ation of IT ser­vice con­tracts for tenders of SAR 10m or more. This is the single most con­sequen­tial date in the Saudi cal­en­dar for a tech­no­logy buyer, and it is not a pri­vacy date. It changes the arith­metic of a bid rather than the law­ful­ness of a de­ploy­ment. Two com­mer­cial dates sit im­me­di­ately be­fore it. The AWS Saudi Ar­a­bia re­gion, an­nounced in March 2024 with three Avail­ab­il­ity Zones and an an­nounced in­vest­ment of USD 5.3bn, was still not live as at early Septem­ber 2026, when AWS re­it­er­ated a Decem­ber 2026 launch. The Mi­crosoft Azure Saudi Ar­a­bia East re­gion in the East­ern Province, also with three Avail­ab­il­ity Zones, is tar­geted for the fourth quarter of 2026 and is like­wise not live. It is to be noted that the USD 5.3bn fig­ure is an­nounced and has not been dis­closed as com­mit­ted or as spent.

A third ar­range­ment is weaker than its cov­er­age sug­ges­ted. The Pub­lic In­vest­ment Fund, SITE and Mi­crosoft signed a non-bind­ing memor­andum of un­der­stand­ing on 20 Novem­ber 2025 to ex­plore the

de­liv­ery of Mi­crosoft sov­er­eign cloud ser­vices in the King­dom, sub­ject to reg­u­lat­ory ap­provals. It is not a joint ven­ture and no value has been pub­lished. Sep­ar­ately, stc Group op­er­ates as a sov­er­eign cloud pro­vider using Or­acle Alloy, al­though the op­er­ator-con­trol and key-cus­tody terms are not pub­lic, which is pre­cisely the in­form­a­tion a buyer with clas­si­fied work­loads needs.

The hub law, still a draft

The Com­mu­nic­a­tions, Space and Tech­no­logy Com­mis­sion pub­lished a draft Global AI Hub Law on 14 April 2025, with con­sulta­tion clos­ing on 14 May 2025. The draft cre­ates Private, Ex­ten­ded and Vir­tual Hubs: in sub­stance, data em­bassies op­er­at­ing under for­eign law on Saudi ter­rit­ory. If en­acted it would be the most sig­ni­fic­ant struc­tural change in the re­gional pic­ture, be­cause it would offer a law­ful route to for­eign gov­ern­ing law in­side the King­dom rather than out­side it. It re­mains a draft and no com­mence­ment date has been pub­lished. It should be tracked, not planned around.

The takeaway for the King­dom is se­quen­cing. Clas­si­fic­a­tion pre­cedes con­trol se­lec­tion, con­trol se­lec­tion pre­cedes re­gion se­lec­tion, and all three pre­cede the 1 April 2027 pro­cure­ment change, which is the only firm reg­u­lat­ory date on the ho­ri­zon and which binds bid­ders rather than op­er­at­ors. Where the pub­lic re­cord is si­lent, as it is on CST class cri­teria, on the exact NDMO la­bels and on the key-cus­tody terms of the sov­er­eign cloud ar­range­ments, the si­lence is to be closed by writ­ten con­firm­a­tion from the coun­ter­party rather than by as­sump­tion.

The UAE: the first published sovereignty taxonomy in the region

The UAE has produced the only sovereignty taxonomy in the Gulf that a buyer can act on directly. The tier, and not the federal privacy statute, is what decides where a workload may sit.

The po­s­i­tion in the United Arab Emir­ates is un­usual: the pri­vacy stat­ute is the weaker in­stru­ment and the cloud se­cur­ity policy is the stronger one. Fed­eral De­cree-Law No. 45 of 2021 has been in force since 2 Janu­ary 2022, but the core Ex­ec­ut­ive Reg­u­la­tions ap­pear still to be un­is­sued as at 2026 and no ad­equacy list has been pub­lished, which leaves the trans­fer pro­vi­sions dif­fi­cult to op­er­ate. The Na­tional Cloud Se­cur­ity Policy v2.0, is­sued by the UAE Cyber Se­cur­ity Coun­cil and re­por­ted on 15 Oc­to­ber 2026 as an up­date to the first re­lease of May 2023, does the op­pos­ite: it sets out three sov­er­eignty tiers with named con­di­tions, and it is

Digital SovereigntyVolge Quarterly13 •

the most dir­ectly ac­tion­able sov­er­eignty tax­onomy pub­lished any­where in the re­gion.

Who the policy binds

The policy ap­plies on the sup­ply side to all cloud ser­vice pro­viders serving UAE con­sumers, and on the de­mand side to fed­eral min­is­tries and au­thor­it­ies to­gether with non-gov­ern­ment crit­ical in­form­a­tion in­fra­struc­ture en­tit­ies. Where an Emir­ate runs its own crit­ical in­form­a­tion in­fra­struc­ture pro­gramme, that Emir­ate's lead au­thor­ity as­sesses and en­forces, which means the ap­plic­able su­per­visor can dif­fer between two en­tit­ies in the same sec­tor de­pend­ing on where they sit. Free zones re­main sep­ar­ate: the DIFC op­er­ates under Data Pro­tec­tion Law No. 5 of 2020 and the ADGM under its Data Pro­tec­tion Reg­u­la­tions 2021. A buyer with en­tit­ies in­side and out­side a free zone is there­fore deal­ing with more than one re­gime in a single coun­try.

The three tiers

TierWhen it appliesWhat it requires
Tier 1, Baseline secure cloudAll providers, irrespective of data classificationFoundational controls
Tier 2, Partial sovereign cloudData classified confidential or restrictedAll consumer data stored strictly within UAE geographical boundaries and legal jurisdiction. On a valid foreign disclosure order, the provider must make reasonable efforts to redirect the request to the consumer and must inform the consumer and the UAE authorities
Tier 3, Sovereign cloudData classified above confidential or restrictedAll data under exclusive UAE jurisdiction. Consumer data and metadata not disclosed to any authority other than those explicitly approved by the UAE. All foreign access requests denied by default. Expect UAE-based key management, UAE-resident redundancy, UAE-licensed telecommunications routing and UAE-cleared personnel as eligibility conditions

Three rules run across all three tiers and are easy to miss be­cause they are not tier-spe­cific. Data loc­a­tion must be known at all stages. Hos­ted en­cryp­tion keys and their backups must be gen­er­ated, stored and man­aged within the UAE. And the con­sumer, not the pro­vider, must as­sess whether hold-your-own-key is re­quired. Where tiers over­lap, the most strin­gent con­trol ap­plies, which re­moves the tempta­tion to argue a work­load down into a cheaper tier by ref­er­ence to one of its less sens­it­ive com­pon­ents.

The tier de­scrip­tions above rest on a law firm sum­mary dated 15 Oc­to­ber 2026. The primary text of the Na­tional Cloud Se­cur­ity Policy v2.0 was not re­trieved and the con­di­tions should be checked against it be­fore a tier­ing de­cision is treated as settled.

At the sovereign tier, foreign access requests are denied by default: that is a design constraint on the operator, not a clause in a contract.

What each tier asks of the buyer

Tier 1 asks for di­li­gence and little more, and it ap­plies re­gard­less of clas­si­fic­a­tion, so there is no work­load in scope of the policy that es­capes it. Tier 2 asks for res­id­ency and for a dis­clos­ure pro­tocol: the re­quire­ment that the pro­vider make reas­on­able ef­forts to re­dir­ect a for­eign order to the con­sumer, and in­form both the con­sumer and the UAE au­thor­it­ies, is a pro­ced­ural ob­lig­a­tion that a buyer can and should see evid­enced in the pro­vider's own doc­u­mented pro­cess rather than as­ser­ted in a sales re­sponse. Tier 3 asks for some­thing closer to an op­er­at­ing model: ex­clus­ive jur­is­dic­tion over data and metadata, denial of for­eign ac­cess re­quests by de­fault, and a set of eli­gib­il­ity con­di­tions cov­er­ing key man­age­ment, re­dund­ancy, rout­ing and per­son­nel clear­ance. The dis­tance between Tier 2 and Tier 3 is not a fea­ture flag. It is a dif­fer­ent sup­ply chain.

The trans­fer po­s­i­tion under the fed­eral stat­ute is the weak link. Art­icles 22 and 23 turn on the ad­equacy of the des­tin­a­tion, but with no ad­equacy list pub­lished, ad­equacy can­not be es­tab­lished by ref­er­ence to a list. In prac­tice trans­fers pro­ceed on stand­ard con­trac­tual clauses, con­sent or Data Of­fice ap­proval. The status of the core Ex­ec­ut­ive Reg­u­la­tions could not be con­firmed, and a date of full com­pli­ance for the fed­eral law that cir­cu­lates in sec­ond­ary com­ment­ary could not be veri­fied against any primary in­stru­ment and is there­fore not treated here as a date at all.

What has actually been built, and under what licence

The UAE has the deep­est built ca­pa­city in the re­gion. Mi­crosoft op­er­ates the live UAE North and UAE Cent­ral re­gions. Mi­crosoft's an­nounced com­mit­ment to the UAE runs to USD 15.2bn through 2029, of which USD 7.3bn is stated as in­ves­ted by the end of 2025 and USD 7.9bn is planned for 2026 to 2029; more than USD 10bn of the total is ear­marked for cloud and ar­ti­fi­cial in­tel­li­gence data centres and over USD 3bn for local op­er­a­tions and re­search. This builds on a USD 1.5bn equity in­vest­ment in G42 that car­ries a board seat. On 5 Novem­ber 2025 Mi­crosoft and G42 an­nounced a 200 MW data centre ex­pan­sion to be de­livered by Khazna Data Cen­ters, with op­er­a­tions ex­pec­ted be­fore the end of 2026; site loc­a­tions and

Digital SovereigntyVolge Quarterly14 •

cap­ital ex­pendit­ure were not dis­closed. The e& and AWS UAE Sov­er­eign Launch­pad is framed on local data res­id­ency, but its terms are not pub­lic.

One point of con­trol de­serves nam­ing be­cause it is fre­quently as­sumed and not found. No pub­lished golden-share in­stru­ment or formal op­er­ator-con­trol in­stru­ment between a GCC state en­tity and a hy­per­scaler could be loc­ated. The nearest pub­lished con­trol fea­tures in the UAE are Mi­crosoft's board seat at G42 and the in-coun­try key cus­tody rule in the Cloud Se­cur­ity Policy. A buyer re­ly­ing on state con­trol as a sov­er­eignty as­sur­ance is re­ly­ing on some­thing that has not been pub­lished.

A Fed­eral Re­gister no­tice dated 10 July 2026 is re­por­ted to have moved the UAE from Coun­try Groups D:3 and D:4 to A:5, clear­ing G42, Core42 and MGX for li­cence-free ad­vanced chip pur­chases. This rests on sec­ond­ary re­port­ing; the primary no­tice text was not re­trieved. Key cus­tody and op­er­ator-ac­cess terms for Core42 and for the e& and AWS ar­range­ment are like­wise not pub­lic.

The takeaway is that in the UAE the tier­ing de­cision is the ar­chi­tec­ture de­cision, and it is made be­fore a pro­vider is se­lec­ted rather than after. The three cross-tier rules, and in par­tic­u­lar in-coun­try key cus­tody and the hold-your-own-key as­sess­ment, are the items most likely to be over­looked in a Tier 1 or Tier 2 de­ploy­ment, be­cause they do not feel like sov­er­eignty re­quire­ments and they are not ne­go­ti­able.

Qatar, Bahrain, Oman and Kuwait: four regimes that are not one regime

The four smaller GCC markets are routinely treated as a single residual category. They are not. One applies the consumer's home law to locally hosted data, one licenses every cloud operator and fences two classification levels inside its border, one works through classification tiers, and one has no general data protection statute at all.

The habit of group­ing Qatar, Bahrain, Oman and Kuwait as the rest of the Gulf is the single most ex­pens­ive sim­pli­fic­a­tion avail­able to a re­gional buyer, be­cause the four dif­fer from one an­other more than either of the two large mar­kets dif­fers from its neigh­bour. Bahrain's Cloud Law points jur­is­dic­tion out­wards. Oman's cloud bylaw li­censes the op­er­ator and fences two levels of data in­side the coun­try. Qatar's po­s­i­tion turns on a five-tier clas­si­fic­a­tion scheme and a gov­ern­ment cloud-first policy. Kuwait has no gen­eral data pro­tec­tion stat­ute and reg­u­lates through the tele­com­mu­nic­a­tions and in­form­a­tion tech­no­logy li­cence in­stead. A de­ploy­ment tem­plate built for any one of them will fail in at least two of the oth­ers.

The op­er­at­ive in­stru­ment for place­ment is the Na­tional Cyber Se­cur­ity Agency's Na­tional Data Clas­si­fic­a­tion Policy V3.0, es­tab­lished in May 2023, which sets five tiers, C0 to C4, for gov­ern­ment en­tit­ies and a min­imum

of four tiers for non-gov­ern­ment en­tit­ies. Along­side it, the MCIT Cloud First Policy, doc­u­ment P005 v1.0.0, pub­lished in April 2024, ap­plies to all gov­ern­ment agen­cies. The built po­s­i­tion is reas­on­ably ma­ture for the size of the mar­ket: Mi­crosoft's Qatar Cent­ral re­gion launched in Au­gust 2022 with the local part­ner MEEZA, and Google Cloud's Doha re­gion opened in May 2023 with three zones, hav­ing been com­mit­ted to the Gov­ern­ment of Qatar in March 2020.

Qatar: classification first

Qatar op­er­ates under Law No. 13 of 2016 on Per­sonal Data Pri­vacy Pro­tec­tion, under which cross-bor­der trans­fer is re­stric­ted un­less the des­tin­a­tion en­sures ad­equate pro­tec­tion, the com­pet­ent au­thor­ity ap­proves, or a stat­utory ex­cep­tion ap­plies. The reg­u­lator is cited vari­ously as the Na­tional Cyber Se­cur­ity Agency and as the MCIT Com­pli­ance and Data Pro­tec­tion De­part­ment, and the sources do not re­con­cile the two. Pen­al­ties are re­por­ted in the range of QAR 1m to QAR 5m with no cus­todial ele­ment, and no en­force­ment ac­tion was found.

One sec­ond­ary sum­mary states that C4 data is ex­empt from cloud mi­gra­tion. This is un­veri­fied and should be checked against the primary clas­si­fic­a­tion policy be­fore it is re­lied upon in a place­ment de­cision.

Bahrain: the jurisdiction runs the other way

Bahrain's Per­sonal Data Pro­tec­tion Law No. 30 of 2018 has been in force since 1 Au­gust 2019, su­per­vised by the Per­sonal Data Pro­tec­tion Au­thor­ity. Res­ol­u­tion No. 42 of 2022 per­mits dir­ect trans­fer without the au­thor­ity's per­mis­sion to lis­ted coun­tries and ter­rit­or­ies, and Res­ol­u­tion No. 44 of 2022 also gov­erns out­bound trans­fers; the of­fi­cial texts are avail­able in Ar­abic only. Pen­al­ties are re­por­ted at up to BHD 20,000 per breach plus crim­inal sanc­tions for un­au­thor­ised cross-bor­der trans­fer, and a Cloud First Policy has been in place since April 2017.

Bahrain is the only Gulf state that has legislated to push locally hosted data under foreign law rather than pull foreign data under its own.
Digital SovereigntyVolge Quarterly15 •

The dis­tinct­ive in­stru­ment is Le­gis­lat­ive De­cree No. 56 of 2018, the Cloud Law. Art­icle 3 sub­jects data stored in des­ig­nated Bahraini data centres by over­seas cloud con­sumers to the law of the con­sumer's home state. Every other re­gime in the Gulf seeks to ex­tend local jur­is­dic­tion over data held loc­ally. Bahrain's pro­vi­sion does the re­verse, and does so de­lib­er­ately, as an in­duce­ment to for­eign con­sumers who want phys­ical prox­im­ity without a change of gov­ern­ing law. The qual­i­fy­ing data centres are des­ig­nated by a Coun­cil of Min­is­ters res­ol­u­tion, and whether that res­ol­u­tion has been is­sued could not be con­firmed, which is a sig­ni­fic­ant gap in an oth­er­wise at­tract­ive pro­pos­i­tion. Bahrain's built po­s­i­tion is also the old­est in the re­gion: AWS opened three fa­cil­it­ies in July 2019, the first hy­per­scaler re­gion in the Gulf, and Bahrain's In­form­a­tion and eGovernment Au­thor­ity re­ports 1,357 gov­ern­ment in­form­a­tion tech­no­logy op­er­a­tions moved to AWS, on a page last up­dated in March 2025.

Oman: the licence and the fence

Oman has moved fur­thest, most re­cently. The Per­sonal Data Pro­tec­tion Law, Royal De­cree No. 6/2022, was pub­lished on 13 Feb­ru­ary 2022, its Ex­ec­ut­ive Reg­u­la­tions fol­lowed by Min­is­terial De­cision No. 34/2024 pub­lished on 4 Feb­ru­ary 2024, and the re­gime be­came fully en­force­able from 5 Feb­ru­ary 2026. Trans­fers run under Art­icle 23 of the law and Art­icle 37 of the Reg­u­la­tions, with firms read­ing the con­sent re­quire­ment dif­fer­ently and an­onymised trans­fers treated as out­side it. Pen­al­ties are re­por­ted from OMR 500 to OMR 500,000 for un­law­ful cross-bor­der trans­fer.

The cloud bylaw is the harder in­stru­ment. TRA De­cision No. 1152/2/19/2024-20, is­sued in Septem­ber 2024 and in force the day after Gaz­ette pub­lic­a­tion, re­quires a li­cence to es­tab­lish, op­er­ate or provide cloud or data centre ser­vices, gran­ted for three years. Art­icle 12 pro­hib­its trans­fer­ring Levels 3 and 4 data, which ex­pli­citly in­clude gov­ern­mental and fin­an­cial data, out­side Oman without prior TRA ap­proval. Art­icle 28 provides for ad­min­is­trat­ive pen­al­ties and per­mits may be sus­pen­ded. The full level defin­i­tions and the li­cence classes were not re­trieved, so the bound­ary of Levels 3 and 4 bey­ond the gov­ern­mental and fin­an­cial cat­egor­ies can­not be stated from pub­lic ma­ter­ial. Oman also has no hy­per­scaler re­gion dom­i­ciled in the Sul­tan­ate as at May 2026: pro­vi­sion is through Omani op­er­at­ors and the na­tional shared ar­ti­fi­cial-in­tel­li­gence plat­form Mu'een, with the Oman Data Park Mus­cat fa­cil­ity lis­ted at 10 MW. The com­bin­a­tion of a fenced

clas­si­fic­a­tion level and no do­mestic hy­per­scaler re­gion is the tight­est con­straint in the four.

Kuwait: regulation through the licence

Kuwait has no single na­tional data pro­tec­tion stat­ute. CITRA Res­ol­u­tion No. 26 of 2024 on data pri­vacy su­per­sedes Res­ol­u­tion No. 42 of 2021 and ap­plies to CITRA-li­censed tele­com­mu­nic­a­tions and in­form­a­tion tech­no­logy ser­vice pro­viders rather than to con­trol­lers gen­er­ally. Breach no­ti­fic­a­tion is re­por­ted as 24 hours by one source and 72 hours by an­other, and the two are un­re­con­ciled. CITRA is also re­por­ted to have re­pealed the 2021 Data Clas­si­fic­a­tion Policy at the same time, which could not be con­firmed. The CITRA Cloud Com­put­ing Reg­u­lat­ory Frame­work, ver­sion 2.4 cited, ap­plies to li­censed pro­viders op­er­at­ing data centres in Kuwait and car­ries stor­age, clas­si­fic­a­tion and loc­al­isa­tion re­quire­ments for gov­ern­ment and cit­izen data; its res­ol­u­tion num­ber is not pub­lic. No en­force­ment ac­tion was found. On the built side, the Google re­gion is not live, with re­por­ted re­quests for 60 MW across three sites or a single Su­laib­iya site at 30 MW, both marked planned, and a Mi­crosoft Azure ar­ti­fi­cial-in­tel­li­gence re­gion lis­ted at 50 MW, planned. The Oore­doo and NVIDIA Kuwait Sov­er­eign AI Lab, lis­ted at 10 MW, is de­scribed as op­er­a­tional.

Mega­watt fig­ures for Kuwait, Oman and Bahrain in this chapter de­rive from an index site and are mostly marked planned or es­tim­ated. They are in­dic­at­ive and are not pub­lished op­er­ator fig­ures.

The takeaway is that the four smal­ler mar­kets each re­quire their own place­ment rule, and that the bind­ing con­straint dif­fers in each: gov­ern­ing law in Bahrain, op­er­ator li­cens­ing and fenced levels in Oman, clas­si­fic­a­tion tier­ing in Qatar, and the pro­vider's li­cence status in Kuwait. Where the sources are un­re­con­ciled, as on the Qatari reg­u­lator, the Kuwaiti no­ti­fic­a­tion period and the Bahraini des­ig­na­tion res­ol­u­tion, the primary texts are the only re­li­able au­thor­ity, and two of them are pub­lished in Ar­abic only.

What has actually been built

The gap between the Gulf's announced cloud capacity and its live cloud capacity is the most important single fact in this edition. Both of the Kingdom's hyperscaler regions remain unlaunched, and several of the arrangements marketed as sovereign have no published terms at all.

The re­gion's built po­s­i­tion is strong in the United Arab Emir­ates, Qatar and Bahrain, and still pro­spect­ive in Saudi Ar­a­bia, Oman and Kuwait. That dis­tinc­tion mat­ters more than the head­line in­vest­ment fig­ures, be­cause a re­gion that is not live can­not host a work­load and a memor­andum of un­der­stand­ing

Digital SovereigntyVolge Quarterly16 •

can­not be ar­chi­tec­ted against. The table below sep­ar­ates what is op­er­at­ing from what has been an­nounced, and re­cords, where it ex­ists, the an­nounced value or ca­pa­city. It is to be noted that in al­most every row the an­nounced value is an­nounced only: it has not been dis­closed as com­mit­ted or as spent.

ArrangementStatusDateAnnounced value or capacity
AWS Bahrain, three facilitiesLive. The first hyperscaler region in the regionOpened July 2019Not published. Bahrain's iGA reports 1,357 government IT operations moved to AWS, page last updated March 2025
Microsoft Azure UAE North and UAE CentralLiveNot stated in the sourcesNot published
Microsoft Qatar Central, with local partner MEEZALiveLaunched August 2022Not published
Google Cloud Doha, three zonesLiveOpened May 2023. Committed to the Government of Qatar March 2020Not published
Google Cloud DammamLiveOpened 2023Not published
Oracle Jeddah and RiyadhLiveNot stated in the sourcesNot published
AWS Saudi Arabia, three Availability ZonesNot live. As at early September 2026 AWS reiterated a December 2026 launchAnnounced March 2024USD 5.3bn announced, not disclosed as committed or spent
Microsoft Azure Saudi Arabia East, Eastern Province, three Availability ZonesNot liveTargeted Q4 2026Not published
Microsoft UAE investment programmePart investedThrough 2029USD 15.2bn announced; USD 7.3bn stated as invested by end-2025; USD 7.9bn planned 2026 to 2029; more than USD 10bn earmarked for cloud and AI data centres; over USD 3bn for local operations and research; builds on a USD 1.5bn equity investment in G42 carrying a board seat
Microsoft and G42 UAE expansion, delivered by Khazna Data CentersAnnounced. Operations expected before end-2026Announced 5 November 2025200 MW. Site locations and capex not disclosed
ArrangementStatusDateAnnounced value or capacity
PIF, SITE and Microsoft sovereign cloud in Saudi ArabiaNon-binding memorandum of understanding to explore delivery, subject to regulatory approvals. Not a joint ventureSigned 20 November 2025No value published
stc Group on Oracle AlloyOperating as a sovereign cloud providerNot stated in the sourcesOperator-control and key-custody terms not public
e& and AWS UAE Sovereign LaunchpadFramed on local data residencyNot stated in the sourcesTerms not public
Ooredoo and NVIDIA Kuwait Sovereign AI LabOperationalNot stated in the sourcesListed at 10 MW
Batelco (Beyon) and Qareeb Data Centers, Bahrain edge AI-ready data centreLaunchedJanuary 2026Listed at 10 MW
Oman Data Park Muscat AI facilityLive. No hyperscaler region domiciled in the Sultanate as at May 2026; provision via Omani operators and the national shared-AI platform Mu'eenAs at May 2026Listed at 10 MW
Google Cloud KuwaitNot live. PlannedNot publishedReported requests for 60 MW across three sites, or a single Sulaibiya site at 30 MW. Both marked planned
Microsoft Azure AI region, KuwaitPlannedNot publishedListed at 50 MW, planned

Mega­watt fig­ures for Kuwait, Oman and Bahrain de­rive from an index site and are mostly marked planned or es­tim­ated. They should be treated as in­dic­at­ive and not as pub­lished op­er­ator fig­ures. Where the sources do not state a launch date for a live re­gion, none is given above rather than in­ferred.

Live, announced, and the space in between

What the table shows first is that the re­gion's old­est hy­per­scaler foot­print is the smal­lest mar­ket's. AWS opened three fa­cil­it­ies in Bahrain in July 2019, and Bahrain has the only pub­lished mi­gra­tion volume in the re­gion: 1,357 gov­ern­ment in­form­a­tion tech­no­logy op­er­a­tions moved, on a page last up­dated in March 2025. No com­par­able pub­lished fig­ure ex­ists for any other GCC state. That is not evid­ence that mi­gra­tion has not happened else­where; it is evid­ence that it has not been pub­lished, and the two should not be con­fused.

What the table shows third is that the word sov­er­eign is doing more work in the mar­ket than the pub­lished re­cord sup­ports. Three of the ar­range­ments most often de­scribed as sov­er­eign, the stc Group

Digital SovereigntyVolge Quarterly17 •

de­ploy­ment on Or­acle Alloy, Core42 in the UAE, and the e& and AWS Sov­er­eign Launch­pad, have no pub­lic key-cus­tody or op­er­ator-ac­cess terms. Those terms are the sub­stance of sov­er­eignty: who holds the keys, who can be com­pelled, and what the op­er­ator is con­trac­tu­ally able to see. In their ab­sence the label is a mar­ket­ing de­scrip­tion rather than a veri­fi­able con­trol, and the only way to con­vert it into one is a writ­ten an­swer from the coun­ter­party on key cus­tody, op­er­ator ac­cess and re­sponse to for­eign legal pro­cess.

What the table shows second is that Saudi Ar­a­bia, the largest mar­ket and the most act­ive policy-maker, has no hy­per­scaler re­gion live from the two largest pro­viders. The AWS re­gion was an­nounced in March 2024 and as at early Septem­ber 2026 the Decem­ber 2026 launch was being re­it­er­ated rather than de­livered. The Azure Saudi Ar­a­bia East re­gion is tar­geted for the fourth quarter of 2026. A buyer plan­ning a 2027 Saudi de­ploy­ment is there­fore plan­ning against two un­launched re­gions and a pro­cure­ment rule that be­gins to bite on 1 April 2027. Google Cloud Dammam and the Or­acle re­gions in Jed­dah and Riy­adh are live, which nar­rows the prac­tical field rather than re­mov­ing it.

An announced region cannot host a workload, and a non-binding memorandum of understanding cannot be architected against.

What the table shows fourth is the dis­tinc­tion between an­nounced, com­mit­ted and spent, and how rarely the pub­lic re­cord per­mits it. Mi­crosoft's UAE pro­gramme is the ex­cep­tion that proves the rule: of USD 15.2bn an­nounced through 2029, USD 7.3bn is stated as in­ves­ted by the end of 2025 and USD 7.9bn is planned for 2026 to 2029. That is a dis­clos­ure struc­ture no other ar­range­ment in the table matches. The AWS Saudi Ar­a­bia fig­ure of USD 5.3bn is an­nounced and has not been dis­closed as com­mit­ted or spent. The Mi­crosoft and G42 200 MW ex­pan­sion an­nounced on 5 Novem­ber 2025 car­ries no dis­closed site loc­a­tions or cap­ital ex­pendit­ure. The PIF, SITE and Mi­crosoft memor­andum of 20 Novem­ber 2025 is ex­pli­citly non-bind­ing, is not a joint ven­ture, is sub­ject to reg­u­lat­ory ap­provals, and car­ries no pub­lished value.

The takeaway is that a ca­pa­city plan should be built on the live column and noth­ing else, with an­nounced ca­pa­city treated as op­tion­al­ity rather than sup­ply. Where a pro­vider's sov­er­eignty claim rests on an ar­range­ment whose terms are not pub­lic, the claim is un­veri­fied until the terms are ob­tained in writ­ing, and the ab­sence of any pub­lished golden-share or formal op­er­ator-con­trol in­stru­ment any­where in the Gulf means state in­volve­ment can­not be re­lied upon to sup­ply the as­sur­ance in its place.

Sovereign AI: announced capacity against energised capacity

The Gulf's sovereign artificial-intelligence programmes are measured almost entirely in announced megawatts. No operating megawatt figure and no energised GPU count has been published for the region's two flagship clusters, and the compute they depend on sits behind foreign export decisions.

The single most use­ful dis­cip­line a buyer can apply to the Gulf's sov­er­eign ar­ti­fi­cial-in­tel­li­gence build-out is to ask what is en­er­gised. The an­nounced num­bers are very large and are be­com­ing lar­ger. HUMAIN in Saudi Ar­a­bia tar­gets ap­prox­im­ately 3 GW by 2030 and more than 6 GW by 2034. Star­gate UAE is a 1 GW cluster in­side a 5 GW cam­pus in Abu Dhabi. Against those fig­ures, no pub­lished op­er­at­ing mega­watt fig­ure and no en­er­gised GPU count ex­ists for HUMAIN, and no of­fi­cial con­firm­a­tion of com­mis­sion­ing for Star­gate UAE could be loc­ated. The ca­pa­city is an­nounced. Whether it is run­ning is not pub­lic.

HUMAIN: the phased numbers

HUMAIN and NVIDIA an­nounced a part­ner­ship in May 2025 pro­ject­ing up to 500 MW and sev­eral hun­dred thou­sand graph­ics pro­cessing units over five years. That was su­per­seded in spe­cificity, though not in am­bi­tion, by an ex­pan­sion an­nounced on 22 Oc­to­ber 2026 cov­er­ing up to 84 MW in two phases. Phase one runs from the fourth quarter of 2026 at 14 MW of Black­well HGX B300, ap­prox­im­ately 6,000 GPUs. Phase two runs from mid-2027 at 70 MW of Vera Rubin, ap­prox­im­ately 21,000 GPUs. Ne­bius is named as an­chor cus­tomer for up to 50 MW at Oxagon. Riy­adh and Dammam sites were re­por­ted at up to 100 MW each ini­tially, with launch tar­geted for 2026.

It is to be noted that these fig­ures do not re­con­cile into a single ca­pa­city num­ber and should not be added. The 500 MW of May 2025 is a five-year pro­jec­tion. The 84 MW of Oc­to­ber 2026 is a two-phase pro­gramme. The 3 GW by 2030 and more than 6 GW by 2034 are tar­gets an­nounced only. The 100 MW per

Digital SovereigntyVolge Quarterly18 •

site for Riy­adh and Dammam is a re­port of an ini­tial fig­ure. Each is a sep­ar­ate state­ment on a dif­fer­ent basis, and the only hon­est ag­greg­ate is that none of them is an op­er­at­ing fig­ure.

Sep­ar­ately, AWS and HUMAIN an­nounced an AI Zone with more than USD 5bn an­nounced and up to 50 MW avail­able by 2028, using AWS Train­ium and NVIDIA in­fra­struc­ture. The USD 5bn is an­nounced, not dis­closed as com­mit­ted or spent, and the 50 MW is an avail­ab­il­ity tar­get for 2028 rather than a cur­rent fig­ure.

No published operating megawatt figure and no energised GPU count exists for HUMAIN. The gap between announced and energised is the whole question.

Stargate UAE: a target date that has passed

Star­gate UAE is a 1 GW cluster being built by Khazna in­side the 5 GW UAE and US AI Cam­pus in Abu Dhabi. The first phase is 200 MW, with up to 35,000 NVIDIA GB300. The tar­get was com­ple­tion in the third quarter of 2026. That tar­get date has passed and no of­fi­cial con­firm­a­tion of com­mis­sion­ing could be loc­ated. The cor­rect state­ment of the po­s­i­tion is there­fore neither that the cluster is run­ning nor that it is late, but that its status is not pub­lic. For a buyer eval­u­at­ing whether a sov­er­eign ar­ti­fi­cial-in­tel­li­gence plat­form in the UAE can carry a pro­duc­tion work­load in 2027, that is the find­ing, and it is not one a vendor roadmap will sup­ply.

The export control layer

Two de­cisions in Wash­ing­ton gov­ern whether the sil­icon ar­rives. On 19 Novem­ber 2025 US Com­merce au­thor­ised ad­vanced chip ex­ports to G42 in the UAE and HUMAIN in Saudi Ar­a­bia, each up to the equi­val­ent of 35,000 NVIDIA GB300, con­di­tioned on se­cur­ity and re­port­ing re­quire­ments mon­itored by the Bur­eau of In­dustry and Se­cur­ity. The li­cence num­bers, the full list of con­di­tions and the de­liv­ery sched­ules are not pub­lic. On 10 July 2026 the UAE was moved to Coun­try Group A:5, with G42, Core42 and MGX cleared for li­cence-free pur­chases. Saudi Ar­a­bia is not covered by that change and re­mains on the Novem­ber 2025 li­cence basis.

The 10 July 2026 Coun­try Group re­as­sign­ment rests on sec­ond­ary re­port­ing dated to a Fed­eral Re­gister no­tice of that date; the primary no­tice text was not re­trieved and should be checked. The con­di­tions at­tach­ing to the 19 Novem­ber 2025 au­thor­isa­tions are not pub­lic and the fig­ures above state only what was re­por­ted.

The asym­metry cre­ated by those two dates is the most sig­ni­fic­ant struc­tural fact in the re­gional com­pute pic­ture. Since 10 July 2026 the UAE's named en­tit­ies buy without a li­cence, while Saudi Ar­a­bia's flag­ship pro­gramme buys under a li­cence whose con­di­tions are not pub­lished and whose de­liv­ery sched­ule is not pub­lished. Two na­tional pro­grammes with com­par­able am­bi­tion there­fore sit on dif­fer­ent pro­cure­ment foot­ings, and a buyer com­mit­ting to a Saudi sov­er­eign ar­ti­fi­cial-in­tel­li­gence plat­form is ac­cept­ing a sup­ply de­pend­ency whose terms it can­not read.

How the numbers should be read

  • An­nounced: a pub­lic state­ment of in­tent with no dis­clos­ure of con­tract­ing. The 3 GW by 2030 and more than 6 GW by 2034 HUMAIN tar­gets, and the more than USD 5bn AWS and HUMAIN AI Zone fig­ure, sit here.
  • Con­trac­ted or phased: a dated pro­gramme with named hard­ware and named ca­pa­city. HUMAIN phase one at 14 MW of Black­well HGX B300 from the fourth quarter of 2026, and phase two at 70 MW of Vera Rubin from mid-2027, sit here.
  • Li­censed: cleared for the sil­icon to move. The 19 Novem­ber 2025 au­thor­isa­tions for G42 and HUMAIN, each up to the equi­val­ent of 35,000 GB300, and the 10 July 2026 UAE re­as­sign­ment to A:5, sit here.
  • En­er­gised: draw­ing power and serving work­loads. Noth­ing in the Gulf sov­er­eign ar­ti­fi­cial-in­tel­li­gence pro­gramme sits here on pub­lished evid­ence.

The takeaway is that ca­pa­city plan­ning against sov­er­eign ar­ti­fi­cial-in­tel­li­gence plat­forms in the Gulf is cur­rently plan­ning against an­nounce­ments. The ques­tion that dis­tin­guishes a us­able plat­form from a press re­lease is a short one and it is an­swer­able by the op­er­ator rather than by the mar­ket: what is en­er­gised today, what is con­trac­ted with a de­liv­ery date, and under which ex­port au­thor­isa­tion does the hard­ware ar­rive. Until the first of those three is pub­lished, the an­nounced mega­watt fig­ures should carry no weight in a work­load de­cision.

Digital SovereigntyVolge Quarterly19 •

What sovereignty costs

No vendor has published a sovereign-cloud price delta for any Gulf market. The only measurable sovereign premium in the world is European, and the only firm Gulf cost figures are construction costs, which are the lowest of any region.

The hon­est an­swer to what sov­er­eignty costs in the Gulf is that no one has pub­lished it. No GCC sov­er­eign-cloud price delta is pub­lished by any vendor. No pub­lished tender or con­tract value for GCC gov­ern­ment cloud could be loc­ated: not from Etimad, not from the UAE, not from Qatar, and the Saudi Deem ser­vice ap­pears only as a gov­ern­ment cloud cat­egory in a World Bank re­port with no con­tract de­tail at­tached. What ex­ists in­stead is a European proxy that can be meas­ured, a con­struc­tion cost index that can be com­pared, and a pipeline fig­ure that is an­nounced rather than com­mit­ted. Those three are use­ful. They are not a price.

The European proxy

The AWS European Sov­er­eign Cloud is the only sov­er­eign of­fer­ing in the world whose premium can be meas­ured, be­cause AWS pub­lishes its list prices through its own cal­cu­lator and a buyer can there­fore com­pute the gap for a spe­cific work­load. The meas­ure­ments do not agree. tecRacer meas­ured roughly 15 per cent above eu-cent­ral-1 in Frank­furt across com­mon ser­vices in Janu­ary 2026. De­voteam puts the fig­ure at 10 to 15 per cent. Other com­ment­ary cites 20 to 30 per cent as an in­dustry es­tim­ate. One com­par­ison found three ser­vices slightly cheaper in the sov­er­eign en­vir­on­ment than out­side it. The spread between the low and the high of those ac­counts is wide enough that none of them can be ad­op­ted as the num­ber, and the range should be car­ried as a range.

Mi­crosoft's sov­er­eign add-on pri­cing is less clear still: the sources con­flict between no extra list cost and a range of 15 to 20 per cent, and the po­s­i­tion is that it is not re­li­ably pub­lic. It is to be noted that trans­pos­ing any of these fig­ures to the Gulf would be an ex­tra­pol­a­tion rather than a find­ing, and that the re­search sup­port­ing this edi­tion con­tains no basis for it. The European premium tells a Gulf buyer that a sov­er­eign premium ex­ists and is likely to be meas­ured in low tens of per cent some­where. It does not tell that buyer what a Gulf sov­er­eign tier will be priced at.

No GCC sovereign-cloud price delta is published by any vendor. That is the finding, and no proxy converts into one.

What can be costed: the concrete

Con­struc­tion cost is the one di­men­sion on which the Gulf po­s­i­tion is firmly quan­ti­fied, and it fa­vours the re­gion. Turner and Town­send's tenth Data Centre Con­struc­tion Cost Index places the Middle East at USD 9.93 per watt, the cheapest re­gion sur­veyed.

Region or countryData centre construction cost, USD per watt
Middle East9.93
North America12.06
Asia12.10
Europe12.76
Saudi Arabia10.80
Qatar9.80
United Arab Emirates9.20

Source: Turner and Town­send, tenth Data Centre Con­struc­tion Cost Index. Re­gional and coun­try fig­ures are drawn from the same index and are not ad­dit­ive. The same source fore­casts Middle East con­struc­tion cost in­fla­tion at 5.1 per cent in 2027, the second-highest of any re­gion.

Two ob­ser­va­tions fol­low. The first is that the Gulf's cost ad­vant­age in con­struc­tion is real but nar­row in ab­so­lute terms: USD 9.93 per watt against USD 12.76 in Europe is a dif­fer­ence of a little under a quarter, and the fore­cast of 5.1 per cent Middle East con­struc­tion cost in­fla­tion in 2027, the second-highest of any re­gion, erodes it. The second is that the dir­ec­tion of travel glob­ally is against the buyer. JLL's global shell-and-core es­tim­ate stands at ap­prox­im­ately USD 11.3m per MW in 2026 against USD 7.7m per MW in 2020. That es­tim­ate is global and not GCC-spe­cific, and should not be read as a Gulf fig­ure, but it in­dic­ates the trend that any sov­er­eign ca­pa­city com­mit­ment made in 2027 is being made into.

The pipeline, and what it is not

GlobalData and MEED track GCC data centre in­vest­ment above USD 93bn across more than 174 act­ive and planned pro­jects. This is an an­nounced pipeline. It is not com­mit­ted and it is not spent, and the dis­tinc­tion is not pedantic: a pipeline fig­ure of that size, pub­lished without a com­mit­ted sub­set, tells a buyer about in­tent and noth­ing about de­livered ca­pa­city. Ar­izton pro­jects Middle East data centre mar­ket rev­enue of USD 7.61bn in 2025 rising to USD 20.74bn by 2031, with cu­mu­lat­ive in­vest­ment of USD 33.79bn for 2025 to 2030. Those are ana­lyst pro­jec­tions rather than re­por­ted

Digital SovereigntyVolge Quarterly20 •

fig­ures, and they are not re­con­ciled with the USD 93bn pipeline be­cause the two meas­ure dif­fer­ent things.

It is also to be noted what is ab­sent. No GCC-spe­cific pub­lic cloud spend­ing fore­cast from IDC, Gart­ner or Syn­ergy was avail­able for this edi­tion. No pub­lished tender or con­tract value for gov­ern­ment cloud in any of the six states was loc­ated. The com­bined ef­fect is that a Gulf buyer can­not bench­mark a sov­er­eign cloud price against a com­par­able pub­lic trans­ac­tion, be­cause no com­par­able pub­lic trans­ac­tion has been pub­lished.

The takeaway is that pri­cing a sov­er­eign de­ploy­ment in the Gulf is cur­rently an ex­er­cise in first-prin­ciples cost­ing rather than bench­mark­ing. What is meas­ur­able is the con­struc­tion cost per watt, which is the low­est of any re­gion and rising at the second-fast­est rate; what is meas­ur­able by proxy is a European sov­er­eign premium some­where in a dis­puted range from 10 to 30 per cent; and what is not avail­able at any price is a pub­lished Gulf delta or a com­par­able con­tract value. Any busi­ness case that presents a Gulf sov­er­eign premium as a single fig­ure has in­ven­ted it, and the ab­sence of the num­ber is a stronger ne­go­ti­at­ing fact than any es­tim­ate of it.

A framework for placing a workload

Four of the six Gulf states have published a classification or tiering scheme, and in each case it is the scheme rather than the privacy statute that decides where a workload may run. Placement is therefore a classification exercise first and a procurement exercise second.

The prac­tical mech­an­ism by which sov­er­eignty binds a work­load in the Gulf is clas­si­fic­a­tion. The United Arab Emir­ates pub­lishes three sov­er­eignty tiers and at­taches named con­di­tions to each. Qatar pub­lishes five clas­si­fic­a­tion tiers for gov­ern­ment en­tit­ies and a min­imum of four for oth­ers. Saudi Ar­a­bia op­er­ates a two-axis model in which the Na­tional Data Man­age­ment Of­fice sets sens­it­iv­ity and the Na­tional Cy­ber­se­cur­ity Au­thor­ity sets the cor­res­pond­ing con­trol level. Oman fences two of its levels in­side the na­tional bor­der. In every one of those four cases the label at­tached to the data de­term­ines the host­ing model, and the se­quence that fol­lows from this is fixed: clas­sify, then se­lect the con­trol level, then se­lect the re­gion, then se­lect the pro­vider. Re­vers­ing that se­quence is how work­loads end up in the wrong place.

The UAE tier de­scrip­tions rest on a law firm sum­mary dated 15 Oc­to­ber 2026 rather than on the primary policy text. The exact NDMO clas­si­fic­a­tion la­bels are con­tested between sources. Oman's full level defin­i­tions and li­cence classes, and Qatar's claimed C4 cloud-mi­gra­tion ex­emp­tion, were not re­trieved. Each should be checked against the primary in­stru­ment.

The four published schemes

JurisdictionSchemeLevelsWhat the top levels require
United Arab EmiratesNational Cloud Security Policy v2.0, UAE Cyber Security CouncilThree sovereignty tiersTier 2 applies where data is classified confidential or restricted: all consumer data stored strictly within UAE geographical boundaries and legal jurisdiction. Tier 3 applies above that: exclusive UAE jurisdiction, data and metadata not disclosed to any authority other than those explicitly approved by the UAE, all foreign access requests denied by default
QatarNCSA National Data Classification Policy V3.0, established May 2023Five tiers, C0 to C4, for government entities; a minimum of four tiers for non-government entitiesNot fully retrieved from public material. One secondary summary states C4 is exempt from cloud migration; this is unverified
Saudi ArabiaNDMO national data classification plus NCA Cloud Cybersecurity Controls CCC-2:2024Four classification levels and four corresponding cloud control levelsControl Level 1 applies to top secret data and Control Level 2 to secret data. CCC-2:2024 covers government bodies and private owners and operators of critical national infrastructure
OmanTRA cloud and data centre bylaw, Decision No. 1152/2/19/2024-20, September 2024Levels referenced to 4; full definitions not retrievedArticle 12 prohibits transferring Levels 3 and 4 data, explicitly including governmental and financial data, outside Oman without prior TRA approval

How a buyer uses them

The UAE scheme is the most dir­ectly ac­tion­able be­cause it states con­di­tions rather than prin­ciples. Tier 1, baseline se­cure cloud, re­quires found­a­tional con­trols of all pro­viders ir­re­spect­ive of data clas­si­fic­a­tion, which means no in-scope work­load is ex­empt. Tier 2, par­tial sov­er­eign cloud, ap­plies where data is clas­si­fied con­fid­en­tial or re­stric­ted and re­quires that all con­sumer data be stored strictly within UAE geo­graph­ical bound­ar­ies and legal jur­is­dic­tion, with a dis­clos­ure pro­tocol: on a valid for­eign dis­clos­ure order the pro­vider must make reas­on­able ef­forts to re­dir­ect the re­quest to the con­sumer and must in­form both the con­sumer and the UAE au­thor­it­ies. Tier 3, sov­er­eign cloud, ap­plies above con­fid­en­tial or re­stric­ted and places all

Digital SovereigntyVolge Quarterly21 •

data under ex­clus­ive UAE jur­is­dic­tion, with con­sumer data and metadata not dis­closed to any au­thor­ity other than those ex­pli­citly ap­proved by the UAE and all for­eign ac­cess re­quests denied by de­fault. The eli­gib­il­ity con­di­tions to ex­pect at Tier 3 are UAE-based key man­age­ment, UAE-res­id­ent re­dund­ancy, UAE-li­censed tele­com­mu­nic­a­tions rout­ing and UAE-cleared per­son­nel.

Two rules in the UAE scheme have dis­pro­por­tion­ate prac­tical ef­fect. The first is that where tiers over­lap, the most strin­gent con­trol ap­plies, which means a com­pos­ite work­load in­her­its the ob­lig­a­tions of its most sens­it­ive com­pon­ent and can­not be av­er­aged down. The second is that across all tiers, data loc­a­tion must be known at all stages, hos­ted en­cryp­tion keys and their backups must be gen­er­ated, stored and man­aged in the UAE, and the con­sumer must as­sess whether hold-your-own-key is re­quired. That last ob­lig­a­tion sits with the buyer and not with the pro­vider, which makes it the con­di­tion most fre­quently left un­per­formed.

Where tiers overlap the most stringent control applies: a composite workload inherits the obligations of its most sensitive component.

The Saudi model is used dif­fer­ently be­cause it sep­ar­ates the two ques­tions. The clas­si­fic­a­tion level an­swers how sens­it­ive the data is; the CCC-2:2024 con­trol level an­swers what must there­fore be done. Level 1 at­taches to top secret data and Level 2 to secret data, and the scope of CCC-2:2024 cov­ers gov­ern­ment bod­ies and private own­ers and op­er­at­ors of crit­ical na­tional in­fra­struc­ture, which means a private en­ter­prise out­side that defin­i­tion is not within the con­trols at all and is gov­erned in­stead by its sec­tor reg­u­lator and by the Per­sonal Data Pro­tec­tion Law. Es­tab­lish­ing whether an en­tity is in scope is there­fore the first ques­tion in the King­dom, and it pre­cedes clas­si­fic­a­tion.

Qatar's scheme is used as a gate. Five tiers for gov­ern­ment en­tit­ies and a min­imum of four for non-gov­ern­ment en­tit­ies, under the Na­tional Data Clas­si­fic­a­tion Policy V3.0 es­tab­lished in May 2023, sit along­side the MCIT Cloud First Policy, doc­u­ment P005 v1.0.0 of April 2024, which ap­plies to all gov­ern­ment agen­cies. The com­bin­a­tion means a Qatari gov­ern­ment work­load is pushed to­wards cloud by policy and con­strained by tier, and the claimed ex­emp­tion of C4 from cloud mi­gra­tion, if it is con­firmed, is the point at which the two in­stru­ments meet. It is un­veri­fied and should not be as­sumed in either dir­ec­tion.

Oman's scheme is used as a bound­ary rather than a gradi­ent. The op­er­at­ive pro­vi­sion is Art­icle 12 of the cloud bylaw: Levels 3 and 4, which ex­pli­citly in­clude gov­ern­mental and fin­an­cial data, may not leave Oman without prior TRA ap­proval. Be­cause the full level defin­i­tions were not re­trieved, the prac­tical ap­proach is to treat gov­ern­mental and fin­an­cial data as fenced and to es­tab­lish the status of any­thing ad­ja­cent to those cat­egor­ies with the reg­u­lator be­fore design­ing a cross-bor­der flow. The con­straint is sharpened by the ab­sence of any hy­per­scaler re­gion dom­i­ciled in the Sul­tan­ate as at May 2026.

The takeaway is a single or­der­ing, ap­plied per jur­is­dic­tion and per en­tity. Es­tab­lish whether the en­tity is in scope of the na­tional cloud in­stru­ment. Clas­sify the data under that jur­is­dic­tion's own scheme and not under a group stand­ard. Read the con­trol level or tier that the clas­si­fic­a­tion com­pels. Only then test which live re­gions and li­censed pro­viders can sat­isfy it. Where the clas­si­fic­a­tion la­bels or level defin­i­tions are con­tested or un­re­trieved, as they are in three of the four schemes above, the clas­si­fic­a­tion is pro­vi­sional until con­firmed against the primary text, and a pro­vi­sional clas­si­fic­a­tion should not be used to jus­tify the cheaper tier.

The dated calendar, 2026 to 2028

Only three dates in the Gulf's next three years bind anybody. The rest are vendor targets, and the distinction between the two is the most useful line a buyer can draw across a planning horizon.

A cal­en­dar of Gulf di­gital sov­er­eignty looks crowded and is not. Of the dated events between 2026 and 2028, three im­pose ob­lig­a­tions on iden­ti­fi­able parties: Oman's Per­sonal Data Pro­tec­tion Law be­com­ing fully en­force­able, the UAE Na­tional Cloud Se­cur­ity Policy v2.0 bind­ing pro­viders and spe­cified con­sumers, and the Saudi local con­tent weight­ing tak­ing ef­fect in the fin­an­cial eval­u­ation of gov­ern­ment IT tenders. The re­mainder are com­mer­cial tar­gets set by vendors, which may move without any­body being in breach. The table sep­ar­ates the two, be­cause a plan that treats a vendor tar­get as a dead­line will be built on the wrong found­a­tion.

DateEventBinding onNature
5 February 2026Oman PDPL fully enforceableAll controllers and processors in OmanRegulatory
In force 2026Oman TRA cloud and data centre bylaw. Level 3 and 4 data cannot leave Oman without TRA approvalProviders and data centre operators in OmanRegulatory
Digital SovereigntyVolge Quarterly22 •
DateEventBinding onNature
From 15 October 2026 reportingUAE National Cloud Security Policy v2.0All providers serving the UAE; federal ministries and authorities; non-government critical information infrastructure; Emirate government entities where no Emirate CII programme existsRegulatory
Q4 2026 targetMicrosoft Azure Saudi Arabia East regionNobody. A vendor targetCommercial
December 2026 targetAWS Saudi Arabia regionNobody. A vendor targetCommercial
1 April 2027Saudi local content weighting in the financial evaluation of IT service contractsBidders for Saudi government IT tenders of SAR 10m or moreRegulatory
Mid-2027HUMAIN phase two, 70 MW of Vera RubinNobody. A vendor targetCommercial
2028AWS and HUMAIN AI Zone, up to 50 MW availableNobody. A vendor targetCommercial
Not datedSaudi Global AI Hub LawNobody. A draft, no commencement date publishedDraft

One fur­ther com­pli­ance dead­line for the UAE fed­eral data pro­tec­tion law cir­cu­lates in sec­ond­ary com­ment­ary. It could not be veri­fied against any primary in­stru­ment and is there­fore ex­cluded from the cal­en­dar above rather than car­ried with a caveat.

What the calendar contains

The reg­u­lat­ory entries have a com­mon char­ac­ter: each of them changes what a named class of party must do, and each of them is trace­able to a pub­lished in­stru­ment. Oman's po­s­i­tion is the heav­iest be­cause two in­stru­ments land close to­gether. The Per­sonal Data Pro­tec­tion Law, Royal De­cree No. 6/2022 pub­lished on 13 Feb­ru­ary 2022, with Ex­ec­ut­ive Reg­u­la­tions by Min­is­terial De­cision No. 34/2024 pub­lished on 4 Feb­ru­ary 2024, be­came fully en­force­able from 5 Feb­ru­ary 2026 and binds all con­trol­lers and pro­cessors in the Sul­tan­ate. The TRA cloud and data centre bylaw, De­cision No. 1152/2/19/2024-20 of Septem­ber 2024, took ef­fect the day after Gaz­ette pub­lic­a­tion and binds pro­viders and data centre op­er­at­ors, with Levels 3 and 4 data pro­hib­ited from leav­ing without prior TRA ap­proval. A buyer op­er­at­ing in Oman is there­fore sub­ject to a new pri­vacy re­gime and a new pro­vider li­cens­ing re­gime within the same period.

The Saudi entry is the one with the clearest com­mer­cial con­sequence. From 1 April 2027 local con­tent car­ries weight in the fin­an­cial eval­u­ation of IT ser­vice con­tracts for tenders of SAR 10m or more, bind­ing bid­ders rather than op­er­at­ors. It is a pro­cure­ment rule and not a pri­vacy rule, and it is the only date in the

table that changes who wins work rather than what work may law­fully be done.

The UAE entry is the broad­est in scope. From the re­port­ing of 15 Oc­to­ber 2026, the Na­tional Cloud Se­cur­ity Policy v2.0 binds all pro­viders serving the UAE, fed­eral min­is­tries and au­thor­it­ies, non-gov­ern­ment crit­ical in­form­a­tion in­fra­struc­ture en­tit­ies, and Emir­ate gov­ern­ment en­tit­ies where no Emir­ate crit­ical in­form­a­tion in­fra­struc­ture pro­gramme ex­ists. The last of those four is the one most often missed, be­cause it makes the ap­plic­able su­per­visor de­pend on whether the rel­ev­ant Emir­ate runs its own pro­gramme.

Three dates bind somebody. Five are vendor targets that may move without anybody being in breach.

What the calendar does not contain

The cal­en­dar con­tains no com­mence­ment date for the Saudi Global AI Hub Law, be­cause none has been pub­lished. The draft was pub­lished by the Com­mu­nic­a­tions, Space and Tech­no­logy Com­mis­sion on 14 April 2025 with con­sulta­tion clos­ing on 14 May 2025, and it would cre­ate Private, Ex­ten­ded and Vir­tual Hubs, which is to say data em­bassies op­er­at­ing under for­eign law. It re­mains a draft. It is the largest single un­cer­tainty in the Gulf's three-year pic­ture and it has no date.

The cal­en­dar also con­tains no en­force­ment dates, be­cause no named pub­lished fine or en­force­ment de­cision under any of the six GCC data pro­tec­tion laws could be loc­ated. It con­tains no com­mis­sion­ing date for Star­gate UAE, whose third-quarter 2026 tar­get has passed with no of­fi­cial con­firm­a­tion loc­ated. It con­tains no date on which the status of the UAE fed­eral Ex­ec­ut­ive Reg­u­la­tions will be re­solved, be­cause their status could not be con­firmed. And it con­tains no en­er­gised ca­pa­city mile­stone for any sov­er­eign ar­ti­fi­cial-in­tel­li­gence pro­gramme in the re­gion, be­cause en­er­gised as op­posed to an­nounced ca­pa­city is not pub­lished for HUMAIN or for Star­gate UAE.

Digital SovereigntyVolge Quarterly23 •

The takeaway is that a three-year sov­er­eignty plan for the Gulf has three fixed points and a great deal of vendor-de­pend­ent op­tion­al­ity around them. The three reg­u­lat­ory dates can be planned against and should be. The com­mer­cial tar­gets should be car­ried with a stated fall­back, since two of them con­cern Saudi re­gions that were still un­launched at the latest re­por­ted po­s­i­tion and one con­cerns a 2028 avail­ab­il­ity fig­ure. The un­dated items, and above all the draft hub law, war­rant mon­it­or­ing of the primary in­stru­ment rather than a place in a plan.

The dependence question

Every sovereign artificial-intelligence platform in the Gulf runs on foreign silicon moving under foreign export licences whose conditions are not published. Sovereignty over data is achievable in the region. Sovereignty over compute is not, and a buyer should price the difference rather than ignore it.

The un­com­fort­able fact un­der­neath the Gulf's sov­er­eignty pro­gramme is that its most ad­vanced layer is its least sov­er­eign. Data res­id­ency can be en­gin­eered: it is a mat­ter of re­gion se­lec­tion, key cus­tody and rout­ing, and the UAE Na­tional Cloud Se­cur­ity Policy v2.0 shows that it can be spe­cified in writ­ing and tested. Com­pute can­not be en­gin­eered in the same way, be­cause the hard­ware on which every an­nounced sov­er­eign ar­ti­fi­cial-in­tel­li­gence plat­form in the re­gion de­pends is de­signed and man­u­fac­tured out­side the re­gion and moves under ex­port au­thor­isa­tions gran­ted out­side the re­gion. The con­trol a buyer has over the first is sub­stan­tial. The con­trol it has over the second is, on pub­lished evid­ence, none.

What the licences actually say, and do not

On 19 Novem­ber 2025 US Com­merce au­thor­ised ad­vanced chip ex­ports to G42 in the UAE and HUMAIN in Saudi Ar­a­bia, each up to the equi­val­ent of 35,000 NVIDIA GB300, con­di­tioned on se­cur­ity and re­port­ing re­quire­ments mon­itored by the Bur­eau of In­dustry and Se­cur­ity. The li­cence num­bers are not pub­lic. The full con­di­tion list is not pub­lic. The de­liv­ery sched­ules are not pub­lic. What is pub­lic is the ceil­ing and the fact of con­di­tion­al­ity. On 10 July 2026 the UAE was re­por­ted to have moved from Coun­try Groups D:3 and D:4 to A:5, clear­ing G42, Core42 and MGX for li­cence-free pur­chases; Saudi Ar­a­bia was not covered and re­mains on the Novem­ber 2025 li­cence basis.

Three con­sequences fol­low for a buyer. The first is that the com­pute sup­ply for the King­dom's flag­ship pro­gramme is gov­erned by con­di­tions that can­not be

read, which means the risk can­not be as­sessed, only ac­know­ledged. The second is that the two largest Gulf mar­kets now sit on dif­fer­ent foot­ings, with the UAE's named en­tit­ies pur­chas­ing without a li­cence and Saudi Ar­a­bia's pur­chas­ing under one. The third is that both foot­ings are re­voc­able by a for­eign ad­min­is­trat­ive de­cision, and the two dates in this para­graph are them­selves the evid­ence that such de­cisions change: the po­s­i­tion in July 2026 was not the po­s­i­tion in Novem­ber 2025.

The 10 July 2026 Coun­try Group re­as­sign­ment rests on sec­ond­ary re­port­ing; the primary Fed­eral Re­gister text was not re­trieved. The con­di­tions at­tach­ing to the 19 Novem­ber 2025 au­thor­isa­tions are not pub­lic and no claim about their con­tent is made here.

Sovereignty over data can be specified in a contract. Sovereignty over compute currently cannot, because the conditions are not published.

What a buyer can control

  • Data loc­a­tion at every stage. The UAE Cloud Se­cur­ity Policy re­quires it across all three tiers, and it is test­able against a pro­vider's doc­u­mented ar­chi­tec­ture.
  • Key cus­tody. Hos­ted en­cryp­tion keys and their backups must be gen­er­ated, stored and man­aged within the UAE. Whether hold-your-own-key is re­quired is an as­sess­ment the con­sumer must make, not the pro­vider.
  • Re­sponse to for­eign legal pro­cess. At UAE Tier 2 the pro­vider must make reas­on­able ef­forts to re­dir­ect a valid for­eign dis­clos­ure order to the con­sumer and in­form the con­sumer and the UAE au­thor­it­ies. At Tier 3 all for­eign ac­cess re­quests are denied by de­fault.
  • Gov­ern­ing law, in one jur­is­dic­tion only. Art­icle 3 of Bahrain's Le­gis­lat­ive De­cree No. 56 of 2018 sub­jects data stored in des­ig­nated Bahraini data centres by over­seas cloud con­sumers to the law of the con­sumer's home state, sub­ject to the des­ig­na­tion res­ol­u­tion whose is­su­ance could not be con­firmed.
  • Cross-bor­der move­ment of the most sens­it­ive classes. Art­icle 12 of Oman's cloud bylaw pro­hib­its Levels 3 and 4 data, in­clud­ing gov­ern­mental and fin­an­cial data, from leav­ing Oman without prior TRA ap­proval.

The asym­metry between those two lists is the hon­est state­ment of the Gulf's sov­er­eignty po­s­i­tion in 2027. The first list is spe­cific, writ­ten and test­able. The second is a set of de­pend­en­cies whose terms are

Digital SovereigntyVolge Quarterly24 •

with­held from the party bear­ing the risk. It is to be noted that this is not a cri­ti­cism of the Gulf pro­grammes: no jur­is­dic­tion out­side the small num­ber that man­u­fac­ture ad­vanced ac­cel­er­at­ors is in a dif­fer­ent po­s­i­tion, and the ex­port con­trol de­cisions of Novem­ber 2025 and July 2026 placed the UAE and Saudi Ar­a­bia among the most fa­vour­ably treated non-man­u­fac­tur­ing jur­is­dic­tions in the world. The point is nar­rower. A sov­er­eignty claim that cov­ers the data layer should not be read as cov­er­ing the com­pute layer, and the pub­lished re­cord does not sup­port ex­tend­ing it.

What a buyer cannot control

  • Whether the sil­icon ar­rives, and when. De­liv­ery sched­ules under the 19 Novem­ber 2025 au­thor­isa­tions are not pub­lic.
  • Under what con­di­tions it ar­rives. The full con­di­tion list mon­itored by the Bur­eau of In­dustry and Se­cur­ity is not pub­lic.
  • Whether the li­cens­ing basis per­sists. The UAE's move to Coun­try Group A:5 on 10 July 2026 did not ex­tend to Saudi Ar­a­bia, which demon­strates that the basis is coun­try-spe­cific and change­able.
  • Who can see the data in a sov­er­eign ar­range­ment whose terms are un­pub­lished. Key cus­tody and op­er­ator-ac­cess terms for the stc Group de­ploy­ment on Or­acle Alloy, for Core42 and for the e& and AWS Sov­er­eign Launch­pad are not pub­lic.
  • Whether a state share­hold­ing sup­plies con­trol. No pub­lished golden-share or formal op­er­ator-con­trol in­stru­ment between a GCC state en­tity and a hy­per­scaler could be loc­ated. The nearest pub­lished con­trol fea­tures are Mi­crosoft's board seat at G42, arising from a USD 1.5bn equity in­vest­ment, and the UAE in-coun­try key cus­tody rule.

The takeaway is that the two lay­ers should be as­sessed and doc­u­mented sep­ar­ately. For the data layer, the con­trols are spe­cifiable and the right course is to spe­cify them: loc­a­tion at all stages, key cus­tody, hold-your-own-key where the as­sess­ment re­quires it, and the pro­vider's doc­u­mented re­sponse to for­eign legal pro­cess. For the com­pute layer, the only de­fens­ible treat­ment is to re­cord the de­pend­ency ex­pli­citly, to note that the li­cence con­di­tions and de­liv­ery sched­ules are not pub­lic, and to hold a fall­back for the case in which the au­thor­isa­tion basis changes. A plan that as­sumes the com­pute de­pend­ency away is as­sum­ing away the only part of the stack whose gov­ern­ing terms the buyer has never seen.

India, for contrast

India has built the opposite of the Gulf model: a phased national statute with no general localisation mandate, and subsidised common compute at a published price. The contrast shows that the Gulf has chosen sovereignty by infrastructure where India has chosen sovereignty by rulemaking.

India is in­cluded here for one reason: it is the nearest large jur­is­dic­tion that has pur­sued di­gital sov­er­eignty by a dif­fer­ent route, and the dif­fer­ence is in­struct­ive rather than com­pet­it­ive. Where the Gulf states have le­gis­lated res­id­ency and clas­si­fic­a­tion and then built re­gions and clusters to sat­isfy them, India has no­ti­fied a single na­tional stat­ute with a phased com­mence­ment, has de­clined so far to no­tify any spe­cific loc­al­isa­tion man­date, and has put sub­sid­ised com­pute into the mar­ket at a price that is at least partly pub­lished. The con­trast is between sov­er­eignty ex­pressed as in­fra­struc­ture and sov­er­eignty ex­pressed as rule­mak­ing, and the Gulf buyer's in­terest in it is in see­ing which of the two pro­duces a po­s­i­tion a buyer can plan against.

Commencement, in phases

The Di­gital Per­sonal Data Pro­tec­tion Rules 2025 were no­ti­fied on 13 Novem­ber 2025 as G.S.R. 846(E), al­though the Press In­form­a­tion Bur­eau re­lease car­ries the date 14 Novem­ber 2025 and the two dates are un­re­con­ciled in the sources. Com­mence­ment is phased. The Data Pro­tec­tion Board pro­vi­sions took ef­fect im­me­di­ately. The con­sent man­ager rules fol­low at twelve months, in Novem­ber 2026. The du­ties of prin­cipal data fi­du­ciar­ies fol­low at eight­een months, which Rule 1(2) puts at 13 or 14 May 2027, the am­bi­gu­ity track­ing the no­ti­fic­a­tion date con­flict.

Des­ig­na­tions of Sig­ni­fic­ant Data Fi­du­ciar­ies under Sec­tion 10 are still pending. The ad­di­tional du­ties that at­tach on des­ig­na­tion in­clude a res­id­ent data pro­tec­tion of­ficer, an in­de­pend­ent aud­itor and an an­nual im­pact as­sess­ment. On loc­al­isa­tion, the po­s­i­tion is that fi­du­ciar­ies may be sub­ject to gov­ern­ment dir­ec­tions on re­stric­ted cat­egor­ies in­clud­ing local stor­age, but no spe­cific loc­al­isa­tion man­date has been no­ti­fied. That is the cent­ral struc­tural dif­fer­ence from the Gulf: the power to re­quire loc­al­isa­tion ex­ists and has not been ex­er­cised, whereas in Oman and Kuwait the re­quire­ment is already writ­ten into the cloud in­stru­ment.

Digital SovereigntyVolge Quarterly25 •
India holds the power to mandate localisation and has not used it. The Gulf has written the requirement into the cloud instrument and is building to satisfy it.

Compute, at a disputed price

The IndiaAI Mis­sion re­ports 38,231 graph­ics pro­cessing units on­boarded to com­mon com­pute, per a Lok Sabha reply dated 25 March 2026, with a fur­ther 20,000 an­nounced under AI Mis­sion 2.0 in Feb­ru­ary 2026, com­ple­tion not con­firmed. The price is where the com­par­ison be­comes genu­inely use­ful. IndiaAI com­mon com­pute is offered at roughly Rs 65 per GPU-hour ac­cord­ing to the same 25 March 2026 Lok Sabha reply, while other sources cite Rs 115.85 to Rs 150. Those ac­counts con­flict and are not re­con­ciled.

Even al­low­ing for that con­flict, the con­trast with the Gulf is stark on a point of kind rather than de­gree. India has a pub­lished fig­ure for on­boarded com­pute, stated to a par­lia­ment on a date, and at least one pub­lished unit price. For HUMAIN and for Star­gate UAE, no pub­lished op­er­at­ing mega­watt fig­ure and no en­er­gised GPU count ex­ists, and no GCC vendor has pub­lished a sov­er­eign-cloud price delta at all. A buyer in the Gulf com­par­ing op­tions can there­fore es­tab­lish what In­dian com­mon com­pute costs per GPU-hour within a dis­puted range, and can­not es­tab­lish what Gulf sov­er­eign ca­pa­city costs within any range.

The In­dian GPU-hour fig­ures are un­re­con­ciled across sources and the 38,231 and 20,000 GPU fig­ures rest on a par­lia­ment­ary reply and an an­nounce­ment re­spect­ively, with com­ple­tion of the second not con­firmed. The no­ti­fic­a­tion date con­flict of 13 against 14 Novem­ber 2025 propag­ates into the Rule 1(2) com­mence­ment date and is left un­re­solved here.

What the difference shows

Three things fol­low for a Gulf reader. The first con­cerns trans­par­ency as a pro­cure­ment asset. India's phased com­mence­ment dates, its pending des­ig­na­tions and its com­pute volumes are all stated pub­licly, with dates and with an iden­ti­fi­able source, and the con­flicts in the re­cord are vis­ible pre­cisely be­cause so much of it is pub­lished. In the Gulf the most sig­ni­fic­ant fig­ures, in­clud­ing en­er­gised ca­pa­city, sov­er­eign price deltas, gov­ern­ment cloud con­tract val­ues and the exact clas­si­fic­a­tion la­bels in two schemes, are not pub­lished at all, so there is noth­ing for sources to con­flict about. A buyer should not mis­take the ab­sence of con­tra­dic­tion for the pres­ence of cer­tainty.

The second con­cerns the shape of the ob­lig­a­tion. India's stat­ute as­signs du­ties and de­fers them, with the

heav­iest set, the prin­cipal data fi­du­ciary du­ties, ar­riv­ing at eight­een months, and with the des­ig­na­tion of sig­ni­fic­ant fi­du­ciar­ies still to come. The Gulf's in­stru­ments as­sign du­ties by clas­si­fic­a­tion and apply them on com­mence­ment, as Oman's 5 Feb­ru­ary 2026 en­force­ab­il­ity and the UAE Cloud Se­cur­ity Policy's im­me­di­ate scope both demon­strate. The In­dian model gives longer no­tice of a less spe­cified ob­lig­a­tion. The Gulf model gives shorter no­tice of a more spe­cified one. For plan­ning pur­poses the Gulf model is easier to en­gin­eer against and harder to defer.

The third con­cerns loc­al­isa­tion it­self. India's choice to hold the loc­al­isa­tion power in re­serve, ex­er­cis­able by dir­ec­tion on re­stric­ted cat­egor­ies, means an In­dian de­ploy­ment car­ries a con­tin­gent li­ab­il­ity rather than a fixed con­straint. The Gulf's choice to write res­id­ency and clas­si­fic­a­tion into in­stru­ments means a Gulf de­ploy­ment car­ries a fixed con­straint and no con­tin­gent li­ab­il­ity of that kind. Neither is bet­ter in the ab­stract. The fixed con­straint is more ex­pens­ive to sat­isfy and cheaper to plan around; the con­tin­gent one is cheaper today and can­not be sized.

The takeaway, for the Gulf and not for India, is that the re­gion's weak­est point is not its rules but its dis­clos­ure. The rules are spe­cific, dated and in­creas­ingly ac­tion­able, and the UAE tier­ing scheme is the clearest sov­er­eignty tax­onomy pub­lished any­where covered by this edi­tion. What is miss­ing is the op­er­at­ing data: en­er­gised ca­pa­city, sov­er­eign price deltas, con­tract val­ues, en­force­ment de­cisions and op­er­ator-ac­cess terms. Where India's re­cord can be checked and found to con­flict, the Gulf's fre­quently can­not be checked at all, and the ap­pro­pri­ate re­sponse in a work­load de­cision is to treat an un­pub­lished fig­ure as un­known rather than as fa­vour­able.

The in­stru­ment is Cir­cu­lar C 14/2021, ef­fect­ive 15 July 2021, bind­ing all banks op­er­at­ing in the UAE on a solo and group-wide basis. One ex­cep­tion is writ­ten in. Art­icle 6.2 per­mits branches of for­eign banks, sub­ject to ap­proval, to com­ply “by re­tain­ing a copy of the Mas­ter Sys­tem of Re­cord, up­dated on at least a daily basis, within the UAE”. It con­cedes the primary loc­a­tion for a for­eign branch; it does not con­cede the in-coun­try copy, and it does not op­er­ate without ap­proval. Art­icle 6.3 adds that cus­tomer Con­fid­en­tial Data “must not be shared out­side the UAE without Cent­ral Bank ap­proval and ob­tain­ing prior writ­ten con­sent from the cus­tomer”. Above the loc­a­tion rule sits an ap­proval gate: Art­icle 8.1 re­quires prior non-ob­jec­tion be­fore out­sourcing any ma­ter­ial activ­ity, and Art­icle 3 re­quires a re­gister of every ar­range­ment, re­cord­ing whether Con­fid­en­tial Data is in­volved. That re­gister is the

Digital SovereigntyVolge Quarterly26 •

arte­fact a buyer will be asked for. The trans­ition is closed, Art­icle 13.3 hav­ing re­quired all agree­ments, in­clud­ing pre-ex­ist­ing ones, to com­ply “by no later than 31 Decem­ber 2023”.

Sovereignty by sector

What the rules require of a banking, health, energy, government, telecommunications or logistics workload, and the sequence of questions by which any workload is placed.

Banking: the only sector where the rule is written as a place

Financial services is the one Gulf sector in which a regulator has reduced sovereignty to a sentence about geography. The UAE writes that sentence hardest, Saudi Arabia writes it as a default with an approval route out, and Bahrain has deleted the sentence it once had.

Bank­ing is where Gulf sov­er­eignty rules are most legible, be­cause one reg­u­lator named a place rather than de­scribed a con­trol. Art­icle 6.1 of the Cent­ral Bank of the UAE Out­sourcing Reg­u­la­tion for Banks re­quires that “the Mas­ter Sys­tem of Re­cord, which in­cludes all Con­fid­en­tial Data, is con­tinu­ously main­tained and stored within the UAE”. That is not a risk ex­pect­a­tion or a ma­tur­ity level but a flat ob­lig­a­tion, and its ob­ject is defined widely: the Mas­ter Sys­tem of Re­cord is “the col­lec­tion of all data, in­clud­ing Con­fid­en­tial Data, re­quired to con­duct all core activ­it­ies of a Bank”. A buyer want­ing to know what sov­er­eignty costs here should read that defin­i­tion against their own ap­plic­a­tion in­vent­ory, be­cause most core sys­tems fall in­side it.

Read the definition of the Master System of Record against your own application inventory before reading anything else.

Saudi Arabia: a default, not a prohibition

The Saudi po­s­i­tion is widely de­scribed as ab­so­lute res­id­ency. On the primary text it is not. Sec­tion 3.4.3 of the Saudi Cent­ral Bank Cyber Se­cur­ity Frame­work, ver­sion 1.0 of May 2017, provides that “in prin­ciple only cloud ser­vices should be used that are loc­ated in Saudi Ar­a­bia, or when cloud ser­vices are to be used out­side Saudi Ar­a­bia that the Mem­ber Or­gan­iz­a­tion should ob­tain ex­pli­cit ap­proval from SAMA”. The qual­i­fier and the ex­press al­tern­at­ive both mat­ter. The same clause re­quires ap­proval “prior to using cloud ser­vices or sign­ing the con­tract with the cloud pro­vider”, an

un­usu­ally early gate: ap­proval pre­cedes sig­na­ture, not de­ploy­ment.

The sharper Saudi gate is not the loc­a­tion clause. Para­graph 42 of the Rules on Out­sourcing re­quires writ­ten non-ob­jec­tion for any out­sourcing to a pro­vider loc­ated over­seas, and limb (c) re­quires the “Ra­tionale for out­sourcing (in­clud­ing why it can­not be done within KSA)”. The ap­plic­ant must argue a neg­at­ive. That is a dif­fer­ent spe­cies of ob­lig­a­tion from a pro­hib­i­tion, and it ex­plains the pub­lished pat­tern: Saudi in­sti­tu­tions on private cloud, or buy­ing pub­lic cloud through a man­dated in-King­dom re­seller, rather than seek­ing ap­provals they would have to jus­tify.

The Frame­work uses “should” rather than “must” and is en­forced through ma­tur­ity as­sess­ment, the pub­lished timetable re­quir­ing full com­pli­ance by the end of 2019 at min­imum ma­tur­ity level three. The con­trast with the UAE's flat “must” is sig­ni­fic­ant.

Bahrain deleted its residency rule

Bahrain runs the other way, de­lib­er­ately. Rule­book mod­ule OM-2.1.7 provides that “Prior CBB ap­proval is re­quired on any out­sourcing to a third-party out­side Bahrain (ex­clud­ing cloud data ser­vices)”, with post-no­ti­fic­a­tion within five work­ing days of sig­na­ture suf­fi­cing for a “third-party cloud data ser­vices pro­vider in­side or out­side Bahrain”. Cloud is carved out of off­shore ap­proval and off­shore host­ing is per­mit­ted in terms. The archived pre­de­cessor, in force to 31 Decem­ber 2019, said the op­pos­ite: OM-3.9.2 re­quired that ser­vice pro­viders hand­ling cus­tomer in­form­a­tion “must be li­censed by the CBB and loc­ated in Bahrain”. A jur­is­dic­tion that re­moves its own res­id­ency rule and leaves the re­cord vis­ible is mak­ing an ar­gu­ment, not merely de­reg­u­lat­ing.

StateInstrumentLocation obligation on a banking workloadApproval
UAEOutsourcing Regulation for Banks, C 14/2021, effective 15 July 2021Master System of Record and all Confidential Data must be maintained and stored in the UAE. Foreign branches may instead hold a daily-updated copy in country, with approvalPrior non-objection for material outsourcing. Separate approval plus customer consent to share Confidential Data abroad
Saudi ArabiaCyber Security Framework v1.0, May 2017, s.3.4.3; Rules on Outsourcing, Chapter VIn-Kingdom by default, “in principle”, with explicit approval as the route offshoreApproval before using cloud or signing the contract. Written non-objection for all overseas outsourcing, with a case for why the work cannot be done in the Kingdom
BahrainCBB Rulebook OM-2.1.7, added January 2020, chapter replaced July 2022, amended April 2023 and May 2026None. Offshore hosting of banking data is expressly permittedCloud data services carved out of prior approval. Post-notification within five working days of signature
Digital SovereigntyVolge Quarterly27 •
StateInstrumentLocation obligation on a banking workloadApproval
QatarTechnology Risks Regulation for Banks; a 2024 cloud instrument is reportedNot established. No QCB instrument could be readNot established
KuwaitCybersecurity Baselines for the Kuwaiti Banking Sector, v1.0, January 2020Not established. The cloud security section was not retrievableNot established. No cloud-specific CBK circular was located
OmanCircular BM 1185, Rules for Availing Cloud Services by Licensed Institutions, 8 May 2022Not established. The text was not retrievedNot established

The last three rows re­cord a re­search limit, not a reg­u­lat­ory va­cuum. Kuwait's baselines carry sec­tions titled “Third Party Out­sourcing” and “Cloud Se­cur­ity” at pages 42 and 43 of 55, and the re­trieved file trun­cated at page 37. Oman's BM 1185 is cor­rob­or­ated by name and date, but not one op­er­at­ive word was re­trieved. Un­es­tab­lished is not the same as per­missive. The UAE and Bahrain rule­books were re­trieved in full.

The empty enforcement file

Named moves are thin­ner than the cov­er­age sug­gests. A Bahraini bank an­nounced on its own news­room on 9 Feb­ru­ary 2021 that it had mi­grated its in­ter­na­tional re­mit­tance sys­tem to in-King­dom cloud re­gions, with no fig­ure pub­lished. First Abu Dhabi Bank's data centre mi­gra­tion, an­nounced 6 March 2024, is framed around sov­er­eign con­trols to “help achieve data sov­er­eignty and meet its UAE reg­u­lat­ory ob­lig­a­tions”, and Mashreq's Oc­to­ber 2024 se­lec­tion of a cloud-at-cus­tomer data­base was jus­ti­fied partly by the need to “com­ply with local data res­id­ency reg­u­la­tions”. Those two, and the re­gion's one com­pleted core bank­ing mi­gra­tion, were all an­nounced by vendors or in­teg­rat­ors rather than by the banks.

A widely quoted fig­ure, that about 92 per cent of a UAE group's core bank­ing sys­tems are in cloud, comes from an in­ter­view page car­ry­ing no date, and should not reach a board paper un­dated.

What a buyer will test is en­force­ment, and the re­cord does not sup­port it. Across the six states no pub­lished pen­alty on a bank by a Gulf fin­an­cial reg­u­lator is ex­pressly groun­ded in out­sourcing, cloud, res­id­ency or tech­no­logy gov­ernance. The UAE en­force­ment list­ing runs to roughly sixty re­leases between Novem­ber 2019 and Decem­ber 2025 and not one cites those grounds. Saudi ar­chi­tec­ture ex­plains part of this: the In­struc­tions for Pub­lish­ing Bank­ing Pen­al­ties of 17 Decem­ber 2017 re­quire banks to dis­close pun­it­ive de­cisions by cat­egory, and the cat­egor­ies are su­per­vis­ory in­struc­tions, cus­tomer pro­tec­tion, due di­li­gence and cash-ma­chine per­form­ance. There is no tech­no­logy or out­sourcing cat­egory, so a res­id­ency breach would be in­vis­ible.

The takeaway is un­com­fort­able for both sides. The rules are the re­gion's most pre­script­ive and the ceil­ings are rising: the UAE max­imum on a li­censed fin­an­cial in­sti­tu­tion moved to not more than AED 1,000,000,000 under Art­icle 168 of Fed­eral De­cree-Law No. 6 of 2025, in force 16 Septem­ber 2025, from AED 200,000,000. Saudi Ar­a­bia's most tech­no­logy-rel­ev­ant stat­utory fig­ure is the bank­ing-secrecy limb of the Bank­ing Con­trol Law, a fine not ex­ceed­ing SAR 20,000. In a sec­tor with a flat loc­a­tion man­date, a rising ceil­ing and no pub­lished case, the risk is not the fine. It is the power, held by both reg­u­lat­ors, to order an out­sourcing ar­range­ment ter­min­ated.

Healthcare: one state legislates the place, the rest legislate the permission

Only the United Arab Emirates has a health-specific data localisation rule. Elsewhere in the Gulf health data is reached as a sensitive category under the general data law, and what is required is a permit or a transfer condition rather than a location.

In health­care a single in­stru­ment car­ries al­most the whole re­gional bur­den, and buy­ers routinely at­trib­ute its ef­fect to states with no equi­val­ent. Art­icle 13 of UAE Fed­eral Law No. 2 of 2019 on the Use of In­form­a­tion and Com­mu­nic­a­tion Tech­no­logy in Health Fields provides that “the health in­form­a­tion and data re­lated to the health ser­vices provided in the State may not be stored, pro­cessed, gen­er­ated or trans­ferred out­side the State, un­less in the cases defined by vir­tue of a de­cision is­sued by the Health Au­thor­ity in co­ordin­a­tion with the Min­istry”. Three fea­tures de­serve at­ten­tion be­fore any ar­chi­tec­ture is drawn. It cov­ers four verbs, so a com­pu­ta­tion that never moves the re­cord still en­gages it. Its trig­ger is the place of ser­vice, not the pa­tient's na­tion­al­ity. And the gate­way is a de­cision of a health au­thor­ity, defined to in­clude any local gov­ern­mental health au­thor­ity, so an emir­ate-level body can open it.

The law is­sued on 6 Feb­ru­ary 2019, pub­lished in Of­fi­cial Gaz­ette 647, in force three months after pub­lic­a­tion under Art­icle 31. Art­icle 2 ap­plies it “in­clud­ing the Free Zones”, clos­ing the route most often as­sumed open. The pen­alty is spe­cific: Art­icle 24 provides that a vi­ol­a­tion of Art­icle 13 “shall be pun­ished by a fine of not less than AED (500.000) five hun­dred thou­sand and not more than AED (700.000) seven hun­dred thou­sand”. Art­icle 25 adds a dis­cip­lin­ary track against in­sti­tu­tions run­ning to AED 1,000,000 and can­cel­la­tion of au­thor­isa­tion to use the fed­eral cent­ral sys­tem. Art­icle 20(1)(a) re­quires health data kept “no less than (25) twenty-five years” from the last pro­ced­ure.

Digital SovereigntyVolge Quarterly28 •

The exemptions do not relieve the residency burden

The ex­emp­tions sit in a Min­istry of Health and Pre­ven­tion res­ol­u­tion, num­ber 51 of 2021, is­sued 28 April 2021 and ef­fect­ive 16 May 2021 on pub­lic­a­tion in Gaz­ette 702. It is not Cab­inet Res­ol­u­tion No. 32 of 2020, which is the im­ple­ment­ing reg­u­la­tion and car­ries no ex­emp­tion list. The cat­egor­ies cover pa­tients treated abroad, over­seas labor­at­ory samples, sci­entific re­search, in­sur­ance and claims man­age­ment, co­oper­at­ing au­thor­it­ies, con­sumer health devices, phar­ma­covi­gil­ance, re­mote med­ical ser­vices, and trans­fers the health au­thor­it­ies or the pa­tient re­quest, each con­di­tioned typ­ic­ally on writ­ten con­sent and en­cryp­tion. The com­mer­cially sig­ni­fic­ant point is that sev­eral of those law­ful routes still re­quire a copy of the health in­form­a­tion to be kept in­side the UAE.

Two reput­able pub­lished tab­u­la­tions of this res­ol­u­tion give eight cat­egor­ies and ten re­spect­ively, and neither is the gaz­ette. That con­flict is un­re­con­ciled and should be re­solved against the in­stru­ment be­fore an ar­chi­tec­ture de­pends on a par­tic­u­lar cat­egory. Sec­ond­ary sum­mar­ies giv­ing the Art­icle 13 range as up to AED 2,000,000 are wrong against the min­istry's own text, which was re­trieved in full.

Lawful export is not the same as lawful exit: several exemptions still require a copy to remain in the country.

Saudi Arabia has no health hosting rule, and says so by example

No pub­lished rule re­quires the health data of Saudi pa­tients to be hos­ted in­side the King­dom. The Min­istry of Health's Saudi Health In­form­a­tion Ex­change Policies, doc­u­ment IS0303 ver­sion 1.0, was re­trieved in full and searched: it con­tains no host­ing, loc­al­isa­tion, res­id­ency, cloud or data-centre-loc­a­tion pro­vi­sion of any kind. That is a re­li­able neg­at­ive on the primary in­stru­ment most likely to carry one. What it does con­tain is the op­pos­ite duty, that “Data SHALL NOT be de­leted at any time from the Saudi Health In­form­a­tion Ex­change”.

Health data is reached in­stead as sens­it­ive data under the Per­sonal Data Pro­tec­tion Law, Royal De­cree M/19 of 16 Septem­ber 2021 as amended in March 2023, in force 14 Septem­ber 2023. On loc­a­tion the reg­u­lator's own guid­ance works an ex­ample in which data of people liv­ing in the King­dom sits on a cloud solu­tion “hos­ted in the USA”, and con­cludes that “such stor­age of per­sonal data will be reg­u­lated by the PDPL” even though the data is held abroad. A reg­u­lator pub­lish­ing that ex­ample is not op­er­at­ing a loc­al­isa­tion re­gime.

Draft amend­ments that would re­quire con­trol­lers to store per­sonal data within the King­dom went to con­sulta­tion from 6 Oc­to­ber to 5 Novem­ber 2026, with entry into force stated as sixty days after gaz­ette pub­lic­a­tion if ad­op­ted. That rests on law-firm re­port­ing, the draft text it­self not hav­ing been re­trieved, and is not settled.

Qatar forbids the restriction, and Oman has just moved

Qatar points the other way. Art­icle 15 of Law No. 13 of 2016 provides that “the Con­trol­ler shall be for­bid­den from tak­ing any de­cision or meas­ure that may limit the Cross-Bor­der Data Flow”, with that flow defined as ac­cess, use or stor­age “without re­stric­tions of the State's bor­ders”. What Qatar re­quires is per­mis­sion, not place: Art­icle 16 classes health data as of a spe­cial nature, pro­cess­able “only after ob­tain­ing the per­mis­sion from the Com­pet­ent De­part­ment”. Vendor ma­ter­ial as­sert­ing a Qatari health res­id­ency re­quire­ment groun­ded in this law should be re­jec­ted, be­cause the law con­tains none.

Oman also re­quires a per­mit. Art­icle 5 of Royal De­cree 6/2022 pro­hib­its pro­cessing health data “ex­cept after ob­tain­ing a per­mit” from the min­istry, which has 45 days to de­cide, si­lence count­ing as re­jec­tion. Art­icle 23 on cross-bor­der trans­fer is per­missive. Royal De­cree 68/2026, in force from 7 Septem­ber 2026, ex­ten­ded the law to pro­cessing “in­side or out­side the Sul­tan­ate”. Bahrain treats health data as sens­it­ive and re­stricts ex­port by des­tin­a­tion ad­equacy under Art­icle 12 of Law No. 30 of 2018, with crim­inal ex­pos­ure: un­law­ful trans­fer car­ries im­pris­on­ment up to one year and a fine of BD 1,000 to BD 20,000. Kuwait has no gen­eral data pro­tec­tion law and no health-spe­cific host­ing in­stru­ment was loc­ated, which is it­self the find­ing.

The retention rules do not agree

A re­gional pro­vider faces a con­tra­dic­tion no ar­chi­tec­ture re­solves. The UAE re­quires health data kept for not less than twenty-five years. Saudi Ar­a­bia's ex­change policy says its data shall never be de­leted. Oman's new Art­icle 15 re­quires that the con­trol­ler and pro­cessor “shall erase per­sonal data im­me­di­ately upon the end of the pur­pose of its pro­cessing”. These can­not all be sat­is­fied by one re­ten­tion policy, so the re­gional es­tate must be par­ti­tioned by jur­is­dic­tion for reas­ons un­con­nec­ted to host­ing loc­a­tion.

Digital SovereigntyVolge Quarterly29 •

The takeaway is that health­care has the re­gion's sharpest stat­utory lan­guage and its least vis­ible com­pli­ance. No en­force­ment ac­tion, pro­sec­u­tion or pub­lished de­cision was found against any Gulf en­tity for a health data host­ing or res­id­ency breach, under any of the five pen­alty re­gimes above. The ob­lig­a­tions exist and are un­lit­ig­ated in pub­lic, and the ab­sence of cases may re­flect non-pub­lic­a­tion rather than non-en­force­ment. For a buyer the op­er­at­ive risk is not the fine. It is that the UAE rule bites on pro­cessing and gen­er­a­tion as well as stor­age, so an ana­lyt­ics or model-train­ing work­load touch­ing Emir­ati clin­ical data en­gages Art­icle 13 even if the re­cord never leaves the coun­try.

Energy and utilities: a borrowed obligation, a secret perimeter, and a clause that has been deleted

No Gulf state has an energy-sector hosting instrument. Operators are caught by general critical-infrastructure frameworks, no state publishes who is designated, and the in-Kingdom cloud clause the market still cites was removed from the Saudi controls in 2024.

The po­s­i­tion in en­ergy is that the sec­tor has no rules of its own. Every host­ing ob­lig­a­tion traced here reaches an oil com­pany, a re­finery or a water and elec­tri­city util­ity through a gen­eral cy­ber­se­cur­ity or cloud frame­work, by vir­tue of being crit­ical na­tional in­fra­struc­ture, a gov­ern­ment en­tity, an af­fil­i­ate of one, or a holder of gov­ern­ment data. That ab­sence is the find­ing, and it is not for want of power. Abu Dhabi's De­part­ment of En­ergy, es­tab­lished under Law No. 11 of 2018, pub­lishes its own gov­ern­ing frame­work and its own re­spons­ib­il­it­ies, which in­clude “Reg­u­lat­ing all as­pects of the En­ergy Sec­tor through de­vel­op­ing policies, codes, stand­ards, rules, res­ol­u­tions”. Neither “cyber” nor “data” nor “in­form­a­tion se­cur­ity” ap­pears among them. The power ex­ists; no code has been made under it.

The Saudi clause that is no longer there

The most con­sequen­tial thing a buyer can learn from this sec­tor is that the Saudi in-King­dom cloud host­ing re­quire­ment, still the most cited host­ing clause in the Gulf, has been de­leted. The Na­tional Cy­ber­se­cur­ity Au­thor­ity's Cloud Cy­ber­se­cur­ity Con­trols are now at edi­tion CCC-2:2024, and the Au­thor­ity states that they “have been up­dated to re­flect changes re­lated to data loc­al­iz­a­tion re­quire­ments”. Annex D re­cords two de­le­tions in terms. Sub­con­trol 2-3-P-1-10 formerly read “Provide cloud com­put­ing ser­vices from within the King­dom, in­clud­ing sys­tems used for stor­age, pro­cessing, and dis­aster re­cov­ery cen­ters”. Sub­con­trol

2-3-P-1-11 covered “mon­it­or­ing, and sup­port”. Both are gone.

The stated ra­tionale is a trans­fer of com­pet­ence, not a re­lax­a­tion: “Con­trols re­lated to data loc­al­iz­a­tion have been trans­ferred from the doc­u­ment to the Na­tional Data Man­age­ment Of­fice (NDMO) at the Saudi Data and Ar­ti­fi­cial In­tel­li­gence Au­thor­ity”, and en­tit­ies “must refer to the Na­tional Data Man­age­ment Of­fice re­gard­ing data loc­al­iz­a­tion be­fore tak­ing any ac­tion”. The ob­lig­a­tion has moved rather than van­ished. Any ad­vice as­sert­ing that the Saudi cloud con­trols man­date in-King­dom host­ing by clas­si­fic­a­tion level is out of date against the pub­lished text. The suc­cessor rules sit with a body whose own site re­jects auto­mated re­trieval; they were not ob­tained and are not char­ac­ter­ised here.

Two cor­rec­tions fol­low. The four levels are data clas­si­fic­a­tion levels, not pro­vider tiers: level 1 ap­plies to data clas­si­fied as top secret through to level 4 pub­lic, with the highest level gov­ern­ing a mixed data­set. And what sur­vives on loc­a­tion con­cerns people, not data. Con­trol 1-4-P-1-1 re­quires that “Po­s­i­tions of cy­ber­se­cur­ity func­tions in CSP's data cen­ters within the King­dom must be filled with qual­i­fied and suit­able Saudi na­tion­als”, and the Es­sen­tial Cy­ber­se­cur­ity Con­trols, now at ECC-2:2024, re­quire man­aged cy­ber­se­cur­ity op­er­a­tions centres using re­mote ac­cess to sit en­tirely in­side the King­dom. Sov­er­eignty ex­pressed as staff­ing and op­er­a­tions loc­a­tion is a dif­fer­ent com­mer­cial prob­lem from data res­id­ency.

The obligation has moved rather than vanished, and it now sits with a body whose rules are not readable.

Nobody publishes who is designated

Scope turns on des­ig­na­tion, and des­ig­na­tion is al­most every­where in­vis­ible. The Saudi con­trols bind “all private sec­tor en­tit­ies own­ing, op­er­at­ing or host­ing Crit­ical Na­tional In­fra­struc­tures (CNIs)”, and no Saudi re­gister or sec­tor list was loc­ated: the peri­meter is self-identi­fy­ing. Oman holds the power ex­pressly, Royal De­cree 64/2020 re­quir­ing the Cyber De­fence Centre to pre­pare a clas­si­fic­a­tion of cyber in­fra­struc­ture and identify the rel­ev­ant sec­tors and en­tit­ies, and pub­lishes no out­put. Bahrain's strategy for 2025 to 2028 or­gan­ises it­self around pro­tect­ing crit­ical na­tional in­fra­struc­ture and names no sec­tor at all. Dubai is the half-ex­cep­tion: its Elec­tronic Se­cur­ity Centre pub­lishes ten crit­ical sec­tors, among them “Oil & Gas” and “Elec­tri­city & Water”, la­bels them “Ex­amples of Crit­ical Sec­tors”, and does not pub­lish the roster of des­ig­nated or­gan­isa­tions. Qatar's po­s­i­tion could not be es­tab­lished, its cyber agency's portal re­turn­ing an empty shell.

Digital SovereigntyVolge Quarterly30 •

Kuwait prohibits, Oman gates, Dubai does not publish

Two states do reach a host­ing res­ult, and neither does it through en­ergy law. Kuwait's Cloud Com­put­ing Reg­u­lat­ory Frame­work, ver­sion 2.4, car­ries the only ex­press private-sec­tor res­id­ency pro­hib­i­tion found in the re­gion. Clause 4.2.1.1 re­quires sub­scribers to en­sure noth­ing is hos­ted or stored out­side Kuwait “for any pur­pose, or in any format, whether tem­por­ar­ily or per­man­ently” where the data falls in the third or fourth clas­si­fic­a­tion tiers, or is per­sonal data held by gov­ern­ment bod­ies, private com­pan­ies or ser­vice pro­viders. Oman reaches a sim­ilar res­ult by con­sent: Art­icle 4(5) of the Cyber De­fence Centre sys­tem re­quires ap­proval of the Centre be­fore stor­ing any sens­it­ive data, or pro­cessing it, out­side the Sul­tan­ate, a duty con­fined neither to per­sonal data nor to gov­ern­ment bod­ies.

What the market is actually buying

The pub­lished de­ploy­ment re­cord points to­wards the hy­per­scaler stack, bought through a na­tional in­ter­me­di­ary. The Emir­ati na­tional oil com­pany's ar­ti­fi­cial in­tel­li­gence joint ven­ture an­nounced on 10 March 2025 a con­tract of USD 340 mil­lion to de­ploy its agen­tic plat­form across the up­stream value chain, stat­ing that it “will in­teg­rate best-in-class tech­no­lo­gies, in­clud­ing Azure cloud stack, agen­tic AI plat­form func­tion­al­ity, Open Sub­sur­face Data Uni­verse frame­work (OSDU), and OpenAI mod­els”. On the Saudi side a non-bind­ing memor­andum of 12 Feb­ru­ary 2026 lists among its work­streams “Di­gital Sov­er­eignty and Data Res­id­ency: Ex­plor­ing the de­vel­op­ment of a roadmap for de­ploy­ing solu­tions on the Mi­crosoft cloud, en­hanced with sov­er­eign con­trols”, in­clud­ing “meet­ing na­tional data res­id­ency re­quire­ments”. No fig­ure is at­tached to it.

The struc­tural move is con­sol­id­a­tion. On 1 Novem­ber 2026 the Saudi na­tional oil com­pany closed its ac­quis­i­tion of a 49 per cent stake in the sov­er­eign-fund ar­ti­fi­cial in­tel­li­gence vehicle, con­trib­ut­ing ap­prox­im­ately SAR 9.9 bil­lion in cash in 2026 against a stated plan to de­ploy three gigawatts of data centre ca­pa­city by 2030. Two days later the ex­clus­ive in-King­dom re­seller through which Saudi cus­tom­ers must buy one hy­per­scaler's ser­vices was fol­ded into that same vehicle.

The takeaway is that in this sec­tor the bind­ing con­straint is not a res­id­ency clause but a des­ig­na­tion the buyer can­not see and a coun­ter­party list that is nar­row­ing. No pub­lished pen­alty or en­force­ment ac­tion touch­ing Gulf en­ergy-sec­tor host­ing or data hand­ling was loc­ated, and the Saudi au­thor­ity's ex­press powers

to identify cy­ber­se­cur­ity vi­ol­a­tions date only from Royal De­cree M/117 of 22 Decem­ber 2024, with no out­come yet pub­lished. Six of the nine rel­ev­ant reg­u­lat­ors could not be reached, so the struc­tural point is safe to state and the ab­so­lute claim is not. Di­li­gence in en­ergy runs to the des­ig­na­tion ques­tion first, the in­ter­me­di­ary second, and the in­stru­ment last.

Government: the state built the sovereign cloud instead of regulating it

Gulf governments are the largest buyers of sovereign cloud and the least regulated users of it. The UAE expressly exempts government data from its only data protection law, no federal cloud or hosting instrument exists, and the binding Dubai rules are not published.

The strik­ing fact about pub­lic-sec­tor work­loads is that the state has largely de­clined to reg­u­late it­self by res­id­ency rule. Art­icle 2(2) of UAE Fed­eral De­cree-Law No. 45 of 2021 provides that the law shall not apply to, among other things, “Gov­ern­ment Data” and “Gov­ern­mental en­tit­ies which con­trol or pro­cess Per­sonal Data”. Gov­ern­ment data is ex­cluded as a cat­egory and gov­ern­ment en­tit­ies are sep­ar­ately ex­cluded as con­trol­lers and pro­cessors, so the cross-bor­der pro­vi­sions of the fed­eral per­sonal data re­gime do not reach a gov­ern­ment en­tity's host­ing de­cisions at all. The bound­ary is drawn at cor­por­ate form: Art­icle 1 defines an es­tab­lish­ment to in­clude “com­pan­ies wholly owned by the fed­eral or the local gov­ern­ment, or in which they are share­hold­ers”. State-owned com­pan­ies are in scope; gov­ern­ment en­tit­ies are not.

The law is­sued on 20 Septem­ber 2021 and comes into force on 2 Janu­ary 2022. Art­icle 28 re­quired the ex­ec­ut­ive reg­u­la­tions within six months of pro­mul­ga­tion, and Art­icle 29 starts the com­pli­ance clock for con­trol­lers and pro­cessors only from the date those reg­u­la­tions are is­sued. No primary evid­ence that they have been is­sued was found, and four primary in­dic­a­tions are con­sist­ent with non-is­su­ance, among them of­fi­cial guid­ance up­dated 4 Decem­ber 2025 still de­scrib­ing the fed­eral data reg­u­lator's func­tions in the fu­ture tense, and a reg­u­lator with no reach­able web­site. The po­s­i­tion is un­con­firmed either way rather than pos­it­ively es­tab­lished.

No federal instrument, and a strong negative

The fed­eral gov­ern­ment cloud is a plat­form, not a policy. The com­plete pub­lic­a­tions cata­logue of the UAE's di­gital gov­ern­ment au­thor­ity was enu­mer­ated across its own guidelines, strategies, policies, re­ports, laws and stand­ards fil­ters, run­ning to twenty titles, and it con­tains no cloud policy, cloud-first policy, cloud ad­op­tion stand­ard, data clas­si­fic­a­tion stand­ard or host­ing in­stru­ment. That is a strong primary neg­at­ive rather than an ab­sence of look­ing, be­cause the cata­logue in­cludes its own laws and stand­ards cat­egor­ies. What ex­ists in­stead is a fed­eral net­work de­scribed as a “Sov­er­eign Cloud”, with forty-six en­tit­ies stated to

Digital SovereigntyVolge Quarterly31 •

be­ne­fit from its cloud in­fra­struc­ture, el­even cent­ral ser­vices and a pub­lished avail­ab­il­ity tar­get of 99.9 per cent, and a ser­vice cata­logue at ver­sion 1.1 of Janu­ary 2025 of­fer­ing eight cloud ser­vices priced “Free” to fed­eral gov­ern­ment en­tit­ies.

A government that builds the sovereign cloud and sets an adoption target has chosen procurement over regulation.

Dubai's taxonomy is about disclosure, not place

Dubai le­gis­lates data and does not le­gis­late loc­a­tion. Law No. 26 of 2015 Reg­u­lat­ing Data Dis­sem­in­a­tion and Ex­change in the Emir­ate of Dubai came into force on pub­lic­a­tion, ap­plies to local and fed­eral gov­ern­ment en­tit­ies and to per­sons pro­du­cing or ex­chan­ging data re­lat­ing to the emir­ate “in­clud­ing Spe­cial De­vel­op­ment Zones and free zones, such as the Dubai In­ter­na­tional Fin­an­cial Centre”, and clas­si­fies data into “Open Data” and “Shared Data” under a Dubai Data Manual ad­op­ted in co­ordin­a­tion with the elec­tronic se­cur­ity centre. All twenty-one art­icles were read. The law con­tains no in-coun­try host­ing re­quire­ment, no res­id­ency clause, no loc­al­isa­tion pro­vi­sion and no ref­er­ence to cloud com­put­ing of any kind. Its tax­onomy gov­erns who may re­ceive data, not where it may sit.

Where a pen­alty power over gov­ern­ment data ex­ists, it is del­eg­ated and un­pub­lished. Art­icle 16 provides that a vi­ol­ator “will be pun­ished by the pen­al­ties and meas­ures pre­scribed by a res­ol­u­tion of the Chair­man of the Ex­ec­ut­ive Coun­cil”, and that res­ol­u­tion was not found. A res­id­ency rule could in prin­ciple live in the Dubai Data Manual, which was not re­triev­able. With the In­form­a­tion Se­cur­ity Reg­u­la­tion avail­able only on email re­quest, the hon­est find­ing for Dubai is that the po­s­i­tion can­not be de­term­ined from pub­lic sources.

Targets in place of instruments

Abu Dhabi has gone fur­thest in com­mit­ment and no dis­tance at all in in­stru­ment. Its De­part­ment of Gov­ern­ment En­able­ment, es­tab­lished under Law No. (14) of 2023, an­nounced a Gov­ern­ment Di­gital Strategy 2025 to 2027 de­ploy­ing “AED13 bil­lion” and aim­ing “to achieve 100% ad­op­tion of sov­er­eign cloud com­put­ing for gov­ern­ment op­er­a­tions”. That is the strongest sov­er­eign-cloud com­mit­ment of any UAE jur­is­dic­tion and it is a strategy tar­get in a press re­lease. The de­part­ment's com­plete pub­lished legal in­vent­ory con­tains three laws and two policies, and no in­form­a­tion

se­cur­ity stand­ard, data clas­si­fic­a­tion policy, cloud policy or host­ing re­quire­ment.

Saudi Ar­a­bia binds its gov­ern­ment dif­fer­ently, through cy­ber­se­cur­ity con­trols rather than data law. The Cloud Cy­ber­se­cur­ity Con­trols apply to “any gov­ern­ment agency in the King­dom of Saudi Ar­a­bia in­side or out­side the King­dom in­clud­ing min­is­tries, au­thor­it­ies, es­tab­lish­ments and other en­tit­ies and their com­pan­ies and sub-en­tit­ies” as a cloud ser­vice ten­ant, and re­quire “Con­tinu­ous com­pli­ance with all laws, reg­u­la­tions, in­struc­tions, de­cisions, reg­u­lat­ory frame­works and con­trols, and man­dates re­gard­ing cy­ber­se­cur­ity in the King­dom”. The sanc­tion is non-com­pli­ance as­sessed by the reg­u­lator, not a fine in the in­stru­ment. A re­por­ted Cloud First Policy of around Oc­to­ber 2021 could not be loc­ated or dated and is not re­lied on.

Kuwait is the clearest and the most mis­described. Its Data Clas­si­fic­a­tion Policy, ver­sion 2.3, sets four tiers from “Pub­lic Data” to “Highly Sens­it­ive Data” and im­poses no ob­lig­a­tion that any tier be stored in­side Kuwait. What the tiers trig­ger is en­cryp­tion in trans­mis­sion, cata­loguing and re­port­ing: the reg­u­lator is to ob­tain “The doc­u­ments that show the loc­a­tions of stored data ac­cord­ing to clas­si­fic­a­tion tiers”. Stor­age loc­a­tion is re­por­ted and audited, not pro­hib­ited. The on­shore ele­ment sits in a sep­ar­ate in­stru­ment con­di­tion­ing a pro­vider's li­cence on host­ing the two most sens­it­ive tiers in Kuwait.

Bahrain's re­por­ted Cloud First Policy of April 2017 could not be con­firmed, and a widely re­peated claim that sev­enty per cent of the sys­tems of sev­enty-two gov­ern­ment agen­cies mi­grated to one hy­per­scaler within three years could not be veri­fied as to fig­ure, speaker, date or venue. It should not be used. Oman's min­istry pub­lishes the titles “Cloud and Host­ing Ser­vices Stand­ard” and “Cloud Gov­ernance Frame­work” in its own lib­rary index; their con­tent and status were not ob­tained.

The takeaway is that gov­ern­ment is the only sec­tor where the reg­u­lator and the reg­u­lated are the same party, and the Gulf has re­solved that by build­ing rather than bind­ing. No pub­lished pen­alty, en­force­ment ac­tion or named ad­verse find­ing against any Gulf gov­ern­ment en­tity for a host­ing or pub­lic-sec­tor data breach was loc­ated. The dis­cip­line is policy, frame­work com­pli­ance, audit, re­port­ing and plat­form li­cens­ing. For a com­mer­cial buyer the prac­tical con­sequence is the re­verse of what the rhet­oric sug­gests: the en­force­able choke­point is up­stream, in pro­vider au­thor­isa­tion and plat­form re­gis­tra­tion, and it binds the sup­plier rather than the min­istry.

The same frame­work also pro­hib­its dir­ectly, which makes Kuwait the only Gulf state with both levers in one in­stru­ment. Clause 4.2.1.1 re­quires sub­scribers to en­sure noth­ing is hos­ted or stored out­side Kuwait “for any pur­pose, or in any format, whether tem­por­ar­ily or per­man­ently” where the data falls in the third or fourth

Digital SovereigntyVolge Quarterly32 •

tier, or is per­sonal data of in­di­vidu­als held by gov­ern­ment bod­ies, private com­pan­ies or ser­vice pro­viders. Clause 4.2.1.3 re­quires pro­viders to dis­close to the reg­u­lator the loc­a­tions of their in-coun­try data centres and the coun­tries of any data centres used to pro­cess or trans­fer Kuwaiti sub­scribers' con­tent.

Telecommunications: the only sector where the regulator licenses the host

Telecoms is distinctive because the sector regulator licenses the cloud provider as well as regulating the operator's data. Kuwait's framework is the clearest residency instrument in the Gulf, Saudi Arabia runs class licensing, and the UAE's position cannot be established from published sources.

Tele­com­mu­nic­a­tions in­verts the logic of every other sec­tor in this part. Else­where the ob­lig­a­tion at­taches to the reg­u­lated en­tity and asks where it may put its data. In tele­coms it at­taches up­stream, to who­ever wishes to sell host­ing at all, and the lever is a li­cence rather than a pro­hib­i­tion. Kuwait states this most plainly. Clause 2.4 of its Cloud Com­put­ing Reg­u­lat­ory Frame­work, ver­sion 2.4, provides that the Au­thor­ity li­censes cloud ser­vice pro­viders host­ing third-tier and fourth-tier data who have data centres in­side Kuwait, and clause 2.1 con­fines con­tract­ing for pub­lic-sec­tor cloud ser­vices to those li­censed by the Au­thor­ity with a data centre and in­fra­struc­ture in­side the coun­try. The res­id­ency out­come is achieved by con­trolling the seller.

One pro­vi­sion goes bey­ond loc­a­tion and de­serves at­ten­tion. Clause 4.3.3 pro­hib­its a pro­vider com­ply­ing with a for­eign jur­is­dic­tion's laws from hand­ing sub­scriber con­tent to any third party in­clud­ing “a local or for­eign gov­ern­ment, or pub­lic au­thor­it­ies”, with dis­clos­ure per­mit­ted only on of­fi­cial re­quest from Kuwaiti au­thor­it­ies under Kuwaiti law. That is a block­ing pro­vi­sion, not a res­id­ency pro­vi­sion, and it de­cides whether an in-coun­try re­gion ac­tu­ally an­swers the sov­er­eignty ques­tion. The frame­work enters into force thirty days after gaz­ette pub­lic­a­tion; that date was not re­trieved, so the com­mence­ment date can­not be stated.

The residency outcome is achieved by controlling the seller, not by forbidding the buyer.

Saudi Arabia licenses by class, and the sharper gate is commercial

Saudi Ar­a­bia runs a class li­cens­ing re­gime for cloud, ad­min­istered by the Com­mu­nic­a­tions, Space and Tech­no­logy Com­mis­sion rather than by the cy­ber­se­cur­ity au­thor­ity. The clearest pub­lished ac­count comes from a hy­per­scaler's own tech­nical doc­u­ment­a­tion, which re­cords that the Com­mis­sion “has gran­ted a Class C li­cense (cov­er­ing Qual­i­fy­ing, Class A, B, and C

li­censes)” to its Dammam re­gion, and that “the qual­i­fic­a­tion is based on an as­sess­ment by the Na­tional Cy­ber­se­cur­ity Agency (NCA) against the NCA's Es­sen­tial Cy­ber­se­cur­ity Con­trols (ECC) and the Cloud Cy­ber­se­cur­ity Con­trols (CCC)”. The ar­chi­tec­ture is a tele­coms li­cence whose con­di­tions are set by cy­ber­se­cur­ity con­trols, which is why the de­leted loc­al­isa­tion sub­con­trols dis­cussed earlier mat­ter here too.

That ac­count is primary to the pro­vider and sec­ond­ary as to the frame­work. The Com­mis­sion's own li­cens­ing re­gister is cli­ent-rendered and re­turned no res­ults when re­trieved on 10 Novem­ber 2026, and the Cloud Com­put­ing Reg­u­lat­ory Frame­work it­self was not ob­tained. The class struc­ture is re­por­ted at the strength stated and the op­er­at­ive word­ing of each class is not es­tab­lished. Vendor claims about Gulf cloud li­cence classes are among the least re­li­able ma­ter­ial in this field and should be checked against the re­gister be­fore they are re­lied on.

The sharper Saudi gate is com­mer­cial rather than reg­u­lat­ory. The same doc­u­ment­a­tion re­cords that ac­cess to ser­vices from the Dammam re­gion “is avail­able only to KSA-based cus­tom­ers that have signed up to pur­chase cloud ser­vices through CNTXT”, and that cus­tom­ers with a Saudi billing ad­dress “are re­quired to pur­chase Google Cloud ser­vices for the Dammam me-central2 re­gion or any other Google Cloud re­gion” through that re­seller. A Saudi buyer's route to that pro­vider is a single in­ter­me­di­ary, for every re­gion and not merely the in-King­dom one. On 3 Novem­ber 2026 that re­seller was fol­ded into the sov­er­eign fund's ar­ti­fi­cial in­tel­li­gence vehicle. Res­id­ency achieved by ex­clus­ive dis­tri­bu­tion is a dif­fer­ent risk from res­id­ency achieved by stat­ute, and it con­cen­trates rather than di­ver­si­fies.

Qatar recommends, the UAE cannot be read

Qatar's tele­coms reg­u­lator pub­lishes a Cloud Policy Frame­work dated 7 June 2022, de­scrib­ing it in its own words as de­fin­ing “a com­pre­hens­ive set of policy and reg­u­lat­ory re­com­mend­a­tions” and es­tab­lish­ing “a cloud-friendly en­vir­on­ment for for­eign and do­mestic in­vest­ments in data centres and cloud ser­vices”. On that de­scrip­tion it is a policy frame­work, not a li­cens­ing re­gime, and no cloud ser­vice pro­vider li­cence or re­gis­tra­tion cat­egory ap­pears in the reg­u­lator's pub­lished li­cens­ing nav­ig­a­tion. The doc­u­ment sits be­hind a chal­lenge gate and any res­id­ency clause in it is un­veri­fied. The ab­sence of a li­cence cat­egory is an ab­sence-of-evid­ence read­ing from a nav­ig­a­tion tree, not a con­firmed neg­at­ive.

Digital SovereigntyVolge Quarterly33 •

The United Arab Emir­ates is the sig­ni­fic­ant gap, and it should be re­por­ted as one rather than filled. The na­tional in­form­a­tion portal re­cords that the tele­com­mu­nic­a­tions reg­u­lator “de­veloped the ‘UAE In­form­a­tion As­sur­ance Reg­u­la­tion’” and “will des­ig­nate the crit­ical en­tit­ies as per the UAE CIIP Policy to im­ple­ment the IA Reg­u­la­tion”, ap­ply­ing its re­quire­ments “to the use, pro­cessing, stor­age and trans­mis­sion of in­form­a­tion or data”. That is a scope clause, not a loc­a­tion clause: it says the con­trols apply to stor­age, not where stor­age must be. The reg­u­la­tion, its date and any res­id­ency pro­vi­sion could not be ob­tained, the reg­u­lator do­main re­turn­ing empty bod­ies. A widely re­peated claim that UAE policy re­quires in­ter­net-of-things data to be held in coun­try is un­veri­fied.

The operator has become the compliance product

What the sec­tor sells is more re­veal­ing than what it is told. Gulf op­er­at­ors have be­come the hosts of re­cord for sov­er­eignty-con­strained work­loads. A Saudi op­er­ator sub­si­di­ary hosts one hy­per­scaler's Riy­adh re­gion, launched in Oc­to­ber 2024 as part of a stated USD 1.5 bil­lion in­vest­ment. A sep­ar­ate Saudi cloud com­pany, launched on 5 June 2022, is held by that op­er­ator at 55 per cent along­side a hy­per­scaler at 10 per cent, with cap­ital of SAR 894 mil­lion. In the UAE an op­er­ator joint ven­ture sup­plies the data centre ca­pa­city be­hind one hy­per­scaler's ex­pan­sion, and in Feb­ru­ary 2024 an­other op­er­ator an­nounced work with a hy­per­scaler to es­tab­lish sov­er­eign cloud cap­ab­il­it­ies “to meet the data res­id­ency and se­cur­ity re­quire­ments im­posed on gov­ern­ment en­tit­ies and reg­u­lated in­dus­tries in the UAE”.

En­force­ment can­not be char­ac­ter­ised. The only pub­lished tele­coms pen­alty loc­ated is a sanc­tion of 3.5 mil­lion Qatari riy­als on Oore­doo Qatar by the reg­u­lator's Fin­an­cial Sanc­tions Com­mit­tee for “Vi­ol­at­ing In­struc­tions Is­sued by the CRA”. The de­cision was not opened, so whether it touches data, host­ing or cloud is un­known, and it must not be called a data pen­alty. The Saudi, Emir­ati and Kuwaiti en­force­ment re­gisters were not reached, so the neg­at­ive find­ing other sec­tors sup­port can­not be stated here.

The takeaway is that tele­coms is where Gulf sov­er­eignty is be­com­ing a product rather than a rule. In four of the six states the op­er­ator is sim­ul­tan­eously the reg­u­lated en­tity, the li­censed host, the sov­er­eign-cloud vehicle and, in­creas­ingly, the only route to a hy­per­scaler. A buyer eval­u­at­ing a tele­coms-hos­ted sov­er­eign offer should there­fore ask the li­cence ques­tion rather than the res­id­ency ques­tion: which class of li­cence the pro­vider holds, what it was as­sessed

against, whether the pur­chase route is ex­clus­ive, and whether the con­tract car­ries a block­ing pro­vi­sion of the Kuwaiti kind. Res­id­ency without a block­ing pro­vi­sion an­swers where the data sits and not who can com­pel it.

Aviation, logistics and ports: the sector with no rule, and why that is the risk

No Gulf aviation regulator and no Gulf port authority has published a data hosting or residency instrument. The international layer legislates where data must be sent, never where it must reside. The absence of a sectoral middle layer is the finding.

This is the sec­tor in which the hon­est an­swer is that there is no sec­tor-spe­cific ob­lig­a­tion, and it is es­tab­lished rather than as­sumed. Across every Gulf avi­ation in­stru­ment read in full and every re­gister read in full, there is no avi­ation-sec­tor or port-sec­tor data host­ing or res­id­ency pro­vi­sion of any kind. Qatar's com­plete pub­lished avi­ation-laws tax­onomy con­tains no in­form­a­tion-se­cur­ity, cy­ber­se­cur­ity or data cat­egory, and its Civil Avi­ation Se­cur­ity Reg­u­la­tions 2019 were re­trieved in full and searched: the terms “cyber”, “per­sonal data”, “pas­sen­ger data” and “Ad­vance Pas­sen­ger” do not ap­pear. Oman's com­plete list of civil avi­ation reg­u­la­tions con­tains no title men­tion­ing cyber or in­form­a­tion se­cur­ity. The Saudi cloud con­trols con­tain no oc­cur­rence of “avi­ation”, “air­port” or “air trans­port”.

The international layer legislates transfer, not location

The dis­tinc­tion a buyer most needs here is between a duty to send data and a duty to hold it some­where, and on the re­trieved in­stru­ments that dis­tinc­tion holds without ex­cep­tion. Annex 9 to the Chicago Con­ven­tion ob­liges con­tract­ing states to cre­ate a pas­sen­ger data single win­dow, to es­tab­lish an ad­vance pas­sen­ger in­form­a­tion sys­tem, to sup­port it “by ap­pro­pri­ate legal au­thor­ity” and to con­fine data ele­ments to the stand­ard mes­sage format. Its only loc­a­tional lan­guage is a trans­mis­sion des­tin­a­tion: the ex­plan­at­ory note re­cords that “this in­form­a­tion is elec­tron­ic­ally trans­mit­ted to the bor­der con­trol agen­cies in the des­tin­a­tion or de­par­ture coun­try”. Noth­ing in it ad­dresses where the data then rests.

The push model is a transfer obligation, not a hosting obligation, and the Gulf has added nothing to it.
Digital SovereigntyVolge Quarterly34 •

United Na­tions Se­cur­ity Coun­cil Res­ol­u­tion 2396 of 2017, ad­op­ted under Chapter VII, is to the same ef­fect. Para­graph 11 de­cides that “Mem­ber States shall re­quire air­lines op­er­at­ing in their ter­rit­or­ies to provide API to the ap­pro­pri­ate na­tional au­thor­it­ies”, and para­graph 12 that states “shall de­velop the cap­ab­il­ity to col­lect, pro­cess and ana­lyse” pas­sen­ger name re­cord data. These are col­lec­tion, pro­vi­sion, ana­lysis and shar­ing du­ties; ter­rit­ory ap­pears only as the trig­ger identi­fy­ing which flights are caught. The civil avi­ation cyber res­ol­u­tion chain runs four deep from 2016 to the cur­rent text ad­op­ted in 2025, and the 2019 res­ol­u­tion was re­trieved in full: it con­tains no ref­er­ence whatever to loc­al­isa­tion, res­id­ency or the ter­rit­orial loc­a­tion of sys­tems or data.

Maritime: a recommendation, widely sold as a mandate

The mari­time po­s­i­tion is the same and is more often mis­described. The In­ter­na­tional Mari­time Or­gan­iz­a­tion res­ol­u­tion on mari­time cyber risk man­age­ment in safety man­age­ment sys­tems, ad­op­ted on 16 June 2017, was re­trieved in full. It is four op­er­at­ive para­graphs. Its verb is “ENCOURAGES” and its ad­dressee is ad­min­is­tra­tions, mean­ing flag states, not shipown­ers: it en­cour­ages them “to en­sure that cyber risks are ap­pro­pri­ately ad­dressed in safety man­age­ment sys­tems no later than the first an­nual veri­fic­a­tion of the com­pany's Doc­u­ment of Com­pli­ance after 1 Janu­ary 2021”. It works through the safety man­age­ment code and flag-state veri­fic­a­tion. It con­tains no ref­er­ence to data loc­a­tion, res­id­ency, host­ing, cloud, serv­ers, jur­is­dic­tion, cross-bor­der trans­fer or stor­age. Vendor ma­ter­ial routinely presents it as a man­dat­ory cyber rule bind­ing op­er­at­ors dir­ectly, and that is wrong on the text.

The ac­com­pa­ny­ing guidelines, of 5 July 2017 and as re­vised on 7 June 2022, were both re­trieved in full. They state in terms that “these Guidelines are re­com­mend­at­ory”, set out five func­tional ele­ments and list eight classes of vul­ner­able ship­board sys­tem. Neither ver­sion men­tions host­ing, res­id­ency, data loc­a­tion, cloud or server loc­a­tion. The man­dat­ory port fa­cil­ity se­cur­ity code, in force since 1 July 2004, pred­ates the ques­tion: the word “cyber” does not ap­pear in the or­gan­isa­tion's own au­thor­it­at­ive de­scrip­tion of it.

One premise com­monly stated in this field could not be veri­fied and should not be re­peated: that a man­dat­ory mari­time single win­dow took ef­fect on 1 Janu­ary 2024. What is veri­fied is that a man­dat­ory elec­tronic-ex­change duty on pub­lic au­thor­it­ies has ap­plied since 8 April 2019, and that the single win­dow it­self is framed as a re­com­men­ded prac­tice. The or­gan­isa­tion's own live page, re­trieved on 10 Novem­ber 2026, still de­scribes it that way and men­tions no 2024 man­dat­ory single win­dow. Either that page is stale or the in­stru­ment is not where it is usu­ally placed. The con­flict is un­re­con­ciled.

Three hon­est gaps. The Emir­ati civil avi­ation re­gisters are pop­u­lated by script and re­turned no re­cords, so no find­ing either way is avail­able, and the Saudi

avi­ation au­thor­ity's site could not be read. Ad­vance pas­sen­ger in­form­a­tion rules for all six states could not be ob­tained, so whether any Gulf re­gime re­quires such data to be held in coun­try rather than merely pushed is un­known. Cus­toms single win­dows, the most prom­ising un­tested place for a real trade-data host­ing ob­lig­a­tion, could not be reached at all, and no en­force­ment search was pos­sible.

The Gulf layer added nothing

Where a Gulf reg­u­lator does pub­lish some­thing, it gov­erns only it­self. The Saudi Trans­port Gen­eral Au­thor­ity, the mari­time reg­u­lator, pub­lishes a Cy­ber­se­cur­ity Gen­eral Policy last up­dated 16 Decem­ber 2024. Every one of its nine clauses has the Au­thor­ity it­self as the sub­ject, and none im­poses any duty on a port, a ter­minal op­er­ator, a ship­ping com­pany or a li­censee. It con­tains no data loc­a­tion, host­ing, res­id­ency or cloud pro­vi­sion. Its op­er­at­ive pointer is clause five, that the Au­thor­ity “com­plies with the reg­u­lat­ory, legal, and le­gis­lat­ive re­quire­ments is­sued by the Na­tional Cy­ber­se­cur­ity Au­thor­ity”: the sec­tor reg­u­lator de­fers up­ward. Clause six ad­opts an in­ter­na­tional in­form­a­tion se­cur­ity stand­ard by choice, the same vol­un­tary stand­ard the mari­time guidelines point to.

Port au­thor­it­ies pub­lish less still. Abu Dhabi Mari­time's full index of mar­ine no­tices and cir­cu­lars was re­trieved and searched for cyber, data, host­ing, pri­vacy and single win­dow, and no cir­cu­lar title men­tions any of them. The cor­por­ate sites of the Emir­ati and Omani port groups were re­trieved in full and searched: the only data-re­lated arte­fact in each is a cor­por­ate pri­vacy policy. The Kuwaiti ports au­thor­ity pub­lishes noth­ing of the kind at all, though its site car­ries a no­tice that it is under de­vel­op­ment. The Arab re­gional avi­ation body main­tains a stand­ing cy­ber­se­cur­ity work­ing group whose pub­lished-re­cords page re­turns “No re­cords”.

The takeaway is that this sec­tor's data gov­ernance is bor­rowed in both dir­ec­tions, up­ward from the na­tional cyber and data re­gime and side­ways from vol­un­tary in­ter­na­tional stand­ards, with noth­ing in between. For a buyer that is not re­as­sur­ance. A sec­tor with no sec­toral in­stru­ment has no sec­toral safe har­bour either, so the host­ing ques­tion is de­cided en­tirely by whichever gen­eral rule catches the en­tity: a crit­ical-in­fra­struc­ture des­ig­na­tion it can­not see, a gen­eral data pro­tec­tion law, or the terms of a bor­der or cus­toms sys­tem it does not con­trol. The ab­sence of a rule is why di­li­gence here is harder, not easier.

Rows re­cord what was es­tab­lished from re­trieved in­stru­ments. Qatar's bank­ing cloud po­s­i­tion, Kuwait's and Oman's bank­ing cloud rules, and the Emir­ati tele­coms as­sur­ance reg­u­la­tion could not be read and are marked as not es­tab­lished rather than as ab­sent. Entries read­ing “noth­ing” mean that the in­stru­ment named was re­trieved and con­tains no loc­a­tion re­quire­ment, not that no ob­lig­a­tion could ever arise.

Digital SovereigntyVolge Quarterly35 •

The six compared, and the test for placing any workload

Across the six sectors only two carry an instrument that names a place, and only one of those is a flat mandate. Everywhere else the binding question is not where the data sits but who must approve, who is designated, and who is permitted to sell the hosting.

What the com­par­ison shows is that sec­tor mat­ters less than the form the ob­lig­a­tion takes. Of the six sec­tors ex­amined, only fin­an­cial ser­vices and health­care are gov­erned by an in­stru­ment that names a ter­rit­ory, and of those only the Emir­ati bank­ing and health rules are flat man­dates. In the other four sec­tors the op­er­at­ive con­straint is pro­ced­ural rather than geo­graphic: an ap­proval that must pre­cede sig­na­ture, a des­ig­na­tion the en­tity can­not see, or a li­cence con­di­tion that binds the pro­vider rather than the buyer. A buyer who or­gan­ises di­li­gence around the ques­tion “must this data stay in coun­try” will there­fore get the wrong an­swer in two thirds of cases, be­cause in those cases the rule does not speak about coun­try at all.

SectorRegulator and instrumentWhat must stay in countryPrior approval
Banking and financial servicesCBUAE, Outsourcing Regulation for Banks C 14/2021, effective 15 July 2021. SAMA, Cyber Security Framework v1.0 of May 2017, s.3.4.3, and Rules on Outsourcing. CBB, Rulebook OM-2.1.7UAE: the Master System of Record and all Confidential Data. Saudi Arabia: cloud services, in principle, unless approved otherwise. Bahrain: nothingYes in the UAE and Saudi Arabia. In Saudi Arabia before the contract is signed. Bahrain carves cloud out and takes post-notification within five working days
HealthcareMOHAP and the health authorities, UAE Federal Law No. 2 of 2019, Art. 13, with MOHAP Resolution 51 of 2021. Elsewhere the general data law onlyUAE: health data related to services provided in the state, and a copy under several exemptions. Saudi Arabia, Qatar, Bahrain, Oman, Kuwait: nothingNo general approval to host. Qatar and Oman require a permit to process health data at all. UAE export needs an exemption and usually written patient consent
SectorRegulator and instrumentWhat must stay in countryPrior approval
Energy, oil and gas, utilitiesNo sector regulator instrument found. NCA, ECC-2:2024 and CCC-2:2024. CITRA, Cloud Computing Regulatory Framework v2.4. Oman, Royal Decree 64/2020Saudi Arabia: no cloud hosting rule since the 2024 deletion; managed security operations centres only. Kuwait: tiers three and four, and personal data. Oman: nothing, but see approvalKuwait licenses the provider. Oman requires Cyber Defence Centre approval before any sensitive data is stored or processed abroad. Dubai requires CSP certification to sell to government
Government and public servicesTDRA and the UAE Data Office, Federal Decree-Law No. 45 of 2021, Art. 2(2). DESC, ISR under Resolution 13 of 2012. NCA, CCC-2:2024. CITRA, Data Classification Policy v2.3Federal UAE: nothing, government data being excluded from the data law. Dubai: cannot be determined, the rules not being published. Kuwait: nothing under the classification policyNo approval regime found. The discipline is framework compliance, audit, reporting and platform registration, and it binds the provider more than the entity
TelecommunicationsCST, class licensing for cloud. CITRA, Cloud Computing Regulatory Framework v2.4. CRA, Cloud Policy Framework of 7 June 2022. TDRA, UAE Information Assurance RegulationKuwait: tiers three and four, and personal data, with no temporary exception. Saudi Arabia: not established from the framework itself. UAE and Qatar: not establishedYes, as a licence rather than a consent. Saudi Arabia grants class licences assessed against the NCA controls. Kuwait licenses providers holding the top two tiers. Qatar publishes recommendations, not a licence
Aviation, logistics and portsNo Gulf aviation regulator or port authority instrument found. ICAO Annex 9, UNSCR 2396, IMO Resolution MSC.428(98), MSC-FAL.1/Circ.3/Rev.2Nothing. No instrument retrieved imposes any storage or hosting location requirement at either the international or the Gulf layerNone on hosting. The duties are to transmit passenger data, to manage cyber risk in safety management systems, and to exchange port information electronically

What the table cannot show

Three things es­cape the grid, and each has de­cided a real ar­chi­tec­ture. The first is des­ig­na­tion. In four of the six sec­tors scope turns on whether the en­tity is crit­ical na­tional in­fra­struc­ture, and no Gulf state pub­lishes its

Digital SovereigntyVolge Quarterly36 •

roster. Dubai pub­lishes ten sec­tors and not the or­gan­isa­tions; Saudi Ar­a­bia defines the peri­meter func­tion­ally and leaves the en­tity to identify it­self; Oman holds the power on the face of its de­cree and pub­lishes no out­put. An ob­lig­a­tion whose ad­dressee is secret can­not be planned against from the in­stru­ment alone.

The second is that loc­a­tion and con­trol are dif­fer­ent ques­tions. Kuwait is the only state ex­amined whose cloud in­stru­ment con­tains a block­ing pro­vi­sion, pro­hib­it­ing a pro­vider from sur­ren­der­ing sub­scriber con­tent to “a local or for­eign gov­ern­ment, or pub­lic au­thor­it­ies” when com­ply­ing with for­eign law. Res­id­ency without such a clause an­swers where the data sits and not who can com­pel its pro­duc­tion, which is usu­ally the ques­tion the board was ac­tu­ally ask­ing.

The third is that the ob­lig­a­tion in­creas­ingly travels with the pur­chase route rather than the rule. A Saudi buyer of one hy­per­scaler's ser­vices must buy through a single ex­clus­ive in-King­dom re­seller for every re­gion, and that re­seller was ab­sorbed into a sov­er­eign fund vehicle on 3 Novem­ber 2026. Dubai makes cer­ti­fic­a­tion man­dat­ory for any pro­vider selling cloud to its gov­ern­ment and cer­ti­fies no hy­per­scaler, while cer­ti­fy­ing the state util­ity's own sub­si­di­ary. Sov­er­eignty de­livered by ex­clus­ive dis­tri­bu­tion con­cen­trates coun­ter­party risk at the mo­ment it re­solves jur­is­dic­tional risk.

An obligation whose addressee is secret cannot be planned against from the instrument alone.

The sequence that places a workload

The ques­tions below are ordered so that each an­swer nar­rows the next. It is to be noted that the order mat­ters: tak­ing them in any other se­quence pro­duces the fa­mil­iar error of ask­ing a host­ing ques­tion of a re­gime that does not reg­u­late host­ing.

  • What class of data does the work­load hold, in the terms the rel­ev­ant state uses? Saudi Ar­a­bia and Kuwait both clas­sify in four levels, and in both the level is a prop­erty of the data rather than of the pro­vider: in Saudi Ar­a­bia level one is top secret through to level four pub­lic, and in Kuwait the tiers run from pub­lic data to highly sens­it­ive data, with med­ical re­cords in the third tier. Clas­sify first, be­cause in those two states the clas­si­fic­a­tion se­lects the rule.
  • Which in­stru­ment catches it, and does that in­stru­ment name a place at all? Only the Emir­ati bank­ing and health rules and the Kuwaiti cloud frame­work name a ter­rit­ory. If the catch­ing in­stru­ment is a cy­ber­se­cur­ity con­trol set, a gov­ern­ment strategy, a gen­eral data pro­tec­tion law or an in­ter­na­tional con­ven­tion, the host­ing ques­tion is not ad­dressed and the next ques­tion be­comes the right one.
  • Is the re­quire­ment in-coun­try host­ing, or in-coun­try cus­tody of some­thing nar­rower? This is where most of the cost sits. The Emir­ati bank­ing rule re­quires the sys­tem of re­cord it­self, or for a for­eign branch a daily-up­dated copy. Sev­eral Emir­ati health ex­emp­tions per­mit law­ful ex­port while still re­quir­ing a copy to re­main. The sur­viv­ing Saudi loc­a­tion rules reach a se­cur­ity op­er­a­tions centre and the na­tion­al­ity of its staff, not the data.
  • Must an ap­proval pre­cede de­ploy­ment, and pre­cede what ex­actly? In Saudi Ar­a­bia the cloud ap­proval must be ob­tained be­fore the con­tract is signed, not be­fore go-live, and any over­seas out­sourcing needs a writ­ten non-ob­jec­tion sup­por­ted by a case for why the work can­not be done in the King­dom. In the UAE shar­ing con­fid­en­tial cus­tomer data abroad needs both reg­u­lat­ory ap­proval and writ­ten cus­tomer con­sent. In Bahrain cloud is carved out and post-no­ti­fic­a­tion within five work­ing days suf­fices.
  • Is the pro­vider per­mit­ted to serve this work­load, and by whom is it per­mit­ted? Kuwait li­censes pro­viders host­ing the top two tiers and re­quires in-coun­try data centres. Saudi Ar­a­bia grants cloud class li­cences as­sessed against its cy­ber­se­cur­ity con­trols. Dubai makes cer­ti­fic­a­tion man­dat­ory for any pro­vider selling to gov­ern­ment. In each case the choke­point is up­stream of the buyer.
  • Who can com­pel pro­duc­tion, and does the con­tract say so? Ask for the block­ing pro­vi­sion, the gov­ern­ment-ac­cess re­port­ing com­mit­ment, and the ter­min­a­tion and re­turn clauses. The Emir­ati bank­ing reg­u­lator may order an out­sourcing ar­range­ment ter­min­ated where it presents undue risk to con­fid­en­tial data, a sharper rem­edy than any fine in the re­gion.

Two cau­tions on using this se­quence. It re­solves the pub­lished po­s­i­tion and not the su­per­vis­ory one: in sev­eral states the op­er­at­ive rules are not pub­lic doc­u­ments, Dubai's in­form­a­tion se­cur­ity reg­u­la­tion and cloud pro­vider stand­ard being avail­able only on email re­quest, and the Saudi loc­al­isa­tion rules hav­ing been trans­ferred in 2024 to a body whose pub­lic­a­tions could not be re­trieved. And it re­solves ob­lig­a­tions, not prac­tice. Across all six sec­tors no pub­lished pen­alty ex­pressly groun­ded in host­ing, cloud or data res­id­ency was loc­ated any­where in the Gulf's reg­u­lated peri­meter.

Digital SovereigntyVolge Quarterly37 •

The takeaway for the edi­tion is that the Gulf's sov­er­eignty re­gime is not con­ver­ging on res­id­ency. It is con­ver­ging on au­thor­isa­tion. Two of the six sec­tors tell a buyer where to put the data; four tell them who must say yes first, or who is al­lowed to sell them the ca­pa­city. That is a more tract­able prob­lem than loc­al­isa­tion and a less com­fort­able one, be­cause an ap­proval can be with­held, a des­ig­na­tion can be made without no­tice, and an ex­clus­ive dis­tri­bu­tion route can be con­sol­id­ated into a state vehicle in a single week, as happened in Saudi Ar­a­bia at the start of this Novem­ber. The in­stru­ment is the easy part of the di­li­gence. The coun­ter­party is the hard part.

The year ahead: the Calls

A Call is a dated, falsifiable prediction with a stated confidence, written to be graded in the 2028 Scorecard. Ten Calls for GCC digital sovereignty in 2027: the heart of this edition.

The Calls: 2027, at a glance

Ten dated, falsifiable predictions for GCC digital sovereignty. Confidence is stated so that a contrarian medium-confidence Call and a high-confidence base case are read (and scored) differently.

  • Call 1: Clas­si­fic­a­tion-driven res­id­ency be­comes a de­fault RFP clause, High, Re­solves 2027
  • Call 2: SDAIA ad­equacy + SCCs be­come the de-facto GCC trans­fer mech­an­ism, Me­dium–High, Re­solves 2027
  • Call 3: A Saudi sov­er­eign model is rep­lic­ated in ≥2 other states, Me­dium, Re­solves 2027
  • Call 4: Star­gate UAE's first 200 MW goes live and sets the nar­rat­ive, Me­dium, Re­solves 2027
  • Call 5: US ex­port pos­ture stays the biggest swing factor, High, Re­solves 2027
  • Call 6: HYOK + con­fid­en­tial com­put­ing be­come top-tier stand­ard, Me­dium, Re­solves 2027
  • Call 7: Oman's en­forced PDPL trig­gers vis­ible com­pli­ance de­mand, Me­dium, Re­solves 2027
  • Call 8: A na­tional Ar­abic LLM enters a gov­ern­ment pro­duc­tion work­flow, Me­dium–High, Re­solves 2027
  • Call 9: Kuwait's hy­per­scaler re­gions stay com­mit­ted, not live, Me­dium, Re­solves 2027
  • Call 10: The 15–30% sov­er­eign premium per­sists, Me­dium, Re­solves 2027

Each Call draws on the sec­tor evid­ence in Part I and on Volge's Rules of the Game reg­u­lat­ory tracker. No Score­card ap­pears in Vol. I: the 2028 edi­tion grades these against the re­cord.

Con­fid­ence: High · Re­solves end-2027

Calls one to three

1. Classification-driven residency becomes a default RFP clause

By end-2027, clas­si­fic­a­tion-driven data res­id­ency (sov­er­eignty-by-design) is a de­fault clause in GCC gov­ern­ment cloud re­quests for pro­posal, spe­cify­ing a tier-to-host­ing map rather than a blanket loc­al­isa­tion rule.

The ar­chi­tec­ture is in place across all six re­gimes, each already routes host­ing through a clas­si­fic­a­tion tier, and the shift from man­date to ar­chi­tec­ture makes the clause the path of least res­ist­ance for a pro­cure­ment of­ficer. The mech­an­ism ex­ists; 2027 is when it be­comes boil­er­plate.

2. SDAIA adequacy and SCCs become the de-facto GCC transfer mechanism

Saudi Ar­a­bia's SDAIA ad­equacy list and stand­ard con­trac­tual clauses be­come the de-facto ref­er­ence mech­an­ism for GCC cross-bor­der trans­fers; no uni­fied GCC-wide trans­fer in­stru­ment emerges in 2027.

Con­fid­ence: Me­dium–High · Re­solves end-2027

The 2024 Data Trans­fer Reg­u­la­tion gives Saudi Ar­a­bia the re­gion's most com­plete trans­fer frame­work. SDAIA has since con­sul­ted, from 6 Oc­to­ber to 5 Novem­ber 2026, on draft amend­ments that would re­quire per­sonal data to be kept in the King­dom, so the Call is graded on the trans­fer re­gime's in­flu­ence sep­ar­ately from that pending loc­al­isa­tion duty. The smal­ler states lack the ca­pa­city to build their own; a single Gulf in­stru­ment would re­quire polit­ical con­ver­gence that is not on the 2027 agenda.

3. A Saudi sovereign hosting model is replicated in ≥2 other states

A Saudi-ap­proved sov­er­eign host­ing model (the Center3, HUMAIN or SDAIA tem­plate) is re­cog­nised or rep­lic­ated across at least two other GCC states by end-2027.

Con­fid­ence: Me­dium · Re­solves end-2027

Saudi scale makes its model the nat­ural ref­er­ence, and smal­ler states short of hy­per­scaler steel have reason to adopt rather than build. The con­fid­ence is me­dium be­cause na­tional pride and the Emir­ates' rival part­ner­ship model both cut against straight­for­ward rep­lic­a­tion.

The build is fun­ded, staffed and under con­struc­tion by Khazna, but the first phase was not live as at mid-Oc­to­ber 2026, Khazna now in­dic­ates a Q4 2026 go-live, and Septem­ber 2026 re­port­ing sug­gests re-plan­ning from one site into sev­eral. Con­fid­ence is cut ac­cord­ingly.

Digital SovereigntyVolge Quarterly38 •

De­liv­ery risk is real but the nar­rat­ive dom­in­ance is near-cer­tain given the scale and the back­ers.

Calls four to six

4. Stargate UAE's first 200 MW goes live and sets the 2027 narrative

Star­gate UAE's first 200 MW cluster goes live in 2026 and the sov­er­eign-cloud and sov­er­eign-AI nar­rat­ive it an­chors dom­in­ates GCC pro­cure­ment con­ver­sa­tions through 2027.

Con­fid­ence: Me­dium · Re­solves end-2027

5. US export posture stays the single biggest swing factor

United States ex­port-li­cence pos­ture re­mains the single biggest swing factor for GCC sov­er­eign-AI ca­pa­city through 2027, whether through fur­ther eas­ing or a China-di­ver­sion claw­back.

Con­fid­ence: High · Re­solves end-2027

The 2025-26 se­quence (Dif­fu­sion Rule, res­cis­sion, li­cence-by-li­cence, Coun­try Group A:5) shows the re­gion's ef­fect­ive com­pute ceil­ing mov­ing on Wash­ing­ton's de­cisions. The live vari­ables for 2027 are the 6 April 2027 ex­piry of Sup­ple­ment 8 eli­gib­il­ity for G42 and Core42, and Saudi Ar­a­bia's ex­clu­sion from Coun­try Group A:5. This also shows the ceil­ing mov­ing on Wash­ing­ton's de­cisions alone. No Gulf vari­able has com­par­able lever­age over ca­pa­city.

6. HYOK and confidential computing become top-tier standard

Hold-your-own-key or ex­ternal key man­age­ment, to­gether with con­fid­en­tial com­put­ing, be­come stand­ard re­quire­ments for GCC top-tier (Secret and L4) work­loads by end-2027.

Con­fid­ence: Me­dium · Re­solves end-2027

The con­trols are ma­ture and already spe­cified in the most ad­vanced tenders, and they are what allow top-tier work­loads to move to cloud without an air-gap. Con­fid­ence is me­dium be­cause stand­ard­isa­tion across six re­gimes at dif­fer­ing ma­tur­ity is un­even.

Calls seven and eight

7. Oman's fully-enforced PDPL triggers visible compliance demand

Oman's fully-en­forced PDPL (ef­fect­ive 5 Feb­ru­ary 2026) trig­gers vis­ible 2027 com­pli­ance and loc­al­isa­tion de­mand, and at least one other GCC state tight­ens its cross-bor­der trans­fer rules over the year.

Con­fid­ence: Me­dium · Re­solves end-2027

En­force­ment began on sched­ule, and Royal De­cree 68/2026 then widened the law from 7 Septem­ber 2026. The de­mand driver is now ex­tra­ter­rit­orial reach rather than the Feb­ru­ary cliff. A first fully-en­forced small-state re­gime typ­ic­ally pulls neigh­bours to­ward tighter rules. The second clause (an­other state tight­en­ing) is the source of the me­dium rat­ing.

8. A national Arabic LLM enters a government production workflow

At least one na­tional Ar­abic large lan­guage model (ALLaM, Fal­con, Jais or Fanar) is ad­op­ted into a named, non-pilot GCC gov­ern­ment pro­duc­tion work­flow with a pub­lic ref­er­ence, by end-2027. The Min­istry of Com­merce's use of HUMAIN's AI cloud from 1 Septem­ber 2026 does not by it­self sat­isfy this threshold.

Con­fid­ence: Me­dium–High · Re­solves end-2027

ALLaM already powers HUMAIN Chat, Mi­crosoft and HUMAIN an­nounced on 26 Au­gust 2026 an in­tent to offer it through Mi­crosoft Foundry, and the UAE Cab­inet set an ob­ject­ive in April 2026 to move half of fed­eral ser­vices to agen­tic AI within two years, so the threshold has been raised to keep the Call falsifi­able; the sov­er­eignty logic of a home-hos­ted model makes pro­duc­tion ad­op­tion a mat­ter of when, not whether. Con­fid­ence short of high re­flects the gap between pilot and pro­duc­tion.

Calls nine and ten

9. Kuwait's announced hyperscaler regions stay committed, not live

Kuwait's an­nounced Google Cloud and Mi­crosoft Azure re­gions re­main com­mit­ted-but-not-live into 2027, keep­ing the coun­try's sov­er­eignty telco- and NVIDIA-de­livered through Oore­doo and KISR.

Con­fid­ence: Me­dium · Re­solves end-2027

Both re­gions were an­nounced (2023 and 2025) without live dates, and Kuwait's grid and data-centre base is thin (AGBI, Feb 2026). The telco-de­livered stop­gap (Oore­doo's H200 site, KISR's ICARUS) is already the work­ing sov­er­eignty layer.

10. The 15–30% sovereign premium persists

The sov­er­eign premium (the 15–30% mark-up of sov­er­eign over pub­lic cloud) per­sists through 2027; sov­er­eignty re­mains a cost of Gulf data con­trol, not yet a sav­ing.

Con­fid­ence: Me­dium · Re­solves end-2027

The ten Calls are the firm's con­sidered judge­ments as of July 2026, each writ­ten to be graded against the pub­lic re­cord in the 2028 Score­card.

Digital SovereigntyVolge Quarterly39 •

The Call grades per­sist­ence rather than mag­nitude, the band hav­ing been re­stated to BCG's 15 to 30 per cent. The premium's sources, lower util­isa­tion, scarce vet­ted staff and added key and con­fid­en­tial-com­put­ing lay­ers, do not re­solve in a single year while the re­gions are still filling. Cheap power off­sets the build cost but not the buyer's premium.

How the Calls are made

A Call is not a forecast in the ordinary sense. It is a dated, falsifiable proposition with a stated confidence, constructed so that a reader can grade it a year later without recourse to the author.

Three dis­cip­lines gov­ern every Call. First, falsifi­ab­il­ity: each is writ­ten so that a clear real-world out­come would mark it right or wrong: 'a na­tional Ar­abic LLM enters a gov­ern­ment pro­duc­tion work­flow' can be checked; 'AI ad­op­tion grows' can­not. Second, dat­ing: every Call re­solves at a stated point, here end-2027, so that it can­not be quietly de­ferred. Third, cal­ib­rated con­fid­ence: a Call is rated High, Me­dium-High, Me­dium or Low, and the rat­ings are meant to be read as prob­ab­il­it­ies: a well-cal­ib­rated set of Me­dium Calls should be wrong about as often as it is right.

Evidence and confidence

Each Call is built from the sourced evid­ence in Part I (the mar­ket siz­ing, the reg­u­lat­ory cross­walk, the com­pute com­mit­ments) and from Volge's Rules of the Game reg­u­lat­ory tracker. Con­fid­ence re­flects two things: the strength of the mech­an­ism (is there a spe­cific, dated cause?) and the num­ber of in­de­pend­ent ways the Call could fail. Call 5, on United States ex­port pos­ture, is High be­cause the mech­an­ism is proven and sin­gu­lar; Call 3, on model rep­lic­a­tion, is Me­dium be­cause na­tional pride, rival mod­els and pro­cure­ment in­er­tia each offer a sep­ar­ate route to fail­ure.

A Call that cannot be graded against the record is an opinion, not a Call.

The con­fid­ence rat­ings are also a hedge against the au­thor. A High Call is a claim the firm ex­pects to be judged harshly on if it fails; a Me­dium Call sig­nals genu­ine un­cer­tainty and should not be scored as a miss with the same weight. The 2028 Score­card will grade the full set and, cru­cially, as­sess cal­ib­ra­tion (whether the Highs came in more often than the Me­di­ums) be­cause a fore­caster who is right half the time on Me­dium Calls is bet­ter cal­ib­rated than one who is right nine times in ten but rated them all High.

The standard

Volge Quarterly is gov­erned by Volge's Morph­eus stand­ard: con­clu­sion first, every fig­ure sourced and year-stamped, every Call dated and falsifi­able. The Calls are reasoned judge­ments, not guar­an­tees; and they are writ­ten to be marked.

HUMAIN went live on 1 September 2026 on NVIDIA HGX B300, with the Ministry of Commerce among its first customers. It is a $100bn bet that sovereignty and scale are the same project: national ownership of chips, data centres, a model and a cloud, bundled into one programme.

Na­tional mod­els of com­pute · Volge Quarterly 2027

By domain, and three scenarios

The year read from four angles (technology, markets, regulation and delivery) and resolved into bull, base and bear cases for GCC digital sovereignty in 2027.

Technology and markets

Read as technology, 2027 is the year the sovereign stack's upper layers mature while its foundation stays imported. Read as a market, it is the year sovereign capacity is bought at a premium the buyer can no longer avoid.

Technology

The tech­no­logy story is one of a stack matur­ing from the top down. Model layer, key-man­age­ment layer and con­fid­en­tial-com­put­ing layer are all reach­ing pro­duc­tion read­i­ness in-re­gion: na­tional LLMs move to­ward gov­ern­ment work­flows, hold-your-own-key schemes enter the most sens­it­ive tenders, and hard­ware en­claves (Intel TDX, AMD SEV-SNP, NVIDIA Con­fid­en­tial Com­put­ing) make top-tier cloud host­ing vi­able without an air-gap. The one layer that does not ma­ture in-re­gion is the sil­icon, which is fab­ric­ated, li­censed and rate-lim­ited abroad. The tech­nical fron­tier of 2027 is there­fore the trust bound­ary: how much sov­er­eignty can be en­gin­eered above a sup­ply chain the re­gion does not own.

Markets

The mar­ket story is one of ca­pa­city bought faster than it can be sup­plied. The Saudi cloud mar­ket grows from $15.4bn in 2025 to­ward $27.9bn by 2030, and the

Digital SovereigntyVolge Quarterly40 •

UAE's from $12.8bn to­ward $56.3bn by 2031 [Mordor, 2025]; Middle East live data-centre ca­pa­city rises from about 1.2 GW at end-2025 to 2.2 GW in 2026 and 3.2 GW in 2027, with the 14 GW an­nounced likely to de­liver closer to 5 GW by 2030 [Knight Frank, Data Centre Atlas 2026]; MEA coloca­tion grows from $3.3bn to­ward $12.9bn by 2031 [Ar­izton, 2025]. Against that de­mand, the con­straints bind: vet­ted staff are scarce, power is abund­ant but grid con­nec­tions are not every­where ready, and chips are capped. The sov­er­eign premium of 15–30% is the price of buy­ing into that sup­ply-con­strained mar­ket, and Call 10 holds that it per­sists.

The read

Tech­no­logy ma­tures above the sil­icon; the mar­ket pays a premium for ca­pa­city it can­not yet sup­ply at scale. Both point to the same 2027 dis­cip­line: clas­sify pre­cisely, so that neither the en­gin­eer­ing nor the spend ex­ceeds what the work­load's tier re­quires.

Regulation and delivery

Read as regulation, 2027 is the year enforcement catches up with legislation. Read as delivery, it is the year the gap between an announced region and a live one decides which states have sovereignty in fact.

Regulation

The reg­u­lat­ory story is en­force­ment, not new law. The stat­utes largely exist (Qatar since 2017, Bahrain since 2019, the Emir­ates and Saudi Ar­a­bia since 2021-22, Kuwait's reg­u­la­tion since 2024), and the pivotal 2027 event is Oman's PDPL be­com­ing fully en­force­able on 5 Feb­ru­ary 2026 and widened by Royal De­cree 68/2026 from 7 Septem­ber 2026, which adds ex­tra­ter­rit­orial reach, cuts the ex­emp­tions from ten to six and cre­ates a right to human re­view of auto­mated de­cisions, the re­gion's one hard cliff. Around it, breach-no­ti­fic­a­tion norms con­verge on 72 hours, Saudi Ar­a­bia's trans­fer re­gime be­comes the de-facto ref­er­ence (Call 2), and the Emir­ates' still-un­pub­lished fed­eral ex­ec­ut­ive reg­u­la­tions re­main the re­gion's largest single piece of un­fin­ished le­gis­lat­ive busi­ness. No uni­fied Gulf in­stru­ment ar­rives; con­ver­gence runs through clas­si­fic­a­tion, not stat­ute.

Delivery

The de­liv­ery story is the gap between an­nounce­ment and avail­ab­il­ity. Kuwait's Google and Mi­crosoft re­gions, an­nounced in 2023 and 2025, re­main not-live, so its sov­er­eignty is car­ried by Oore­doo and KISR (Call 9);

the Emir­ates' Star­gate first phase is a 2026 de­liv­ery test whose suc­cess sets the re­gional nar­rat­ive (Call 4). De­liv­ery is where the year sep­ar­ates states that have spe­cified sov­er­eignty from states that have built it; and the sep­ar­ator is not cap­ital, which is abund­ant, but hy­per­scaler steel, vet­ted staff and grid con­nec­tions, which are not.

The read

Reg­u­la­tion is con­ver­ging through en­force­ment and clas­si­fic­a­tion; de­liv­ery is di­ver­ging through the an­nounce-to-live gap. The states that close that gap in 2027 are the ones whose sov­er­eignty is more than a stat­ute.

Three scenarios for 2027

The year resolves along one dominant axis: United States export posture and the pace of sovereign-cloud delivery. Three scenarios bound the range.

Bull: the architecture delivers

Coun­try Group A:5 holds and eases fur­ther; Star­gate UAE's first 200 MW lands on sched­ule and a second phase is com­mit­ted; clas­si­fic­a­tion-driven res­id­ency be­comes stand­ard RFP lan­guage across all six states; a na­tional Ar­abic LLM reaches pro­duc­tion in gov­ern­ment. Sov­er­eign ca­pa­city scales, the premium be­gins to com­press at the mar­gin, and the Gulf con­sol­id­ates as the third pole of sov­er­eign AI after the United States and China. Calls 1, 4, 5 and 8 all re­solve firmly right.

Base: mandate becomes architecture, unevenly

The cent­ral case. Ex­port pos­ture stays broadly per­missive but re­mains the dom­in­ant vari­able; Star­gate's first phase lands with the ex­pec­ted slip­page; Saudi Ar­a­bia's trans­fer re­gime be­comes the de-facto ref­er­ence; Oman's en­force­ment bites; Kuwait's re­gions stay com­mit­ted-not-live; the 15–30% premium per­sists. Sov­er­eignty is spe­cified and largely de­livered by the two poles, im­pro­vised by the smal­ler states, and the clas­si­fic­a­tion switch be­comes the shared op­er­at­ing layer. Most Calls re­solve as rated.

Bear: the throttle tightens

A China-di­ver­sion claw­back re-im­poses li­cens­ing or re-tiers the Emir­ates; chip flows slow; Star­gate's first phase slips into 2027; grid and tal­ent con­straints bind harder than ex­pec­ted. Sov­er­eign-AI ca­pa­city stalls against a ceil­ing set abroad, the premium widens as scarcity deep­ens, and the de­pend­ence para­dox

Digital SovereigntyVolge Quarterly41 •

moves from a man­aged con­di­tion to an act­ive con­straint. Call 5 dom­in­ates the year, and Calls 4 and 8 re­solve late or wrong.

The year turns on one axis: the licence in Washington, and the steel in the ground.
Oman's PDPL becomes the Gulf's one hard 2027 cliff: fully enforceable from 5 February 2026. The rest of the region's sovereignty runs on choices; this one runs on a date.

By do­main · Volge Quarterly 2027

What to watch, and the record

What the year turns on, the signals worth tracking as it runs, and the reference annex: sources, standards and glossary behind every figure in this edition.

The watchlist

The signals that will seed next year's Calls. Each is a specific, observable event whose occurrence would move the 2028 read: watched here so that the 2028 edition can grade both the Calls and the conditions that shaped them.

SignalWhy it mattersWhat to watch
US export re-tieringSets the sovereign-AI ceiling (Call 5)Any change to UAE Country Group A:5 status; new licence conditions
Stargate UAE phase 2Confirms or slows the flagship build (Call 4)First 200 MW live date; second-phase commitment
UAE federal Exec RegsCloses the region's largest legislative gapPublication of PDPL executive regulations and grace-period trigger
Oman enforcement actionsTests the 5 Feb 2026 cliff (Call 7)First fines or transfer refusals under the enforced PDPL
Kuwait region go-liveWould falsify Call 9Google or Microsoft Kuwait region reaching general availability
National LLM in productionResolves Call 8ALLaM, Falcon, Jais or Fanar in a named government workflow
Sovereign premium dataTests Call 10Published or tendered sovereign-vs-public price differentials
Cross-border precedentTests Call 2SDAIA adequacy findings; any move toward a GCC-wide instrument

The watch­list is not a set of Calls; it is the field of sig­nals from which the 2028 Calls will be drawn and against which this year's will be graded.

The discipline

Each sig­nal is spe­cific and ob­serv­able, so that a year from now its oc­cur­rence or non-oc­cur­rence is a mat­ter of re­cord, not in­ter­pret­a­tion: the same stand­ard the Calls are held to.

Regulatory crosswalk

The full regulatory crosswalk behind this edition, by country, on the axes a hosting decision turns on. Every figure elsewhere in the edition traces to this table or to the numbered sources that follow.

StateLaw & dateBreachCross-border ruleMax penalty
Saudi ArabiaPDPL M/19 (2021) / M/148 (2023); enforced 14 Sep 202472hData Transfer Regulation 2024: adequacy / SCCs / BCRs. Draft amendments consulted 6 Oct to 5 Nov 2026 would add an in-Kingdom storage dutySAR 5m (10m repeat); +2yr & SAR 3m for sensitive misuse
UAE (federal)PDPL Decree-Law 45/2021; in force 2 Jan 2022; Exec Regs unpublished72h (de-facto)Adequacy-based; free zones separateSet by unpublished Regs
UAE (DIFC)DP Law 5/2020; 2025 amendment72hGDPR-aligned adequacy / SCCsPrivate right of action (2025)
UAE (ADGM)DP Regs 202172hGDPR-aligned; CommissionerTo $28m
QatarPDPPL Law 13/2016; in force 13 Feb 201772hAdequacy; QFC DP Regs 2021 separateQAR 1–5m (QFC to $1.5m)
KuwaitCITRA DPPR Res 42/2021 → 26/2024; in force 19 Feb 202472hAdequacy required; L3/L4 in-country (Res 112)Regulatory (CITRA)
BahrainPDPL Law 30/2018; in force 1 Aug 2019NotifyOpen host; Data Embassy Decree 56/2018BHD 1,000–20,000; to 1yr
OmanPDPL RD 6/2022; Exec Regs MD 34/2024; enforced 5 Feb 202672hSensitive transfers need CDC approvalTo RO 500,000 (Art 23)

Sources: na­tional stat­utes and reg­u­lator pub­lic­a­tions; Volge Rules of the Game tracker. Cur­rent to July 2026. The UAE ap­pears three times be­cause the fed­eral law and the DIFC and ADGM free-zone re­gimes are dis­tinct.

Reading the crosswalk

The de­cis­ive columns are the cross-bor­der rule and the clas­si­fic­a­tion note within it: they are what a tier-to-host­ing map is built on, and what sep­ar­ates the

Digital SovereigntyVolge Quarterly42 •

loc­al­isers (Saudi Ar­a­bia, Kuwait, Oman) from the open hosts (Bahrain, Qatar).

Sources

Numbered sources for the figures and claims in this edition. Where a live URL is available it is given; statutory instruments are cited by decree or law number and date.

  • 1. Mi­crosoft Source EMEA: Saudi Ar­a­bia East re­gion, cus­tomer avail­ab­il­ity tar­geted for Novem­ber 2026 across three avail­ab­il­ity zones; no launch-day ser­vice mat­rix pub­lished (Mi­crosoft, 31 Au­gust 2026).
  • 2. Mi­crosoft MEA: Saudi re­gion con­struc­tion com­plete on three sites, avail­ab­il­ity ex­pec­ted 2026 (2024).
  • 3. Mi­crosoft: $1.5bn in­vest­ment in Abu Dhabi's G42, with a Brad Smith board seat (2024).
  • 4. Mi­crosoft / DCD: Mi­crosoft and Core42 to build a sov­er­eign cloud and AI in­fra­struc­ture for Abu Dhabi (2025).
  • 5. Mi­crosoft: $15.2bn UAE in­vest­ment and a 200MW G42/Khazna data-centre ex­pan­sion (2025).
  • 6. AWS: Middle East (me-cent­ral-2) Saudi Ar­a­bia re­gion, a $5.3bn com­mit­ment (2024).
  • 7. AWS: Middle East (UAE) re­gion GA, ~$5bn planned by 2036 (2022).
  • 8. AWS: Middle East (Bahrain) re­gion, the first hy­per­scale re­gion in the ME (2019).
  • 9. Or­acle: first Middle East OCI Su­per­cluster in Abu Dhabi, 4,000+ Black­well GPUs (2025).
  • 10. Or­acle: $14bn AI and cloud in­vest­ment in Saudi Ar­a­bia over ten years (2025).
  • 11. Google Cloud: global loc­a­tions ref­er­ence (Doha and Dammam re­gions; no UAE re­gion).
  • 12. NVIDIA: HUMAIN part­ner­ship to build AI factor­ies, 18,000 GB300 and 500MW (2025).
  • 13. Re­u­ters: Saudi Ar­a­bia launches HUMAIN under the PIF, chaired by MBS (2025).
  • 14. AMD: $10bn HUMAIN col­lab­or­a­tion de­liv­er­ing 500MW of AI com­pute (2025).
  • 15. OpenAI: In­tro­du­cing Star­gate UAE, a 1GW cluster within a 5GW cam­pus (2025).
  • 16. G42: US ap­proval for ad­vanced AI-chip ex­ports under an RTE frame­work (2025).
  • 17. Tom's Hard­ware: US li­cense to ship 500,000 Black­well GPUs a year to the UAE (2025).
  • 18. The Eco­nomic Times / Re­u­ters: US eases AI-chip ex­ports to the UAE under Coun­try Group A:5 (2026). AWS has since dated its Saudi re­gion to Decem­ber 2026, with the sep­ar­ate HUMAIN AI Zone pushed to 2028 (AWS, Septem­ber 2026).
  • 19. TII: Fal­con LLM fam­ily (Fal­con-H1 and Fal­con Ar­abic).
  • 20. Ar­izton / GlobeNewswire: GCC data-centre coloca­tion mar­ket reach­ing US$9.49bn by 2030 (2025).
  • 21. Knight Frank: Global Data Centres Re­port 2025 (Middle East live IT ca­pa­city, MW).
  • 22. Mordor In­tel­li­gence: KSA and UAE cloud-com­put­ing mar­ket siz­ing.
  • 23. SDAIA: Per­sonal Data Pro­tec­tion over­view (Saudi PDPL, SDAIA/NDMO frame­work).
  • 24. Saudi Bur­eau of Ex­perts: PDPL, Royal De­cree M/19.
  • 25. u.ae: UAE data-pro­tec­tion laws (Fed­eral De­cree-Law 45/2021).
  • 26. DLA Piper: UAE and GCC data-pro­tec­tion law sum­mar­ies.
  • 27. NCSA Qatar: Per­sonal Data Pri­vacy Pro­tec­tion Law.
  • 28. CITRA Kuwait: Cloud Com­put­ing Reg­u­lat­ory Frame­work (four tiers).
  • 29. Bahrain: Provid­ing Cloud Com­put­ing Ser­vices to For­eign Parties (Data Em­bassy, De­cree 56/2018).
  • 30. Al Tamimi. "Dip­lo­matic im­munity for data: Bahrain's Data Em­bassy Law".
  • 31. CMS: Oman PDPL en­ter­ing the en­force­ment phase (2026).
  • 32. Core42: Sov­er­eign Pub­lic Cloud (In­sight, 200+ con­trols on Azure).
  • 33. Khazna Data Cen­ters: 673MW port­fo­lio, tar­get­ing over 1GW of ca­pa­city by 2030.
  • 34. PwC: Po­ten­tial im­pact of AI in the Middle East (~$320bn by 2030).
  • 35. Cush­man & Wake­field: Abu Dhabi and Dubai take top global data-centre growth rank­ings (2025).
  • 36. SemiAnalysis. AI ar­rives in the Middle East: the US strikes a deal with the UAE and KSA (2025).

All fig­ures were re­freshed to Novem­ber 2026 and are year-stamped at point of use. Stat­utory cita­tions are to the in­stru­ment as amended. This edi­tion is not in­vest­ment ad­vice.

Digital SovereigntyVolge Quarterly43 •

Glossary and method

The working vocabulary of Gulf digital sovereignty, defined as used in this edition.

  • Data clas­si­fic­a­tion. A scheme sort­ing data into sens­it­iv­ity tiers (e.g. Qatar C0–C4), each mapped to a per­mit­ted host­ing model. The switch of this edi­tion.
  • Data res­id­ency. A re­quire­ment that data be phys­ic­ally stored within a defined jur­is­dic­tion.
  • Loc­al­iser. A state (Saudi Ar­a­bia, Kuwait, Oman) that re­quires sens­it­ive or gov­ern­ment data to re­main in-coun­try.
  • Open host. A state (Bahrain, Qatar) that in­vites for­eign data onto its soil, in Bahrain's case under the cus­tomer's home law.
  • Data em­bassy. Bahrain's De­cree 56/2018 ar­range­ment: for­eign data on Bahraini soil gov­erned by the cus­tomer's home law, bey­ond local au­thor­ity ac­cess.
  • Sov­er­eign cloud. A cloud re­gion op­er­ated to na­tional re­quire­ments (res­id­ency plus vet­ted local op­er­a­tion and cus­tomer key con­trol).
  • BYOK / HYOK. Bring-your-own-key / hold-your-own-key: schemes giv­ing the cus­tomer con­trol of en­cryp­tion keys; under HYOK the op­er­ator never holds them.
  • Con­fid­en­tial com­put­ing. Hard­ware-isol­ated pro­cessing of data in use, via Intel TDX, AMD SEV-SNP or NVIDIA Con­fid­en­tial Com­put­ing.
  • Air-gap. A net­work phys­ic­ally dis­con­nec­ted from ex­ternal net­works, re­served for the top clas­si­fic­a­tion tier.
  • Sov­er­eign premium. The es­tim­ated 15–30% cost of sov­er­eign over pub­lic cloud.
  • Coun­try Group A:5. The US ex­port-con­trol des­ig­na­tion mak­ing ad­vanced-chip flows to a named state li­cence-free.
  • Na­tional LLM. A large lan­guage model trained and hos­ted in-re­gion: ALLaM (KSA), Fal­con & Jais (UAE), Fanar (Qatar).
  • The Call. A dated, falsifi­able pre­dic­tion with a stated con­fid­ence, writ­ten to be graded in the fol­low­ing year's Score­card.
  • Morph­eus stand­ard. Volge's house dis­cip­line: con­clu­sion first, every fig­ure sourced and year-stamped, every Call dated and falsifi­able.

Method note

Fig­ures are re­con­ciled across in­de­pend­ent sources; where sources dis­agree on scope, a range is given rather than a false point es­tim­ate. All data was cur­rent to July 2026 and is year-stamped at point of use. The Calls are the firm's reasoned judge­ments, not guar­an­tees, and are writ­ten to be graded against the pub­lic re­cord.

Digital SovereigntyVolge Quarterly44 •
Digital Sovereignty

Classification is the switch. Every Gulf regime, localiser or open host, routes the same question (what tier is this data) to the same three answers: public region, sovereign region, or air-gap.

Version · VSP-OTG-005 · 2026
volgePublished
every quarter
About Volge Quarterly

Volge Quarterly is Volge's signature series, published every quarter for enterprise customers. Each edition takes one subject, sets out where it currently stands on the published record, and makes a set of dated, falsifiable judgements on where it is going, written to give a buyer something firmer than a forecast: every figure carries its source and its date, every judgement carries the date on which it resolves, and the following year's edition grades each one hit, missed or partial.

Where a figure is not published, the edition says so rather than estimating it. Where published sources disagree, both are given and the disagreement is stated rather than averaged away. A number that does not survive checking is corrected here rather than repeated.

The edition carries no recommendation of any supplier and no offer of service. Where a vendor, platform or deployment is named it is because it is part of the published record of the subject.

Terms of use

This edition may be shared freely. It may not be altered or republished without permission, and figures carry their stated basis and date. Names and marks appearing in it are the property of their respective owners.