Skip to content
Beta

Build a Governed Platform with the Landing Zone Configurator

Last updated on

Stackit LogoStackit Logo
STACKIT

Build a Governed Platform with the Landing Zone Configurator

Guide Platform Engineers from landing-zone requirements through reviewed platform deployment to reusable project templates and application self-service.

PLAN

Align the Platform Requirements

Bring organization structure, ownership, compliance, connectivity, and workload discovery into one baseline. Start this platform stream early enough to support the first migration wave.

Design and mobilizeLanding zonesOverview In 6 trails

To design a landing zone effectively, enterprises usually provide:

  • Organization and ownership model: Entities, project boundaries, and accountability model.
  • Compliance and policy requirements: Regulatory obligations and internal control policies.
  • Security requirements: IAM standards, network segmentation, encryption, and logging expectations.
  • Operations and support constraints: Incident handling, escalation paths, and handover model.
  • Application portfolio insights: Discovery findings about workload archetypes and dependencies.
OPS

Connect the Accelerator and Configurator

Open the Landing Zone Configurator demo

The Accelerator provides reusable infrastructure code; teams use it directly through CLI and pipelines or through the Configurator's editor, templates, and authorized Runner

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.

Explore the Landing Zone Accelerator
BASE

Understand the Execution Model

The Web UI uses the Configurator API for validation, Assistant proposals, templates, and job orchestration; an isolated OpenTofu Runner provisions customer landing zones

The browser brings editor, chat, catalog, and job views together. The Configurator API coordinates identity, validation, Assistant proposals, versioned templates, and deployment jobs. STACKIT Model Serving supplies the models used by the Assistant.

An isolated Runner performs the authorized infrastructure operation with the versioned Accelerator. Configuration and job records support continuity across the workflow, while technical credentials are handled through the separate credential-management path.

BASE

Establish Workspace and Ownership

Open the hosted Configurator and establish the context for the work before choosing a configuration or project offering.

Ready to continue: The team knows where it is working, who owns the result, and which delivery workflow to follow.

Open the Configurator
AUTO

Choose the Reference Topology

The repository provides eight reference configurations in src/config/. Choose the simplest topology that satisfies the required network, security, organizational, tenant, and regional boundaries.

Decision: Record the reference configuration, domain boundaries, address plan, and owning teams. Carry those choices into the Configurator before adding optional platform services.

STEP

Configure and Version the Platform Baseline

Output: A coherent platform draft connecting the reference topology to the organization’s requirements. Save the reviewed configuration as the basis for platform delivery and template preparation.

Review checkpoint: Confirm the saved revision, intended target, and change owner before moving from configuration work to infrastructure execution.

OPS

Review Assistant Proposals

Describe the intended outcome in the context of the configuration: for example, a shared corporate network with application projects for development and production. The Assistant helps explain the available configuration and proposes changes for review.

  1. Describe the requirement and the choices already agreed with the platform team.
  2. Review the field-by-field differences and answer any clarification questions.
  3. Accept the desired changes into the configuration draft.
  4. Review the full configuration and save it explicitly.
  5. Continue with the deployment review when you are ready to provision.

Human decisions remain visible throughout: accepting a proposal updates the draft, saving records the configuration, and approving deployment starts the infrastructure change.

OPS

Prepare and Review the Platform Plan

Create a Plan from the saved platform configuration, intended deployment target, and authorized credential profile. Follow the execution output and use the proposed resource changes as the basis for the deployment decision.

Decision: Accept the reviewed saved Plan for explicit Apply, or return to the configuration with a clear change request.

LIVE

Apply and Validate the Platform

A draft is reviewed and saved, then a Plan is created and reviewed before a separate Apply decision starts the Runner and produces an environment for validation

The Configurator coordinates the job; the isolated Runner executes the versioned Accelerator with OpenTofu. Authorize Apply of the reviewed saved Plan and follow the job to its result.

  • Validate the foundation: Check the delivered organization structure, shared connectivity, and selected platform services against the reviewed design.
  • Record the baseline: Retain the configuration revision, deployment reference, and platform target for later application delivery.
  • Accept ownership: Identify the responsible platform team and agree operational handover.

Output: An accepted shared foundation from which the team can publish application project offerings.

BASE

Design Templates and Publish the Catalog

Turn the platform design into a small set of project offerings that application teams can understand and reuse.

Output: A reviewed project template draft with a clear purpose, target, parameter contract, and owning platform team.

Review the template, bind it to the intended platform target, and publish a version for the permitted catalog audience.

Outcome: A reusable catalog offering. Existing instances retain their selected version; subsequent publications become new choices for application delivery.

AUTO

Pilot with an Application Owner

Validate the offering with an Application Owner before repeating it across teams and migration waves.

Output: A demonstrated self-service path and a short feedback list for the next template version. Agree the owner of each improvement before expanding the catalog.

Follow the Application Owner workflow
GOAL

Hand Over and Improve the Baseline

Use instance and job history to retain the relationship between configuration, selected template version, execution, and outcome. Review drift as a separate maintenance activity. Treat a version change as a reviewed delivery decision, and use an explicit deletion workflow when retiring an application environment.

Feed lessons from pilot workloads and migration waves into the next platform configuration and template versions. This closes the loop from platform standards to application delivery and back into continuous improvement.

Outcome: A repeatable lifecycle in which the current environment stays understandable and improvements become reusable for the next application team.

Trail historyAdded Nov 10, 2026LWUpdatedNo updates · 1 bar = 1 week i
Maintainer
LWLukas WeberrußHead of STACKIT Cloud Migration Framework · STACKITOwnerActive 12 of the last 12 weeks · 58 updatesSTACKITwww.linkedin.com/in/lukas-weberruß-a360b081Contributed in STACKIT