1035 points • 5 days ago • Article Link

作者描述了一次有意识的迁移：把整个数字基础设施从美国云服务迁向 European 替代方案，原因是他们对自己的数据和工具托管在自己无法控制、司法环境日益不可预测的服务器上感到越来越不安。作者认为，数字主权不是流行语，而是关于知道数据存放在哪里、不会因为一次政策变更或企业并购就失去对关键工具访问权的一种务实立场。这次迁移与其说是出于偏执，倒不如说是为了让基础设施选择与价值观保持一致。

分析工具是首个改动点。 Google Analytics 被自托管的 Matomo 替代：所有数据保留在作者自有服务器上，因而无需显示 Cookie 同意横幅。代价是增加了维护工作——作者必须负责更新与备份——但报告全面且界面熟悉。邮件服务从 Google Workspace 迁到 Proton Mail，后者基于 Switzerland，侧重隐私而非广告，在协议层面提供端到端加密。需要注意的是，Proton 的过滤系统不及 Gmail 强大，尤其无法根据邮件正文过滤；即便是高级方案，自定义域名也被限制为三个。密码管理也迁入 Proton 生态，采用 Proton Pass——一个端到端加密的开源工具，受同一 Switzerland 司法管辖，从 1Password 迁过去更多是横向替换而非升级。

在计算资源上，DigitalOcean 被 Scaleway 取代——这家位于 France 的云提供商出乎意料地给作者留下好印象：控制面板简洁、服务器启动迅速，并在选择地点时显示预计 CO2 排放量，这促使作者将大部分基础设施托管在 Paris 。对象存储从 AWS S3 迁到 Scaleway 的 S3 兼容服务，使用 rclone 迁移；由于 bucket 体量大，这一机械化过程耗时一周多。异地备份从 Backblaze 迁到 OVHcloud，作为 European 最大的云提供商之一，一旦配置生命周期规则把旧备份转入冷存储，会更划算；不过 OVH 的控制面板被形容为迷宫，需要耐心并配合终端操作才能顺利使用。

事务性邮件从 Twilio SendGrid 切换到 Lettermint——一个更精简的 European 服务，投递表现良好、定价透明；通过合并两个 SendGrid 账户，作者实际上节省了成本。错误追踪由 Sentry 改为自托管的 Bugsink，仅需一行配置就能接收 Sentry 的 SDK 。 Bugsink 功能本就精简，缺少性能监控和高级告警，但对作者来说，一个带堆栈跟踪的远程错误日志已足够，而且数据完全不离开他们的基础设施。 AI API 集成从 OpenAI 转到 Mistral——这家总部在 Paris 的提供商提供开放权重模型和清晰的 API，迁移在质量上属横向，但在资金去向和提供商价值观上更有意义。

并非所有服务都迁移。 Cloudflare 仍被保留为 CDN，因为其主要作用是缓存并保护已公开的内容，这改变了关于主权的考量；而其诸如安全规则和 Workers 平台等功能，Bunny CDN 未能充分替代。支付处理仍使用 Stripe，尽管作者更倾向于 EU 司法管辖，因为迁移会牵扯到账单逻辑、 webhook 和税务发票等，需要谨慎时机；Dutch 替代方案 Mollie 在他们的用例下反而更昂贵。 AI 代码辅助从 OpenAI 切到 Claude Code，后者仍基于美国，但作者之所以选择，是因为 Anthropic 在安全性和透明度方面的方法更有结构性基础；作者也指出，像 Alibaba 的 Qwen 这样的本地模型在完全在自有硬件上运行推理方面正变得越来越可行。 GitHub 也保留用于面向公众的 NPM 包和开源问题跟踪——网络效应和开发者预期让它成为现实的选择。

