“欧盟制造” – 基于欧洲基础设施的创业之路
I tried building my startup entirely on European infrastructure

原始链接: https://www.coinerella.com/made-in-eu-it-was-harder-than-i-thought/

## 构建欧洲创业技术栈:充满挑战但也值得的旅程 从AWS切换到完全欧洲的基础设施比预期的要复杂,但最终为了数据主权、GDPR合规以及支持欧盟科技公司,这一切都是值得的。作者成功地构建了一个技术栈,利用了多家供应商:Hetzner提供核心计算(价格出奇地实惠),Scaleway提供补充服务,如电子邮件和存储,Bunny.net提供CDN和安全,Nebius提供基于欧洲的AI推理。 大量自托管的实施使用了Kubernetes和Rancher,用于源代码控制(Gitea)、分析(Plausible)、CRM(Twenty CRM)等服务——优先考虑数据控制,尽管增加了维护工作。Hanko提供欧洲身份验证,但完全避免使用美国服务仍然很困难(Google Ads、Apple App Store、社交登录)。 虽然成本降低并且实现了数据驻留,但过渡并非一帆风顺。欧盟生态系统提供的资源较少,文档较薄,社区规模也小于美国巨头。需要积极努力克服默认设置倾向于美国供应商的情况。尽管存在挑战,作者认为这项努力是值得的,并倡导有意识地选择支持和构建于不断成熟的欧洲科技环境中。

这场 Hacker News 讨论围绕着完全基于欧洲基础设施构建初创公司的挑战,正如 coinerella.com 文章中所述。一个关键的结论是,在没有大量长期投资的情况下,*完全* 避免使用美国服务几乎是不可能的,尤其是在广告(Google Ads)和身份提供商(Google/Apple 登录)方面。 用户分享了他们使用欧洲供应商的经验:Scaleway 经常被赞扬为 Equinix Metal 和 Linode 的强大替代品,而 OVH 则收到了褒贬不一的评价。人们对域名系统 (ICANN) 中与美国的纠缠表示担忧。 对于源代码管理,建议使用 Gitea 的替代方案(Forgejo & Codeberg)。 寻找能够处理大规模营销邮件的欧盟供应商的困难也被强调,Mailjet(现在由美国公司所有)和 Brevo 被提及,但并非没有保留。 几位用户分享了他们当前的欧洲技术栈,包括 OVH 和 Scalingo,并寻求 PaaS 解决方案的替代方案。 讨论最终赞赏了文章对现状的现实评估。
相关文章

原文

When I decided to build my startup on European infrastructure, I thought it would be a straightforward swap. Ditch AWS, pick some EU providers, done. How hard could it be?

Turns out: harder than expected. Not impossible, I did it, but nobody talks about the weird friction points you hit along the way. This is that post.

Why bother?

Data sovereignty, GDPR simplicity, not having your entire business dependent on three American hyperscalers, and honestly, a bit of stubbornness. I wanted to prove it could be done. The EU has real infrastructure companies building serious products. They deserve the traffic.

The stack

Here's what I landed on after a lot of trial, error, and migration headaches.

Hetzner handles the core compute. Load balancers, VMs, and S3-compatible object storage. The pricing is almost absurdly good compared to AWS, and the performance is solid. If you've never spun up a Hetzner box, you're overpaying for cloud compute.

Scaleway fills the gaps Hetzner doesn't cover. I use their Transactional Email (TEM) service, Container Registry, a second S3 bucket for specific workloads, their observability stack, and even their domain registrar. One provider, multiple services, it simplifies billing if nothing else.

Bunny.net is the unsung hero of this stack. CDN with distributed storage, DNS, image optimization, WAF, and DDoS protection, all from a company headquartered in Slovenia. Their edge network is genuinely impressive and their dashboard is a joy to use. Coming from Cloudflare, I felt at home rather quickly.

Nebius powers our AI inference. If you need GPU compute in Europe without sending requests to us-east-1, they're one of the few real options.

Hanko handles authentication and identity. A German provider that gives you passkeys, social logins, and user management without reaching for Auth0 or Clerk. More on this in the "can't avoid" section — it doesn't eliminate American dependencies entirely, but it keeps the auth layer European.

Self-hosting: Rancher, my beloved

This is where things get fun... and time-consuming. I self-host a surprising amount:

  • Gitea for source control
  • Plausible for privacy-friendly analytics
  • Twenty CRM for customer management
  • Infisical for secrets management
  • Bugsink for error tracking

All running on Kubernetes, with Rancher as the glue keeping the whole cluster sane.

Is self-hosting more work than SaaS? Obviously. But it means my data stays exactly where I put it, and I'm not at the mercy of a provider's pricing changes or acquisition drama.

For email, Tutanota keeps things encrypted and European. UptimeRobot watches the monitors so I can sleep.

Transactional email with competitive pricing. This one surprised me. Sendgrid, Postmark, Mailgun, they all make it trivially easy and reasonably cheap.
The EU options exist, but finding one that matches on deliverability, pricing, and developer experience took real effort. Scaleway's TEM works, but the ecosystem is thinner. Fewer templates, fewer integrations, less community knowledge to lean on when something goes wrong.

Leaving GitHub. If you live in GitHub's ecosystem Actions, Issues, code review workflows, the social graph... walking away feels like leaving a city you've lived in for a decade. You know where everything is. Gitea is actually excellent, and I'd recommend it without hesitation for the core git experience. But you'll miss the ecosystem. CI/CD pipelines need to be rebuilt. Integrations you took for granted don't exist. The muscle memory of gh pr create takes a while to unwire.

Domain TLD pricing. This one is just baffling. Certain TLDs cost significantly more when purchased through European registrars. I'm talking 2-3x markups on extensions that are cheap everywhere else. I never got a satisfying explanation for why. If anyone knows, I'm genuinely curious.

What you realistically can't avoid

Here's the honest part. Some things are American and you just have to accept it:

Google Ads and Apple's Developer Program. If you want to acquire users and distribute a mobile app, you're paying the toll to Mountain View and Cupertino. There is no European alternative to the App Store or Play Store. This is just the cost of doing business.

Social logins. Your users expect "Sign in with Google" and "Sign in with Apple."
You can add email/password and passkeys, but removing social logins entirely is a conversion killer. Every one of those auth flows hits American servers. The silver lining: Hanko, a German identity provider, handles the auth layer itself, so at least your user management and session handling stay in Europe, even if the OAuth flow touches Google or Apple.

AI. If you want Claude, and I very much want Claude, that's Anthropic, that's the US.
The EU AI ecosystem is growing, but for frontier models, the options are mostly American. You can run open-weight models on European inference providers, but if you want Claude, you're making a transatlantic API call.

Was it worth it?

Yes, with caveats. My infrastructure costs are lower than they'd be on AWS. My data residency story is clean. I understand my stack deeply because I had to ... there's no "just click the AWS button" escape hatch.

But it took longer than I expected. Every service I self-host is a service I maintain.
Every EU provider I chose has a smaller community, thinner docs, and fewer Stack Overflow (or Claude) answers when things break at 2 AM.

If you're thinking about doing this: go in with your eyes open. The EU infrastructure ecosystem is real and maturing fast. But "Made in EU" is still a choice you have to actively make, not one you can passively fall into. The defaults of the tech industry pull you west across the Atlantic, and swimming against that current takes effort.

It's effort worth spending. But it is effort.

If you curious to see the finished product, here it is: hank.parts.

联系我们 contact @ memedata.com