Skip to content
Beta

Migration at a Glance

Last updated on

Stackit LogoStackit Logo
STACKIT

Migration at a Glance

Fast, image-first tour of the STACKIT Migration Framework for trade-fair booths and quick briefings: one visual per phase and module, looping automatically.

PLAN

The Cloud Journey

Start at the tourist information office, prepare at basecamp, and follow the path to migration, operations, and innovation. Ask where your organization stands today. These six illustrated stations are a simplified story, not the formal framework phases.

Mountain journey to STACKIT with German signs for orientation, strategy, preparation, migration, operations, and innovation, plus basecamp and a landing zone lodge
Mountain journey to STACKIT with German signs for orientation, strategy, preparation, migration, operations, and innovation, plus basecamp and a landing zone lodge
PLAN

Migration Phases

STACKIT Cloud Migration Framework Journey across the four phases Assess, Design and Mobilize, Migrate, and Run with their key modules. Assess PHASE 1 Assess Design & mobilize PHASE 2 Design & mobilize Migrate PHASE 3 Migrate Run PHASE 4 Run PLANNING Discovery Discovery Map apps and dependencies. Design Design Define target patterns. Migration plan Migration plan Sequence waves for delivery. Rapid discovery Rapid discovery Inventory workloads to create an early scope and cost baseline. TCO report TCO report Model migration economics to support investment and planning decisions. Readiness assessment Readiness assessment Assess technology and organization gaps before detailed design starts. Deepdive workshop Deepdive workshop Explore STACKIT services and platform options for target design. Briefings & workshops Briefings & workshops Align stakeholders on goals, scope, and migration expectations. Business case Business case Compare value, effort, and investment per application. Enablement ENABLEMENT Center of Excellence Trainings & Learning Paths Documentation & Reference Landing zone Landing zone Establish the secure platform base for migrated workloads. Security & compliance Security & compliance Define security and compliance controls for migration and operations. Target operating model Target operating model Define roles, processes, and ownership for target operations. Migration factory setup Migration factory setup Prepare teams, tools, and runbooks for scalable migration execution. Migrate MIGRATE Relocate Relocate Rehost Rehost Replatform Replatform Optimize Optimize Improve sizing, performance, and cost after cutover. Repurchase Repurchase Evaluate SaaS options when replacement delivers better value. Refactor Refactor Restructure strategic workloads for cloud- native scalability and agility. Operating model handover Operating model handover TOM validation and ownership transfer Hypercare Hypercare Post-cutover stabilization bridge. Operate Operate Steady-state cloud operations. Support Support Manage incidents and service requests across support responsibilities. Customer Success Customer Success Track adoption, outcomes, and value realization with stakeholders.
STACKIT Migration Framework phase overview from Assess through Design and Mobilize and Migrate to Run
BASE

Assess

Frame Assess as the fast, low-commitment phase that builds an initial fact base and qualifies migration intent before deeper design work starts.

Overview In 2 trails

Assess is the first phase of the STACKIT Migration Framework. It creates a fact-based baseline for migration decisions before architecture design and wave delivery begin.

The phase combines technical discovery with commercial and organizational alignment so that later migration work starts with clear priorities and transparent assumptions.

Assess typically starts when a migration initiative has strategic sponsorship but no decision-ready baseline yet.

  1. Start when migration scope, business drivers, and decision stakeholders are defined at a high level.
  2. Build the baseline through Rapid Discovery, readiness evaluation, cost modeling, and stakeholder workshops.
  3. End when scope assumptions, migration readiness, and financial direction are clear enough to start detailed design.

Assess is completed when stakeholders can approve moving into Design and Mobilize with a shared understanding of cost, risk, and delivery feasibility.

Assess reduces uncertainty early and aligns business and IT before large implementation effort is committed.

Financial transparency

A first cost corridor and TCO perspective are available for investment decisions.

Readiness clarity

Gaps in technology, governance, capabilities, and operating model are visible early.

Stakeholder alignment

Leadership, delivery teams, and technical owners align on goals, scope, and expectations.

Risk reduction

Key assumptions and migration constraints are documented before target design starts.

Rapid Discovery
Rapid discovery process Input data is processed through rapid discovery tooling to produce decision-ready outputs for early migration choices. Input dataCMDB & inventory exportsAsset lists, hosts, base platform factsHypervisor & cloud reportsUsage, footprint, and utilization signalsPlatform listsKubernetes, database, and OS baselinesRapid discovery toolingIngest & normalize datasetsStandardize source records and schemaClassify & aggregate assetsConsolidate by technology and quantityApply assumptionsConfidence levels and growth factorsOutput informationConsolidated asset baselineFact base for scope and planningInitial STACKIT sizingFirst capacity assumptionsPrice indication & TCO corridorEarly cost orientation for decisions
Rapid Discovery process turning raw source data into a decision-ready baseline
Readiness Assessment

