Google Cloud · Partner services
Google Cloud partner in Saudi Arabia: architecture, migration, GKE, data and operations
Interkey is a Google Cloud partner in Saudi Arabia. We design the landing zone, move workloads onto Google Cloud in dependency order, run GKE clusters and data platforms such as BigQuery, set up monitoring, and operate the estate after go-live on an agreed scope, with engineers in Riyadh. The Google Cloud contract and billing follow the reseller route Google sets for organisations billed in the Kingdom; our part is the engineering and the operation around it.
In short
- What Interkey is: a Google Cloud partner working with organisations in Saudi Arabia.
- What we do: architecture and landing zone, migration, GKE, data platforms such as BigQuery, monitoring and operation after go-live.
- What we do not do: replace the purchase route. Your Google Cloud contract, invoices and platform support come through the reseller route Google sets for Saudi Arabia.
- Who it is for: IT and platform leaders moving workloads to Google Cloud, or already on it and short of people to run it.
- How it is priced: by scope, written down before work starts; no fixed list price.
At a glance: what Interkey delivers on Google Cloud
Each service can be bought on its own, but most programmes run them in this order, because each one depends on the one above it.
| Service | What it covers | Google Cloud products involved | What you hold at the end |
|---|---|---|---|
| Classification and placement | Every application gets a placement decision and a reason, including those that stay where they are | Region choice, Dammam included; control packages where a workload needs them | An inventory with a decision per workload |
| Landing zone | Identity, network boundaries, guardrails and cost tags, defined as code | Resource hierarchy, IAM, VPC, organisation policies | A foundation your team can rebuild from the repository |
| Migration | Rehost, replatform or rewrite, decided per workload and moved in dependency order | Compute Engine, Cloud SQL, GKE, Cloud Run | Workloads live on Google Cloud, with a rollback plan used or retired |
| Containers on GKE | Cluster design, upgrades with a tested rollback, capacity and policies | Google Kubernetes Engine (GKE) | Clusters with a named operator and an upgrade calendar |
| Data platforms | Data moved and modelled, with access rules agreed with data owners | BigQuery, Cloud SQL, Cloud Storage | An analytics platform with owners, costs and access written down |
| Monitoring and operation | Patching, capacity, identity hygiene, guardrail changes and a monthly cost report | Cloud Monitoring and Cloud Logging, or Datadog beside them | A managed service on an agreed scope, or a documented handover |
What a Google Cloud partner does, and what stays with the reseller
Reseller and partner are often treated as one word. They are different jobs. Google states that organisations billed in Saudi Arabia buy Google Cloud through its reseller route, and that this route is also the way into the Dammam region (me-central2). The entity you sign with holds your billing account, invoices you and provides Google Cloud platform support. Our Google Cloud in Saudi Arabia guide sets out that route step by step, including what happens to an account that is already billed in Saudi Arabia.
Read more
A Google Cloud partner does the work the platform does not do for you: deciding what goes where, building the foundation, moving the applications and running them. That is Interkey's role. Settle early who you call for what: platform faults go to the entity you contracted with; the parts of the estate Interkey builds and operates are covered by Interkey's service agreement, with coverage hours and response targets written into it.
What a Google Cloud programme has to cover
A Google Cloud estate that works in year three has four things in place: each workload sits where its data classification allows; the landing zone was built before the first workload, not improvised for it; every application moved for a reason, in dependency order; and someone named operates it.
Most trouble comes from skipping one of these: a pilot project built by hand becomes production, a GKE cluster falls out of support, a BigQuery bill doubles because no one owns the queries. That is a programme problem, and a partner is there to prevent it.
How Interkey works as your Google Cloud partner
Architecture and landing zone. We start with classification: which classes of data may live where, citing your own policy. For workloads that must stay in the Kingdom, the Google Cloud Dammam region is the candidate, and the control package each one needs is a classification decision, not a default. Our data residency guide for Saudi Arabia covers that question across providers. The landing zone is then written as code: resource hierarchy, identity, network boundaries, organisation policies and cost tags.
Read more
Migration. Each application is rehosted, replatformed, rewritten or retained, decided per workload, then moved in waves in dependency order. Databases that cannot stop are moved with iblync, Interkey's own replication platform, while production stays in service. The method is on our cloud migration page.
GKE and containers. Applications that move to containers land on GKE, with cluster design, policies, upgrades with a tested rollback and capacity planning. The Kubernetes migration path explains how applications are prepared.
Data platforms and BigQuery. BigQuery is Google's managed data warehouse. We move data into it, model it with your data owners, set access rules and make the cost of each dataset visible, so a reporting platform does not become an unexplained line on the bill.
Relateddata residency guide for Saudi Arabiacloud migration page
Monitoring and operation after go-live
Google's Cloud Monitoring and Cloud Logging stay in place on every project. Where a team needs services, applications and cost in one view, across Google Cloud and the systems that stay on premise, we add Datadog; our Google Cloud monitoring page shows how GKE, Cloud Run, Cloud SQL and BigQuery are read together.
After the move, Interkey can operate the estate as a managed service on an agreed scope: patching, capacity, identity hygiene, guardrail changes and a monthly report of what changed and what it cost. See managed cloud services. If your own team will run it, the landing zone is built for them and the handover includes the runbooks.
Working with a Google Cloud partner in Saudi Arabia
- Engineers in Riyadh. Design reviews, workshops and support in Arabic and English, on the Saudi working week; extended coverage is designed and priced per agreement.
- The Dammam region. Check Google's product list for me-central2 before you design: not every Google Cloud service is offered in every region.
- Your security team decides access. Service accounts, roles and remote access are reviewed before anything is connected.
- Existing commitments. If you already hold Google Cloud discounts on another account, check with the reseller whether they carry over before you switch route.
How a Google Cloud project with Interkey runs
-
Inventory and classification.
Applications, data classes, dependencies and the reason each one would move, or stay.
-
Purchase route confirmed.
Your billing account set up, or moved, through the reseller route Google sets for Saudi Arabia.
-
Landing zone built.
Identity, network, guardrails and cost tags as code, reviewed by your security team.
-
First wave.
A low-risk workload moved end to end, to prove the landing zone and the runbooks.
-
Later waves.
The rest of the inventory in dependency order, with monitoring in place before each cutover.
-
Operate or hand over.
Interkey runs the estate on an agreed scope from Riyadh, or hands over to your team and stays on for support.
What drives the cost and the timeline
There are two bills. Google Cloud consumption is billed to your account by the entity you contract with, at Google's prices for the services and region you use. Interkey's work is quoted by scope, and the scope depends on:
- the number of applications and how tightly they depend on each other;
- whether a landing zone exists and how much of it is undocumented;
- data volume, and which databases must move without downtime;
- the number of GKE clusters and how far behind their upgrades are;
- the controls your data classification requires;
- the coverage hours you need after go-live.
Read more
Durations are estimates, not promises: a few weeks for inventory and classification, a few more for the landing zone, then migration waves over months for most estates. Estate size, approval cycles and how much is known about the applications drive them.
Questions buyers ask
What does a Google Cloud partner in Saudi Arabia do for our organisation?
The engineering around the platform: classification and placement, the landing zone, migration, GKE and data platforms, monitoring, and operation after go-live. Interkey does this as a Google Cloud partner, with engineers in Riyadh.
Is a Google Cloud reseller in Saudi Arabia the same as a Google Cloud partner?
No. The reseller route Google sets for Saudi-billed organisations holds your contract, billing and platform support. A partner such as Interkey designs, moves and runs what you build on Google Cloud. Most organisations need both.
Can we buy Google Cloud through Interkey and pay in Saudi riyals?
Google Cloud is bought through the reseller route Google sets for the Kingdom, and invoicing terms are set by the entity you sign with. Interkey quotes its own engineering and operations work separately.
Do all our workloads have to run in the Dammam region?
Only those your data classification requires to stay in the Kingdom. Others may run in a wider set of regions, subject to latency and cost. We decide it per workload and confirm the services it needs are offered in Dammam.
How long does a Google Cloud migration with a partner take in KSA?
As an estimate, a few weeks for inventory and classification, a few more for the landing zone, then migration waves over months. The size of the estate, approval cycles and unknown dependencies drive it.
Can Interkey run our GKE clusters and BigQuery platform after the move?
Yes, as a managed service on an agreed scope: cluster upgrades with a tested rollback, capacity, policies, data access and a monthly cost report. Coverage hours and response targets are written into the agreement.
Next
Read next
Next step
Plan your Google Cloud project with Interkey
Tell us what you want to run on Google Cloud, where its data has to stay, and whether you already have a Google Cloud account. We will reply with the questions that shape the design and a proposed first step.
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