Skip to main content
Version: v1.1

Platform Model

AosEdge connects cloud-side management with edge-side execution.

This page explains the platform model at a high level. It does not describe internal AosCloud architecture, internal AosCore components, APIs, protocols, or code.

Platform model overview​

AosEdge has two main layers.

AosCloud is the management and orchestration layer.

AosCore is the runtime layer installed on a Unit.

Users interact with AosCloud. Units run AosCore. AosCloud sends target state and operational instructions. AosCore applies them locally and reports actual state back.

This creates a feedback loop:

  1. Users define intent in AosCloud.
  2. AosCloud manages this intent across fleets and Units.
  3. AosCore applies the target state on each Unit.
  4. Units report actual state, telemetry, logs, alerts, and deployment results.
  5. Users review the feedback and continue operation.

Cloud-side management with AosCloud​

AosCloud provides the cloud-side environment for managing the platform.

At product level, AosCloud supports:

  • Organizations and users
  • Roles and access control
  • Fleets, Unit Sets, and Units
  • Deployment planning and verification
  • Campaign management
  • Monitoring and operational visibility
  • API and UI access where available

AosCloud is where users manage the fleet-wide view of the system.

For cloud-side details, see AosCloud documentation.

Edge-side execution with AosCore​

AosCore runs on the Unit.

At product level, AosCore is responsible for:

  • Receiving instructions from AosCloud
  • Managing Deployable Items on the Unit
  • Applying target state locally
  • Reporting actual state back to AosCloud
  • Supporting monitoring, logs, alerts, and troubleshooting
  • Enforcing local runtime constraints

AosCore is the edge-side part of the system. It is installed into the OEM-controlled environment and operates locally on the Unit.

For runtime and integration details, see AosCore documentation.

Units and fleets​

A Unit is the managed edge system.

A fleet is a group of Units managed together.

Unit Sets can be used to organize smaller groups for staged operations, verification, rollout planning, or operational separation.

This structure allows the platform to work at several levels:

  • Individual Unit
  • Unit Set
  • Fleet
  • Organization or tenant scope

Deployment content model​

AosEdge uses unified deployment terminology.

A Deployable Item is the public-facing concept for content that can be delivered, installed, managed, and monitored on a Unit.

A Deployment Bundle groups multiple Deployable Items that must be delivered or managed together.

This model allows the documentation to describe delivery and lifecycle management consistently without making the top-level platform model depend on lower-level implementation categories.

State feedback loop​

AosEdge uses a feedback loop between the cloud and the edge.

AosCloud defines the target state.

AosCore applies the target state on the Unit.

The Unit reports actual state back to AosCloud.

This feedback helps users understand:

  • Whether the intended deployment was applied
  • Whether the Unit is healthy
  • Whether the Unit needs attention
  • Whether verification or rollout can continue
  • Whether troubleshooting is required

Operational visibility​

AosEdge provides operational visibility across managed Units.

Depending on the configured platform capabilities, users may see:

  • Unit status
  • Deployment state
  • Health and connectivity information
  • Resource usage
  • Logs
  • Alerts
  • Verification and campaign progress

This visibility helps OEMs, Fleet Owners, Service Providers, and Admins operate the system without direct physical access to every Unit.

Where detailed architecture lives​

This page explains the platform model only.

Use dedicated documentation sections for deeper details:

For the entry point, see AosEdge Overview.

For terminology, see Key Concepts and Glossary.

For practical scenarios, see Typical Use Cases.

For users and organizations, see Roles and Responsibilities.