总体评价是积极的：大多数迁移只花了半天时间，少数耗时更久，但没有发生严重问题。两个月下来，一切平稳运行。作者的结论是，European 云生态大体成熟，工具可靠且功能完善，唯一阻碍他们的只是惰性。数字主权就是要意识到谁在持有你的数据、政治变化会带来什么影响，而这次迁移证明，完全可以主要依靠 European 基础设施来运行专业级的数字技术栈。 The author describes a deliberate migration of their entire digital infrastructure away from US-based cloud services toward European alternatives, driven by a growing unease with how much of their data and tooling sat on servers they didn't control, in a jurisdiction they found increasingly unpredictable. Digital sovereignty, they argue, isn't a buzzword but a practical stance about knowing where your data lives and not being one policy change or corporate acquisition away from losing access to critical tools. The migration was less about paranoia and more about aligning infrastructure choices with values.

Analytics was the first target. Google Analytics was replaced with a self-hosted Matomo instance, which keeps all data on the author's own server and eliminates the need for cookie consent banners. The tradeoff is maintenance overhead, since the author is now responsible for updates and backups, but the reporting is comprehensive and the interface familiar. Email moved from Google Workspace to Proton Mail, which is based in Switzerland and built around privacy rather than advertising, with end-to-end encryption at the protocol level. The adjustment worth noting is that Proton's filter system is more limited than Gmail's, particularly the inability to filter on email body content, and custom domains are capped at three even on higher-tier plans. Password management followed into the Proton ecosystem with Proton Pass, an end-to-end encrypted, open-source tool under the same Swiss jurisdiction, making the move from 1Password more of a lateral shift than an upgrade.

For compute, DigitalOcean was replaced with Scaleway, a French cloud provider that turned out to be a pleasant surprise with a clean control panel, fast server provisioning, and the notable feature of displaying projected CO2 emissions alongside location choices, which led the author to host most infrastructure in Paris. Object storage migrated from AWS S3 to Scaleway's S3-compatible offering using rclone, a mechanical process that took over a week due to bucket size. Offsite backups moved from Backblaze to OVHcloud, Europe's largest cloud provider, which is cheaper once lifecycle rules are configured to move older backups to cold storage, though the OVH control panel is described as a labyrinth that requires patience and terminal work to navigate.

Transactional email shifted from Twilio SendGrid to Lettermint, a leaner European service with solid deliverability and straightforward pricing that actually cut costs by allowing the author to merge two SendGrid accounts. Error tracking moved from Sentry to Bugsink, a self-hosted tool that accepts Sentry's SDK with a one-line configuration change. Bugsink is bare-bones with no performance monitoring or advanced alerting, but for the author's needs, a simple remote error log with stack traces, it works perfectly with no data leaving their infrastructure. AI API integrations switched from OpenAI to Mistral, a Paris-based provider with open-weight models and a clean API, making the transition lateral in quality while meaningfully better in terms of where the money goes and the values behind the provider.

Not everything moved. Cloudflare remains as the CDN because its role is to cache and protect already-public content, making the sovereignty calculus different, and its feature set including security rules and the Workers platform wasn't matched closely enough by the European alternative Bunny CDN. Stripe remains as the payment processor despite the author's preference for EU jurisdiction, because migration touches billing logic, webhooks, and tax invoicing in ways that require careful timing, and Mollie, the Dutch alternative, is more expensive for their use case. AI code assistance moved from OpenAI to Claude Code, which is still US-based but chosen because Anthropic's approach to safety and transparency feels more structurally grounded, and the author notes that local models like Alibaba's Qwen are becoming increasingly viable for running inference entirely on your own hardware. GitHub also remains for public-facing NPM packages and open source issue tracking, where network effects and developer expectations make it the practical choice.

The overall assessment is positive. Most migrations took an afternoon of work, a few took longer, and none were catastrophic. Two months in, everything runs without incident. The author's conclusion is that the European cloud ecosystem is mostly mature, the tools are reliable and capable, and the only thing that was stopping them was inertia. Digital sovereignty, they argue, is about being conscious of who holds your data and what happens when politics shift, and this migration proved it's entirely possible to run a professional digital stack mostly from European infrastructure.