pde-prob-v8-cloud-egress-fee-vendor-lock-in

Cloud Data Egress Fees and Proprietary Lock-in Block Enterprise Multi-Cloud Switching

Cloud egress fees ($0.09/GB AWS, $0.087/GB Azure) are the visible symptom. Free switching programs (2024) proven ineffective — require full exit, not partial migration. Real lock-in is proprietary managed services, reconfiguration costs, dual-running during migration. EU responding with DMA gatekeeper designation (Nov 2026, 10% global turnover fines) and Data Act switching-fee ban (Jan 2027). 37signals documented $10M+ savings over 5 years repatriating from AWS, but took 2 years with dedicated engineering.

Actor: Enterprise IT teams, cloud architects, and procurement managers operating workloads on AWS, Azure, or GCP who need the flexibility to switch providers or run multi-cloud Signals: 5 Evidence: 5 Sources: 5

Cloud vendor lock-in is a structural infrastructure problem distinct from AI-specific costs. The egress fee ($0.09/GB) is the visible symptom, but the real lock-in is proprietary service dependencies, reconfiguration costs, and dual-running during migration. EU regulators escalated from voluntary free switching (2024, proven ineffective) to mandatory DMA gatekeeper designation (November 2026, 10% global turnover fines) and Data Act switching-fee ban (January 2027). 37signals proved repatriation works ($10M+ over 5 years) but it took 2 years. Counter-evidence: egress fees are <1% of annual cloud spend per EU report; free switching programs exist; but structural lock-in from proprietary services persists regardless.

SIGNATURE VISUAL

Evidence Chain: From Signals to Commercial Opportunity

5 independent signals cross-validated, proving this is a real, severe, and growing problem.

RAW SIGNALS
5
5 independent source signals
Industry surveys · Engineering blogs · Financial disclosures
→
REPEATED PROBLEM
75%
Enterprises exceeding AI cost budgets
State of FinOps Report 2026
→
WORKAROUNDS
100x
Agent AI amplifies token consumption
Teams building custom Prometheus monitoring
→
MONEY SIGNAL
$1M→3mo
Annual budget exhausted in 3 months
Futurum Report · Agent AI
→
SOLUTION GAP
37x
Model price gap across two orders of magnitude
DeepSeek V3 vs GPT-5
→
COMMERCIAL OPPORTUNITY
$885B
Inference market 2030 projection
From $120B (2025) growing 219%
HYPOTHESIS
Problem Reality 88
Commercial Opportunity 78
Confidence 85
Decision GO

Problem Statement

FACT

Cloud egress fees ($0.09/GB AWS, $0.087/GB Azure) are the visible symptom. Free switching programs (2024) proven ineffective — require full exit, not partial migration. Real lock-in is proprietary managed services, reconfiguration costs, dual-running during migration. EU responding with DMA gatekeeper designation (Nov 2026, 10% global turnover fines) and Data Act switching-fee ban (Jan 2027). 37signals documented $10M+ savings over 5 years repatriating from AWS, but took 2 years with dedicated engineering.

Who Experiences This

FACT
Actor
Enterprise IT teams, cloud architects, and procurement managers operating workloads on AWS, Azure, or GCP who need the flexibility to switch providers or run multi-cloud
Context
AWS and Azure hold combined 65-70% share of EU cloud revenue (Q1 2026). EU regulators are designating both as DMA gatekeepers (final decision expected November 2026). Egress fees charge $0.087-$0.09/GB but the real lock-in is proprietary service dependencies and reconfiguration costs.

What Are They Trying to Accomplish?

FACT

Switch cloud providers or run multi-cloud without prohibitive egress fees, proprietary lock-in, or regulatory complexity.

What Gets in the Way?

FACT

Cloud egress fees ($0.09/GB AWS, $0.087/GB Azure) are the visible symptom. Free switching programs (2024) proven ineffective — require full exit, not partial migration. Real lock-in is proprietary managed services, reconfiguration costs, dual-running during migration. EU responding with DMA gatekeeper designation (Nov 2026, 10% global turnover fines) and Data Act switching-fee ban (Jan 2027). 37signals documented $10M+ savings over 5 years repatriating from AWS, but took 2 years with dedicated engineering.

