A developer has described moving much of a personal and business technology stack to European or privacy-oriented providers, presenting the exercise as a practical test of digital sovereignty rather than a claim that every replacement was superior. The migration covered analytics, email, passwords, computing, object storage, transactional mail and error tracking.
Data location, jurisdiction and dependence on a provider's future policy were the main selection criteria. The author replaced Google Analytics with a self-hosted Matomo instance, keeping visitor data on an independently managed server. That brought direct control but also transferred responsibility for updates, backups and system health to the operator.
Email and password management moved into Proton's Swiss-based ecosystem. The account praised its privacy-focused business model and encryption while identifying constraints: mail filters could not search message bodies, custom-domain allowances were limited for the author's needs, and the service cost more than some alternatives. Moving from 1Password to Proton Pass was described as a lateral change made partly for consolidation, rather than a clear functional upgrade.
Infrastructure changes produced a similar balance. The author moved workloads from DigitalOcean to Scaleway and found the European platform's controls, private networking and server provisioning suitable for the required work. Scaleway's display of projected carbon emissions influenced the choice to host most computing in Paris. Its S3-compatible storage reduced application changes, although transferring large buckets with rclone reportedly required more than a week of continuous synchronization.
OVHcloud became a backup destination because the author found its cold-storage lifecycle pricing favorable for that use. Configuration was less approachable, however, with lifecycle controls requiring documentation research and terminal work. Transactional email moved from two SendGrid accounts to Lettermint, reducing costs and simplifying accounts at the expense of SendGrid's broader analytics, integrations and accumulated support material. A self-hosted tool called Bugsink was also selected for error tracking because it accepted Sentry's SDK, though the author characterized it as comparatively basic.
The report's central finding is not that geography removes operational compromise. Regional and self-hosted services can reduce certain dependencies and give an operator clearer control over data, but they may demand more maintenance, migration effort and product evaluation. Some chosen providers are European Union-based, while Proton is Swiss; the stack is therefore better understood as a sovereignty-oriented portfolio than a strictly EU-only system.
As a first-person case study, the migration does not establish broader performance, compliance or cost results. It does offer a concrete inventory of trade-offs for teams considering whether jurisdiction and ownership should carry more weight in infrastructure decisions. Any organization attempting a similar move would still need to validate contractual, security and regulatory requirements for its own workloads.
