# What is the shared responsibility model for self-hosted software?

Canonical page: https://launchinyourcloud.com/questions/shared-responsibility/

It is the documented split of operating and security duties between your team, the software vendor and the hosting provider. Assign named owners for access, upgrades, backups, monitoring and incidents, with response times and a tested handoff.

Answer page: https://launchinyourcloud.com/questions/shared-responsibility/
Answer reviewed: 2026-11-21

- [Use the shared-responsibility guide](/guide/shared-responsibility/)
- [Download the shared-responsibility template](/downloads/shared-responsibility-template.md)


## Make each operating task assignable

“Managed” and “self-hosted” are too broad to assign on-call duties. An infrastructure provider can operate the physical hosts while your team remains responsible for the guest OS and application. A managed platform changes that split, but does not automatically take over application configuration or data recovery.

## Example responsibilities to record

- **Application upgrade:** who prepares, approves, executes and verifies it?
- **Backup and restore:** who takes the backup, controls access and demonstrates a restore?
- **Identity:** who grants access, reviews it and removes leavers?
- **Incident:** who detects the problem, declares it, communicates and restores service?

Use the downloadable matrix to record a primary owner, an escalation contact and a response target for each task. Test at least one handoff during the trial. A responsibility with two interested parties still needs one person accountable for making the work happen.

