Deployment & tenancy
Run on our cloud, a dedicated cell, or in your country
Choose how much you share. Every model runs the same software, the same APIs and the same controls — you can move up as you grow.
Compare
What changes between models
| Feature | Pooled | Bridge | Silo | Sovereign |
|---|---|---|---|---|
| Plans | Sandbox, Starter | Growth | Enterprise | Sovereign |
| Database | Shared, row-level isolation | Dedicated | Dedicated | Dedicated, in your estate |
| Compute | Shared | Shared | Dedicated cell | Your data centre or national cloud |
| Encryption keys | Platform-managed | Bring your own key | Bring your own key | Hold your own key |
| Region pinning | — | ✓ | ✓ | ✓ In-country |
| Availability target | 99.9% | 99.95% | 99.99% | 99.99% |
| Upgrade window | Continuous | Continuous | Agreed windows | Agreed windows |
Availability figures are targets set per plan in your agreement. Sovereign deployments: Planned (2028).
Environments
Sandbox, UAT and production for every bank
Rehearse every change. Configuration is promoted between environments with a diff and an approval, never copied by hand.
- Sandbox with simulated NIP, KYC and SMS
- UAT with production-like data volumes
- Promotion with maker-checker and rollback
Environments
- Production
- ✓ Operational
- UAT
- ◷ Promotion in review
- Sandbox
- ◆ Sandbox
Example of the Tenant Console view.
How we run it
Kubernetes
EKS, AKS, GKE, or OpenShift on-prem.
Keys
Cloud KMS or FIPS 140-3 Level 3 HSMs.
Observability
OpenTelemetry metrics, logs and traces.
GitOps
Every change to infrastructure is reviewed code.
Not sure which model fits?
Tell us about your regulator and data residency rules; we'll recommend one.