Evidence & Source Traceability

Signals (5)

#1: AWS and Azure face EU gatekeeper designation with 10% fines over cloud lock-in

Source
shattered.io — EU DMA Gatekeeper Analysis (2026-10-07)
Actor
Enterprise cloud customers in the EU running workloads on AWS or Azure
Context
The European Commission issued a preliminary gatekeeper view in June 2026 that both AWS and Azure should be designated under the DMA. Bloomberg reported October 2, 2026 that a final decision could come as soon as November 2026. AWS and Azure hold combined 65-70% share of EU cloud revenue.
Pain
Enterprises face structural lock-in: egress fees ($0.09/GB AWS, $0.087/GB Azure), proprietary service dependencies, and reconfiguration costs that make switching prohibitively expensive. DMA designation would require interoperability, limits on self-preferencing, and measures to reduce customer lock-in within 6 months.
Quote
“The practical complaint behind this case is simple: moving data out of a cloud provider costs money, and the EU has decided that this cost — combined with proprietary service dependencies — creates a gatekeeper effect that stifles competition.”
Workaround
EU Data Act's Article 34(2) caps egress charges for 'in parallel use' multi-cloud running at the provider's own cost, from 12 September 2025. But this only covers the transition overlap period, not the full migration.
Money
DMA penalties: up to 10% of worldwide annual turnover for first infringement. AWS and Azure combined EU revenue estimated at tens of billions. 37signals documented $10M+ savings over 5 years after repatriation.
https://shattered.io/aws-azure-eu-gatekeeper-designation-2026/

#2: Cloud free switching programs have little practical effect on competition

Source
Foundation for American Innovation / TechPolicy.press (2026-10-01)
Actor
Businesses and policymakers evaluating cloud competition reforms
Context
Analysis of the 2024 voluntary egress fee waivers by AWS, Azure, and GCP. These were introduced to get ahead of EU mandates and FTC pressure. The authors argue the waivers have had negligible practical impact on cloud competition.
Pain
Free switching programs require full cloud exit (not partial migration), which most enterprises cannot do. Small businesses can already move data freely. Large businesses negotiate egress discounts. The real lock-in is product bundling: hyperscalers tie marketplace discounts to hosting on their cloud, creating economic lock-in beyond egress fees.
Quote
“At best, eliminating egress fees is benignly unproductive in the effort to improve competition in the cloud. Such concentration, combined with anticompetitive business practices, erodes customer choice, creates lock-in, and leads to higher prices for businesses and their consumers.”
Workaround
The authors recommend cutting through product bundles rather than focusing on egress fees. But no regulatory framework has yet addressed the bundling problem directly.
Money
Cloud marketplace commissions create tiered discounts that incentivize hosting on the provider's own cloud. Software companies pay for marketplace access, and customers get discounts only when purchasing through the cloud marketplace.
https://www.techpolicy.press/cloud-needs-more-than-fee-waivers-to-be-competitive

#3: Repatriate to OVHcloud or Renegotiate AWS and Azure: UK enterprise cost analysis

Source
CompareTheCloud.net — UK Enterprise Analysis (2026-10-01)
Actor
UK enterprises running steady-state workloads on AWS or Azure considering repatriation
Context
Detailed cost comparison and migration analysis for UK enterprises. Includes AWS/Azure/OVHcloud pricing checked live on September 29, 2026. Documents the EU Data Act's egress cap provisions and the CMA cloud market investigation findings.
Pain
Moving 50TB out of AWS costs $4,292/month at list price; Azure costs $4,182/month. But the real migration cost is not egress — it's rebuilding proprietary managed services (databases, AI platforms, serverless), running dual-cloud during transition, and the 2-year timeline before savings materialize. 37signals is the clearest evidence case.
Quote
“Rebuilding those integrations is usually the single biggest source of migration risk and cost, more than the compute or storage price difference itself.”
Workaround
EU Data Act caps 'in parallel use' egress charges at provider's own cost from September 12, 2025. AWS extended free-switching window from 60 to 90 days in September 2025. But neither covers the full migration cost.
Money
37signals documented savings that 'will now top ten million over five years' after repatriating from AWS. But it took roughly two years to fully materialize and depended on dedicated engineering staff and a hardware refresh cycle.
https://www.comparethecloud.net/articles/repatriating-to-ovhcloud-or-renegotiating-aws-and-azure-for-uk-enterprises

