Hesse’s multi-cloud strategy, published in September 2026, puts open standards, interoperability, and workload portability at the centre of its approach to provider dependence. It raises a practical question for organisations in Germany and the wider DACH market: can a workload move if regulation, price, or business priorities change? 

Enterprise architects, platform teams, procurement teams, and risk leaders all shape this decision. Reversibility means being able to move a workload, retrieve its data, or change provider within an acceptable time and cost. It allows an organisation to meet current needs without closing off future operational, data, or commercial choices. 

A workload’s best home can change. Public cloud, private cloud, hybrid cloud, and on-premises infrastructure offer different levels of performance, control, scalability, and cost. The workload, whether an application, database, AI model, or business system, should drive the choice. 

For German and DACH organisations, this is also a cloud sovereignty issue. Sovereignty covers control over technology, data, operations and legal exposure. Data residence is one part of the decision, rather than the whole of it. 

Start Cloud Strategy With the Workload 

Technology decisions often begin with a preferred provider or a general policy such as “cloud first”. A better starting point is the workload. First, establish its performance and availability needs. Then set the rules for data sensitivity, location, recovery time, and future growth. 

Different workloads lead to different choices. An AI training job may benefit from specialist public-cloud computing capacity. A stable business system that holds sensitive information may need tighter control of a private cloud or an on-premises environment. 

Assessing each workload separately makes the trade-offs clear. A provider-specific service may deliver a worthwhile advantage. The team should still record what would need to change, how long a move could take, and what it might cost. 

Decide What Must Remain Reversible 

Reversibility does not require every workload to be ready to move at any moment. It requires a deliberate decision about which choices must stay open and where provider dependence is acceptable. 

Operational reversibility asks whether another team or provider could run the workload without a complete rebuild. Data reversibility covers export in a usable format and within an acceptable period. Commercial reversibility depends on contract terms such as exit charges, audit rights, and transition support. 

The Hesse strategy covers four operating pillars: on-premises, off-premises, community, and public cloud. This gives the public administration more than one placement option. The flexibility is useful only if common standards work in practice and workloads can move when requirements change. 

Test Whether Multiple Clouds Add Resilience 

Multi-cloud may reduce provider dependence and provide more options during an outage. Contracts with several providers, however, do not make a workload portable. 

In his Tech Show Frankfurt 2026 keynote, Sebastian Damrath described the specialist silos that can form around AWS, Microsoft Azure, Google Cloud and regional providers. Each silo can demand its own skills and operating tools. When workloads are tightly tied to those services, multi-cloud can duplicate cost and complexity. 

Resilience depends on shared standards and clear ownership. Teams also need to test recovery and migration plans. If data cannot move, or a critical service cannot be restored elsewhere, a second provider may offer less protection than expected. 

Use Platform Engineering to Standardise Delivery 

At Tech Show Frankfurt’s Cloud Day 1 sessions, speakers described “paved roads”: pre-approved deployment patterns that set requirements for identity, networking, compliance, support, and cost before a workload goes live. 

Platform engineering teams use these patterns to provide a repeatable route into production. Delivery teams still choose services within agreed guardrails, while support and dependencies are handled consistently. 

Common patterns also make it easier to estimate the work of recreating a deployment. They expose exceptions and help teams judge whether a benefit justifies the portability limit. 

Price the Exit Before Signing 

Technology procurement should price the exit as carefully as the entry. Teams should confirm data-export fees, formats and transfer times, along with notice periods, audit rights, where support data is stored and transition support. 

The EU Data Act has applied since 12 September 2025 and includes rules intended to make provider switching more effective and improve cloud interoperability. Organisations must still test data exports and estimate the work of moving a workload. 

For cloud buyers in Germany and DACH, those rights should become contract requirements and tested migration procedures. Entry discounts lose value when leaving is expensive or disruptive. 

Keep Future Options Open 

A reversible cloud strategy makes dependencies visible. A proprietary service may justify its limits, but the decision should record the benefit, constraint, and exit route. 

Before approving a cloud infrastructure decision, teams should ask: 

• What does this workload need now? 
• Which data, interfaces, and operating processes must remain portable? 
• Which provider-specific dependencies are justified? 
• How much time, money and disruption would a change require? 

For Germany and DACH, the next test is implementation. Hesse’s strategy and the EU Data Act set a direction, but portability matters only when organisations have tested data exports, migration plans, and transition support. Teams should review the decision when the workload, regulation, or contract changes.