Responsibility Model

This page defines who handles what across the Self-Managed, Co-Managed, and Launchpad 90 service models. Use it to understand the boundary between DevOpsCentral's platform responsibilities and your application-level responsibilities.

Legend

Symbol	Meaning
DevOpsCentral	DevOpsCentral is responsible
Customer	You (the customer) are responsible
Shared	Both parties share responsibility
Plan-dependent	Varies by Co-Managed tier or signed agreement

Infrastructure and Platform

Area	Self-Managed	Co-Managed Basic	Co-Managed Pro	Co-Managed Scale
Physical infrastructure, power, network, cooling	DevOpsCentral	DevOpsCentral	DevOpsCentral	DevOpsCentral
Hypervisor and OpenStack platform	DevOpsCentral	DevOpsCentral	DevOpsCentral	DevOpsCentral
VM provisioning and lifecycle	Customer	DevOpsCentral	DevOpsCentral	DevOpsCentral
VM operating system patching	Customer	DevOpsCentral	DevOpsCentral	DevOpsCentral
VM operating system configuration	Customer	Shared	Shared	Shared
Kubernetes control plane	Customer	DevOpsCentral	DevOpsCentral	DevOpsCentral
Kubernetes worker node OS patching	Customer	DevOpsCentral	DevOpsCentral	DevOpsCentral
Kubernetes version upgrades	Customer	DevOpsCentral	DevOpsCentral	DevOpsCentral
Kubernetes add-ons and CNI/CSI	Customer	DevOpsCentral	DevOpsCentral	DevOpsCentral

Monitoring and Incident Management

Area	Self-Managed	Co-Managed Basic	Co-Managed Pro	Co-Managed Scale
Infrastructure health monitoring	Customer	DevOpsCentral	DevOpsCentral	DevOpsCentral
Application health monitoring	Customer	Customer	DevOpsCentral	DevOpsCentral
Custom metrics and priority alerts	Customer	Customer	Customer	DevOpsCentral
Cloud infrastructure incident triage	DevOpsCentral	DevOpsCentral	DevOpsCentral	DevOpsCentral
Managed OS/Kubernetes incident triage	Customer	DevOpsCentral	DevOpsCentral	DevOpsCentral
Incident triage (application layer)	Customer	Customer	Shared	Shared
P1 incident acknowledgment and triage	Customer	Customer	Customer	DevOpsCentral
Cloud infrastructure incident remediation	DevOpsCentral	DevOpsCentral	DevOpsCentral	DevOpsCentral
Managed OS/Kubernetes incident remediation	Customer	DevOpsCentral	DevOpsCentral	DevOpsCentral
Incident remediation (application)	Customer	Customer	Customer	Customer

Backups and Data Protection

Area	Self-Managed	Co-Managed Basic	Co-Managed Pro	Co-Managed Scale
Daily backups	Customer	DevOpsCentral	DevOpsCentral	DevOpsCentral
Backup restore verification	Customer	Customer	DevOpsCentral	DevOpsCentral
Database backup configuration	Customer	DevOpsCentral	DevOpsCentral	DevOpsCentral
Database restore (platform-managed backups)	Customer	DevOpsCentral	DevOpsCentral	DevOpsCentral
DR planning	Customer	Customer	Customer	DevOpsCentral
DR recovery testing	Customer	Customer	Customer	DevOpsCentral
Application-level data export/import	Customer	Customer	Customer	Customer

CI/CD and Deployment

Area	Self-Managed	Co-Managed Basic	Co-Managed Pro	Co-Managed Scale
CI/CD platform operations	Customer	DevOpsCentral	DevOpsCentral	DevOpsCentral
CI/CD pipeline configuration	Customer	Customer	DevOpsCentral	DevOpsCentral
CI/CD pipeline maintenance and tuning	Customer	Customer	DevOpsCentral	DevOpsCentral
Release approval	Customer	Customer	Customer	Customer
Deployment execution	Customer	Customer	Shared	Shared

Database Management

Area	Self-Managed	Co-Managed Basic	Co-Managed Pro	Co-Managed Scale
Database server installation and configuration	Customer	DevOpsCentral	DevOpsCentral	DevOpsCentral
Database server patching and uptime	Customer	DevOpsCentral	DevOpsCentral	DevOpsCentral
Database backups (platform level)	Customer	DevOpsCentral	DevOpsCentral	DevOpsCentral
Schema design and changes	Customer	Customer	Customer	Customer
Query performance and optimisation	Customer	Customer	Customer	Customer
Data integrity	Customer	Customer	Customer	Customer

Database ownership within the managed scope

DevOpsCentral owns database server configuration, backups, patching, and uptime monitoring within the agreed managed scope of the platform. Customers always own schema design, queries, and data integrity. Proactive restore verification and DR testing vary by tier: see the Co-Managed Tiers table.

Application and Security

Area	Self-Managed	Co-Managed Basic	Co-Managed Pro	Co-Managed Scale
Application code development	Customer	Customer	Customer	Customer
Application deployment	Customer	Customer	Shared	Shared
Application-level security	Customer	Customer	Customer	Customer
Platform-level security (firewall, DDoS, network isolation)	DevOpsCentral	DevOpsCentral	DevOpsCentral	DevOpsCentral
Access management (your team)	Customer	Customer	Customer	Customer
Access management (platform)	DevOpsCentral	DevOpsCentral	DevOpsCentral	DevOpsCentral
Secrets management (application)	Customer	Customer	Customer	Customer
OS-level security hardening	Customer	DevOpsCentral	DevOpsCentral	DevOpsCentral

Key Distinctions

Managed Platform vs Application

The most important distinction in the responsibility model is the boundary between the managed platform and the application.

• Managed platform: DevOpsCentral always owns physical infrastructure and the OpenStack platform. Under Co-Managed, its responsibility extends to Kubernetes, worker-node OS, monitoring, and platform security within scope. Under Self-Managed, the customer owns VM OS, Kubernetes, and workload operations.
• Application: Your code, database schemas, queries, data, release approval, and application-level security. You own this regardless of service model.

RPO and RTO

Exact RPO (Recovery Point Objective) and RTO (Recovery Time Objective) are defined in the signed order or SLA, not in this documentation. The Co-Managed tiers determine whether backup, restore verification, and DR testing are included, but the specific targets are agreed per customer.

Related Pages

• Co-Managed DevOps — full service description
• Pricing Explained — invoice structure and plan costs
• Solutions Overview — compare all service models
• Terms & Conditions — legal framework
• Infrastructure — platform technical details
• Contact — reach the team

---

Clear responsibility boundaries for your infrastructure