DebugInit
Run DebugInit where your business requires.
Select the operating model that balances control, security, performance, compliance, cost and support.
Managed cloud • customer cloud • on-premises • hybrid • air-gapped
Five operating models
Control and operational burden move together. The third column is what each option actually asks of you.
| Model | Suits | What it means in practice |
|---|---|---|
| Managed cloud | Teams who want the system running, not the infrastructure | We run it: environments, patching, backup, monitoring and upgrades. Least operational burden, least direct control over the estate. |
| Customer cloud | Organisations with an existing cloud account and policy | It runs in your tenancy under your controls and your billing. You own the account boundary; we operate inside it. |
| On-premises | Data-residency or regulatory constraints that rule out cloud | Your hardware, your network, your operations team — with our support. The most control and the most work. |
| Hybrid | A processing boundary that has to stay inside, with the rest outside | Split by workload rather than by preference. Adds an integration surface that has to be designed, not assumed. |
| Air-gapped | Environments with no outbound connectivity by policy | Updates, models and support arrive through a controlled process instead of a network. Slowest to change; sometimes the only option. |
Scroll the table sideways to see every column.
Managed cloud, customer cloud, on-premises and hybrid deployments are available at launch. Air-gapped deployment is evaluated separately, based on the infrastructure, update, dependency, support and security requirements of the specific environment — it is not a default, click-to-buy option.
Responsibility matrix
Who operates what. Agreed before an engagement rather than discovered during an incident.
| Area | DebugInit | You |
|---|---|---|
| Infrastructure | Managed cloud: ours | Customer cloud, on-premises, air-gapped: yours |
| Patching and upgrades | We supply and schedule releases | Self-hosted: you apply them, on an agreed cadence |
| Backup and recovery | Managed cloud: run and tested by us | Self-hosted: your policy, our documented procedure |
| Monitoring | Application health and platform alerts | Self-hosted: host, network and capacity |
| Identity | The permission model and its enforcement | Your directory, your provisioning, your access reviews |
| AI providers | The gateway, and the ability to switch provider | Which provider is permitted, and where its data may go |
Scroll the table sideways to see every column.
Portability
A deployment decision should be reversible. The same platform runs across all five models, configuration is data rather than a bespoke build, and your business data is exportable on terms written into the agreement.
The same applies to AI: the model gateway sits in front of replaceable providers, so changing vendor — or moving inference inside a boundary — is a configuration decision rather than a migration project.
Design a deployment against your constraints
Bring the policy, the residency requirement or the network restriction you have to satisfy, and we will map it to a model and a responsibility split.