OddessyDOCUMENTATION
GET STARTED Live

Control plane and edge architecture

Understand the identity, fleet, model, release and physical-control boundaries in an Oddessy deployment.

Last updated 27 July 2026 ยท Documentation version 2026.07

Reference architecture

Oddessy control plane and edge architecture showing identity, tenancy, releases, outbound heartbeat, local camera and model runtime, audit and the authoritative industrial-control boundary
Oddessy separates the AWS control plane, customer edge plane and authoritative site-control plane.

Control plane

The AWS control plane uses Cognito for invited users, DynamoDB for tenant-scoped device state and short-lived enrolment records, S3 for private versioned artifacts, Lambda/API Gateway for the service API, and CloudFront for the public and authenticated web surfaces.

Edge plane

The Linux runtime maintains an outbound heartbeat, reports hardware profile, camera/model/health provenance and consumes an approved OTA directive. It verifies artifact size and SHA-256 before a root-owned updater activates a versioned slot. Failed core health checks restore the previous slot.

Windows plane

The Windows MSI installs a LocalSystem service for enrolment, health, model-manifest and device management. Windows upgrades use the approved MSI channel rather than Linux slot-based OTA.

Not a safety PLC

The reference controller and its software make no safety-PLC claim. Production deployments require site-specific risk assessment, segmentation, credential policy and functional-safety engineering.