Account governance
Structure organizations, projects, and environments with clear ownership boundaries.
A platform landing zone is the company-wide target operating baseline for cloud adoption on STACKIT. It defines the cross-cutting controls and platform guardrails that every product team must inherit.
Without this baseline, migration teams usually face inconsistent controls, duplicated design decisions, and delayed approvals.
The platform owns the shared rules and services; each application team owns its workload and the resources it consumes within that baseline. An Application Landing Zone is therefore a consumer of the platform, not a second implementation of organization-wide governance.
| Boundary | Shared platform responsibility | Application responsibility |
|---|---|---|
| Organization and identity | Folder structure, approved roles and access patterns | Named project ownership and application access |
| Connectivity | Shared Network Areas, routing, DNS and central network services | Workload networks and connections within the approved target |
| Audit and evidence | Collection scope, Telemetry Router, archive and investigation services | Produce events in the governed project and use the agreed audit path |
| Delivery and operations | Versioned foundation, Platform Contract and service ownership | Independent application lifecycle, workload runbook and acceptance |
Example: The Platform Owner requires central audit logging for governed application projects and explicitly permits a separate sandbox exception. The platform implements the collection scope and shared destinations; application teams choose approved targets without redefining that rule.
Result: A clear handoff boundary: the platform supplies reviewed references and guardrails, while application delivery consumes them with explicit ownership.
Account governance
Structure organizations, projects, and environments with clear ownership boundaries.
Identity and access
Define IAM model, role patterns, least-privilege principles, and separation of duties.
Security and compliance
Implement mandatory controls, logging, evidence pathways, and policy enforcement.
Network architecture
Define segmentation, connectivity patterns, and secure communication standards.
Cost management
Establish tagging, budget controls, chargeback/showback, and cost transparency.
Automation
Provision and evolve the baseline through OpenTofu/Terraform-based Infrastructure as Code.