Assess technical, process, personnel, financial, and governance readiness, then assign every gap to an owner and migration-wave gate.

Readiness assessment at a glance Five readiness dimensions turn workshop evidence into an owned migration backlog and explicit wave gates. Five dimensions. One actionable migration baseline. Validate workshop evidence, expose gaps, and convert every finding into an owned action. 1 Technical Accounts, IAM, networkAutomation and guardrailsObservability baseline 2 Process Onboarding and changeRecovery and incidentsException handling 3 Personnel CCoE and platform rolesSecurity and operationsRole-based capability 4 Financial Approved budgetCost allocation and FinOpsValue tracking 5 Governance Security and complianceData protectionControls and reporting OUTPUT Owned readiness backlog → blockers and pre-wave actions → evidence-based wave gates
Five readiness dimensions leading from validated evidence to an owned backlog and migration-wave gates
LIFT

Design and Mobilize

Position Design and Mobilize as the phase carrying most of the framework's substance: it turns Assess signals into an executable, factory-ready delivery plan.

Overview In 2 trails

Design and Mobilize is the planning and enablement phase between Assess and Migrate. It translates baseline findings into executable target designs, governance, and migration factory readiness.

The phase ensures that migration delivery starts with clear architectural decisions, security controls, team setup, and wave planning.

This phase starts after Assess confirms migration scope, readiness, and commercial direction.

  1. Start with detailed discovery of applications, dependencies, and migration constraints.
  2. Build target designs, business cases, and migration waves while setting up delivery structures.
  3. End when the first migration waves are approved, runbooks are ready, and governance is operational.

Design and Mobilize is complete when migration teams can begin wave run with stable inputs, controls, and responsibilities.

This phase turns strategy into delivery readiness and prevents uncontrolled migrations.

Architecture readiness

Target patterns and migration paths per workload are defined and validated.

Factory enablement

Roles, processes, tooling, and runbook governance are established before scale-up.

Security by design

Security and compliance requirements are integrated into design and planning from the start.

Execution confidence

Waves are sequenced with dependency awareness and operational feasibility.

Discovery
Discovery source-to-decision flow Discovery separates technical and human-driven inputs, runs technical-first and human-enriched analyses, and hands over both insight streams to follow-on modules. Discovery inputsTechnical and automated discoveryInfrastructure inventoryCMDB, VM, database, middleware, storageRuntime and utilization dataCPU, memory, I/O, network and seasonalityIntegration and flow signalsNetwork paths, APIs, identity, data movementAssessment-driven human inputSecurity and compliance contextData classes, controls, audit requirementsOwner and business inputCriticality, release windows, lifecycle plansDiscovery analysis toolingTechnical-first analysesNormalize and correlateUnify records and technical identitiesDependency mappingInfer communication and couplingUtilization and sizing analysisEstimate baseline demand corridorsPreliminary segmentationCluster by stack and environmentHuman-driven analyses (application owner input)Criticality and risk calibrationValidate business impact and constraintsWave feasibility and sequencingReconcile dependencies with release windowsAssumption and gap registerTrack open points and confidenceHandover outputsTool-derived outputsDesignTarget architecture options and sizing factsLanding zonePlatform guardrails and account structure needsMigration planWave backlog, sequencing, and cutover windowsAssessment-validated outputsSecurity and complianceControl needs, data classes, remediation pointsOperating modelRole model, ownership boundaries, process impactBusiness caseValue/risk profile and modernization priorities
Discovery analysis flow turning technical and stakeholder input into decision-ready outputs
Design
R-strategy migration method Decision flow from discovery to production with the seven R-strategies: Relocate, Rehost, Replatform, Repurchase, Refactor, Retain, and Retire. R-strategy migration methodFrom discovery and path selection through the seven R-strategies to validation, transition, and production.DiscoveryDiscoveryAssess / prioritizeAssess / prioritizeDetermine migration pathDetermine migration pathValidationValidationTransitionTransitionProductionProductionRelocateRelocate(move VM)Define Landing ZoneDefine Landing ZoneUse migration toolsUse migration toolsAUTOMATEMANUALInstallInstallConfigConfigDeployDeployValidation & handoverRehostingRehosting(move application)Define Landing ZoneDefine Landing ZoneUse migration toolsUse migration toolsAUTOMATEMANUALInstallInstallConfigConfigDeployDeployReplatformingReplatforming(lift and reshape)Define Landing ZoneDefine Landing ZoneMap Target PlatformMap Target PlatformAdapt Platform StackAdapt Platform StackRepurchasingRepurchasing(replace, drop and shop)Purchase COTS/SaaS and licensingPurchase COTS/SaaS and licensingMigrate business processMigrate business processRefactoringRefactoring(re-architecting applications)Redesign application/ infrastructure architectureRedesign application/ infrastructure architectureApp code developmentApp code developmentFull ALM/SDLCFull ALM/SDLCIntegrationIntegrationRetain/moveRetain/movekeep for now or move laterRetire/decommissionRetire/decommissionLanding zone foundationLanding zone foundationShared platform base for all paths
R-strategy method with seven migration paths: Relocate, Rehost, Replatform, Repurchase, Refactor, Retain, and Retire
STACKIT LogoSTACKIT Logo
Workload Migration Use Cases STACKIT · Design And Mobilize › Design Open page ↗