#4: AI Vendor Exit Clauses: 0 to 90 days to export data; DMA duties land mid-commitment

Source
Beri.net — AI Vendor Exit Clauses Analysis (2026-10-05)
Actor
Enterprises evaluating AI service vendor lock-in and exit clause risk
Context
Analysis of how AI service vendor contracts handle data export, model deprecation, and change of control — and how the upcoming AWS/Azure DMA duties intersect with existing 3-year cloud commitment renewals.
Pain
AI vendor exit clauses give 0 to 90 days to export data. When DMA duties land midway through a 3-year cloud commitment, enterprises face a regulatory-commercial collision: new compliance obligations vs. existing contractual lock-in.
Quote
“AWS and Azure DMA Duties Land Midway Through a 3-Year Commit”
Workaround
Enterprises should review exit clauses before signing new commitments. But standard contracts from AWS/Azure do not offer meaningful exit flexibility.
Money
3-year cloud commitments signed in late 2026 could run headlong into DMA obligations that don't exist yet on paper. Contract terms may need to be renegotiated.
https://www.beri.net/article/ai-vendor-exit-clauses-data-export-model-deprecation-change-of-control-price-transition

#5: 欧盟将AWS、Azure纳入DMA管控:全球云行业格局重塑

Source
Bloomberg / 彭博社 (via Toutiao) (2026-10-04)
Actor
European enterprise cloud customers and domestic cloud providers (OVHcloud, Scaleway)
Context
Chinese-language coverage of the Bloomberg report on EU's DMA designation for AWS and Azure. Details the regulatory timeline, potential fines (10% global turnover), and impact on European cloud sovereignty.
Pain
Enterprises face bundling, customer lock-in, and high migration barriers. Once committed to AWS/Azure, switching requires high data migration costs, complex technical adaptation, and extended system reconstruction. European domestic providers cannot break through these barriers.
Quote
“企业一旦选择两大平台的云服务,后续想要切换至欧洲本土云厂商,将面临极高的数据迁移成本、复杂的技术适配难题、漫长的系统重构周期”
Workaround
European providers (OVHcloud, Scaleway) positioning as alternatives. But feature parity with AWS/Azure managed services is incomplete.
Money
DMA fines up to 10% of global annual turnover. European providers expect to gain market share as regulatory barriers reduce lock-in.
https://m.toutiao.com/article/7692729440157942335/

Evidence (5)

#1: EU DMA cloud gatekeeper designation: AWS/Azure pricing, fines, and timeline

Source
shattered.io (REGULATORY_ANALYSIS) — 2026-10-07
Excerpt
“AWS internet egress: $0.09/GB. Azure internet egress: $0.087/GB. Combined EU cloud revenue share: 65-70% (Q1 2026). DMA preliminary gatekeeper view issued June 2026; final decision expected November 2026. Maximum DMA infringement fine: 10% of worldwide annual turnover. Data Act switching-fee deadline: January 12, 2027.”
Supports
Specific pricing data, regulatory timeline, and penalty structure for cloud vendor lock-in.
https://shattered.io/aws-azure-eu-gatekeeper-designation-2026/

#2: Cloud free switching programs have negligible practical impact on competition

