Cloud infrastructure sited and operated on your terms
THE MODEL
A cloud platform, not just a rack
EU Cloud in a Box is dedicated hardware with Edora’s cloud platform and operations on top.
You work with compute, storage and networking through the portal, API and Terraform. The platform is built on OpenStack, KVM and Ceph and can replace classic virtualisation and basic hyperscaler infrastructure.
VMs, containerised applications and data-intensive workloads can all be suitable candidates. How much change is needed depends on your integrations and how dependent you are on the current platform.
Edora delivers:
- Dimensioning of compute, storage and networking
- Build and configuration of the platform
- Integration with datacentre and network
- Operations and monitoring
You remain responsible for workloads and applications.
PLACEMENT
Put the capacity where it makes most sense
EU Cloud in a Box describes the dedicated cloud installation. The name does not mean it has to stand in your own datacentre.
Your datacentre
The capacity is installed in your facility and integrated with your existing power, cooling and network infrastructure.
That lets you place the cloud platform close to local data, production systems, OT environments and other latency-critical workloads. Edora builds and operates the platform, while you provide the agreed datacentre infrastructure.
Edora datacentre
The capacity can instead be placed with Edora, if you would rather not use your own server room or take on the physical datacentre facility yourself.
You still get dedicated hardware and the same Edora Cloud platform. Your locations can be connected directly to the capacity through the agreed network solution.
The choice depends on data placement, existing facilities, connectivity, redundancy and economics, among other things.
THE DIFFERENCE
More than on-premises hardware
Plenty of suppliers can deliver dedicated racks. The difference lies not in the cabinet alone, but in the coherence between the cloud platform, the network and the operations.
Part of Edora's cloud infrastructure
EU Cloud in a Box can be connected to Edora’s other cloud and datacentre locations through Edora Cloud Connect.
That makes it possible to establish backup, disaster recovery and geographic redundancy over direct optical links. Traffic between the directly connected locations therefore does not have to travel over the public internet.
European jurisdiction, operations in Denmark
Edora is Danish-owned, operates the cloud platform from Denmark and is subject to Danish law and applicable EU regulation.
That gives a clear line between platform operator, operations and jurisdiction. The specific data placement, supply chain and division of responsibility are documented as part of the solution.
Local operations if connectivity is lost
An installation in your datacentre is designed so that local workloads and core platform functions can continue if the link to Edora’s other locations is broken.
When the link is restored, the configured replication and synchronisation resume. Which functions remain available during a connectivity failure is defined and tested as part of the specific architecture.
USE CASES
Four situations where the model makes sense
Data has to sit in a specific physical location
Primary data and workloads can be placed in your own facility. Any backup and replication follows the data architecture and locations agreed with you.
Cloud capacity has to move closer to the systems
OT, production and other latency-critical environments can have the cloud capacity placed in the same facility as the systems the platform is there to support.
The existing platform has to be replaced
EU Cloud in a Box can serve as the target platform for a VMware exit or selective repatriation from a hyperscaler.
We establish what can be moved as is, what needs adapting, and what should perhaps stay where it is.
You want to offer cloud to your own customers
Datacentres, telecoms operators and MSPs can build a cloud offering under their own brand on dedicated Edora capacity.
FROM SCOPING TO OPERATIONS
A concrete route to your cloud platform
-
01
Establish needs and placement
We go through workloads, capacity consumption, data flows, integrations and availability requirements.
At the same time we assess whether the platform is better placed in your own datacentre or with Edora.
-
02
Design and compare the models
We outline the relevant capacity, network architecture, data placement and division of responsibility.
Where both placements are viable, we also compare investment, ongoing operations and what each option demands of your own organisation.
-
03
Build and go live
Edora delivers and configures the cloud foundation, integrates it with the agreed infrastructure and carries out testing and commissioning.
The platform then moves into the agreed operating model.
THE CAPACITY
A complete cloud foundation with room to grow
The standard configuration is adapted to the workloads, capacity requirements and availability requirements the solution has to support.
Usable storage capacity depends among other things on the chosen Ceph configuration and the redundancy requirements.
The final configuration is set on the basis of your actual workloads and expected capacity growth, not from a standard package alone.
PUBLIC PROCUREMENT
Procurement & framework agreements
In Denmark, Edora is a supplier on the SKI framework agreements 02.17 IT consultants and 02.22 IT operations, and has been admitted to the forthcoming 02.03 Servers and storage, which takes effect on 1 September 2026.
02.03 can be used for relevant hardware and associated services, including servers, storage, network equipment, racks, cooling, backup power, software and support. 02.17 can cover assistance with architecture, build and testing, among other things, while 02.22 can be used for relevant operational services.
The right procurement route depends on the content of the purchase and the terms in force under each agreement. We help clarify the appropriate model.
QUESTIONS & ANSWERS
What most people ask first
Does EU Cloud in a Box have to sit in our own datacentre?
No. The dedicated capacity can be placed in your own datacentre or with Edora. The cloud platform and the underlying operations are fundamentally the same in both models.
Can the data stay in our own datacentre?
Yes, the solution can be designed so that primary data and workloads run locally. Any backup, replication and disaster recovery follows the data architecture and locations agreed with you.
What does the installation require of our server room?
That depends on the configuration. Requirements for rack space, power, cooling, networking, physical security and access are established during the technical review.
Who owns the hardware?
The acquisition and ownership model is set out in the specific solution. Whichever model applies, the capacity is dedicated, and responsibility for hardware, platform and other operations is documented before the build begins.