Deployment
Deployed where your data is allowed to live.
Managed cloud inside the Kingdom, private cloud, or entirely within your own perimeter. The product is the same. What changes is who operates it and where the boundary sits.
Three ways to run it
One product. Three boundaries.
Managed cloud, in-Kingdom
We operate the platform on infrastructure inside Saudi Arabia. Fastest to start, and the option most organizations use for a first deployment.
Private cloud
The platform runs in your own cloud account inside the Kingdom, under your network controls, operated jointly during rollout.
On-premise
A single-tenant installation inside your own data centre, including air-gapped environments with no outbound connectivity at all.
The on-premise edition is built so that cloud-only features cannot be switched on, rather than merely being discouraged.
Choosing between them
What actually differs.
Managed cloud in-Kingdom
On-premise
We operate and update the platform
Your team operates it, on a release cadence you control
Data resides in the Kingdom
Data never leaves your own perimeter
Fastest path to a working pilot
Suited to air-gapped and highly regulated environments
Capacity managed for you
Hardware sized with you before installation
Licensed as a subscription
Licensed per installation, activated offline
What a rollout looks like
From first conversation to first answer.
Discovery
We agree the first use case, the sources it needs, and who is entitled to what. This is where most of the real decisions get made.
Connect
The first sources are connected with your approval, one at a time, each keeping the access rules it arrived with.
Teach
Your structure and your terminology are taught to the platform, so answers use the words your teams use.
Pilot
A defined group asks real questions against real material, and the answers are checked against what those people already know.
Roll out
Access widens by department, with administrators reviewing usage as it grows rather than after it has.
What we need from you
A short list, and none of it is a surprise.
- A named owner for the first use case
- Access to the sources that use case depends on
- Your permission model, or a decision about who should see what
- A pilot group who will actually ask questions
- For on-premise: sizing, network policy and an installation window
- A point of contact for the security review
We will tell you which deployment fits, and what it takes to stand it up.