Full Report
Attempt to go 'Made in EU' offers big tech escapees a reality check where lower cloud bills come with higher effort Building a startup entirely on European infrastructure sounds like a nice sovereignty flex right up until you actually try it and realize the real price gets paid in time, tinkering, and slowly unlearning a decade of GitHub muscle memory.…
Analysis Summary
# Industry News: Sovereignty vs. Convenience: The Reality of the ‘Made in EU’ Cloud Stack
## Summary
A deep-dive case study of a startup (hank.parts) migrating from AWS to an entirely European infrastructure stack reveals a significant "sovereignty tax." While the move achieved lower cloud bills and data residency, it required unlearning a decade of US-centric ecosystem habits and replacing managed SaaS with high-effort self-hosting.
## Key Details
- **Date:** February 20, 2026
- **Companies Involved:** hank.parts (Startup), Hetzner, Scaleway, Bunny.net, Nebius, Hanko, Rancher/SUSE.
- **Category:** Market Trend / Infrastructure Migration.
## The Story
The founder of *hank.parts*, a European car parts marketplace, attempted to build a production-grade stack using exclusively European providers to escape the gravitational pull of US hyperscalers (AWS/Azure/GCP). The journey involved stitching together a fragmented ecosystem: **Hetzner** for raw compute, **Scaleway** for registries, **Bunny.net** for CDN, **Nebius** for AI/GPU, and **Hanko** for auth.
The founder reported that while the technical capabilities exist, the "glue" is missing. To avoid US-based SaaS lock-in, the startup had to self-host critical tools like secrets management, CRM, and CI/CD (using Gitea and Rancher). The experiment highlighted that "sovereignty" is currently a manual process requiring high engineering overhead to replace the "it just works" experience of the integrated Silicon Valley ecosystem.
## Business Impact
### For the Companies Involved
- **Hetzner/Scaleway:** Proven as viable, cost-effective alternatives for core infrastructure.
- **hank.parts:** Traded higher OpEx (engineering time) for lower CapEx (cloud bills) and eliminated the risk of vendor-driven "acquisition drama" or pricing hikes from US giants.
### For Competitors
- **US Hyperscalers:** Remain insulated by "ecosystem gravity" (GitHub, LinkedIn, social logins) rather than just raw infrastructure superiority.
- **European Providers:** Face a clear directive—they must improve interoperability and "community" features to compete with the social and workflow aspects of US platforms.
### For Customers
- **End Users:** May experience slightly higher latency or friction (e.g., lack of familiar social logins), but benefit from stricter data privacy and local jurisdiction protections.
### For the Market
- Highlights a growing "Sovereignty Gap": The market has the tools to host data in Europe, but lacks the integrated developer experience required for rapid scaling.
## Technical Implications
- **Self-Hosting Burden:** Moving away from managed services (DBaaS, managed K8s) increases the "tinkering" requirement, making Kubernetes management tools like **Rancher** critical components.
- **AI Latency:** AI inference remains a hurdle; while European GPU providers like Nebius exist, the most advanced models still often require calls to US-based API endpoints.
- **The GitHub Moat:** The "social graph" of coding (pull requests, issues, community) is harder to replicate than the Git repository itself.
## Strategic Analysis
- **Market Positioning:** European providers are positioned as the "Value and Privacy" choice, while US providers maintain the "Speed and Integration" crown.
- **Competitive Advantage:** Sovereignty-focused stacks offer immunity to US legislative changes (e.g., Cloud Act) and offer predictable, lower pricing.
- **Challenges:** The "Long Tail" of software (error tracking, CRM, analytics) is where the US monopoly is strongest; replacing these requires significant DevOps maturity.
## Industry Reactions
- **Founder Sentiment:** Described the experience as "leaving a city you’ve lived in for a decade"—functional but emotionally and procedurally taxing.
- **Analyst Perspective:** The experiment proves that the "Made in EU" stack is no longer a pipe dream, but remains a "pro-users" niche due to the high barrier to entry.
## Future Outlook
- **Predictable Growth in "Sovereignty-as-a-Service":** Expect more European mid-market providers to offer bundled, pre-integrated stacks to reduce the "tinkering" time identified here.
- **What to Watch:** Whether European regulatory pressure (GDPR, Data Act) eventually makes this high-effort path the mandatory path for EU startups.
## For Security Professionals
- **Shared Responsibility Shift:** Moving from AWS to a self-hosted "Made in EU" stack shifts significantly more security responsibility onto the internal team. You are no longer securing a configuration; you are securing the underlying systems (OS patching, container registry hardening, etc.).
- **Data Residency Compliance:** This approach provides the highest level of assurance for GDPR compliance and data sovereignty, eliminating "Schrems II" style legal risks.
- **Supply Chain Security:** Using tools like Gitea and self-hosted CI/CD offers total control over the software supply chain, but requires dedicated security resources to maintain that infrastructure against vulnerabilities.