HOW IT WORKS
From one community node to a distributed compute fabric
A CEAC operates locally but is designed to become part of a wider distributed infrastructure system. Compute, storage, connectivity, energy and telemetry are brought together at each node, while workloads that exceed local capability can be routed elsewhere.
LOCAL → FEDERATED → REMOTE
01
LOCAL REQUEST
A household, organisation, device or local service requests a digital or AI task.
02
LOCAL DECISION
The node determines whether the workload is appropriate for local execution based on capability, policy, availability and resource demand.
03
LOCAL EXECUTION
Suitable workloads can run on local CEAC compute without unnecessarily traversing remote infrastructure.
04
FEDERATED PLACEMENT
As the CEAC network develops, workloads can be placed across suitable nodes according to locality, available compute, network conditions and resilience, with energy-aware placement forming part of the future architecture.
FEDERATION PROTOTYPE
05
CLOUD / HYPERSCALE ESCALATION
Workloads that are unsuitable for CEAC hardware can continue to remote cloud, hyperscale or specialist compute.
06
MEASUREMENT
Node telemetry provides visibility into compute utilisation, network activity, energy use and system health, supporting better operation and future optimisation.
Distribution changes what infrastructure can be used
Very large data centres require very large sites, very large power connections and concentrated network infrastructure. A smaller node can potentially use opportunities that are individually too small for hyperscale development.
- Smaller electrical connections
- Local renewable generation
- Existing community sites
- Local storage
- Local network infrastructure
- Local waste-energy opportunities where appropriate
- Geographically dispersed demand
CEAC is designed to aggregate these smaller opportunities into a wider distributed infrastructure layer.