Application runtime migration

Migration of complete application runtimes across VM and platform targets, including dependencies, cutover behavior, and operating handover.

Container platform migration

Migration between Kubernetes platforms with separate treatment of stateless and stateful workload profiles.

Data migration

Migration of large file volumes, databases, and data platform workloads with explicit consistency, performance, and integrity boundaries.

Identity and access migration

Migration of IAM foundations such as SSO, federation, roles, service accounts, and permission models.

Network and connectivity migration

Migration of routing, DNS, firewall rules, segmentation, private connectivity, and cross-environment communication paths.

Integration and API migration

Migration of API contracts, messaging, eventing, and integration endpoints across source and target estates.

Security and compliance controls migration

Migration of controls, evidence chains, key material, and audit requirements required for regulated production readiness.

Operations and observability migration

Migration of monitoring, alerting, logging, incident workflows, and service-level operations baselines.

Delivery and resilience migration

Migration of CI/CD pipelines, automation controls, backup chains, and disaster recovery capabilities.

Select the Target Pattern and Runtime

Service model decision guide (IaaS, PaaS, SaaS)

Section titled “Service model decision guide (IaaS, PaaS, SaaS)”

Use this as a practical orientation for application design:

  • Choose IaaS when: You need deep OS/runtime control, legacy dependencies, or custom networking constraints that managed platforms cannot satisfy.
  • Choose PaaS when: You want faster delivery and lower operations burden while keeping application ownership and portability goals.
  • Choose SaaS when: The business process can adopt a standard product model and differentiation does not require custom platform operation.

Do not choose based on team habit only. Choose based on measurable requirements, operating capacity, and life cycle goals.

Runtime selection guide for typical STACKIT targets

Section titled “Runtime selection guide for typical STACKIT targets”

VM runtime (IaaS)

Best for low-change migrations and components needing OS-level control, custom agents, or strict legacy compatibility.

Kubernetes runtime (PaaS-like ops model)

Best for containerized workloads needing controlled scalability, release automation, and standardized platform operations.

Cloud Foundry runtime (PaaS)

Best when teams prioritize developer productivity and fast app delivery over low-level platform control.

Static delivery with Object Storage/CDN

Best for frontend/static workloads with high distribution needs and minimal backend runtime complexity.

SaaS replacement path

Best when process fit and standard capabilities provide higher value than migrating and operating the existing application stack.

Prepare the Runbook and Cutover

Every migration runbook should include these chapters:

  • Scope and context: Application scope, source and target context, assumptions, exclusions.
  • Owners and decision rights: Technical owner, release owner, rollback authority, escalation path.
  • Dependencies and prerequisites: Platform readiness, access, data state, external system windows.
  • Cutover plan: Ordered run steps, expected duration, freeze points, communication points.
  • Validation checks: Functional, non-functional, security, and observability checks with evidence.
  • Rollback and contingency: Trigger conditions, rollback steps, fallback communication flow.
  • Handover and Day-1 operations: Operations transfer, incident ownership, post-cutover watch period.

Executable

Steps are concrete, ordered, and assignable to named roles.

Verifiable

Validation points define clear pass/fail criteria and required evidence.

Recoverable

Rollback path is complete, timed, and linked to explicit trigger conditions.

Handover-ready