Source
TechPolicy.press / Foundation for American Innovation (POLICY_ANALYSIS) — 2026-10-01
Excerpt
“In 2024, AWS, Azure, and GCP introduced fee exemptions for customers switching clouds. An EU-commissioned report found one-time data transfer costs represent less than 1% of yearly cloud expenses. The real lock-in is product bundling through cloud marketplaces with tiered discounts.”
Supports
Proves that egress fee waivers alone don't solve lock-in; structural barriers persist.
https://www.techpolicy.press/cloud-needs-more-than-fee-waivers-to-be-competitive

#3: UK enterprise cloud repatriation: 50TB egress costs $4,292/month; 37signals saves $10M

Source
CompareTheCloud.net (ENTERPRISE_COST_ANALYSIS) — 2026-10-01
Excerpt
“Moving 50TB out of AWS: $4,292/month at list price. Azure: $4,182/month. 37signals documented savings 'will now top ten million over five years' after repatriating from AWS. But it took roughly two years to fully materialize. EU Data Act caps 'in parallel use' egress from September 12, 2025.”
Supports
Concrete cost data for egress fees and real repatriation case study with savings timeline.
https://www.comparethecloud.net/articles/repatriating-to-ovhcloud-or-renegotiating-aws-and-azure-for-uk-enterprises

#4: AI vendor exit clauses: 0-90 days to export; DMA duties collide with 3-year commitments

Source
Beri.net (LEGAL_ANALYSIS) — 2026-10-05
Excerpt
“Analysis of how AI vendor exit clauses provide 0 to 90 days for data export, and how AWS/Azure DMA duties landing midway through 3-year cloud commitments create regulatory-commercial collision for enterprises.”
Supports
Documents the contractual lock-in dimension and the timing collision between DMA compliance and existing commitments.
https://www.beri.net/article/ai-vendor-exit-clauses-data-export-model-deprecation-change-of-control-price-transition

#5: EU to designate AWS and Azure as DMA gatekeepers: global cloud industry restructuring

Source
Bloomberg / 彭博社 (NEWS_MEDIA) — 2026-10-04
Excerpt
“EU regulators completing investigation to designate AWS and Azure under DMA. Final decision expected November 2026. Once designated, 6-month compliance clock starts. Enterprises face bundling, lock-in, and high migration barriers. European providers (OVHcloud, Scaleway) positioning as alternatives.”
Supports
Confirms regulatory timeline and enterprise lock-in problem from Chinese-language media perspective.
https://m.toutiao.com/article/7692729440157942335/

Scoring

Problem Reality
88
Commercial Opp.
78
Confidence
85

Decision

GO

Cloud vendor lock-in is a real, structural infrastructure problem confirmed by the most significant cloud regulatory intervention in history (EU DMA + Data Act). The egress fee is the visible symptom; proprietary service dependencies are the disease. 37signals proved repatriation works ($10M+ over 5 years) but it took 2 years and dedicated engineering. Clear buyer (enterprise IT, cloud architects). Regulatory timeline creates urgency (DMA November 2026, Data Act January 2027). Risk: low defensibility because providers can adjust pricing faster than startups build tools; free switching programs may reduce urgency if made more effective. Commercial opportunity moderated by long sales cycles and provider adaptation speed.

Research Conclusion

Cloud vendor lock-in is an infrastructure-grade problem with regulatory confirmation. The EU DMA gatekeeper designation (November 2026) and Data Act switching-fee ban (January 2027) represent the first mandatory intervention in cloud lock-in globally. For enterprises, the problem is real but the solution path is long: 37signals needed 2 years and dedicated engineering to realize $10M in savings. The commercial opportunity exists in cloud cost optimization, migration tooling, and multi-cloud management — but defensibility is limited because the big three providers control pricing and terms. This problem is distinct from AI-specific costs (covered by PDE problems v5, v6) because it targets infrastructure-level lock-in regardless of workload type.

Unknowns

What specific DMA compliance obligations will be imposed on AWS/Azure?
How will AWS and Azure restructure pricing in response to Data Act switching-fee ban?
Will European providers (OVHcloud, Scaleway) achieve feature parity with managed services?
What is the actual enterprise adoption rate of multi-cloud strategies post-regulation?
How will AI service lock-in intersect with cloud infrastructure lock-in?