Five years ago, "hosting in Saudi Arabia" meant a rack in a local data centre or a compromise on features. In 2026 the situation has inverted: the Kingdom now hosts multiple live hyperscaler regions with more announced, and the question buyers face is no longer whether they can keep workloads in-country but which of several in-Kingdom options fits. This guide is the inventory we wished existed when clients started asking — what is genuinely live, what is announced, and how to reason about the difference.
Everything below reflects public announcements and vendor documentation as of July 2026. Launch status changes; where something is "announced" rather than live, we say so explicitly.
First, the vocabulary: region, availability zone, edge
Three words do a lot of work in cloud marketing, and conflating them causes expensive mistakes:
- A region is a geographic cluster of data centres offering the provider's services. If a provider has a "Saudi region," your virtual machines, databases and storage can physically run in the Kingdom.
- An availability zone (AZ) is one of several isolated data-centre groups inside a region, each with independent power and networking. Regions with three AZs let you architect for a whole-data-centre failure.
- An edge location / PoP is a small footprint for caching and content delivery. An edge node in Riyadh accelerates your website for Saudi visitors but does not mean your data resides in Saudi Arabia. Treat "we have a presence in KSA" claims with this distinction in mind.
Hyperscaler regions live in the Kingdom (July 2026)
| Provider | Location | Status | Notes (per public announcements) |
|---|---|---|---|
| Oracle Cloud | Jeddah | Live | In-Kingdom since 2020 — the earliest hyperscaler region in KSA |
| Oracle Cloud | Riyadh | Live | Second Saudi region, opened in 2024 |
| Google Cloud | Dammam (me-central2) | Live | Google's Saudi region; also powers the Dammam location of local managed providers |
| Alibaba Cloud / SCCC | Riyadh | Live | Operated through SCCC, a joint venture with stc; two availability zones |
| Huawei Cloud | Riyadh | Live | Launched 2023; publicly described with three availability zones |
Two things stand out from this table. First, Riyadh has become the Kingdom's cloud capital — three of the five live regions sit in or around it. Second, the eastern and western provinces are covered too: Google Cloud in Dammam and Oracle in Jeddah mean latency-sensitive workloads can sit near users on either coast.
Announced, but not yet live as of this writing
- AWS — Riyadh. Announced in March 2024 with a stated USD 5.3 billion investment and a launch targeted for 2026, with three availability zones planned. As of this writing, AWS's own global-infrastructure page still lists Saudi Arabia under announced plans rather than launched regions — check AWS's official Regions page for current status before planning around it.
- Microsoft Azure — Saudi Arabia East. Microsoft publicly confirmed in February 2026 that its Saudi datacenter region is targeted to be available for customer workloads in Q4 2026, with three availability zones. Until then, Azure workloads for Saudi customers run from other regions (commonly the UAE), which matters if you have residency requirements.
- Tencent Cloud. Announced at LEAP 2025 with a stated investment of more than USD 150 million; public reporting during 2025–2026 describes a Saudi cloud region with two availability zones coming online. Verify current service availability on Tencent's official region page before planning around it.
The practical rule for announced regions: never sign a contract that depends on a launch date. Regions slip. If your compliance deadline is fixed and the region date is not, choose from the live column.
A note on region codes — read them carefully
Here is a detail that regularly confuses Saudi buyers comparing documentation: Google Cloud's Dammam region carries the code me-central2, while AWS's UAE region is me-central-1 and its Bahrain region is me-south-1 — three near-identical codes, three different countries, two different providers. Naming schemes are independent across providers, and the resemblance is coincidence; expect more look-alike codes as the announced Saudi regions launch. When a tender document or an architecture diagram says "me-central2" or "me-central-1," always confirm whose region it means against that provider's official documentation.
The local and managed layer
Hyperscaler regions are one layer of the market. Alongside them sits a Saudi ecosystem you should know about: telco-affiliated data-centre and cloud arms (stc's center3, Mobily, salam) and national players offering government-oriented and sovereign-style platforms. For many public-sector and regulated workloads, these are the required route — see our guides to the CST cloud regulatory framework for why provider registration category matters.
Then there is the layer most SMEs actually buy: managed cloud. Raw hyperscaler regions sell you compute by the hour; you still have to assemble email, SSL, DNS, backups, a control panel and support — in Arabic, if your team needs it. A managed Saudi provider packages that. Skyline Cloud, for example, offers cloud servers and managed hosting with Saudi locations in Riyadh (ksa-c-1) and Jeddah (ksa-w-1) plus a Dammam option (ksa-e-1) powered by Google Cloud's in-Kingdom region — wrapped with Skyline Mail, daily backups, free auto-renewing SSL, the S Panel control panel in Arabic and English, SAR billing and ZATCA-compliant invoices, and complemented by global edge locations (London, Frankfurt, Singapore, New York and others) for international audiences. You can try it free for 14 days — no credit card and have a workload running in a Saudi region within the hour.
How to choose: match the layer to the workload
There is no universally correct region — there is a correct pairing of workload and layer:
| Your situation | Sensible starting point |
|---|---|
| Company website, email, small business apps | Managed Saudi cloud (fixed SAR pricing, everything included) |
| Custom SaaS product with a DevOps team | Hyperscaler Saudi region (deep service catalogue, pay-as-you-go) |
| Government or classified data | Providers registered at the appropriate CST category; NCA cloud controls apply |
| Regulated financial workloads | Whatever your regulator's rulebook supports — see our SAMA cloud outsourcing checklist |
| Latency-critical for east/west coast users | Region nearest the users: Dammam (east), Jeddah (west) |
| Heavy steady-state compute you already own hardware for | Compare against colocation first — our colocation vs cloud framework runs the numbers |
Three questions settle most cases:
- Who operates what you cannot? If you have no 24/7 ops team, a raw region transfers that burden to you. Managed layers exist precisely to absorb it.
- What currency and contract do you want? Hyperscaler billing is typically USD-denominated with consumption-based invoices; local managed providers bill fixed amounts in SAR — easier for Saudi budgeting and VAT handling.
- Where must the data live? If personal data residency drives the decision, verify the region, not the brand — our PDPL hosting guide shows how to write it into the contract.
What this build-out means for buyers
The scale of announced investment — AWS's stated USD 5.3 billion, Microsoft's confirmed region, Chinese providers expanding, and a wave of local data-centre construction, all according to public announcements — has a very practical consequence: negotiating leverage has moved to the buyer. Providers competing for Saudi workloads will answer residency questionnaires, commit to SLAs, and price sharply. Use that. Ask every provider the same six location questions (primary site, backup site, sub-processors, support access, exit terms, breach notification) and let the written answers decide.
Frequently asked questions
Which cloud regions are physically inside Saudi Arabia right now?
As of July 2026, per public announcements: Oracle (Jeddah and Riyadh), Google Cloud (Dammam, me-central2), Alibaba Cloud via SCCC (Riyadh), and Huawei Cloud (Riyadh). AWS's Riyadh region (announced for 2026) and Microsoft's Saudi Arabia East region (announced for Q4 2026) were not yet listed as launched at the time of writing — check each provider's official region page for current status.
Does using a global provider's Saudi region satisfy data residency?
It keeps the primary workload in-Kingdom, which is the biggest step — but you must still confirm where backups, replicas and support access happen. Residency is a property of your whole configuration, not the region name.
Is a CDN edge location in Riyadh the same as a Saudi region?
No. Edge locations cache content near users; your actual data and compute remain wherever your origin region is. For residency, the origin region is what counts.
I'm a small business — do I need to care about any of this?
Only the last mile of it: choose a provider whose Saudi location you can verify, whose contract states it, and whose plans you can afford. A managed provider with SAR pricing gets you there without a cloud architect on payroll.
Put a pin in the map
The Saudi cloud map is now rich enough that "we couldn't find in-Kingdom hosting" is no longer a defensible line in any audit or board meeting. Pick your layer, verify the region in writing, and start small: open a free Skyline Cloud account — 14-day trial, no credit card — and deploy your first Saudi-region workload today.
Comments
0 total · 0 threads