From January 2027, the EU Data Act forces cloud providers into a two-month notice period and abolishes switching fees. The explicit goal: move away from U.S.-controlled infrastructure. But a law that removes fees doesn't make your stack switchable. That part is on you — and the time to start is now.
July 2026: Six Months Until It Bites
The EU Data Act has been in force since September 2025, but the provisions that matter most for the cloud — the ones on switching providers — apply in full from January 2027. Today, in July 2026, that leaves roughly six months of lead time. Enough to be ready. Too little to sleep through.
Here's what concretely changes: cloud customers get a termination right with a notice period of no more than two months. And the notorious switching fees disappear — the egress charges and exit penalties hyperscalers have long used to make moving your data expensive, and therefore unattractive. Providers must also actively assist customers in switching and enable functional equivalence at the destination provider.
The policy intent isn't hidden, it's stated: lawmakers want to lower the cost and friction of migrating away from U.S.-controlled infrastructure — toward sovereign, European alternatives. Lock-in is no longer supposed to be a business model.
Klingt interessant?
The Real Point: Switchability Becomes Mandatory
This is the structural shift. Until now, vendor lock-in was the customer's architectural problem — you built yourself into a dependency, and finding the way out was your job. From 2027, lock-in becomes a legal liability for the provider: anyone who artificially obstructs switching or charges fees for it is breaking the law.
In regulatory terms, that's a sharp turn. The market spent years treating lock-in as the normal consequence of technical decisions. Brussels now treats it as a market failure that needs fixing. That moves the burden — and the pressure — from the customer to the provider.
Why That Alone Isn't Enough
And here is the trap I want to flag: a law that removes switching fees does not make your stack switchable.
The Data Act removes the commercial barrier. It does not remove the technical one. If your application is wired deep into a single vendor's proprietary services — the specific managed database, the in-house queue service, the vendor-native identity and AI layer — then the contractual right to leave is worthless as long as leaving is an 18-month re-platforming project.
The math is simple: if the switching fee is zero but the technical migration costs two engineering-years, you've gained nothing. You have the right to use a door your stack won't fit through. The hyperscalers know this. That's why deep integration into proprietary services is the next form of lock-in — one no law can dissolve with the stroke of a pen.
What This Means for CTOs and Tech Leads
Three consequences I think are worth taking seriously:
First: the deadline is an opportunity, not an outcome. January 2027 gives you the right to leave cheaply. Whether you can act on it is decided by your architecture — and that doesn't change because of an EU regulation, only because of work you start now. If you wait until December 2026 to assess how hard-wired you are, you've started too late.
Second: scrutinize what "switchable" actually means. Data export is the floor, not the goal. The relevant question isn't "can I get my data out?" but "will my application run at the next provider without a rewrite?" Anything that runs only on a single provider is a hidden switching-cost line item that appears on no fee schedule.
Third: sovereignty is more than a data center location. The Data Act explicitly targets reducing dependence on U.S.-controlled infrastructure. That's only achievable if switchability is real — commercially and technically. A European data center hosting proprietary U.S. services solves only half the problem.
This Is Exactly Where nopex Comes In
The Data Act clears the commercial hurdle. nopex clears the technical one.
nopex is built provider-agnostic by design. The application logic never knows which vendor is behind it — it runs against an abstraction, not against a single hyperscaler's proprietary service. Switching is therefore not a re-platforming initiative but a configuration decision. Add European data centers, open components where possible, proprietary ones where they add value — but never as a hard, unbreakable dependency.
That's how law and architecture interlock: from 2027 the Data Act removes your switching fee, and nopex removes your switching cost in the code. The contractual right to leave is only worth something once leaving is also a small technical step. That's exactly what nopex is for — so switchability isn't a clause on paper, but a property of the system.
