Choose who operates the platform. Keep responsibilities clear.
Choose the operating model around your team’s responsibilities and data requirements. The comparison below is a scoping guide; the agreed service scope defines the commitments for your environment.
| Area | Managed, customer-cloud | Self-hosted |
|---|---|---|
| Cloud accounts and workloads | Customer owns the accounts, applications, and data. | Customer owns and operates the environment. |
| Platform operation | Keystone operates the management service within the agreed scope. | Customer operates the platform; Keystone support is scoped separately. |
| Access and approvals | Customer authorizes connections and support access. | Customer defines and administers access. |
| Upgrades | Management service upgrades are handled by Keystone; changes in customer environments are coordinated. | Customer schedules and applies upgrades with agreed assistance. |
| Backups and recovery | Customer workload backups remain a customer responsibility unless explicitly included. | Customer defines backups and recovery for platform and workloads. |
| Incidents and support | Agree service boundaries, contacts, response coverage, and escalation. | Agree the support scope for customer-operated systems. |
Define the data boundary
Review what stays with you and what management information is shared. Hosted trials and external AI or monitoring services require their own scope review.
Start with a bounded evaluation
No automatic subscription follows a trial. Ongoing scope, service responsibilities, and commercial terms are agreed before you continue. See how we work.