Day-1 operations and ownership transfer are fully specified.
Business Case
R-strategy matrix: migration investment versus long-term value Each strategy is shown as a range area: X = one-time migration/project investment, Y = long-term value (run-cost impact plus business effects). R-strategy matrix: migration investment versus long-term valueEach strategy is shown as a range area: X = one-time migration/project investment, Y = long-term value (run-cost impact plus business effects).Preferred zone: low investment, high valueLeast attractive zone: high investment, low valueOne-time migration and project cost index (low to high)Long-term value index (low to high)RelocateRehostReplatformRepurchaseRefactorRetainRetireArea width and height represent value ranges. Midpoint dots are orientation anchors, not commitments. Dashed = not a migration path (keep or decommission).VALUE RANGES BY STRATEGYInvestValueRelocate10–2510–25Rehost15–3520–40Replatform30–5540–65Repurchase45–7555–80Refactor55–9060–90Retain5–2010–30Retire20–4550–85
R-strategy investment versus long-term value matrix for business case decisions
Migration Plan
Phase and module model for migration wave planning
Phase and module model for migration wave planning
Landing Zone
Landing zone core components Six building blocks of a secure landing zone. Landing zone core componentsThe six building blocks of a secure platform foundation on STACKIT.Account GovernanceAccount GovernanceHow do I structure my projects?Identity & Access ManagementIdentity & Access ManagementWho can do what on the platform?Security & ComplianceSecurity & ComplianceHow do I monitor and protect?Network ArchitectureNetwork ArchitectureHow are components securely connected?Cost Management and ControlCost Management and ControlHow do I keep spending in control?Automation (IaC)Automation (IaC)How is everything delivered and managed?
Core components of a STACKIT landing zone
STACKIT LogoSTACKIT Logo
Account Governance STACKIT · Design And Mobilize › Landing Zones Open page ↗
STACKIT LogoSTACKIT Logo
Network Architecture STACKIT · Design And Mobilize › Landing Zones Open page ↗
STACKIT Landing Zone Accelerator
Architecture overview of the STACKIT Landing Zone Accelerator
Architecture overview of the STACKIT Landing Zone Accelerator
Enablement

Prepare migration teams through CCoE ownership, role-based STACKIT University learning, trusted documentation, and validated AI guidance.

Migration enablement at a glance Three capabilities combine governance, role-based learning, and trusted references for repeatable migration delivery. Three capabilities turn plans into repeatable delivery. Prioritize enablement from readiness findings and reinforce it with every migration wave. OWNERSHIPCenter of Excellence Standards and guardrailsDecisions, coaching, escalationLearning across migration waves CAPABILITYTrainings & Learning Paths Shared STACKIT fundamentalsRole paths, workshops, expert sessionsPractical readiness evidence KNOWLEDGEDocumentation & Reference STACKIT Docs and product guidanceApproved patterns and runbooksOwners, review dates, evidence AI-assisted guidance • grounded in trusted sources • validated by accountable experts
Three migration enablement capabilities: Center of Excellence, trainings and learning paths, and documentation and reference
AUTO

Migrate

Keep this as concise as Assess and focus on the end-to-end factory flow that runs every wave to completion.

MigrateMigrateOverview In 4 trails
  1. Confirm wave scope, cutover window, rollback criteria, and runbook ownership.
  2. Freeze wave baseline (application version, dependencies, data scope, and interface contracts).
  3. Run pre-migration technical readiness checks in source and target environments.
  4. Run migration runbook steps per workload archetype and R-strategy path.
  5. Perform cutover and route traffic to the STACKIT target according to the wave plan.
  6. Validate technical, functional, and operational acceptance criteria.
  7. Stabilize incidents and known defects in short feedback loops.
  8. Hand over stabilized workloads to Optimize and Operate.
LIVE

Optimize

Keep this concise: Optimize turns freshly migrated workloads into cost- and performance-tuned steady-state services.

MigrateOptimizeOverview In 7 trails

Optimize starts when workloads run on STACKIT and real operating data is available. The module converts post-cutover observations into measurable improvements for performance, stability, and cost efficiency.

Optimize is not a one-time task. It is an iterative cycle that can overlap with early stabilization and post-cutover care.

