Use cases

Four ways a Saudi deal gets stuck.

These are the patterns the desk sees. Each ends the same way: a provisional route, a prepared enquiry, and the right first conversation. Find yours, or let the Path Check find it.

Case 01

A government SaaS pilot on AWS or Azure

The ministry wants the pilot live in Riyadh; your product runs on a hyperscaler with no live Saudi region. The tender cites a CST-registered provider and the security team has started asking about NCA controls.

The likely route

An in-Kingdom, CST-registered provider is the expected destination. The real work is the porting question (what your stack needs from the live in-Kingdom options) plus the buyer’s classification and security review, sequenced so the pilot date survives.

What the Path Check returns

“In-Kingdom provider expected — your current hyperscaler has no live Saudi region,” with the AWS and Azure status facts sourced and the live alternatives named.

The service that applies: Saudi path mapping

Case 02

A regulated private buyer — bank or health group

The deal is commercially agreed, then the buyer’s compliance team asks whether its regulator has approved the cloud arrangement. Nobody on your side knows what SAMA expects, or in what order.

The likely route

Sector approval leads. For a financial institution, SAMA approval of cloud use precedes provider selection — and outside-Kingdom hosting needs explicit approval. Your timeline inherits the customer’s regulatory step, so the route sequences it first.

What the Path Check returns

“Regulated customer: sector approval comes before infrastructure,” with the SAMA outsourcing facts and the order of operations.

The service that applies: Compliance-readiness orientation

Case 03

A stack already in-Kingdom — behind a designated route

You run on Google Cloud or Alibaba Cloud, the region exists in the Kingdom, and yet the purchase stalls: nobody can tell you who actually sells it, on what paper, billed from where.

The likely route

The region is live but the route is designated: CNTXT for Google Cloud Dammam, sccc for Alibaba Cloud Riyadh. The conversation belongs with that route’s commercial team, and arriving with billing structure and service availability framed saves the first month.

What the Path Check returns

“Your stack exists in-Kingdom — but you buy it through a designated route,” with the CNTXT and sccc facts sourced.

The service that applies: Provider and specialist matching

Case 04

A tender with no Saudi entity

The tender is on Etimad, your pipeline says it is winnable, and procurement asks for standing you do not have: a Saudi CR, MISA registration, local-content evidence. Someone proposes a subsidiary; someone else says it takes a year.

The likely route

Contracting standing is the blocker — and the standing question has faster answers than most vendors assume. Etimad has a Foreign Supplier route, MISA review takes up to 10 days per MISA, and which route your tender needs depends on what the tender says, so read it before you spend on any route.

What the Path Check returns

“Contracting standing, not infrastructure, is likely your blocker,” with the Etimad and MISA facts and the questions for the buyer.

The service that applies: Commercial and procurement orientation

Your case

Three minutes finds your route.

Check your Saudi path

Or start from the Saudi cloud map.