Financial transparency
A first cost corridor and TCO perspective are available for investment decisions.
Last updated on
Fast, image-first tour of the STACKIT Migration Framework for trade-fair booths and quick briefings: one visual per phase and module, looping automatically.
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.
Frame Assess as the fast, low-commitment phase that builds an initial fact base and qualifies migration intent before deeper design work starts.
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.
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.
Assess technical, process, personnel, financial, and governance readiness, then assign every gap to an owner and migration-wave gate.
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.
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.
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.
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.
Use this as a practical orientation for application design:
Do not choose based on team habit only. Choose based on measurable requirements, operating capacity, and life cycle goals.
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.
Every migration runbook should include these chapters:
Executable
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
Prepare migration teams through CCoE ownership, role-based STACKIT University learning, trusted documentation, and validated AI guidance.
Keep this as concise as Assess and focus on the end-to-end factory flow that runs every wave to completion.
Keep this concise: Optimize turns freshly migrated workloads into cost- and performance-tuned steady-state services.
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.
Close the journey briefly with the Run phase module map so the audience sees where migration outcomes ultimately land.
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.
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.
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.
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.
Customer Dedicated (Single Tenant): Each customer receives an isolated STACKIT Project and infrastructure environment.
Accelerate your setup. To support a fast, automated, and standardized rollout of your cloud environment, STACKIT provides Infrastructure-as-Code (IaC) assets:
When building your PoC, you must design for growth, stability, and security:
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.
With your Architectural Blueprint defined, model and track your resource consumption against your initial business case estimations:
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:
A standardized Continuous Integration / Continuous Deployment (CI/CD) pipeline automates the lifecycle of both your infrastructure and application workloads.
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.terraform plan for automated verification, followed by terraform apply to provision or update STACKIT resources in the target PoC environment.kubectl apply steps, as they leave no reconcilable desired state. PaaS applications are deployed via Cloud Foundry (cf push).The PoC phase is complete when the following milestones are verified:
Throughout the PoC phase, use the following resources to support your development:
Need assistance? If you encounter technical blockers during your PoC, contact your Partner
Manager or the ISV Factory team at isv-sales@digits.schwarz.
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:
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.
| ID | Dimension | What it assesses |
|---|---|---|
| SML 1 | Strategic | Corporate governance architecture, ownership dependencies, transparency of ownership structures, and executive oversight of service substitution and exit readiness. |
| SML 2 | Legal & Jurisdictional | Applicable legal frameworks, geographic processing boundaries, and legal protection against extraterritorial third-party claims or conflicting access requests. |
| SML 3 | Data | Customer-controlled access management, cross-environment data portability, purpose-bound usage constraints, and long-term cryptographic resilience. |
| SML 4 | Operational | Allocation of day-to-day operational responsibility, restriction and auditing of privileged access, autonomous incident response, and disaster recovery. |
| SML 5 | Supply Chain | Transparency of subprocessors and software components (SBOM), vendor risk governance, critical dependency mitigation, and vendor substitution workflows. |
| SML 6 | Technology | Deployment within approved geographic boundaries, adoption of open standards against vendor lock-in, architectural transparency, and component portability. |
| SML 7 | Security & Compliance | Least-privilege identity and access control, lifecycle data encryption, customer visibility into security logs, and isolation of high-risk operational tasks. |
| SML 8 | Environmental Sustainability | Infrastructure energy dependency profiles, hardware and cooling supply-chain exposure, environmental risk planning, and sustainability metric disclosure. |
| SML 9 | AI | Corporate accountability models, system explainability, reliance on external software providers, and protection of training data and model components. |
Each dimension is assessed on three mandatory implementation levels, so a requirement is never satisfied on paper alone:
| Level | Short form | Description |
|---|---|---|
| 1 Initial | Ad hoc, not standardized | Heavy reliance on external providers. Processes are reactive, digital dependencies are not managed and not embedded in risk management. |
| 2 Managed | Documented, rule-based | Digital dependencies are identified and documented in risk management. Initial contingency and restoration plans exist, but are not yet fully tested. |
| 3 Advanced | Structured, consistent | Sovereignty is anchored as a strategic objective. At least one alternative sourcing option or a documented migration path exists for every business-critical service. Data is predominantly processed within the EU/EEA. |
| 4 Future-Proof | Optimized, robust | Near-complete digital autonomy on self-operated or sovereign-controlled infrastructure, open standards, and European supply chains. Remaining dependencies are deliberate and substitutable at any time. |
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:
| Scope | Abbr. | Meaning for an ISV |
|---|---|---|
| Underlying Service | US | The platform you build on — for a Marketplace ISV, typically STACKIT. |
| Service Provider | SP | Your organization, which develops, operates, and is accountable for the service. |
| Client-facing Service | CFS | The specific product you deliver to your customer. |
This split exists to prevent duplicate audits and to make inherited capabilities auditable:
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:
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:
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.
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:
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:
Before a listing can go live, the commercial parameters agreed upon during Signing must be operationalized:
Commercial placement is divided into two distinct levels depending on your chosen integration depth:
| Level | Scope & execution |
|---|---|
| Stage 1: Marketplace Listing (standard) | Listing Creation: STACKIT Partner Managers (PDMs, ISV Sales, and ISV GTM teams) use the Marketplace Listing Wizard to build your storefront entry using your Product Delivery Sheet. Lead / Inquiry Handling: Customers can discover your product, request quotes, or trigger manual fulfillment. |
| Stage 2: Marketplace Integration (optional) | Automated Provisioning & Metering: Deep API integration between your software and STACKIT Marketplace APIs. Usage-Based Billing: Automated meter tracking and single-click customer provisioning. |
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.