Many right-sizing and tuning decisions are only reliable under real load patterns. After cutover, teams can use production telemetry to separate assumptions from actual behavior.

  1. Collect runtime evidence: utilization, latency, error rates, throughput, and cost drivers.
  2. Identify bottlenecks and waste patterns at workload, platform, and data layers.
  3. Prioritize actions by business impact, risk reduction, and FinOps effect.
  4. Implement tuning changes in controlled increments.
  5. Validate outcomes against SLO, reliability, and cost targets.
  6. Feed lessons learned into future migration waves and operating standards.
  • Rightsizing: Align compute, storage, and network capacity with actual demand profiles.
  • Performance tuning: Improve latency and throughput through configuration, scaling, and architecture adjustments.
  • Reliability hardening: Reduce incident frequency through better resilience, observability, and failure handling.
  • FinOps controls: Improve cost transparency, remove waste, and optimize run-rate efficiency.
GOAL

Run

Close the journey briefly with the Run phase module map so the audience sees where migration outcomes ultimately land.

Overview In 2 trails

Run combines short-term stabilization and long-term service operations. The following model visualizes the intended flow from migration handoff to stable day-2 operations.

Swipe sideways to see the whole diagram
Run phase module model From migration stabilization to durable cloud operations on STACKIT. Run phase module modelFrom migration stabilization to durable cloud operations on STACKIT.Run flowMigrate handoffCutover complete, known risk listHypercarePost-cutover stabilization, fast remediation bridgeOperateSteady-state cloud operations: reliability, security, efficiencySupportIncidents and service requests, shared responsibility rulesCustomer SuccessCentral contact point, adoption and value realizationSemantic mapBridge stageMigrate to Run transition contextTechnical streamHypercare and Operate steady-state executionOperations streamOperate execution and governance cadenceService streamSupport, incidents, and requestsValue streamCustomer success and adoption scaling
LIVE

ISV Onboarding Overview

An email to isv-sales@digits.schwarz gets you a Partner Manager, and a 30-minute discovery call establishes mutual fit before either side invests engineering or legal time. Bring your business or product owner.

In 1 trail

The ISV Factory Framework provides a structured, end-to-end journey designed to seamlessly guide software vendors from initial engagement to full marketplace readiness. Divided into clear phases — ranging from initial onboarding and technical validation to quality assessment and marketplace placement — this framework ensures your solution achieves maximum performance, security, and integration with STACKIT. Explore each step below to understand the key milestones and requirements along your path.

The overview below summarizes the ISV journey from first contact to a live Marketplace listing. It helps vendor and STACKIT teams build a shared understanding of deliverables, dependencies, and expected outcomes across all nine phases.

Swipe sideways to see the whole diagram
STACKIT ISV Factory Framework Journey across the four stages Engage, Enable, Build and validate, and Launch with their nine phases. STAGE 1 Engage STAGE 2 Enable STAGE 3 Build & validate STAGE 4 Launch Contact & Preparation PHASE 01 Contact & Preparation Discovery call, qualification, and mutual fit criteria. Signing & Legal Alignment PHASE 02 Signing & Legal Alignment Base agreement, sales addendum, DPA, and the SLA framework. Partner Portal & Enablement PHASE 03 Partner Portal & Enablement Account activation, user management, and GTM tooling. STACKIT Onboarding & Technical Preparation PHASE 04 STACKIT Onboarding Cloud account, organization, projects, and IAM setup. Technical Proof of Concept PHASE 05 Technical Proof of Concept Tenancy strategy, landing zone, blueprint, and IaC pipelines. ES3 Self Assessment PHASE 06 ES³ Self Assessment Sovereignty maturity across the nine ES³ SML dimensions. Technical Quality Gate & Validation PHASE 07 Quality Gate & Validation Quality pillars, penetration testing, and self-attestation. Placement & Marketplace Enablement PHASE 08 Placement & Marketplace Product Delivery Sheet, SKU creation, and integration depth. Ready for Production PHASE 09 Ready for Production Listing activation, co-marketing, and support routing.
STACKIT LogoSTACKIT Logo
Technical Proof of Concept (PoC) STACKIT · Cloud Framework Open page ↗

The Technical Proof of Concept (PoC) phase is where your architectural planning becomes reality. The goal of this phase is to deploy a working version of your application on STACKIT to validate technical feasibility, performance, and cost-efficiency before moving toward a production-ready state.

A critical decision before rolling out your infrastructure is defining your tenant strategy. This decision heavily impacts your STACKIT Organization, Folder, and Project structure:

  • Multitenant Strategy: Multiple customers share the same infrastructure and application instance, separated logically.

    Multitenant folder and project structure

  • Customer Dedicated (Single Tenant): Each customer receives an isolated STACKIT Project and infrastructure environment.

    Dedicated folder and project structure

