The question arrives mid-procurement, usually from a buyer's security team: where, exactly, will this run? For Saudi government-linked and regulated buyers the acceptable answer is increasingly an in-Kingdom region operated by a CST-registered provider. Here is what exists, what is only announced, and how each region is bought — the purchase route is where most vendors are caught out. Facts checked 30 Aug 2026; every claim links to a first-party source.
The live regions
Google Cloud — Dammam (me-central2). Live since November 2023 with three zones. The purchase route is the surprise: for KSA-billed customers, the region is sold only through CNTXT, Google's designated route. If your billing address is outside the Kingdom you may buy from Google or a partner, but Dammam access is tied to invoiced billing. (Google's Dammam access documentation)
Oracle Cloud — Jeddah (me-jeddah-1) and Riyadh (me-riyadh-1). Jeddah since 2020; Riyadh since 2024, delivered with center3/stc. Note each region has a single availability domain — that shapes your resilience architecture. (Oracle Riyadh region)
Alibaba Cloud — Riyadh, via sccc. Live since June 2022 with two availability zones. You buy from sccc — the Saudi Cloud Computing Company, a joint venture of Alibaba Cloud, stc, and Saudi partners — which localises over 90 Alibaba Cloud products. (Saudi Press Agency, sccc.sa)
Huawei Cloud — Riyadh. Live, and notable for publishing its CST Class C registration, the class covering government-sector data. (Huawei's KSA Class C page)
SITE Cloud — Riyadh RD1 and Jeddah JD1. The Saudi Information Technology Company's sovereign-cloud offering, government-linked, with dedicated-region options. (SITE Cloud regions)
The national providers. stc/Solutions, Mobily, Zain, Salam, NourNet, Detasad and others hold CST registrations and operate in-Kingdom infrastructure. CST publishes the authoritative register — ask any provider for its current class in writing. (CST registered providers)
The two everyone asks about
AWS: announced, not launched. AWS's own infrastructure page lists Bahrain and the UAE (me-central-1) as its live Middle East regions, with Saudi regions among announced plans. Third-party pages have claimed Saudi launch dates; AWS’s own page contradicts them and is the authoritative source. What exists in-Kingdom today: Outposts, Direct Connect, and a Jeddah CloudFront edge. (AWS global infrastructure)
Microsoft Azure: Q4 2026, per Microsoft. The Saudi Arabia East region (Eastern Province, three availability zones) completed datacenter construction in December 2024, and Microsoft has confirmed customer workloads run from Q4 2026. Until Microsoft says it is live, it is not live. (Microsoft's announcement)
What this means for your Saudi path
Three practical consequences:
- If you run on AWS or Azure and the buyer is government-linked, your route almost certainly involves a live in-Kingdom provider — which means a porting question, not just a procurement one. Scope it early.
- If you run on Google Cloud or Alibaba Cloud, your region exists but your purchase goes through a designated route (CNTXT or sccc). The first conversation is with that route's commercial team.
- Azure UAE North and AWS Bahrain sit outside the Kingdom. Whether a Saudi buyer accepts a nearby region depends on the data classification and the customer — for government-linked workloads, usually not.
The fastest way to know which consequence applies to your deal: the Path Check — seven questions, three minutes, a provisional route with these sources attached.