Rehost-ready pattern
Minimal change target for VM-based workloads with inherited central controls.
An application landing zone is a workload-specific implementation blueprint derived from the platform landing zone baseline.
It translates enterprise guardrails into practical patterns for concrete application types, for example VM-centric Rehost, containerized workloads, or data platform workloads.
Application landing zones are not designed in isolation. They require validated discovery input for dependencies, data sensitivity, runtime behavior, and operational constraints.
Typical discovery-driven design inputs:
Rehost-ready pattern
Minimal change target for VM-based workloads with inherited central controls.
Container platform pattern
Segmented, policy-driven setup for Kubernetes-based workload groups.
Data workload pattern
Landing zone profile for data services, integration paths, and stricter controls.
Shared service pattern
Isolated setup for foundational services used by multiple product teams.
The STACKIT Landing Zone Configurator makes the project baseline available through role-based self-service. Platform Engineers define fixed settings and exposed parameters, bind the template to the platform target, and publish a reviewed version. Application Owners choose an available version and order a concrete application instance.
Each instance has its own lifecycle and state. Plan review and an explicit Apply decision connect the selected template to the delivered environment. Use the project and network references in the workload deployment or migration runbook, with clear ownership at handover.
Provision an Application Landing Zone through self-service Follow the Application Owner journey from workload requirements and template selection to deployment and operational ownership. Open page