Accelerate your setup. To support a fast, automated, and standardized rollout of your cloud environment, STACKIT provides Infrastructure-as-Code (IaC) assets:

  • Landing Zone Accelerator — best-practice templates for setting up your STACKIT environment. Dedicated Landing Zone repositories tailored specifically for Multitenant and Customer Dedicated models are planned: github.com/stackitcloud/stackit-landing-zone
  • STACKIT GitHub Repositories — open-source projects, Terraform providers, and SDKs: github.com/stackitcloud

When building your PoC, you must design for growth, stability, and security:

  1. Scaling: How does your application architecture scale to handle sudden user growth or increased workloads without performance degradation?
  2. Redundancy & High Availability (HA): Define your availability requirements. Does your application require a Single-Region setup, or do you need a Multi-Region architecture to prevent downtime?
  3. Compliance (TOMs): By signing the Partner Base Agreement (PBA), your organization technically committed to the Technical and Organizational Measures (TOMs) outlined in Annex 2. Your PoC architecture must reflect and implement these security and data protection standards.

Architectural Blueprinting & Target Design

Section titled “Architectural Blueprinting & Target Design”

Once you have defined your deployment model, isolation strategy, and resilience requirements, translate these specifications into a formal Architectural Blueprint.

Mapping your software components (microservices, stateful data, caching layers, external interfaces) directly to STACKIT services — such as SKE, PostgreSQL Flex, Object Storage and STACKIT Network Area — creates a clear target architecture. This blueprint serves as the essential foundation for precise infrastructure cost modeling and subsequent automation via IaC.

Infrastructure Calculation & Cost Tracking

Section titled “Infrastructure Calculation & Cost Tracking”

With your Architectural Blueprint defined, model and track your resource consumption against your initial business case estimations:

  • Computing Calculator — model your estimated monthly compute, network, and storage footprint for the target PoC architecture: calculator.stackit.cloud/computing
  • STACKIT Price List — reference for a complete overview of all SKUs, as some newer platform services may not yet be reflected in the calculator: STACKIT price list (PDF)

Infrastructure as Code (IaC) & CI/CD Pipelines

Section titled “Infrastructure as Code (IaC) & CI/CD Pipelines”

To achieve high reliability and low operational overhead, manual infrastructure provisioning via the portal should be avoided for production-grade software. Infrastructure as Code (IaC) is the state-of-the-art industry standard for cloud-native deployment.

Using declarative tools ensures your infrastructure is repeatable, version-controlled, and audit-ready:

  • Primary Tooling: Use the official STACKIT Terraform Provider to declare compute, storage, network, SKE (Kubernetes), and database resources: registry.terraform.io
  • Automation-First: Maintain all IaC scripts within version control (e.g., GitHub, GitLab, STACKIT GIT).
  • STACKIT Git Pipelines: If you host your repositories on STACKIT Git, the built-in pipelines run your IaC and build workflows next to the code — the first-steps guide walks through the initial runner and workflow setup: docs.stackit.cloud — Pipelines first steps

A standardized Continuous Integration / Continuous Deployment (CI/CD) pipeline automates the lifecycle of both your infrastructure and application workloads.

  1. Code Commit & Trigger: Changes to application code or IaC templates trigger the automated pipeline.
  2. Linting & Static Security Analysis: Validate Terraform configurations (terraform validate, tflint) and scan container images for vulnerabilities — either by running Trivy directly as a pipeline step, or by relying on the vulnerability scans the STACKIT Container Registry performs on pushed images. Running both gives you a gate in the pipeline and continuous rescanning of images already stored.
  3. Infrastructure Provisioning (IaC Step): Run terraform plan for automated verification, followed by terraform apply to provision or update STACKIT resources in the target PoC environment.
  4. Workload Deployment: Deploy application containers to STACKIT Kubernetes Engine (SKE) with Helm as the packaging format — either driven by the pipeline through the Terraform Helm provider (keeping infrastructure and workload in one declarative run), or pull-based via a GitOps engine such as Argo CD or Flux that reconciles the chart from your Git repository. Avoid imperative kubectl apply steps, as they leave no reconcilable desired state. PaaS applications are deployed via Cloud Foundry (cf push).
  5. Automated Integration Testing: Execute smoke tests against the freshly deployed endpoints to verify service availability.
  6. Secrets Management: Ensure pipeline runners access STACKIT service accounts via short-lived API tokens or integration with STACKIT Secrets Manager — never hardcode API keys or credentials in repositories.
  7. STACKIT Container Registry: Central registry for your build artifacts, including vulnerability scanning of pushed images: docs.stackit.cloud — Container Registry

