Why fremverk exists
#

fremverk was built around a simple observation: enterprises that want to reduce jurisdiction and delivery risk often lack a practical path from hyperscaler dependence to a sovereign operating model.

Too many initiatives stop at strategy decks, compliance presentations, or isolated migrations. We built fremverk for teams that need a real transition, where platform, governance, identity, security, observability, and handover are treated as one connected delivery.

That is why EU-sovereign cloud is not a slogan for us. It is a way to make control, accountability, and day-to-day operations clearer for critical workloads. We have collected the legal and regulatory background here: Read the analysis →

The story behind our approach
#

Our approach is shaped by three practical perspectives.

Søren Hartvig Jensen comes from the hyperscaler-to-sovereign side, with experience across US hyperscaler platforms, target architectures, and transformation paths. Jan Ulnits brings the delivery and operating perspective, shaped by years of turning complex customer engagements into structured execution with clear ownership, momentum, and handover. He and Søren were the original founders of CloudUnit, the company that has now evolved into fremverk. Martin Haslund Johansson comes from the hybrid and classic enterprise side, where existing estates, integrations, and operating realities cannot be ignored.

That combination matters. A credible sovereign platform is not created by changing hosting alone. It has to offer a stronger target state while still working against the environment the customer already runs. That is why we combine platform engineering with governance, security, operations, and realistic migration paths.

fremverk is not built as a one-person profile either. The core is a small, experienced team, backed by specialists when the work calls for deeper support.

How we work with customers
#

We start from the current estate and assess what can realistically be moved, standardised, or modernised.
We design and build landing zones, shared platform services, security controls, and delivery patterns that hold up in production.
We stay through the runbooks, handover, and operating model work until the customer team can take ownership with clarity.

That means customers do not just get a target architecture. They get a more realistic operating foundation for moving from AWS, Azure, Google Cloud, or hybrid environments into a sovereign platform.

If you want the shortest route into the offer, start with the FAQ or the reference platform.