OddessyDOCUMENTATION
GET STARTED Live

Oddessy developer platform

Build governed industrial AI integrations across edge devices, model provenance, verified releases and operator-facing agents.

Last updated 27 July 2026 ยท Documentation version 2026.07
Physical-world control boundary

Oddessy observes, explains and manages approved software workflows. Human review, configured policy, PLC logic, safety relays and safety-rated controls remain authoritative.

Oddessy architecture from authenticated operator and agent access through the AWS control plane and edge runtime to bounded industrial systems
Reference system boundary. Open the vector image for a full-resolution view.

What Oddessy provides

Oddessy is a local-first industrial AI platform for visual inspection, cell safety, site security and flow monitoring. It combines an AWS-hosted control plane with an edge runtime, explicit model provenance, tenant-scoped fleet management and governed software releases.

CapabilityCurrent surfaceBoundary
Fleet managementWindows and Ubuntu enrolment, health and telemetryTenant-scoped identities and outbound device connections
Model provenanceModel name, version, source, runtime and SHA-256Tracked only when a valid digest is declared
Verified releasesPrivate downloads and Linux pull-based OTAApproved artifacts only; SHA-256 required
Agent accessRead-only MCP beta and personal API tokensNo deployment, enrolment or plant-actuation tools
Hosted intelligenceArgo, Security VLM and Industrial VLA demosReal AWS-hosted models; scenario actions remain simulated

Choose your starting point

  1. Evaluate the product. Run the hosted scenarios at oddessy.io and document the intended deployment boundary with an Oddessy administrator.
  2. Request access. Use the invitation CTA at platform.oddessy.io.
  3. Enrol edge compute. Install Oddessy Edge on QCS6490/Ubuntu or the Windows management agent.
  4. Connect an agent. Create a read-only token and connect to https://mcp.oddessy.io/mcp.

Service map

Oddessy public service map linking the product site to Platform, Documentation, MCP, Status and OpenAPI surfaces
The product, management, developer, agent and operational surfaces remain independently addressable.