Start assessment Book a meeting
HYPERSCALER REPATRIATION

Take control back from the hyperscalers

Get a more controllable cloud setup by moving the workloads that no longer need the hyperscaler’s complexity, pricing model or proprietary services.

We help you clarify what should move, what should stay, and how the transition can be carried out in controlled stages.

BENEFITS

An alternative to the current cloud model

More predictable economics

Dedicated capacity can be sized against known workloads and expected growth. That gives a clearer basis for budgeting and long-term capacity planning.

European operations and jurisdiction

Workloads and data can run on Danish infrastructure under Danish and EU law. That is a stronger starting point for organisations with heightened requirements for control and documentation.

About data sovereignty

Less proprietary dependency

Edora Cloud is based on OpenStack, KVM, Ceph and open standards. That reduces dependence on a single proprietary cloud platform and creates a more portable foundation.

See the technology behind the platform

Direct connections

Edora Cloud Connect can connect customer, partner and cloud locations directly. It supports both hybrid architectures and controlled data transport between the connected environments.

See Edora Cloud Connect

THE PROCESS

Move in stages — with a plan for dependencies, testing and rollback

Repatriation is carried out in defined waves. Each wave can be tested and validated before the next part of the environment is moved.

About VMware exit
  1. 01

    Map the environment

    We map workloads, data flows, technical dependencies, capacity consumption, security requirements and current costs.

    The aim is to create a factual basis for decisions — not to assume that everything should move.

  2. 02

    Classify and prioritise

    Each workload is assessed on portability, business criticality, economics and dependence on proprietary services.

    You get a prioritised plan for what can move directly, what requires adaptation, and what should stay.

  3. 03

    Migrate under control

    Workloads are moved in an agreed sequence, with testing and validation after each stage. That reduces risk and leaves room to adjust along the way.

THE DECISION

Move what makes sense

Once workloads become stable and predictable, it can be worth revisiting economics, technical lock-in, data location and jurisdiction.

Book a meeting

Move

Stable VM, container and data-intensive workloads, plus systems that require operations in Denmark, clear jurisdiction or more predictable capacity.

Keep

Workloads that are tightly integrated with proprietary platform services or need the hyperscaler’s global scale and specialised ecosystem.

Combine

Build a hybrid architecture where selected workloads move while others continue to run at the hyperscaler.

BUILT TO BE MOVED

We run our own products on the same foundation

Edora Cloud is not only a platform we offer to others. Edora’s own products already run on the same cloud foundation, and we depend on the platform’s operations, automation and availability ourselves.

The platform delivers compute, storage and networking through a portal and API. Capacity can be hosted at Edora or established as dedicated infrastructure through EU Cloud in a Box.

See the Edora Cloud platform

PUBLIC PROCUREMENT

Procurement & framework agreements

In Denmark, Edora is available via the SKI framework agreements, so relevant Edora services can be procured through the agreements we are party to. That gives Danish public-sector organisations an established route to buying European cloud infrastructure and related services.

Edora is a supplier on 02.22 IT operations and 02.17 IT consultants. That means both the subsequent operations and the consultancy that may be needed for mapping, planning and migration can be procured through frameworks that have already been tendered.

If the procurement also covers servers or storage, Edora has been admitted to the forthcoming 02.03 Servers and storage, which takes effect on 1 September 2026.

Which agreement and award model to use depends on the specific delivery. Our SKI page sets out the individual agreements, services and options.

See Edora's SKI agreements
NEXT STEP

Find out what should move — and what should not

The first conversation starts from your current cloud environment. We identify the relevant workloads, the significant dependencies and a realistic next step. That might be a deeper analysis, a target architecture or a single scoped pilot workload — without you having to commit to a full migration up front.