We move regulated Danish companies from Azure and AWS to European cloud, and make them AI‑native on the way.
Sovereign infrastructure, autonomous agents and architecture that holds. Start with a three-week sovereignty assessment that ends in a go or a no-go.
What we do
Three things, in the order your supervisor asks the questions: where the systems run, what your AI does, and why it holds.
The move, not the destination
We move your systems from Azure, AWS or Google to European infrastructure, as code, with security and the supervisory controls built in. You keep your architecture and can move again.
- Terraform from day one, one thin layer per provider
- Scaleway as the preferred destination; UpCloud, STACKIT or Hetzner when the ground has to be Danish or German
- NIS2, DORA and CRA controls as code, not as a document
Intelligence on your own ground, not at the hyperscalers
We build autonomous agents into your business, not only into the development department, on infrastructure you control, with governance you can show the supervisor.
- Agents that work in your processes, not in a chat window
- Open models such as DeepSeek, Mistral and Qwen, run at a European provider or on your own GPUs, not through an American API
- Evaluation, guardrails and AI Act documentation from the start
Why it holds
Domain-driven design, event-driven architecture and APIs: what makes the move and the agents hold when the auditor and the traffic arrive.
- Bounded contexts as the unit of the move
- Event streams as the source of truth for data
- A rehearsed move that proves you can move again
Read more about each of the threeSee the map of European data centresPortable architecture and the rehearsed move, for those who stay
How we move you
A move is a scoped engineering job with a known end. Four steps, always in this order.
Three weeks. As-is, to-be, a migration proposal and a cost comparison. Ends in a go or a no-go.
Move order per bounded context, what moves first, and what the supervisor needs to see along the way.
The infrastructure is written as Terraform; the applications and their catalogue are not touched. Dev, test and prod are identical in shape.
We bring a workload up at a second European provider and record the hours. That is your exit plan, tested.
The method in full, the map, and the Danish companies that have already moved
Why now
Which means the question of where your systems run is no longer an IT question. It is a supervisory question with a date on it.
Start with an assessment
The first step is fixed in scope, time and price, and it ends in a decision, not a sales meeting.
Sovereignty assessment
- Three weeks
- As-is and to-be for your systems and data
- A migration proposal, per bounded context
- Cost comparison: hyperscaler against European cloud
- Go or no-go, written so it can be shown to the supervisor
Quick assessment
- One week
- As-is and to-be
- For startups and smaller systems
People
Martin Sponholtz
Founder & OwnerTwenty years of systems behind him: Danske Bank, Danske Commodities, OK, Norlys, AeroGuest, Kvarters. Architect and developer in one person, with security, IaC and legal specialists at hand when the assessment calls for them.
Answers the mail himself, within one working day: martin@nomadics.dk
Building something new?
- Startup programmes at European providers instead of AWS credits that run out
- AI‑native from day one, on infrastructure you can take with you
- An architecture that survives your first enterprise customer’s vendor review
The page for startupsWrite to Martin: martin@nomadics.dk