Cloud service providers in Saudi Arabia — a Saudi-resident cloud, priced in SAR

Why "where your cloud provider sits" is now a business decision in Saudi Arabia

For most of the last decade, choosing a cloud provider in the Kingdom meant choosing a foreign region and accepting that your data physically lived elsewhere, reached over a cross-border link. That trade-off has become uncomfortable, and the reason is not one rule — it is that three separate conversations now start with the same question.

• The data-protection conversation. Saudi Arabia has a Personal Data Protection Law and a supervising authority, and cross-border transfer is a topic within it. We are not going to tell you what it obliges your organisation to do — that genuinely depends on your data, your sector and your legal advice. What we can say is that "our infrastructure is in Saudi Arabia and the region was chosen explicitly" is a shorter answer to give than one that begins with a transfer mechanism.
• The cybersecurity-review conversation. The National Cybersecurity Authority publishes control frameworks, and organisations in the Kingdom are increasingly asked where a workload runs and who operates it. Again: your security team decides which controls apply to you. Our job is to make the factual half easy to evidence.
• The finance conversation. ZATCA Phase 2 e-invoicing is the format Saudi finance teams work in. Every Skyline charge is issued as a ZATCA Phase 2 e-invoice in Saudi Riyals, so hosting stops being the line item that needs explaining. We are describing our own invoicing, not your filing obligations.

Put together, the question shifts from "which cloud is biggest?" to something more practical: which provider can answer, in one sentence each, where the data is, what currency the invoice is in, and who operates the platform? Those are the three answers this page is built to give plainly.

Data residency and sovereignty: in-Kingdom today

This is the heart of the matter. Skyline Cloud infrastructure is physically in Saudi Arabia, operated from Riyadh. Your data does not leave the country as a matter of normal operation.

Residency is no longer a simple yes/no, so it is worth being exact about what we can tell you and what only your own provider can:

• Where our infrastructure is. Skyline operates in Saudi Arabia. The compute catalogue offers a single Saudi region, riyadh, alongside eight international regions, and you choose which one at creation — nothing is placed on your behalf.
• What hosting, mail and DNS run on. Saudi-resident infrastructure. Your site files, databases, mailboxes and zones are not relayed through a distant region for a service you did not ask for.
• What we will not tell you. Where anyone else's regions are, what they cost, or what their terms say. Those change, they vary by account and contract, and a marketing page is the worst place to freeze them. Ask your current provider directly and read the answer in your own agreement.
• What we will not decide for you. What any regulation requires of your organisation. We can state where our infrastructure sits; your counsel and your regulator decide what that means for your obligations.

The practical benefit is short answers. When a client questionnaire, a tender annex or an internal review asks where the data sits, the reply is one sentence and needs no cross-border appendix — and because billing is in Saudi Riyals with a ZATCA Phase 2 e-invoice, the finance answer is equally short.

Migrating to a local cloud provider is not the ordeal you fear

The biggest reason teams stay on a foreign provider is migration anxiety. We make it manageable. Skyline offers guided migration support for the common starting points:

• From Google Workspace or Microsoft 365 — move mailboxes, domains and DNS to Skyline Mail with guidance, keeping mail flowing during the cutover.
• From GoDaddy or another shared host — move websites and email across, point DNS, and reissue SSL automatically in S Panel.

A realistic small-business migration looks like: provision your Skyline plan during the free trial → recreate sites/mailboxes → lower DNS TTLs → cut over MX and A records → verify mail and SSL → decommission the old host. Because everything is in one console under one SAR bill, you are not juggling six dashboards. (We are honest about scope: this is guided migration of websites, email, files and DNS — not a free done-for-you lift of an entire AWS/Azure estate.)