Skip to content

AetherIoT platform overview

AetherIoT is the open-source project identity for a family of interoperable, edge-first IoT products. It is not a fourth runtime and does not own a separate wire protocol.

AetherIoT
├── AetherEdge edge runtime, Kernel, CLI, and SDK
├── AetherCloud cloud fusion and governed control plane
└── AetherContracts public specifications, Schemas, fixtures, and TCK
AetherEMS energy-management solution built on the platform
Product Owns Does not own
AetherEdge Live point state, acquisition, deterministic rules, safety interlocks, local history, and final physical execution Cloud placement, provider resources, or public protocol authority
AetherCloud Desired placement, governed cloud jobs, tenant control-plane state, and multi-cloud coordination Edge live-state authority or provider-native actual state
AetherContracts Language-neutral protocol semantics, closed Schemas, fixtures, stable failure classes, and executable conformance evidence Product runtime behavior, credentials, cloud durability, or deployment policy
AetherEMS Energy-domain models, workflows, and solution experience The industry-neutral platform core

Every infrastructure provider remains authoritative for the actual existence and provider-native state of its resources. Cloud failure must not stop a commissioned AetherEdge runtime.

  • Use AetherIoT for the project, community, website, and complete platform.
  • Use AetherEdge for the repository and product that were formerly named AetherIot.
  • Keep existing aether-* crate names, the aether CLI, the aether-edge-sdk package, installer names, and protocol identifiers stable.
  • Preserve historical release artifacts and digest-pinned AetherContracts bundles byte for byte. A new display name never rewrites old evidence.

Read the AetherIot to AetherEdge migration guide for repository and automation changes.

This site is the common entry point. Each product repository remains the source of truth for its implementation details, while AetherContracts remains the sole authority for shared protocol behavior. The unified pages link to those sources instead of copying normative content into a second authority.

Continue with deployment topologies, user journeys, or the Edge to Contracts to Cloud tutorial.