Start assessment Book a meeting
EDORA CLOUD · TECHNOLOGY

The technology behind the platform

The components, the design principles and the choices that make Edora Cloud a platform with no closed layers. Written for the people who have to operate, integrate or evaluate it.

THE COMPONENTS

What the platform is built from

Five components, all open source, all replaceable. Click through them.

OpenStack with a standard API in every environment

OpenStack with a standard API in every environment

OpenStack provides the API, scheduler and orchestration, with state and metadata in MariaDB. The standard API means anything that speaks OpenStack works without modification: Terraform, Ansible and your existing tooling.

Stateless nodes, reinstalled on reboot

Stateless nodes, reinstalled on reboot

The compute nodes run a read-only OS and are provisioned over PXE. A reboot is a reinstallation: no configuration drift, no local state to lose, and a minimal attack surface on the individual node. Faults are handled by replacement, not troubleshooting.

Distributed Ceph with an S3 layer on top

Distributed Ceph with an S3 layer on top

VM disks and data sit in distributed Ceph storage, replicated across nodes by default. MinIO provides the S3-compatible object layer, so existing S3 integrations work without code changes.

Distributed routing on a closed optical network

Distributed routing on a closed optical network

EVPN/BGP distributes routing without central points of failure, and transport runs over dark fibre between locations, bypassing the internet. The full network architecture is described on the Cloud Connect page.

Two independent ways into the platform

Two independent ways into the platform

Skyline is the primary portal and Horizon the secondary, and on top sits Edora’s own management layer with multi-region visibility and local autonomy. There is always a way in, even when one portal is unavailable.

PRINCIPLES

Four choices that explain the rest

No closed layers

Every component is open source. An exit is always technically real, and that also disciplines Edora as a supplier: the platform has to be good enough that you stay by choice.

Stateless by design

Compute nodes carry no state. Replacement instead of troubleshooting, no maintenance windows at node level, and a read-only OS as a security property.

API-first

The portal uses the same APIs as your automation. There is no function that can only be reached by clicking, and therefore no manual process that cannot be automated away.

Local autonomy

Each location routes and operates independently and survives loss of connectivity to the others. Failover is measured in seconds.

WHERE TO NEXT

The technology in context

The network beneath the platform

Cloud Connect: the closed N×100G fibre network that ties the locations together, bypassing the internet.

Cloud Connect

The same stack behind your own walls

EU Cloud in a Box: the entire platform delivered and operated in your own datacentre.

EU Cloud in a Box

The platform at a glance

Back to the product page: concept, workloads and locations.

Edora Cloud
TECHNOLOGY

Talk technology with Finn

Architecture, integrations and migration paths, straight with the person responsible.