Heißt das, ihr migriert alle Bestandskunden weg von AWS?

Nein. Wer heute auf AWS gut aufgehoben ist und keine zusätzlichen Souveränitätsanforderungen hat, bleibt da. Wir erweitern unser Portfolio, nicht unsere Migrationspflicht.

Welche EU-souveränen Anbieter setzt ihr konkret ein?

Anbieter mit Hauptsitz in der EU und ohne US-Muttergesellschaft. Konkrete Namen besprechen wir im Erstgespräch — abhängig von Workload, Compliance-Profil und Performance-Anforderungen.

Reicht der Datenstandort EU bei AWS Frankfurt nicht aus?

Für viele Workloads ja. Für regulierte Branchen und Behörden-nahe Workloads zunehmend nicht — der CLOUD Act greift unabhängig vom physischen Standort, sobald die Mutter US-Recht unterliegt. Das ist die Lücke, die wir mit EU-souveränen Anbietern schließen.

Was kostet eine hybride Architektur mehr?

Aufschlag liegt typisch bei 15–30 % gegenüber Single-Cloud — abhängig vom Trennungsgrad. Dafür bekommt ihr klar abgegrenzte Workloads ohne Souveränitätsrisiko. Im Erstgespräch rechnen wir den TCO für euren konkreten Fall.

Why we no longer host only on AWS

We remain committed to AWS — and yet we are extending our hosting strategy to include EU-sovereign providers. A sober analysis of requirements, risks and our responsibility towards our clients.

28. April 2026

AWS remains a central partner for us

Up front: we continue to value AWS as one of the most reliable and technologically advanced providers worldwide. Outstanding availability, high pace of innovation, an excellent ecosystem for scalable architectures, proven security mechanisms.

For many use cases — in particular highly scaling, globally distributed systems — AWS remains an excellent choice. Our decision therefore does not mean “away from AWS”, but “deliberate use of AWS”.

Why we are extending our strategy

With increasing regulation and rising requirements for data protection and compliance, one topic is moving more and more into focus: digital sovereignty. We understand this as more than just the physical location of servers. The question is who, in case of doubt, has access to data — and whether that access is subject to foreign jurisdictions.

Digital sovereignty is not a buzzword

Many offerings advertise “EU hosting” or “data location Europe”. An important step — but often not enough. One central point is frequently overlooked:

Organisations headquartered outside the EU — in particular with a US parent — can be subject to statutory access obligations (e.g. CLOUD Act).
These can apply even when data is physically stored in the EU.

Physical location alone does not guarantee real sovereignty.

Our definition of true sovereignty

For us, digital sovereignty is only given when:

the operating organisation has its head office in the EU,
it is not subject to any non-European jurisdiction,
the entire data processing remains within that legal area.

That is a noticeably stricter standard than the norm — but in our view a necessary one.

Consequence for our architecture

We are therefore increasingly pursuing a multi-provider approach that deliberately differentiates.

1. AWS — for global scale and complex systems

When performance, global availability and services are the priority.
When regulatory requirements allow it.

2. EU-based providers — for sovereign workloads

For sensitive data and critical business processes.
For clients with high compliance requirements (e.g. healthcare, public sector).

3. Hybrid architectures

A combination of both worlds.
Clear separation of data and services according to protection needs.

Not dogma, but a differentiated decision

We do not believe in “one size fits all”. Instead of ideological decisions, we rely on context-based architecture, transparent risk assessment and clear communication with our clients.

Conclusion

AWS remains an essential part of our toolset — and will continue to be. At the same time, we are extending our approach to meet the growing requirements of digital sovereignty. Technical excellence alone is no longer enough — legal control becomes equally decisive. That is exactly where we focus.

Time to review your hosting strategy?

If you want to reassess your current cloud strategy under sovereignty aspects, we will talk it through with you for 30 minutes. No pitch — we will give you an honest read on where access risks sit and where an EU-sovereign extension makes sense. Free of charge, no obligation.

Frequently asked questions

What clients ask us most often about our multi-cloud strategy — answered openly.

Does that mean you migrate all existing clients away from AWS?+

No. Anyone well-served on AWS today and without additional sovereignty requirements stays there. We are extending our portfolio, not imposing a migration obligation.

Which EU-sovereign providers do you use specifically?+

Providers headquartered in the EU and without a US parent. We discuss specific names in the initial conversation — depending on workload, compliance profile and performance requirements.

Isn’t the EU data location at AWS Frankfurt enough?+

For many workloads yes. For regulated industries and public-sector-adjacent workloads, increasingly not — the CLOUD Act applies regardless of physical location, as soon as the parent is subject to US law. That is the gap we close with EU-sovereign providers.

How much more does a hybrid architecture cost?+

The premium typically sits at 15–30 % over single-cloud — depending on the degree of separation. In return you get clearly delineated workloads without sovereignty risk. In the initial conversation we model the TCO for your specific case.