Deployment
Deploy the platform your way
One product, three deployment models. The same domain modules, workflow engine, and audit pipeline run in every mode — only infrastructure and isolation change.
Compare deployment models
| Dimension | SaaS | Dedicated Private Cloud | On-Premises |
|---|---|---|---|
| Infrastructure owner | Vendor | Vendor, in a dedicated subscription/environment | Customer |
| Tenant model | Shared, multi-tenant | Single tenant | Single tenant |
| Data isolation | Logical isolation (tenant-scoped), optional database-per-tenant tier | Dedicated database/cluster and storage account | Single-tenant database in customer environment |
| Upgrade model | Continuous — vendor-managed releases | Coordinated release windows | Signed offline release bundles, customer-scheduled |
| Monitoring | Vendor-operated, centralised | Vendor-operated, with customer visibility | Customer-operated (contractually defined) |
| Backup responsibility | Vendor | Vendor or jointly, per contract | Customer, unless a managed service is contracted |
| Typical onboarding | Fastest — days, not weeks | Weeks — infrastructure provisioning required | Longest — depends on customer environment readiness |
| Best-fit customer | SMEs and standard enterprise tenants | Regulated or high-volume customers requiring infrastructure isolation | Banks, government, and customers requiring data sovereignty |
| Commercial model | Subscription — [PRICING PENDING BUSINESS APPROVAL] | Contract — [PRICING PENDING BUSINESS APPROVAL] | Licence — [PRICING PENDING BUSINESS APPROVAL] |
Deployment models
SaaS
Vendor-managed, multi-tenant environment with the fastest path to onboarding.
- Vendor-managed environment
- Multi-tenant with logical isolation
- Fastest onboarding
- Subscription commercial model
Dedicated Private Cloud
Isolated infrastructure for one customer, vendor-managed or jointly managed.
- Isolated infrastructure for one customer
- Suited to large and regulated enterprises
- Vendor-managed or jointly managed
On-Premises
Customer data centre or private environment with full data residency and control.
- Customer data centre or private environment
- Customer-controlled infrastructure and data residency
- Signed licence and controlled release packages
Shared responsibility
In SaaS, the vendor owns infrastructure, monitoring, and backups end to end. In dedicated cloud, responsibility is shared or fully vendor-managed depending on contract. On-premises, the customer owns infrastructure, backups, and monitoring unless a managed service is separately contracted — the platform ships with backup/restore scripts and validation either way.
Upgrades, support, and data residency
SaaS receives continuous, vendor-managed releases. Dedicated cloud is upgraded on coordinated release windows. On-premises upgrades ship as signed, offline release bundles the customer schedules. Dedicated cloud and on-premises support customer-controlled data residency and, where required, customer-managed encryption keys.