Migration to European hosting

Leaving a hyperscaler is rarely a compute problem. Compute is easy. The difficulty is the managed services around it — the queue, the object store, the identity provider, the eleven Lambda functions nobody documented — and the egress bill that arrives on the way out.

So we start with an audit rather than a plan: what you run, what it costs, what holds data, what has an open-source equivalent, and what has to be rewritten. You receive that as a document. If it says staying put is cheaper, it says so.

The pattern that usually wins

Dedicated or virtual machines in Romania, Sweden or Germany, described in NixOS. PostgreSQL, MinIO and Redis run by you rather than rented. WireGuard between regions. Backups to a second provider in a second country, so that losing a vendor is an inconvenience rather than an extinction event.

The result is typically 40–70% cheaper per month, materially faster for European users, and — the part clients actually notice — a bill that no longer changes shape without warning.

Sovereignty, concretely

Data at rest in the EU or EEA. Providers incorporated in the EU or EEA, so that foreign disclosure statutes have no jurisdictional hook. Encryption keys held by you. Every one of those is a line in the architecture document, not a marketing claim.