Cloud services · Managed cloud
Managed cloud services in Saudi Arabia: your estate operated after go-live
Managed cloud services are the work that keeps a cloud estate healthy once the migration is over: monitoring, patching, backups that are tested by restoring them, capacity and cost. Interkey provides managed cloud services for organisations in Saudi Arabia on AWS, Google Cloud, in-Kingdom hosting and their own infrastructure, with engineers in Riyadh. The scope is written down before anything is operated, so you know what Interkey runs, what stays with your team and how the service hands back.
In short
- What it is: the cloud estate operated after go-live, on a scope agreed in writing.
- What Interkey runs: monitoring with Datadog, patching and upgrades, backup checks by restore, Kubernetes platform operation, monthly cost reviews and configuration hygiene.
- Where: AWS, Google Cloud, in-Kingdom hosting or your own infrastructure.
- Who: the same Riyadh engineering team that designs and builds these platforms, working in Arabic and English.
- Hours: the Saudi working week as standard; extended or round-the-clock cover is designed and priced per agreement where a platform needs it.
- What it is not: a help desk, a user-device service or security operations.
At a glance: what Interkey runs and what stays with you
The usual scope of a managed cloud service. Your agreement names the exact platforms and environments.
| Area | Interkey operates | You keep |
|---|---|---|
| Monitoring | Datadog agents, integrations, dashboards, alert routing and a monthly alert review | Which services matter and who is paged |
| Patching and upgrades | Operating system, platform and agent versions kept supported, with the next upgrade dated | Approval of change windows |
| Backups | Backup jobs watched and verified by actual restore, with the date and result recorded | Retention rules and what must be recoverable |
| Kubernetes | Cluster upgrades with rehearsed rollback, node capacity, admission policy and image hygiene | The applications on the cluster and their releases |
| Cost | A monthly cost review: idle resources, sizing, tagging gaps and commitments to consider | Budgets and the decision to buy commitments |
| Security posture | Patching, configuration kept to the agreed baseline, identity hygiene and platform-level alerts | Security operations, threat monitoring and incident response |
| Changes and reporting | Changes through an agreed process, and a monthly report of what changed and what it cost | The decisions the report asks for |
What managed cloud services have to cover
A cloud provider runs the data centres, the hardware and its managed services. It does not decide which alerts matter, upgrade your clusters on your calendar, or check that last night's backup restores. That layer is yours, and cloud managed services exist because many teams can build it once but cannot staff it for years.
A useful service is judged on four things:
Read more
- A written scope: platforms, environments, hours, which changes need approval, and how the service ends.
- Routine work done on time: versions supported, backups restored, alerts that reach a named person.
- A monthly account: what happened, what changed, what it cost and what needs a decision.
- A way out: runbooks and records your own team or another provider could use.
Interkey bounds the service to platforms it designs and implements. The full operating model is on our managed services page.
Relatedmanaged services page
Cloud operations: monitoring, patching and backups
Monitoring with Datadog
Nothing else in the service can be checked without monitoring. Interkey implements and operates Datadog, so one platform shows metrics, logs and traces from cloud services, virtual machines and Kubernetes. We keep the agents current, add integrations as the estate grows, route each alert to the team that can act and remove alerts that only make noise. Each month we review what fired and what was missed. Datadog is licensed separately from the operating work, and Interkey can supply both. See how Interkey implements and operates Datadog.
Read more
Patching, upgrades and backups
Most outages in an estate that was correct at go-live start with an upgrade nobody scheduled. The service keeps every platform in scope on a version its vendor still supports, and the next upgrade has a date. Patches go through the change process you approve, in windows that follow the Saudi calendar.
A backup is only proven when it has been restored. Backup jobs are watched for failures, and restores are rehearsed on an agreed schedule, with the date and outcome in the monthly report. Retention and recovery targets remain your decision.
Managed Kubernetes: the platform operated, the workloads yours
"Managed Kubernetes" means two things. A hyperscaler's managed service, such as Amazon EKS or Google Kubernetes Engine, takes the control plane off your hands. It still leaves you the node pools, version upgrades, add-ons, policies and cost of what runs on it. A self-managed cluster in the Kingdom leaves you all of it.
Interkey operates the platform layer in both cases: cluster and add-on upgrades with rehearsed rollback, node capacity, admission policy, registry and image hygiene, and platform-level incidents. Your applications and their releases stay with your teams unless a separate agreement says otherwise. Which kind of cluster fits is usually settled by residency rules; our Docker and Kubernetes page explains that decision.
RelatedDocker and Kubernetes page
Cost reviews and security posture
Cloud bills rarely grow because of price, but because of an environment nobody switched off, storage never tiered, or capacity sized for launch and never revisited. The monthly cost review finds these, names an owner for each and tracks the result. Where cost needs to be read beside performance, Datadog Cloud Cost Management can sit on the same platform as the monitoring.
On security, the service keeps platforms patched, configured to the agreed baseline and monitored for platform-level events, and keeps identity clean: no shared administrative credentials, roles that map to real teams. Interkey is not a security operations provider and does not offer threat monitoring or security incident response; it works with whoever holds that role for you.
Managed AWS, managed Google Cloud and in-Kingdom estates
Managed AWS
Interkey is an AWS partner. AWS says its first Region in the Kingdom is on track to launch in December 2026; until it is live, its Middle East Regions are in Bahrain and the UAE. We operate workloads wherever your data classification allows. See AWS in Saudi Arabia.
Managed Google Cloud
Interkey is a Google Cloud partner. Google Cloud runs a region in Dammam; Saudi-billed organisations buy it through the reseller route Google sets for the Kingdom, and Google's technical support comes through that route. Interkey operates what runs on it. See Google Cloud in Saudi Arabia.
In-Kingdom hosting and your own data centre
Data that may not leave systems you control needs the same discipline, under the same written scope.
How a managed cloud service starts
-
Assess.
The estate as it is: versions, configuration drift, existing monitoring, backups and the upgrade backlog.
-
Agree the scope.
Platforms, environments, hours, approval rules, incident route, monthly report and exit terms, in writing.
-
Document and fix.
Runbooks written from the platform, urgent items from the assessment fixed, monitoring brought to standard.
-
Shadow.
Interkey works alongside your current operator for an agreed period.
-
Take over.
The agreed scope moves to Interkey on a stated date, with change, incident and reporting routes live.
-
Review.
Monthly reports and a quarterly check that the scope still fits.
What drives the cost of a managed cloud service
Each service is quoted from its scope. These are the inputs that move the price.
| Driver | Why it matters |
|---|---|
| Platforms and environments | Each cloud account, cluster and database in scope adds routine work |
| Coverage hours | Out-of-hours and round-the-clock cover need more people on rota |
| State of the estate | Overdue upgrades and missing runbooks are fixed first, and priced separately |
| Rate of change | Frequent releases and new environments mean more change requests |
| Shape of the service | Full operation costs more than backing your own team on escalation and upgrades |
| Licences | Datadog and cloud consumption are billed separately from the operating work |
Support hours, 24/7 cover and residency
The standard pattern is the Riyadh team on the Saudi working week, Sunday to Thursday, in your time zone. For platforms that need cover outside those hours, out-of-hours or round-the-clock support is designed and priced in the agreement, not applied by default. Response targets are set per platform in your scope, and the monthly report shows whether they were met.
Remote access, monitoring data, tickets and runbooks all describe your estate, so where they are held is a classification question too. The operating tooling sits where your policy says the platform's data may live, and the agreement says so. Interkey's engineers are in Riyadh, work in Arabic and English, and implement the platforms they operate.
Questions buyers ask about managed cloud services
What is included in managed cloud services from Interkey?
Monitoring with Datadog, patching and upgrades, backups verified by restore, Kubernetes platform operation, monthly cost reviews, configuration hygiene and a monthly report. The exact platforms and environments are named in your written scope.
Do you offer 24/7 cloud support in Saudi Arabia?
Where a platform needs it. The standard is the Riyadh team on the Saudi working week; out-of-hours or round-the-clock cover is designed and priced in the agreement for the platforms that need it.
Can Interkey run managed Kubernetes on EKS, GKE or servers we own?
Yes. Interkey operates the cluster platform in each case: upgrades with rehearsed rollback, capacity, policy and image hygiene. Your applications and their releases stay with your teams unless agreed otherwise.
How is a managed cloud service priced in KSA?
From its scope: the platforms and environments, the coverage hours, the state of the estate, the rate of change and the shape of the service. Datadog licences and cloud consumption are billed separately.
Does the operating tooling keep our data inside the Kingdom?
It follows your classification policy. Remote access, monitoring data, tickets and runbooks are placed where the policy allows the platform's data to live, and the agreement states where each one is held.
How long before Interkey can take over our cloud operations?
As an estimate, days to a few weeks for a platform Interkey built, and a few weeks to a few months for an inherited estate. Size, overdue upgrades, missing documentation and access approvals decide it.
Next
Read next
Next step
Scope your managed cloud service
Tell us where your estate runs, who operates it today and when it was last upgraded. We will propose a written scope: what Interkey runs, what stays with you, and the hours it needs.
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