SpecsModelExploreRequirements
SpecsModelExploreRequirements
Edge
System at a glance
Containers
Design constraints
How edge fits the platform
Related workflows
Edge
Overview
Guide
Twin streams
Links and Communications

Edge

Edge is everything that runs outside the cloud — on the local gateway that sits next to the sensors, actuators and machinery. It is the platform’s presence in the physical world: it speaks the messy local protocols, survives flaky connectivity, and keeps control loops fast even when the link to the cloud is down.

Responsibility in one sentence

Run reliably on constrained, sometimes-offline hardware — collect telemetry, enforce local rules in milliseconds, and synchronise state with the cloud the moment connectivity allows.

System at a glance

Could not build diagram for model "example-iot".

Containers

Edge Agent

Collects telemetry from drivers, buffers it locally and publishes to the cloud broker.

Edge Rule Runtime

Evaluates rules on the local stream for low-latency, offline-capable control.

Design constraints

The edge is not a small cloud. It is shaped by the hardware it runs on:

  • Tight CPU and memory budgets — the whole stack targets a ~64 MB footprint.
  • No reliable local disk; writes must be durable but frugal.
  • Written in Rust for predictable, GC-free resource use.

How edge fits the platform

Related workflows

Telemetry leaves the edge and flows into the alert pipeline:

Commands from the cloud are dispatched down to the gateway: