Platform Landing Zone
Company-wide foundation for governance, identity, security, networking, cost controls, and automation.
Open Platform Landing ZoneNo login. Sent to the Framework Core Team. The page link is included automatically.
Send your feedback via email now.
Open your email client and create a new email.
Copy the email address and paste it into the To: field:
Copy your feedback text and paste it into the email body (Ctrl+V / Cmd+V):
Last updated on
Explore STACKIT landing-zone design, Accelerator topologies, Configurator workflows, application self-service, and managed delivery in one guided journey.
STACKIT
Explore the STACKIT service portfolio in an interactive map and open product documentation for compute, storage, networking, data, AI, and developer tools.
The sovereign European cloud provider behind the framework, delivering IaaS and PaaS from its own data centers in Germany and Austria.
Hover over a country to highlight its regions. Hover over EU01 or EU02 to show documented region details. Keyboard users can focus the countries and region labels with Tab; on a touch screen, tap a region label.
STACKIT
Explore the STACKIT service portfolio in an interactive map and open product documentation for compute, storage, networking, data, AI, and developer tools.
The sovereign European cloud provider behind the framework, delivering IaaS and PaaS from its own data centers in Germany and Austria.
A landing zone is the shared runway for governed migration. Establish its platform stream during Design and Mobilize, so migration waves inherit a working baseline for controlled delivery and stable operations.
Introduce a landing zone as the structured cloud foundation for governed operations on STACKIT. Use this opening to align stakeholders on the key questions: which guardrails are mandatory, who owns them, and what application needs must be supported.
A landing zone is the structured cloud foundation that defines how your organization operates on STACKIT from day 1. It combines governance, identity, security, network design, cost controls, and automation into one coherent baseline.
Without this foundation, migration waves typically stall due to missing approvals, inconsistent controls, and repeated platform decisions.
The following visual summarizes the core components that should be addressed for a reliable platform baseline.
Start the landing-zone stream as early as possible, in parallel with discovery.
The practical model is a dual track: establish the platform baseline early, then refine application landing zone templates as discovery insights mature.
Platform Landing Zone
Company-wide foundation for governance, identity, security, networking, cost controls, and automation.
Application Landing Zone
Workload-specific implementation patterns derived from the platform baseline and discovery findings.
To design a landing zone effectively, enterprises usually provide:
The Landing Zone Accelerator provides the reusable infrastructure modules and reference topologies. The Landing Zone Configurator adds guided configuration, Assistant-supported review, project template publication, and application self-service on that foundation.
Use the practical Trails to connect the architecture to each team’s delivery workflow.
The following assets provide implementation foundations and delivery approaches:
trueLukas WeberrußLukas WeberrußHead of STACKIT Cloud Migration Framework · STACKITOwnerActive 12 of the last 12 weeks · 58 updates
Lukas WeberrußLukas WeberrußHead of STACKIT Cloud Migration Framework · STACKITOwnerActive 12 of the last 12 weeks · 58 updates
Lukas WeberrußLukas WeberrußHead of STACKIT Cloud Migration Framework · STACKITOwnerActive 12 of the last 12 weeks · 58 updates
Lukas WeberrußLukas WeberrußHead of STACKIT Cloud Migration Framework · STACKITOwnerActive 12 of the last 12 weeks · 58 updates
Tobias M.Tobias M.Head of STACKIT Cloud Framework · STACKITOwnerActive 11 of the last 12 weeks · 196 updates
Tobias M.Tobias M.Head of STACKIT Cloud Framework · STACKITOwnerActive 11 of the last 12 weeks · 196 updates
Tobias M.Tobias M.Head of STACKIT Cloud Framework · STACKITOwnerActive 11 of the last 12 weeks · 196 updates
Lukas WeberrußLukas WeberrußHead of STACKIT Cloud Migration Framework · STACKITOwnerActive 12 of the last 12 weeks · 58 updates
Lukas WeberrußLukas WeberrußHead of STACKIT Cloud Migration Framework · STACKITOwnerActive 12 of the last 12 weeks · 58 updates
Lukas WeberrußLukas WeberrußHead of STACKIT Cloud Migration Framework · STACKITOwnerActive 12 of the last 12 weeks · 58 updates
Tobias M.Tobias M.Head of STACKIT Cloud Framework · STACKITOwnerActive 11 of the last 12 weeks · 196 updates
Lukas WeberrußLukas WeberrußHead of STACKIT Cloud Migration Framework · STACKITOwnerActive 12 of the last 12 weeks · 58 updates
Tobias M.Tobias M.Head of STACKIT Cloud Framework · STACKITOwnerActive 11 of the last 12 weeks · 196 updates
STACKIT · Jul 7, 2026
Explain shared platform responsibilities, application ownership and their contract. Use central audit logging and the approved sandbox exception to make the boundary concrete.
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.
Establish the organizational structure, project boundaries, and ownership model that make landing-zone governance repeatable across teams and environments.
IAM ensures that every action on the platform is attributable, authorized, and aligned with enterprise security requirements.
For migration landing zones, IAM is the control backbone that connects human identities, machine identities, and authorization rules into one governable operating model.
Use this semantic map as a structured entry point into all subtopics of this module.
Map security and compliance topics early so control requirements, evidence, sovereignty decisions, and zero-trust principles inform the landing-zone design.
Use this semantic map as a structured entry point into all subtopics of this module.
In landing zones, Security, and Compliance are implementation constraints that must follow the cross-cutting design baseline from the dedicated module.
Use this page to apply module outcomes to platform and application landing-zone decisions.
Translate the compute-hardening recommendations into an owned, testable VM baseline before onboarding workloads.
The security of your virtual machines (VMs) is paramount to ensuring the integrity of your infrastructure. The following are recommended measures to harden the security of your VMs:
sudo for administrative tasks instead. Implement strong password policies and remove or disable unused users and groups. For secure authentication, we recommend using SSH keys.chmod and chown. The sticky bit should be set for global directories, such as /tmp, and ensure that there are no non-root files in directories such as /bin, /usr/bin, and /sbin.iptables or firewalld, and allow only necessary ports. Deny all access by default and whitelist only the necessary services. You can also use STACKIT Security Groups to allow only necessary ports.sshd\_config. Use SSH keys instead of passwords and disable empty passwords by setting PermitEmptyPasswords no.You can find additional recommendations and guidelines at the following links:
This section is copied from the STACKIT docs automatically, several times a day. It cannot be changed here. Changes belong in the STACKIT docs.
Validate service-local access rules separately from network routing. The following ACL behavior is specific to PostgreSQL Flex; confirm the corresponding rules for every other managed service rather than assuming identical defaults.
With the ACL entries, you control which source IPs are allowed to connect to your instance. Note, that this is an additional security layer and does not replace the need for proper authentication and security best practices. There are two predefined entries: 193.148.160.0/19 and 45.129.40.0/21. They ensure that you can access your instance from STACKIT cloud services. If you want to access your instance from the public net, you need to add the client’s IPv4 address or subnet. The entries follow the CIDR notation. If you want to allow a single IP address (e.g. single host), then set 32as the subnet parameter. E.g. to allow a host with the source IPv4 address of 93.229.84.137, add 93.229.84.137/32 as ACL entry. At the moment, you can’t add IPv6 addresses.
Do not set 0.0.0.0/0 as an ACL IP, because then your instance can be accessed from every IP.
This section is copied from the STACKIT docs automatically, several times a day. It cannot be changed here. Changes belong in the STACKIT docs.
Define segmentation, connectivity, DNS, routing, and secure communication patterns for shared services and workload environments.
Confirm the product connectivity boundaries before choosing a topology. Network Area scope, route precedence, and VPN gateway behavior constrain the design; they do not replace the workload connectivity matrix or security approval.
The source shows pictures here that this page leaves out (1). See them in Concepts
The STACKIT Network Area (SNA) allows projects within an organization to be connected to each other on a network level. This makes it possible to connect various resources of the projects within an SNA and also simplifies the connection with on-prem environments (hybrid cloud).
An SNA project differs from a public project in the fact that it is connected to an internal transfer network. When creating a network in a SNA project, the address range is defined using the specified prefix length from the network ranges of the SNA. To make the connectivity within the SNA projects available, the project router gets connected to the SNA transfer network. When editing the networks of SNA projects, the routing table of all project routers is automatically adjusted, no manual adjustment is necessary. Access control at network level is carried out exclusively by security groups, all incoming traffic is denied by default.
SNA is a global resource which you need to enable for the regions you want to use it in. Currently traffic between regions is only possible via the public internet. Private connectivity between regions inside of an SNA is planned for the future.
Example topology of an SNA with 2 projects:
This section is copied from the STACKIT docs automatically, several times a day. It cannot be changed here. Changes belong in the STACKIT docs.
Routing tables consist of different types of routes serving different purposes and having a different priority in the overall routing context. Route types with a higher priority value are preferred over lower priority ones if they have the same prefix length. If routes of the same route type have the same prefix length, equal-cost-multi-path (ECMP) is performed.
| priority | route type | description |
|---|---|---|
| 4 | system routes | System routes are automatically generated routes for connectivity between projects inside an SNA. System routes are enabled by default for routing tables but can be disabled to manage traffic and isolation within a network environment. |
| 3 | service routes | Service routes are routes which are added by a STACKIT service to reach it. Service routes are always enabled and can’t be disabled/removed by the user directly. |
| 2 | static routes | Static routes are routes which are added by a user. They can have different next-hops such as an IP-address, black hole or the internet. |
| 1 | dynamic routes | Dynamic routes are routes which are learned through a dynamic routing protocol like BGP. Dynamic routes are enabled by default for routing tables but can be disabled. |
This section is copied from the STACKIT docs automatically, several times a day. It cannot be changed here. Changes belong in the STACKIT docs.
A Virtual Private Network (VPN) with STACKIT creates a secure, encrypted connection over the internet between your remote network and your STACKIT Network Area (SNA). This secure tunnel allows data to be transmitted safely, protecting it from eavesdropping, interception, or unauthorized access.
With STACKIT VPN, you can securely connect to your STACKIT Network Area, enabling access to its resources as if you were directly connected to the remote network. This capability is particularly useful for accessing services, applications, and data within the SNA from remote locations, ensuring both privacy and security in all communications.
A STACKIT VPN typically consists of two key components; the VPN gateway and the VPN connection:
STACKIT VPN is an essential tool for securely connecting distributed resources, enabling remote access to cloud-based services while maintaining the integrity and privacy of your data within the STACKIT cloud environment.
This section is copied from the STACKIT docs automatically, several times a day. It cannot be changed here. Changes belong in the STACKIT docs.
trueLukas WeberrußLukas WeberrußHead of STACKIT Cloud Migration Framework · STACKITOwnerActive 12 of the last 12 weeks · 58 updates
Tobias M.Tobias M.Head of STACKIT Cloud Framework · STACKITOwnerActive 11 of the last 12 weeks · 196 updates
Lukas WeberrußLukas WeberrußHead of STACKIT Cloud Migration Framework · STACKITOwnerActive 12 of the last 12 weeks · 58 updates
Lukas WeberrußLukas WeberrußHead of STACKIT Cloud Migration Framework · STACKITOwnerActive 12 of the last 12 weeks · 58 updates
Tobias M.Tobias M.Head of STACKIT Cloud Framework · STACKITOwnerActive 11 of the last 12 weeks · 196 updates
Lukas WeberrußLukas WeberrußHead of STACKIT Cloud Migration Framework · STACKITOwnerActive 12 of the last 12 weeks · 58 updates
Tobias M.Tobias M.Head of STACKIT Cloud Framework · STACKITOwnerActive 11 of the last 12 weeks · 196 updates
STACKIT · Jul 7, 2026
Cost management makes cloud spend visible, attributable, and controllable across migration waves and steady-state operations.
For migration landing zones, this requires a shared financial control model across platform teams, application teams, and business stakeholders.
FinOps should be embedded from the beginning of landing zone design, not added after migration waves start.
Governance and Decision Making and Measurement and Continuous Improvement assign FinOps decision rights and turn financial signals into improvement actions.
Automation ensures that landing-zone capabilities are reproducible, versioned, and tested instead of manually configured.
For migration landing zones, automation is the delivery backbone that connects platform APIs, IaC tools, developer workflows, and release controls into one reliable operating model.
The STACKIT Landing Zone Accelerator provides reusable OpenTofu/Terraform modules for the platform and application project baseline. Teams can use native inputs through CLI and their own delivery pipelines, including a separate application root with its own state.
The STACKIT Landing Zone Configurator provides a guided workflow around the same foundation: edit and review configuration, publish reusable project templates, then prepare and review infrastructure changes before explicitly authorizing Apply. Its isolated Runner executes the versioned Accelerator with OpenTofu.
Choose and document the change owner and delivery path for each environment. Configuration exports and optional GitHub versioning connect the guided workflow to the team’s IaC process.
Terraform or OpenTofu and Ansible solve different parts of one delivery workflow. Keep the boundary explicit so infrastructure changes remain reviewable and host configuration remains repeatable.
Terraform / OpenTofu
Own the infrastructure lifecycle: projects, networks, security controls, compute, storage, managed services, and the outputs required by configuration management.
Ansible
Own configuration inside the reachable target: operating-system packages, middleware, application artifacts, service units, and workload-level validation.
Do not use provisioners or ad hoc scripts to blur ownership between both layers. Triggering Ansible from Terraform can be a practical bridge, but each tool must remain independently understandable, testable, and rerunnable.
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.
Use the selected R-strategy and target architecture for each application to derive the landing-zone capabilities, controls, connectivity, and service patterns its migration requires.
The R-strategy model is the core decision framework in this module. For each application, the selected R-strategy must be justified with architecture, business, risk, and operability evidence.
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:
The following diagram shows how Discovery transforms technical and stakeholder input into decision-ready outputs for the downstream modules.
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.
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 following diagram shows how Discovery transforms technical and stakeholder input into decision-ready outputs for the downstream modules.
This asset provides a reusable foundation for implementing a STACKIT platform landing zone. It is designed for enterprise environments that need a structured baseline for governance, security, networking, cost controls, and automation.
Repository:
The repository provides reusable modules, reference configurations, and independently usable platform and application delivery paths.
src/main.tf orchestrates the platform building blocks and supports combined platform/application configurations.src/application/ provisions one application instance from reviewed platform references, with its own backend and state.src/config/.STACKIT
STACKIT base asset for building a platform landing zone with reusable OpenTofu/Terraform modules, enterprise baseline patterns, and central Kubernetes.
The sovereign European cloud provider behind the framework, delivering IaaS and PaaS from its own data centers in Germany and Austria.
The repository provides eight reference configurations in src/config/. Choose the simplest
topology that satisfies the required network, security, organizational, tenant, and regional
boundaries.
| Design question | Reference configurations | Choose this when |
|---|---|---|
| Does the pilot need its own independent network? | Standalone | A small foundation and public application environment are the right starting point |
| Do corporate workloads share private connectivity? | Hub-and-spoke | Application projects need a common Network Area and shared DNS |
| Does corporate egress need a central inspection point? | Hub-and-spoke with firewall | The network design calls for shared firewall inspection and controlled egress |
| Which domains need separate foundations? | Finance/research, regulated/shared, production/non-production, tenant isolation, or regional hubs | Ownership, network, environment, tenant, or regional boundaries determine the topology |
Decision: Record the reference configuration, domain boundaries, address plan, and owning teams. Carry those choices into the Configurator before adding optional platform services.
This asset provides a reusable foundation for implementing a STACKIT platform landing zone. It is designed for enterprise environments that need a structured baseline for governance, security, networking, cost controls, and automation.
Repository:
The repository provides reusable modules, reference configurations, and independently usable platform and application delivery paths.
src/main.tf orchestrates the platform building blocks and supports combined platform/application configurations.src/application/ provisions one application instance from reviewed platform references, with its own backend and state.src/config/.The repository provides eight reference configurations in src/config/. Choose the simplest
topology that satisfies the required network, security, organizational, tenant, and regional
boundaries.
| Design question | Reference configurations | Choose this when |
|---|---|---|
| Does the pilot need its own independent network? | Standalone | A small foundation and public application environment are the right starting point |
| Do corporate workloads share private connectivity? | Hub-and-spoke | Application projects need a common Network Area and shared DNS |
| Does corporate egress need a central inspection point? | Hub-and-spoke with firewall | The network design calls for shared firewall inspection and controlled egress |
| Which domains need separate foundations? | Finance/research, regulated/shared, production/non-production, tenant isolation, or regional hubs | Ownership, network, environment, tenant, or regional boundaries determine the topology |
Decision: Record the reference configuration, domain boundaries, address plan, and owning teams. Carry those choices into the Configurator before adding optional platform services.
src/modules/governance)Purpose:
platform, landing_zones_corporate, landing_zones_public, sandboxes).Landing-zone classification:
src/modules/management)Purpose:
Landing-zone classification:
src/modules/connectivity)Purpose:
Landing-zone classification:
src/modules/devops)Purpose:
Landing-zone classification:
Choose the smallest accelerator topology when workloads need independent networks and direct internet access without shared private connectivity.
Introduce a central connectivity project, shared Network Area, and DNS when corporate workloads need private east-west communication.
Extend hub-and-spoke with an OPNsense firewall when corporate traffic requires a consistent inspection point and controlled egress path.
Give finance and research independent ownership, address plans, connectivity projects, and private workload domains inside one organization.
Create distinct Network Areas and DNS zones when regulated and shared workloads must have no implicit private routing between them.
Deploy isolated foundations in eu01 and eu02 when regional workloads need their own connectivity, landing-zone, and platform boundaries.
Use separate Network Areas and firewalls when production requires a stronger boundary while development and test can share a non-production domain.
Create independent ownership, address plans, and private connectivity domains when multiple tenants share the organization but must not route to one another.
src/modules/landing-zone)Purpose:
for_each).Landing-zone classification:
src/modules/sandboxes)Purpose:
sandboxes folder.Landing-zone classification:
governancemanagementconnectivitydevopslanding-zone (core ALZ provisioning)sandboxes (supporting ALZ-adjacent environments)This means the repository delivers a strong platform baseline first, while ALZ capabilities are intentionally focused on project landing-zone provisioning and team sandbox enablement.
landing-zone map in your variable files.STACKIT
Configure STACKIT foundations, publish reusable project templates, and provision application landing zones through guided, role-based self-service.
The sovereign European cloud provider behind the framework, delivering IaaS and PaaS from its own data centers in Germany and Austria.
The Landing Zone Accelerator supplies the OpenTofu/Terraform modules and reference configurations. It is the infrastructure foundation for governance, identity, networking, shared services, and application projects.
The Landing Zone Configurator adds the working experience around that foundation: a visual editor, an Assistant, versioned project templates, and controlled infrastructure execution. Both direct IaC use and the guided Configurator workflow build on the Accelerator. Teams choose the working approach that fits their operating model.
STACKIT
Configure STACKIT foundations, publish reusable project templates, and provision application landing zones through guided, role-based self-service.
The sovereign European cloud provider behind the framework, delivering IaaS and PaaS from its own data centers in Germany and Austria.
| Responsibility | Platform Engineer | Application Owner |
|---|---|---|
| Design shared governance, networks, and platform services | Defines and maintains the baseline | Provides workload requirements |
| Prepare reusable application project templates | Sets fixed values and exposed parameters | Provides feedback from application delivery |
| Publish reviewed template versions | Publishes versions for the permitted audience | Selects an available version |
| Request an Application Landing Zone | Enables the catalog and its target bindings | Supplies the project parameters and places the order |
| Review and execute changes | Reviews platform changes with the authorized execution path | Reviews and starts authorized application deployment |
| Accept the environment and hand it into operations | Owns the shared platform baseline | Owns the application’s environment and workload handover |
Select the organization and working environment for the task. STACKIT sign-in establishes identity; workspace membership, catalog access, and technical execution permissions establish what each person can do. Assign membership administration and credential delegation to the appropriate responsible people.
Use audit logging as the running example: governed application projects follow the central rule; the Platform Owner explicitly approves the sandbox exception.
Choose the reference configuration in the editor and align folders, connectivity and shared services with the governed application domain and sandbox boundary.
The Platform Owner publishes the rule in the template. The Application Owner selects an approved version and supplies exposed parameters, but cannot disable mandatory audit logging. An approved sandbox is a separate offering.
In this audit example, the Application Landing Zone's Telemetry Link sends events to the platform Telemetry Router. It forwards directly to Loki inside Observability and, in parallel, to the S3 archive. Grafana makes the events searchable.
The dashboard makes the shared audit path visible: event volume, regional activity, HTTP methods and API actions. Use the filters to narrow the view, then inspect an individual event in the raw audit log list.
STACKIT
Configure STACKIT foundations, publish reusable project templates, and provision application landing zones through guided, role-based self-service.
The sovereign European cloud provider behind the framework, delivering IaaS and PaaS from its own data centers in Germany and Austria.
Use the Assistant to turn the Platform Owner’s rule into a reviewable configuration proposal. Begin with the agreed scope and the intended central services:
Prepare central audit logging for our governed application scope, with an S3 archive and direct ingestion into Loki within Observability. Keep the approved sandbox outside that collection scope. Ask me to confirm retention, reader access and Object Lock choices.
Review the proposal against this platform design and the chosen scope. Check the router’s two destinations, the Observability/Loki ingestion path and reader access. Keep mandatory audit behavior fixed in the governed project template; publish the approved sandbox as a separate offering. Accept, save, Plan and Apply remain separate actions.
Prepare the Plan from the saved revision, inspect shared resources and both audit destinations, then explicitly authorize Apply of the reviewed saved Plan.
Find a controlled project's event in the archive and the Loki-backed investigation view. Confirm the sandbox boundary before accepting the platform.
Prepare the revisioned, non-secret Platform Contract and companion service/policy references as the handoff from a deployed platform to application delivery.
STACKIT
Configure STACKIT foundations, publish reusable project templates, and provision application landing zones through guided, role-based self-service.
The sovereign European cloud provider behind the framework, delivering IaaS and PaaS from its own data centers in Germany and Austria.
The Application Owner consumes the platform offering, rather than configuring the platform.
A sandbox is a separate approved choice, not an audit bypass switch on a governed project. The detailed application workflow remains in the dedicated self-service Trail.
The Web UI and Configurator API guide configuration and review. The isolated Runner executes the Accelerator with OpenTofu against the customer's landing zones.
The Application Landing Zone is the target environment for the next delivery stage. Bring its project, network, identity, and service references into the workload runbook. Review workload-specific access, connectivity, observability, and recovery arrangements with the migration team before starting the wave.
For VMware Relocate, connect the prepared environment to the existing VM landing-zone and migration-tool runbooks. For other workload types, use the relevant target architecture and delivery workflow. Keep the environment acceptance and workload acceptance as identifiable milestones with named owners.
The STACKIT Landing Zone Accelerator provisions the platform baseline as code. This reference architecture adds the layer above it: meshStack registers the STACKIT platform, its landing zones and a set of building block definitions, so application teams order STACKIT projects and routed networks themselves instead of filing a ticket with the platform team.
It is implemented as OpenTofu in the meshStack Hub and deployed once per workspace.
The Accelerator’s management module creates an automation service account, assigns it owner at organization scope, and stores its key in Secrets Manager.
That is exactly the credential this reference architecture needs: it takes one STACKIT service account key with resource-manager.admin on the organization.
So the two run together as one stack — deploy the Accelerator, read the automation key from Secrets Manager, and hand it to the meshStack landing zone.
| Responsibility | Platform Team | Application Team |
|---|---|---|
| Provision the STACKIT platform baseline with the Accelerator | ✅ | ❌ |
| Register the platform, landing zones and building block definitions | ✅ | ❌ |
| Choose the shared address plan (when networking is enabled) | ✅ | ❌ |
| Request STACKIT projects through a landing zone | ❌ | ✅ |
| Order routed networks inside their own projects | ❌ | ✅ |
| Operate the workloads inside their projects | ❌ | ✅ |
STACKIT Project platform is registered in meshStack together with its landing zones, wired to the service account that creates projects.stackit/project building block definition that application teams order to get a STACKIT project, with meshStack roles mapped to STACKIT project roles.stackit/network building block. Each order draws its subnet from the shared plan, so two teams cannot collide on CIDR ranges.STACKIT Project Starterkit definition that composes the two building blocks above into one order. It is always registered, and the landing zones it offers are the ones the deployment actually created.Leaving the network configuration unset deploys the sandbox foundation only, which is the smallest useful starting point.
STACKIT
STACKIT managed service for consulting, setup, and implementation of enterprise landing zones using OpenTofu, `Terragrunt`, and boilerplate accelerators.
The sovereign European cloud provider behind the framework, delivering IaaS and PaaS from its own data centers in Germany and Austria.
This managed asset builds on the STACKIT landing zone foundation and adds structured advisory, setup support, and implementation guidance as a service.
It supports organizations that need both technical accelerators and delivery governance to establish a production-ready cloud baseline.
Terragrunt, and boilerplate patterns.Typical engagements run in close collaboration with platform, security, and application stakeholders. The service can be delivered as a focused setup initiative or integrated into a broader migration factory program.
The STACKIT Landing Zone Accelerator provisions the platform baseline as code. This reference architecture adds the layer above it: meshStack registers the STACKIT platform, its landing zones and a set of building block definitions, so application teams order STACKIT projects and routed networks themselves instead of filing a ticket with the platform team.
It is implemented as OpenTofu in the meshStack Hub and deployed once per workspace.
The Accelerator’s management module creates an automation service account, assigns it owner at organization scope, and stores its key in Secrets Manager.
That is exactly the credential this reference architecture needs: it takes one STACKIT service account key with resource-manager.admin on the organization.
So the two run together as one stack — deploy the Accelerator, read the automation key from Secrets Manager, and hand it to the meshStack landing zone.
STACKIT Project platform is registered in meshStack together with its landing zones, wired to the service account that creates projects.stackit/project building block definition that application teams order to get a STACKIT project, with meshStack roles mapped to STACKIT project roles.stackit/network building block. Each order draws its subnet from the shared plan, so two teams cannot collide on CIDR ranges.STACKIT Project Starterkit definition that composes the two building blocks above into one order. It is always registered, and the landing zones it offers are the ones the deployment actually created.Leaving the network configuration unset deploys the sandbox foundation only, which is the smallest useful starting point.
| Responsibility | Platform Team | Application Team |
|---|---|---|
| Provision the STACKIT platform baseline with the Accelerator | ✅ | ❌ |
| Register the platform, landing zones and building block definitions | ✅ | ❌ |
| Choose the shared address plan (when networking is enabled) | ✅ | ❌ |
| Request STACKIT projects through a landing zone | ❌ | ✅ |
| Order routed networks inside their own projects | ❌ | ✅ |
| Operate the workloads inside their projects | ❌ | ✅ |
Lukas WeberrußLukas WeberrußHead of STACKIT Cloud Migration Framework · STACKITOwnerActive 12 of the last 12 weeks · 58 updates
Lukas WeberrußLukas WeberrußHead of STACKIT Cloud Migration Framework · STACKITOwnerActive 12 of the last 12 weeks · 58 updates
Lukas WeberrußLukas WeberrußHead of STACKIT Cloud Migration Framework · STACKITOwnerActive 12 of the last 12 weeks · 58 updates
Lukas WeberrußLukas WeberrußHead of STACKIT Cloud Migration Framework · STACKITOwnerActive 12 of the last 12 weeks · 58 updates
Lukas WeberrußLukas WeberrußHead of STACKIT Cloud Migration Framework · STACKITOwnerActive 12 of the last 12 weeks · 58 updates
Lukas WeberrußLukas WeberrußHead of STACKIT Cloud Migration Framework · STACKITOwnerActive 12 of the last 12 weeks · 58 updates
Tobias M.Tobias M.Head of STACKIT Cloud Framework · STACKITOwnerActive 11 of the last 12 weeks · 196 updates
Lukas WeberrußLukas WeberrußHead of STACKIT Cloud Migration Framework · STACKITOwnerActive 12 of the last 12 weeks · 58 updates
Lukas WeberrußLukas WeberrußHead of STACKIT Cloud Migration Framework · STACKITOwnerActive 12 of the last 12 weeks · 58 updates
Tobias M.Tobias M.Head of STACKIT Cloud Framework · STACKITOwnerActive 11 of the last 12 weeks · 196 updates
Lukas WeberrußLukas WeberrußHead of STACKIT Cloud Migration Framework · STACKITOwnerActive 12 of the last 12 weeks · 58 updates
Tobias M.Tobias M.Head of STACKIT Cloud Framework · STACKITOwnerActive 11 of the last 12 weeks · 196 updates
Lukas WeberrußLukas WeberrußHead of STACKIT Cloud Migration Framework · STACKITOwnerActive 12 of the last 12 weeks · 58 updates
Lukas WeberrußLukas WeberrußHead of STACKIT Cloud Migration Framework · STACKITOwnerActive 12 of the last 12 weeks · 58 updates
Lukas WeberrußLukas WeberrußHead of STACKIT Cloud Migration Framework · STACKITOwnerActive 12 of the last 12 weeks · 58 updates
Lukas WeberrußLukas WeberrußHead of STACKIT Cloud Migration Framework · STACKITOwnerActive 12 of the last 12 weeks · 58 updates
Lukas WeberrußLukas WeberrußHead of STACKIT Cloud Migration Framework · STACKITOwnerActive 12 of the last 12 weeks · 58 updates
Lukas WeberrußLukas WeberrußHead of STACKIT Cloud Migration Framework · STACKITOwnerActive 12 of the last 12 weeks · 58 updates
Lukas WeberrußLukas WeberrußHead of STACKIT Cloud Migration Framework · STACKITOwnerActive 12 of the last 12 weeks · 58 updates
Lukas WeberrußLukas WeberrußHead of STACKIT Cloud Migration Framework · STACKITOwnerActive 12 of the last 12 weeks · 58 updates
External link
This link goes to an external site outside STACKIT. We do not vet third-party content or downloads, so follow it only if you trust the source.