What kind of organisation is fremverk best suited for?
We are best suited to organisations with real platform responsibility, meaningful compliance or jurisdiction pressure, and an existing cloud or hybrid estate that cannot simply be replaced with generic hosting.
Do all workloads need to move to EU-sovereign cloud?
No. In many cases, only selected workloads, control points, identities, data flows, or delivery paths need stronger European control. A mixed target state is often the right answer.
Is this only relevant for public sector organisations?
No. Public sector is an obvious fit, but the same questions also matter to regulated enterprises, critical suppliers, EU-headquartered companies, and teams facing procurement or customer questions about control and jurisdiction.
Do we have to replace Microsoft Entra or our current identity provider?
No. In many engagements, Entra or another existing enterprise identity provider remains in place. We only introduce a different identity layer when the operating model or sovereignty requirement actually calls for it.
Do you only work with greenfield platforms?
No. The normal starting point is an existing AWS, Azure, Google Cloud, or hybrid estate. The work is usually about designing a credible next state and moving toward it without breaking delivery.
What does a first engagement usually look like?
The smallest starting point is usually a focused workshop or assessment, often similar in shape to Learn. That is used to clarify constraints, identify what needs stronger control first, and define whether the next step should be design work, a platform build, or a migration track.
What can stay hybrid during a transition?
Identity, networking, existing business systems, and some application components can often remain where they are for a period. Hybrid is a normal transition pattern, not a failure state.
Do you only work with T Cloud?
T Cloud is the primary sovereign platform we build around because it has the service coverage and operating model we need for the target state. We also work with the surrounding toolchain, integration patterns, and hybrid dependencies that make that platform usable in practice.
What does the target platform usually include?
Typically one T Cloud account by default, enterprise projects as the main boundary, shared platform-management operations, a platform-connectivity boundary for shared network and DNS patterns, federated identity, infrastructure as code, Git and CI/CD, FunctionGraph-first for lightweight automation, security controls, monitoring, backup, and a clearer operating model for the customer team.
For the concise version, see the reference platform.
Are you replacing the customer team?
No. The model is designed to strengthen the customer team while delivery happens. That can mean advisory support, implementation, or side-by-side delivery with handover and runbooks.
How long does a serious platform build usually take?
It depends on the starting point and scope, but the first usable baseline is usually a scoped piece of work measured in weeks, not a multi-year transformation before anything becomes operational. On this site, a focused Perform is usually 6-10 weeks and Accelerate 12-16 weeks.
How should we decide whether to talk now?
Talk now if the cloud decision already has legal, procurement, customer, or operating-model consequences. If the question is still purely theoretical, start with the blog or a lightweight workshop first.
Let's talk