Deployment models
Delivered the way your infrastructure, licensing and risk posture require.
The same platform capability can be consumed as managed software, a managed service, a branded product, an isolated environment or a set of APIs. The model is selected during architecture and solution design.
01
SaaS
Managed cloud software with continuous upgrades, support, monitoring and configurable enterprise modules.
- Shared managed infrastructure
- Continuous release stream
- Configurable modules
- Standard SLAs
02
CaaS
Customized software capabilities delivered as a managed service around the client's business requirements.
- Capability-led scope
- Managed operation
- Custom engineering included
- Roadmap aligned to the client
03
White Label
Fully branded software with the client's identity, domain, interfaces, communications and operational flows.
- Client branding end-to-end
- Own domains and applications
- Branded notifications
- Client-facing ownership
04
Private Cloud
Dedicated deployment within an isolated cloud environment.
- Isolated resources
- Region selection
- Data-residency options
- Controlled release windows
05
On-Premise
Deployment inside the customer's approved infrastructure where supported.
- Customer-controlled infrastructure
- Network isolation
- Scheduled upgrade cycles
- Support model agreed per contract
06
API Infrastructure
Individual capabilities exposed through secure APIs for integration into existing enterprise systems.
- Capability-level consumption
- Sandbox and production keys
- Scoped permissions
- Webhooks and events
07
Dedicated Enterprise Instance
A separate environment with isolated resources, databases, configurations and release controls.
- Dedicated database
- Independent configuration
- Client-approved releases
- Isolated performance envelope
Commercial model
Custom pricing. No public tiers.
Pricing is determined by deployment model, integrations, transaction volume, infrastructure, users, modules and support requirements. We do not publish monthly plans for enterprise infrastructure.
Assessed during scoping
- Deployment model and hosting responsibility
- Modules enabled and custom engineering required
- Integration surface and third-party dependencies
- Expected transaction and user volumes
- Countries, currencies and operating entities
- Support, SLA and release-control requirements