Deployment
Two deployments. Both keep your data in the Kingdom.
The product is the same either way — the same screens, roles and audit record. What changes is who holds the servers, who operates them, and how quickly it starts.
The point most buyers get backwards
On-premise is not automatically the more compliant choice. An on-premise deployment does not inherit the cloud region's licence: Google Cloud's Dammam region holds a CST Class C licence, granted on an NCA assessment. Inside your own data centre, the assessment is yours — very likely already in place, but yours to produce.
So the honest comparison is not which is safer. The cloud brings a pre-assessed, independently licensed region; on-premise brings absolute control and no external contracting chain. And no region makes a platform compliant on its own — the controls on the tenant side are shared between you and PULSE either way.
Side by side
Eleven questions a procurement committee asks.
| — | In-Kingdom cloud | On-premise |
|---|---|---|
| Where the data sits | A dedicated environment in Google Cloud's Dammam region. A second location is a second zone inside the same region. | Your own data centre, on two servers inside your network. |
| Who can reach it | Your invited users. PULSE's platform administration cannot read your data. | Your invited users, on your network. No internet route exists. |
| Regulatory position | The region holds a CST Class C licence, assessed by the NCA against its cloud controls — independent of PULSE. | Your existing data-centre assessment. No external licence applies. |
| Contracting chain | Google Cloud, sold in the Kingdom through its appointed reseller. Both are named in the sub-processor disclosure. | None. Hardware is bought directly through your own suppliers. |
| Database | PostgreSQL 16, managed in region. | PostgreSQL 16 on your server. No specialist database staff required. |
| Who operates it | PULSE, as part of the service. | Your choice: your IT team, or PULSE under a managed-service agreement. |
| What you provide | Invited users and your contract file. | Two servers, a network segment, an internal mail relay for sign-in codes, a certificate from your own authority, and backup. |
| How updates arrive | Continuously, tested before release. | On a release schedule you approve and apply. |
| Time to go live | Fastest. The environment is created at signature. | Longer: hardware procurement, installation and your change process. |
| Recovery | Managed backup and restore inside the region. | The two servers added to your existing backup schedule. |
| Cost shape | Operating cost: licence, implementation and support. | Capital and operating: hardware bought directly with no PULSE margin, then licence, implementation, support, and a managed service if PULSE operates it. |
Choosing
One question usually settles it.
Choose the cloud if…
- You want it running this quarter.
- An independently licensed region counts for more with your committee than owning the hardware.
- You would rather not add two servers to your IT estate.
Choose on-premise if…
- Policy does not permit any cloud hosting, whatever its licence.
- You want no third party in the contracting chain at all.
- Predictable, approved update windows matter more than immediate ones.
Either way
The product is identical, your data stays in the Kingdom, and the decision can be revisited later — the records move; the screens do not change.
We will take your IT and Security team through either one.
Including a session with the cloud provider's regional team, in your own terms, as part of onboarding.