The PoC phase is complete when the following milestones are verified:

  • Target Architectural Blueprint established and mapped to STACKIT services.
  • Application is successfully deployed and running in the STACKIT PoC project.
  • Infrastructure provisioning is automated using IaC (e.g., Terraform / Landing Zone Accelerator).
  • Tenant isolation strategy (Multitenant or Customer Dedicated) is implemented in the folder/project hierarchy.
  • PoC environment costs calculated and discussed with the Partner Manager.
  • Automated CI/CD deployment pipeline is established.
  • Security and compliance controls (PBA Annex 2 TOMs) are technically validated.
  • Milestone achieved: PoC validated — ready to proceed to the ES³ Self Assessment.

Throughout the PoC phase, use the following resources to support your development:

  • STACKIT Knowledge Base — technical documentation, API references, and practical tutorials: docs.stackit.cloud
  • STACKIT Status Page — real-time information on platform availability and system maintenance: status.stackit.cloud

Need assistance? If you encounter technical blockers during your PoC, contact your Partner Manager or the ISV Factory team at isv-sales@digits.schwarz.

STACKIT LogoSTACKIT Logo
ES³ Self Assessment STACKIT · Cloud Framework Open page ↗

The European Sovereign Stack Standard (ES³) is STACKIT’s digital sovereignty program. It makes the otherwise vague concept of digital sovereignty objectively measurable, in a market where “sovereignty washing” and vague marketing promises are common. Its operational engine is the Sovereignty Maturity Level (SML) Framework, an auditable assessment framework whose criteria have been verified by the independent auditing firm BDO.

The framework follows three guiding principles:

  • Auditability: assessments must be evidence-based, comprehensible, and reproducible.
  • SML classification: maturity levels are assigned based on defined mandatory controls per level.
  • Comparability: results are comparable between services and providers, and over time.

The SML framework builds on the eight sovereignty objectives of the official EU Cloud Sovereignty Framework (CSF) and adds a ninth, future-critical dimension: Artificial Intelligence.

Each dimension is assessed on three mandatory implementation levels, so a requirement is never satisfied on paper alone:

  • Level 1 — Contractual (Regulatory): contractual regulations and assurances, such as service agreements, SLAs, and legal arrangements.
  • Level 2 — Governance & Operations (Organization): organizational responsibilities, policies, procedures, and operational processes.
  • Level 3 — Technical (Technology): technical implementation and system configuration, such as security measures, configurations, and automation.

What Is Assessed — and Who Is Responsible

Section titled “What Is Assessed — and Who Is Responsible”

The object of assessment is always the combination of a client-facing service and its service provider, including the underlying services it is built on. Before the assessment starts, the service is classified by Service Name, Service Provider, and Service Type (IaaS, PaaS, SaaS, Managed Service, AI Service). The Service Type determines only which controls are applicable — it has no influence on the resulting maturity level.

Every control is assigned to exactly one Control Scope, which defines who is responsible for it:

This split exists to prevent duplicate audits and to make inherited capabilities auditable:

  • Controls at SP level are assessed once and inherited across all of your services.
  • Controls at US level are not implemented by you. They are covered by suitable evidence from the platform provider (certificates, audit reports) and are considered inherited — which means the sovereignty maturity of the platform you build on directly shapes the level your own service can reach.
  • Controls at CFS level apply to the specific product you deliver to your customer and must be assessed individually for each service — they are neither inherited from your SP-level controls nor from the underlying platform.

The framework is hierarchical: Dimension → Control Objective → Control → Question → Evidence. You answer at the Control level, not the question level — the questions listed underneath each control in the catalogue are illustrative example questions that help you interpret its intent, not a separate checklist to work through. Each control is answered binary — “Yes”, “No”, or “N/A” — and backed by evidence; a control counts as fulfilled only when it is answered “Yes” and the evidence substantiates it. An “N/A” is accepted only where it is objectively not applicable and justified.

Evidence must be specific, verifiable, and directly assignable to a control. Blanket statements such as “documentation available” or “process exists” are not sufficient; an independent third party must be able to fully comprehend the assessment. Permissible evidence types:

  • Contracts or legal agreements
  • Policies and procedural documentation
  • Technical configurations or system extracts
  • Audit reports or certifications
  • Architecture diagrams

