---
title: "Build a Governed Platform with the Landing Zone Configurator"
description: "Guide Platform Engineers from landing-zone requirements through reviewed platform deployment to reusable project templates and application self-service."
scfTrail:
  tags: ["design-and-mobilize", "landing-zone", "dev-platform", "template"]
  maintainers:
    - user: "lukas.weberruss"
  steps:
    - style: "compass"
      id: "align-requirements"
      title: "Align the Platform Requirements"
      trailContext: "Bring organization structure, ownership, compliance, connectivity, and workload discovery into one baseline. Start this platform stream early enough to support the first migration wave."
      pageId: "migration/design-and-mobilize/landing-zones/overview#typical-enterprise-inputs"

    - style: "chart"
      id: "understand-the-tooling"
      title: "Connect the Accelerator and Configurator"
      trailContext: "Use the Accelerator as the infrastructure foundation and the Configurator as the guided workflow for editor changes, project templates, and authorized execution."
      assetId: "migration/assetcontainer/stackit/landing-zone-configurator.mdx#accelerator-and-configurator"

    - style: "hut"
      id: "understand-execution"
      title: "Understand the Execution Model"
      trailContext: "Connect editor and chat to the API's validation, templates, and orchestration. Use the isolated Runner as the execution path for the versioned Accelerator."
      assetId: "migration/assetcontainer/stackit/landing-zone-configurator.mdx#how-the-configurator-works"

    - style: "hut"
      id: "establish-ownership"
      title: "Establish Workspace and Ownership"
      trailContext: "Open the Configurator, sign in with STACKIT, and select the intended organization and working environment. Agree platform ownership, membership administration, catalog audience, and execution responsibilities."
      assetId: "migration/assetcontainer/stackit/landing-zone-configurator.mdx#start-in-your-workspace"

    - style: "gondola"
      id: "choose-topology"
      title: "Choose the Reference Topology"
      trailContext: "For a small pilot, start with a standalone foundation. For a corporate migration wave, select the shared connectivity and separation model agreed in the target design."
      assetId: "migration/assetcontainer/stackit/landing-zone-foundation-opentofu.mdx#deployment-flavours-and-what-they-enable"

    - style: "stairs"
      id: "configure-platform"
      title: "Configure and Version the Platform Baseline"
      splitRatio: 50
      left:
        - assetId: "migration/assetcontainer/stackit/landing-zone-configurator.mdx#configuration-decisions"
          cards: false
      right:
        - assetId: "migration/assetcontainer/stackit/landing-zone-configurator.mdx#versioning-choices"
          cards: false

    - style: "chart"
      id: "review-assistant-proposals"
      title: "Review Assistant Proposals"
      trailContext: "Describe the desired outcome, answer clarification questions, and inspect the proposed differences. Accept the changes that match the agreed platform design."
      assetId: "migration/assetcontainer/stackit/landing-zone-configurator.mdx#work-with-the-assistant"

    - style: "chart"
      id: "review-platform-plan"
      title: "Prepare and Review the Platform Plan"
      trailContext: "Choose the target and authorized credential profile, prepare the deployment, and request a Plan. Review the proposed resource changes against the saved configuration and platform design."
      assetId: "migration/assetcontainer/stackit/landing-zone-configurator.mdx#review-and-deploy-the-platform"

    - style: "rocket"
      id: "deploy-platform"
      title: "Apply and Validate the Platform"
      trailContext: "Authorize Apply of the reviewed saved Plan, follow the Runner job, and validate the resulting shared platform. Record the platform owner and operational handover."
      assetId: "migration/assetcontainer/stackit/landing-zone-configurator.mdx#apply-and-validate-the-platform"

    - style: "hut"
      id: "design-project-templates"
      title: "Design Templates and Publish the Catalog"
      splitRatio: 50
      left:
        - assetId: "migration/assetcontainer/stackit/landing-zone-configurator.mdx#design-project-templates"
          cards: false
      right:
        - assetId: "migration/assetcontainer/stackit/landing-zone-configurator.mdx#publication-decisions"
          cards: false

    - style: "gondola"
      id: "pilot-self-service"
      title: "Pilot with an Application Owner"
      trailContext: "Test the complete offering with an application team: discover the template, order a project, review the Plan, deploy, and accept the environment. Capture improvements before repeating the pattern."
      assetId: "migration/assetcontainer/stackit/landing-zone-configurator.mdx#pilot-application-self-service"

    - style: "summit"
      id: "handover-and-improve"
      title: "Hand Over and Improve the Baseline"
      trailContext: "Agree platform and application responsibilities, retain execution history, and bring pilot feedback into the next configuration and template versions. Repeat the pattern for subsequent teams and waves."
      assetId: "migration/assetcontainer/stackit/landing-zone-configurator.mdx#operate-and-evolve"

  presentations:
    - id: "platform-overview"
      label: "Platform overview"
      description: "A concise view of the platform-to-self-service model for architects and stakeholders."
      preset: "minimal"
      agenda: false
      steps:
        - "align-requirements"
        - "understand-the-tooling"
        - "establish-ownership"
        - "deploy-platform"
        - "design-project-templates"
        - "pilot-self-service"
    - id: "platform-walkthrough"
      label: "Platform Engineer walkthrough"
      description: "The complete workflow from requirements and topology to a reviewed platform and published project catalog."
      default: true
      launch: true
      preset: "focus"
      steps:
        - "align-requirements"
        - "understand-the-tooling"
        - "understand-execution"
        - "establish-ownership"
        - "choose-topology"
        - "configure-platform"
        - "review-assistant-proposals"
        - "review-platform-plan"
        - "deploy-platform"
        - "design-project-templates"
        - "pilot-self-service"
        - "handover-and-improve"
