Table of Contents
We built CloudUnit in a market where the default cloud answer was usually one of the US hyperscalers. That work gave us deep practical experience in landing zones, identity, networking, automation, operations, platform engineering, and delivery at scale.
That experience still matters. What has changed is the market around it, and the questions clients now need answered.
That is why we are becoming fremverk. The work is no longer only about helping organisations navigate the big US platforms. It is increasingly about helping them move critical workloads, operating models, and engineering practices into EU-sovereign environments without losing speed, quality, or technical discipline.
Why CloudUnit is becoming fremverk#
For us, the CloudUnit name belonged to an earlier chapter. It matched a period when much of the work centered on cloud enablement in ecosystems dominated by US vendors.
The fremverk name is a better fit for what we are actually building now: foundations, operating models, and modern platform capabilities for organisations that need stronger European control over infrastructure, data, and delivery.
This is not a rejection of cloud in general, and it is not a claim that every workload must leave US providers immediately. It is a recognition that many organisations in Europe now need a credible sovereign option, and they need it to work in practice rather than only on paper.
What the name means#
The name is intentionally Nordic in tone.
Frem points to forward movement, progress, and transformation. Verk points to work, craft, and execution. Together, the name says something important about how we want to operate: not only advising on the direction, but helping build the target state and getting the work done.
Why the time is right#
Three changes make this shift timely.
- EU-sovereign cloud platforms are materially more mature than they were a few years ago.
- Regulatory, procurement, and governance pressure has increased across both public and private sectors.
- Customers want a realistic migration path, not a theoretical discussion about sovereignty.
That combination matters.
For a long time, the gap between the sovereignty requirement and the available platform capability was too wide. Today that gap is much narrower. The question is no longer whether there are usable EU alternatives for serious workloads. The real question is how to adopt them with the same engineering discipline that teams already expect from mature cloud programmes.
The expertise still transfers directly#
One of the most common misunderstandings in this space is that moving from a US hyperscaler context to an EU-sovereign cloud context requires starting over.
It does not.
The provider catalogue changes. The legal and operational constraints change. Some architecture choices change. But a large share of the work remains exactly the kind of work experienced cloud teams already know how to do.
- Identity and access management still has to be designed carefully.
- Network boundaries, ingress, egress, and segmentation still matter.
- Infrastructure as code still needs structure, policy, review, and drift control.
- CI/CD still needs isolation, secrets handling, and repeatability.
- Observability, backup, disaster recovery, and cost control still determine whether a platform is viable in production.
- Teams still need operating models that balance central guardrails with delivery autonomy.
That is where our background remains useful. Years spent working with modern cloud operations and DevOps practices on US platforms are not wasted effort. They are transferable engineering capability.
What changes in an EU-sovereign model#
The transfer is real, but it is not one-to-one. EU-sovereign delivery adds different design priorities.
Jurisdiction and operating model#
The conversation is not only about regions and services. It is about who controls the platform, which legal regime applies, how administration is performed, and what evidence can be produced when procurement, compliance, or audit questions appear.
Service mapping and architecture choices#
Teams cannot assume that every managed service, every developer convenience, or every integration pattern will look identical to a hyperscaler baseline. Good architecture work means mapping the real requirement to the real service catalogue instead of forcing old assumptions into a different platform.
Portability has to be more than slogan#
When sovereignty becomes a first-class design concern, portability and exit posture become more concrete. Open tooling, clean interfaces, and deliberately chosen abstractions matter more because they reduce strategic lock-in over time.
What we bring into this next phase#
The move from CloudUnit to fremverk is not a move away from engineering depth. It is a clearer expression of where that depth is applied.
We bring forward the parts that matter most.
- Practical experience with cloud foundations and landing zones.
- Broad knowledge of operational cloud patterns across security, networking, governance, and resilience.
- Platform engineering discipline that keeps environments usable, supportable, and automatable.
- DevOps practices that make delivery repeatable instead of person-dependent.
- A migration mindset focused on reducing risk while keeping business momentum.
That combination is exactly what organisations need when they want to move toward EU-sovereign cloud without turning the journey into a disruptive reset.
What clients should expect from fremverk#
Clients should expect practical decisions rather than abstract sovereignty language.
We help assess what genuinely needs sovereign treatment, what can move now, what should be redesigned, and where existing delivery practices can be carried forward rather than rebuilt. We work across architecture, platform build, security, operations, and migration so the result is not a theoretical target state, but a platform your team can run, govern, and improve.
We are not changing the name to sound different. We are changing it because the work now demands a clearer position.
fremverk is the continuation of the same engineering discipline under a name that more honestly matches the work ahead: helping European organisations build, move, and operate on EU-sovereign cloud with fewer abstractions and more technical clarity.
If you want to discuss what a practical move from hyperscaler-first to EU-sovereign cloud could look like for your organisation, let’s talk.
