Cloud services · Hybrid cloud
Hybrid cloud in Saudi Arabia: splitting an estate by data class
Hybrid cloud means running one estate across more than one place on purpose, for example a public cloud region, a provider inside the Kingdom and infrastructure you operate yourself. For most Saudi organisations it is not a fashion choice. It is where the data classification policy leads. This guide explains when hybrid is the right answer, what has to be designed at the boundaries, and how Interkey plans, builds and operates it from Riyadh.
Published 5 min read
In short
- What it is: one estate that runs in several places by design, with the boundaries between them designed too.
- Why Saudi estates end up there: residency is answered per class of data, so different applications land in different places.
- What the work is: identity across locations, the network between them, guardrails, and one operating model instead of one per location.
- What Interkey does: cloud strategy, landing zone, operation and cost review from Riyadh, in Arabic and English, whichever provider the classification points to.
What hybrid cloud is, and what it is not
Hybrid cloud is a deliberate mix of locations that is run as one estate. It is not the same as buying from two providers. Multi-cloud sounds like leverage and is usually bought as insurance, but it doubles the operating surface, the skills needed and the identity model.
Where each part of a hybrid estate can run
Every row is the right answer for some class of data. Which class belongs in which row is decided by your classification policy, not by a provider.
| Option | What it is | What decides it |
|---|---|---|
| Hyperscaler region inside the Kingdom | A global provider's services delivered from infrastructure located in Saudi Arabia | Data that must stay in the Kingdom but may sit with a global operator. The list of such regions changes, so check it at scoping |
| Hyperscaler region abroad | The same services from a region outside Saudi Arabia | Only data classes your policy allows to leave. Often the widest service catalogue |
| Local provider | A Saudi-operated cloud, usually narrower in services | Workloads where the operator's jurisdiction matters as much as the data's location |
| Provider-managed infrastructure at your site | For example AWS Outposts racks, installed in your own data centre | AWS services on premises. AWS notes that deployments in the Kingdom may need additional authorisation |
| Private, on infrastructure you operate | Your data centre or colocation, run with cloud operating discipline | Data that may not leave systems you control |
See the pages on AWS in Saudi Arabia and Google Cloud in Saudi Arabia for the current region position of each provider.
Why most Saudi estates end up hybrid
The most common design error is a single estate-wide answer: everything in the Kingdom, or everything abroad. A classification policy usually gives different answers for different classes of data, and the estate should reflect that. Some data can sit in a hyperscaler region outside the Kingdom. Some needs infrastructure in the Kingdom. Some cannot leave systems the organisation operates itself. Those three answers point at three different architectures, and they often apply to different applications in the same programme.
Read more
Timing adds to it. Regions in the Kingdom have been announced across the industry, and announced is not live: AWS says its Saudi Region is on track to launch in December 2026, and it was not yet in AWS's list of available Regions on 2 November 2026. A plan that depends on a region opening on schedule takes on a risk it does not control. Legacy systems add a last reason, because modernisation here is incremental and the old system often stays live beside the new one.
What has to be designed at the boundaries
-
Identity.
One identity model across every location, with roles that map to real teams and no shared administrative credential.
-
Network.
Connectivity between locations, segmentation inside them, and the paths data may and may not take.
-
Guardrails.
Policy as configuration: what may be created where, by whom, with which tags and at what cost ceiling. The platform refuses a mistake instead of someone discovering it later.
-
One operating model.
Patching, capacity, identity hygiene and change control done one way across the estate, with a named operator.
What a hybrid estate costs to run
Cloud cost surprises are rarely caused by price. They come from architecture decisions taken without a cost dimension. Hybrid adds three that deserve a line in the plan:
- Data crossing a boundary. Some boundaries charge for data that leaves, and a chatty design between two locations can cost more than the workload itself.
- Two estates at once. During any move you pay for the old environment and the new one.
- Operating capability. Keeping identity clean and guardrails current for years takes a team, so decide who that is before the build.
Every workload should carry a tag that says who owns its bill, so that the monthly cost can be read by owner across all locations.
How Interkey works on hybrid estates
Interkey provides cloud services for organisations in Saudi Arabia, and the work is the same whichever mix the classification produces. It starts with the strategy: which classes of data may live where, and what that means for the shape of the estate. It continues with the landing zone and guardrails, built as code. After the move it covers operation of the estate and a periodic cost and architecture review. If applications have to move first, the cloud migration practice decides what to do with each one, including the ones that stay where they are.
Read more
The first step is a conversation about the estate and the classes of data in it. No provider is named before that. It is the wrong fit for an estate that has already landed in one place, runs at a cost the business accepts and has a team that owns it.
Questions buyers ask about hybrid cloud
What is hybrid cloud in simple terms?
One estate that runs in more than one place on purpose, for example a cloud region and infrastructure you operate, with the connections between them designed and managed together.
Is hybrid cloud the same as multi-cloud?
No. Multi-cloud means more than one cloud provider. Hybrid mixes kinds of location, such as cloud, in-Kingdom hosting and your own data centre.
Do we have to keep some systems on our own infrastructure?
Only if your classification policy says a data class may not leave systems you control. That is a decision per class of data, and the policy settles it, not Interkey.
Which provider should the cloud part use?
None is recommended before the classification is done, and the answer is often more than one afterwards. The provider follows from where each class of data may live and which services the workloads need.
Who operates a hybrid estate afterwards?
Whoever the strategy names. If it is your team, the landing zone is built so they can run it and the handover includes runbooks. If it is Interkey, the estate is taken on under a written managed-services scope.
Next
Related pages
Next step
Discuss a hybrid cloud design
Describe the estate, the classes of data in it and whether you have a classification policy. We will tell you what the first step would be.
Or directly
+966-11-2180999 [email protected]Tawuniya Towers, North Tower, 7th Floor, King Fahad Highway, Olaya, P.O. Box 56835, Riyadh 11564, Saudi Arabia