source_url: "https://framework.stackit.cloud/migration/trails/stackit/landing-zone-configurator-platform/"
source_file: "docs/migration/trails/stackit/landing-zone-configurator-platform.mdx"
---

## Steps

### 1. Align the Platform Requirements

Stage: `compass`

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

Page: [/migration/design-and-mobilize/landing-zones/overview/#typical-enterprise-inputs](/migration/design-and-mobilize/landing-zones/overview/#typical-enterprise-inputs) — source: [/raw/migration/design-and-mobilize/landing-zones/overview.md](/raw/migration/design-and-mobilize/landing-zones/overview.md), section `#typical-enterprise-inputs`

### 2. Connect the Accelerator and Configurator

Stage: `chart`

Use the Accelerator as the infrastructure foundation and the Configurator as the guided workflow for editor changes, project templates, and authorized execution.

Asset: [/migration/assetcontainer/stackit/landing-zone-configurator/#accelerator-and-configurator](/migration/assetcontainer/stackit/landing-zone-configurator/#accelerator-and-configurator) — source: [/raw/migration/assetcontainer/stackit/landing-zone-configurator.md](/raw/migration/assetcontainer/stackit/landing-zone-configurator.md), section `#accelerator-and-configurator`

### 3. Understand the Execution Model

Stage: `hut`

Connect editor and chat to the API's validation, templates, and orchestration. Use the isolated Runner as the execution path for the versioned Accelerator.

Asset: [/migration/assetcontainer/stackit/landing-zone-configurator/#how-the-configurator-works](/migration/assetcontainer/stackit/landing-zone-configurator/#how-the-configurator-works) — source: [/raw/migration/assetcontainer/stackit/landing-zone-configurator.md](/raw/migration/assetcontainer/stackit/landing-zone-configurator.md), section `#how-the-configurator-works`

### 4. Establish Workspace and Ownership

Stage: `hut`

Open the Configurator, sign in with STACKIT, and select the intended organization and working environment. Agree platform ownership, membership administration, catalog audience, and execution responsibilities.

Asset: [/migration/assetcontainer/stackit/landing-zone-configurator/#start-in-your-workspace](/migration/assetcontainer/stackit/landing-zone-configurator/#start-in-your-workspace) — source: [/raw/migration/assetcontainer/stackit/landing-zone-configurator.md](/raw/migration/assetcontainer/stackit/landing-zone-configurator.md), section `#start-in-your-workspace`

### 5. Choose the Reference Topology

Stage: `gondola`

For a small pilot, start with a standalone foundation. For a corporate migration wave, select the shared connectivity and separation model agreed in the target design.

Asset: [/migration/assetcontainer/stackit/landing-zone-foundation-opentofu/#deployment-flavours-and-what-they-enable](/migration/assetcontainer/stackit/landing-zone-foundation-opentofu/#deployment-flavours-and-what-they-enable) — source: [/raw/migration/assetcontainer/stackit/landing-zone-foundation-opentofu.md](/raw/migration/assetcontainer/stackit/landing-zone-foundation-opentofu.md), section `#deployment-flavours-and-what-they-enable`

### 6. Configure and Version the Platform Baseline

Stage: `stairs`

### 7. Review Assistant Proposals

Stage: `chart`

Describe the desired outcome, answer clarification questions, and inspect the proposed differences. Accept the changes that match the agreed platform design.

Asset: [/migration/assetcontainer/stackit/landing-zone-configurator/#work-with-the-assistant](/migration/assetcontainer/stackit/landing-zone-configurator/#work-with-the-assistant) — source: [/raw/migration/assetcontainer/stackit/landing-zone-configurator.md](/raw/migration/assetcontainer/stackit/landing-zone-configurator.md), section `#work-with-the-assistant`

### 8. Prepare and Review the Platform Plan

Stage: `chart`

Choose the target and authorized credential profile, prepare the deployment, and request a Plan. Review the proposed resource changes against the saved configuration and platform design.

Asset: [/migration/assetcontainer/stackit/landing-zone-configurator/#review-and-deploy-the-platform](/migration/assetcontainer/stackit/landing-zone-configurator/#review-and-deploy-the-platform) — source: [/raw/migration/assetcontainer/stackit/landing-zone-configurator.md](/raw/migration/assetcontainer/stackit/landing-zone-configurator.md), section `#review-and-deploy-the-platform`

### 9. Apply and Validate the Platform

Stage: `rocket`

Authorize Apply of the reviewed saved Plan, follow the Runner job, and validate the resulting shared platform. Record the platform owner and operational handover.

Asset: [/migration/assetcontainer/stackit/landing-zone-configurator/#apply-and-validate-the-platform](/migration/assetcontainer/stackit/landing-zone-configurator/#apply-and-validate-the-platform) — source: [/raw/migration/assetcontainer/stackit/landing-zone-configurator.md](/raw/migration/assetcontainer/stackit/landing-zone-configurator.md), section `#apply-and-validate-the-platform`

### 10. Design Templates and Publish the Catalog

Stage: `hut`

### 11. Pilot with an Application Owner

Stage: `gondola`

Test the complete offering with an application team: discover the template, order a project, review the Plan, deploy, and accept the environment. Capture improvements before repeating the pattern.

Asset: [/migration/assetcontainer/stackit/landing-zone-configurator/#pilot-application-self-service](/migration/assetcontainer/stackit/landing-zone-configurator/#pilot-application-self-service) — source: [/raw/migration/assetcontainer/stackit/landing-zone-configurator.md](/raw/migration/assetcontainer/stackit/landing-zone-configurator.md), section `#pilot-application-self-service`

### 12. Hand Over and Improve the Baseline

Stage: `summit`

Agree platform and application responsibilities, retain execution history, and bring pilot feedback into the next configuration and template versions. Repeat the pattern for subsequent teams and waves.

Asset: [/migration/assetcontainer/stackit/landing-zone-configurator/#operate-and-evolve](/migration/assetcontainer/stackit/landing-zone-configurator/#operate-and-evolve) — source: [/raw/migration/assetcontainer/stackit/landing-zone-configurator.md](/raw/migration/assetcontainer/stackit/landing-zone-configurator.md), section `#operate-and-evolve`

