Off the US cloud. Onto European ground.

Five principles

1. Infrastructure as code from day one

   Nothing is clicked together in a portal. Everything that can be recreated lives in Terraform in your own repository.

2. The bounded context as the unit of the move

   We move one delimited business area at a time, with its data and its APIs, never “the whole estate” at once.

3. Parallel running, never a big bang

   The new environment runs beside the old one until the numbers match. Then we switch. Never a weekend with crossed fingers.

4. Your own repositories

   The code, the pipelines and the documentation sit with you from the first day. The day we leave, you lack nothing.

5. A way back at every step

   Every step can be rolled back. That is not pessimism; it is what lets the supervisor and your head of operations say yes.

Six steps

Always in this order. Under each step is what you see on your side while it happens.

1. Assess

   Three weeks with your architects: inventory of systems and data, jurisdiction and supervisory requirements, architectural seams and lock-in, costs today against a European estimate.

   You see: A report with a go or a no-go, a target landscape and a phased plan. Possibly a no.

2. Draw the target landscape

   Which provider, which regions, what is managed and what you run yourselves. Where data lives and who can reach it. The exit plan is written here, not afterwards.

   You see: One diagram your security people and the supervisor can read.

3. Build the landing zone in Terraform

   Network, Kubernetes, databases, secrets, logging and access as code. Dev, test and prod identical in shape, so dev can rehearse what prod must do.

   You see: Three environments that can be deleted and recreated in an afternoon.

4. Move context by context

   The least connected business area first. Data is synchronised, the application runs in both places, differences are measured.

   You see: One area at a time running on European ground while the rest stands untouched.

5. Cut over

   Traffic and data point at the new environment. The old one stays on, but quiet, until the numbers have matched for long enough.

   You see: A date on which the hyperscaler stops sending invoices.

6. Hand over

   Operations documentation, runbooks, access, and the first rehearsed move: a workload brought up at a second European provider, with the hours recorded.

   You see: An estate you can move again yourselves.

The move as code

$ terraform plan
- module.azure.azurerm_kubernetes_cluster.main
- module.azure.azurerm_postgresql_flexible_server.main
- module.azure.azurerm_key_vault.main
+ module.scaleway.scaleway_k8s_cluster.main
+ module.scaleway.scaleway_rdb_instance.main
+ module.scaleway.scaleway_secret.app[7]
  module.platform (unchanged: 7 apps)

Plan: 41 to add, 0 to change, 38 to destroy.

Where the systems can live

European cloud is not one provider in Paris. It is a dense network of data centres, and two of them sit on Danish soil. The map shows where a Danish company can move today, and what is on its way.

Where we move you to

Danish organisations that have already moved

No other Danish site collects them. Every figure is from public sources: the providers’ own pages, Ingeniøren, Version2 and DigiTech.

No C25 company has done anything comparable; the largest have chosen the hyperscalers’ “sovereign” editions. For them the conversation is a different one: not about moving, but about being able to.

The Kvarters migration

What it costs and how long it takes

The assessment gives the number for your estate. As a bearing: a system with a few bounded contexts moves in weeks; Kvarters took five. What moves the price is the number of systems, the volume of data, and how many proprietary services need a replacement.

Book an assessment