---
title: Roles and Responsibilities
description: Define accountable cloud roles and shared responsibilities across platform, workload, security, FinOps, and service management teams.
sidebar:
  label: Roles and Responsibilities
  order: 2
source_url: "https://framework.stackit.cloud/migration/design-and-mobilize/operating-model/roles-and-responsibilities/"
source_file: "docs/migration/design-and-mobilize/operating-model/roles-and-responsibilities.mdx"
---

## Purpose

Clear ownership prevents delays between a STACKIT platform foundation and the teams operating migrated workloads. Document responsibilities with a RACI matrix and validate them against actual operational scenarios, not only organization charts.

## Core responsibilities

| Area | Accountable role | Typical responsibilities |
| --- | --- | --- |
| Platform foundation | Cloud Platform Owner | Landing-zone roadmap, shared guardrails, platform service quality, and provider coordination. |
| Workload operation | Application or Product Owner | Workload reliability, release readiness, data ownership, and business service outcomes. |
| Security and compliance | Security Owner | Control requirements, risk acceptance, assurance criteria, and security incident coordination. |
| Cloud costs | FinOps Lead | Cost allocation, budgets, optimization priorities, and financial reporting. |
| Service management | Service Owner | Support model, incident and change processes, service targets, and continual improvement. |

## Make shared boundaries explicit

Platform teams typically own reusable STACKIT account structures, access patterns, network connectivity, and baseline automation. Workload teams own their application configuration, data, releases, monitoring signals, and recovery procedures. Security and FinOps teams define cross-cutting requirements and support their implementation; they should not become an unbounded approval queue.

For every managed service or workload, clarify the boundary between STACKIT provider operations, the customer platform team, and the application team. Support plans, service documentation, and runbooks should point to the same ownership model.

## Related guidance

- [Platform Landing Zone](/migration/design-and-mobilize/landing-zones/platform-landing-zone/) defines the shared technical baseline owned by the platform team.
- [Application Landing Zone](/migration/design-and-mobilize/landing-zones/application-landing-zone/) defines the workload scope that application teams operate within central guardrails.
- [Security and Compliance: Operating Model and Governance](/migration/design-and-mobilize/security-and-compliance/operating-model-and-governance/) defines the security, compliance, and risk accountabilities that the RACI must include.

## Related assets

<ScfAssetLoader showFilter={false} showSearch={false} frameworkSlug="migration" filterByTag="operating-model" />