Deployment
Deploy where your sovereignty rules require.
The same platform runs as managed SaaS, in a dedicated cloud with your own keys, or fully on-premises and air-gapped. The deployment model is a procurement decision, not a product decision — you do not lose modules by choosing isolation.
- 01
SaaS
Quick start for pilots and teams.
Fully managed and continuously updated. The fastest way to run a pilot or a first programme without standing up infrastructure.
- Fully managed and continuously updated
- Shared infrastructure with database-enforced tenant isolation
- Fastest path from decision to first programme
- 02
Dedicated Cloud
Isolated tenancy, your keys.
An isolated tenancy with customer-managed encryption keys, for organisations whose data governance requires separation from other tenants at the infrastructure layer.
- Isolated tenancy
- Customer-managed encryption keys
- Field-level encryption available
- Regional placement for data residency
- 03
On-Premises
Air-gapped, HSM-backed.
Fully on-premises deployment including air-gapped environments, with Keycloak for identity and HSM-backed encryption. For programmes where data cannot leave the estate.
- Air-gapped deployment supported
- Keycloak identity integration
- HSM-backed encryption
- No outbound telemetry requirement
Modular either way
Deployment model and module adoption are independent choices. An air-gapped on-premises install can start with one module, and a SaaS pilot can run the full set.
Bring your programmes into one auditable environment.
Tell us about your programme, your sovereignty constraints and the tools you are trying to retire. We will show you what a first module looks like.