The entire assessment process chain — service classification, working through the control catalogue, uploading evidence, and tracking your target level — is mapped in the ES³ Tool:

  1. Determine your starting point: Use the ES³ Lens, the interactive presales assessment tool, to get an instant maturity scorecard for your infrastructure before committing to a target level.
  2. Study the framework and catalogue: Read the SML Framework specification and the downloadable framework catalogue, in which every assessment question is listed with its dimension, control, service type, expected evidence type, and evidence example.
  3. Classify your service: Fix Service Name, Service Provider, and Service Type. This classification is binding for the entire assessment and determines which controls apply.
  4. Collect evidence per control: Work through the applicable controls along all three implementation levels, answer each one directly, and assign exactly one piece of specific, verifiable evidence to substantiate your answer.
  5. Agree your target level: Discuss the maturity level your solution should carry with your STACKIT Partner Manager — it determines which controls are mandatory for you via the separate SML mapping table.
  6. Validation: Your results are reviewed as part of the Technical Quality Gate, which is also where the sovereignty seal shown on your Marketplace listing is established.
  • Framework Reviewed: SML framework specification and criteria catalogue reviewed by your security or technical lead.
  • Service Classified: Service Name, Service Provider, and Service Type fixed for the assessment.
  • Assessment Completed: All applicable controls answered across the contractual, organizational, and technical levels, each backed by specific evidence.
  • Target Level Agreed: The intended Sovereignty Maturity Level is aligned with your STACKIT Partner Manager.
  • Results Submitted: Assessment results handed over for validation in the Technical Quality Gate.

For questions on specific controls, sovereignty criteria, or the assessment tooling, contact the ES³ Program team at ES3@digits.schwarz. For questions about how the assessment fits into your ISV onboarding, reach out to the ISV Factory team at isv-sales@digits.schwarz.

STACKIT LogoSTACKIT Logo
Placement & Marketplace Enablement STACKIT · Cloud Framework Open page ↗

The Placement phase transitions your validated software solution into a commercially available product on the STACKIT Marketplace. In this phase, commercial structures are established, product SKUs are generated, and your storefront presence is created.

To get a clear overview of how software solutions are featured and delivered to enterprise customers, watch the official STACKIT Marketplace introduction:

Marketplace Vendor Documentation & Onboarding

Section titled “Marketplace Vendor Documentation & Onboarding”

All technical, operational, and commercial guidelines for listing and integrating your product are maintained in our central vendor documentation.

Please review this documentation to guide you through the following steps:

  • Commercial & Operational Onboarding: Requirements for setting up your vendor profile and commercial structures.
  • Product Submission: Completing the required product details, pricing models, and marketing assets.
  • Listing & Integration Options: Guidance on standard storefront listings as well as automated provisioning and metering via Marketplace APIs.

Before a listing can go live, the commercial parameters agreed upon during Signing must be operationalized:

  1. Product Delivery Sheet: The ISV provides final product details, marketing assets, pricing tiers, and descriptions via the standardized Product Delivery Sheet.
  2. SKU Generation: STACKIT creates the official Stock Keeping Units (SKUs) in the billing engine to enable transaction processing, invoicing, or referral tracking.

Commercial placement is divided into two distinct levels depending on your chosen integration depth:

  • Vendor documentation reviewed by your commercial and technical teams.
  • Product details and commercial structures submitted according to vendor guidelines.
  • Product Delivery Sheet completed and submitted by the ISV.
  • Billing SKUs created in the STACKIT system.
  • Storefront draft generated via the Marketplace Listing Wizard and approved by both teams.
  • Milestone achieved: Commercial listing approved — ready to proceed to Ready for Production.

For questions on vendor documentation, SKU creation, or the Marketplace Listing Wizard, contact your STACKIT Partner Manager or the ISV Factory team at isv-sales@digits.schwarz.

Trail historyActive 4 of the last 12 weeksTBUpdatedNo updates · 1 bar = 1 week i
Maintainers
TBTimo BergenSTACKITOwnerActive 3 of the last 12 weeks · 5 updatesSTACKITtimo.bergen@digits.schwarzLWLukas WeberrußHead of STACKIT Cloud Migration Framework · STACKITOwnerActive 12 of the last 12 weeks · 58 updatesSTACKITwww.linkedin.com/in/lukas-weberruß-a360b081??Name not publicThe Cloud Framework team knows who this is. The name is not shown on the site.TMTobias M.Head of STACKIT Cloud Framework · STACKITOwnerActive 11 of the last 12 weeks · 196 updatesSTACKITwww.linkedin.com/in/tobias-müller-011304172Contributed in STACKIT
Show full history (4 more)