Hundreds of edge sites. One control plane.

edgeContinuum manages distributed edge infrastructure the only way that survives the real world: an agent at every facility reconciles desired state locally, so every site is driven from a single point yet keeps running on its own when the link goes down.

One console and API for the whole fleetAn agent per site: reconciliation happens at the edgeOutages don’t stop a site; it resyncs when the link returns
Single point of management
edgeContinuum
Factory flooredge siteagent
Remote plantedge siteagent
Retail / telco POPedge siteagent
… scaled to hundreds of facilities

Central orchestration dies with the WAN

Most platforms manage remote sites by remote control: a central brain pushes commands over the network, and the day the link drops, nothing at the site can change, heal or restart. At edge scale that design fails weekly. edgeContinuum inverts it: the control plane holds the desired state for every facility, and an agent at each site does the actual reconciliation locally. The center decides what should be true; the edge makes it true, and keeps making it true, connected or not.

Agent-based architecture

An agent at every facility

Each edge site runs its own agent against the local infrastructure. The agent pulls the site’s desired state and reconciles it on site: provisioning, healing, restarts. Deploy one agent or hundreds, one per facility; every new site joins the same console, the same API, the same tenancy model.

Desired state per siteLocal reconciliationOne agent per facilityFleet-wide rollouts
One site, connected
Control planeholds desired state
Site agentpulls & reconcilesagent
Provisionnew resources
Healdrift & failures
Restartwhat stops
The same loop runs at every facility
Link independence

An outage is a non-event

When a site loses its uplink, nothing dramatic happens: workloads keep running, the local agent keeps enforcing desired state, healing and restarting what fails, and local management stays available. When connectivity returns, the site resyncs with the control plane and picks up whatever changed. The same property, taken to its extreme, powers our air-gapped deployments.

Workloads unaffectedHealing continues offlineResync on reconnect
During an outage
Control planeunreachable
Site agentstill reconcilingagent
Clustersrunning
VMsrunning
Databasesrunning
Fleet at scale

Every facility, from one point

Shape your facilities into regions and availability zones and operate them as one platform: curate the catalog once, roll it out everywhere, watch health and usage across the fleet from a single console. Adding facility number two hundred looks exactly like adding the second: connect the infrastructure, the agent takes it from there.

Regions & zonesOne catalog, every siteFleet-wide health viewUsage per site & tenant

Kubernetes at the edge

Managed, conformant clusters at any site, hosted control planes for small footprints.

VMs & databases

The same managed services as your data center, at every facility.

Apps everywhere

Marketplace products rolled out across sites and fleets in one action.

Same guardrails

Organizations, projects and quotas apply at the edge like anywhere else.

Frequently asked questions

What happens when an edge site loses connectivity?
Workloads keep running and the site’s agent keeps reconciling desired state locally: healing, restarts and local management continue. When the link returns, the site resyncs with the control plane automatically.
How many sites can one control plane manage?
The architecture is built for fleets: one agent per facility, deployed by the hundreds, all driven from a single console and API. Reconciliation load stays at the edge, so the center does not become the bottleneck.
What runs at each edge site?
The site’s OpenStack infrastructure plus the edgeContinuum agent. On top of that, the same managed services as anywhere else on the platform: Kubernetes, PostgreSQL, VMs and marketplace apps.
Do we need platform staff at each facility?
No. Sites are operated from the central console; the agent handles on-site reconciliation automatically. Local intervention is for hardware, not for the platform.
Is this a separate edge product?
No, it is the same platform: edge sites are regions like any other, with the same console, API, tenancy and managed services. Autonomy under link loss is how every region works.

Bring the fleet under one console

Book a call and we’ll walk your edge topology: sites, regions, agents and what an outage looks like on the platform. Or start with one site on the free trial.