Edge Devices

Edge appliances are physical or virtual devices deployed on customer premises (OT/IT networks). They act as local sensors and gateways that communicate outbound-only with Monozu Cloud.

Role in the system

graph LR
    subgraph CustomerSite ["Customer Site"]
        EdgeDevice["Edge Appliance<br>(RAUC image)"]
        Network["OT/IT Network"]
        HostAgent["Host Agent<br>(planned)"]
    end

    subgraph MonozuCloud ["Monozu Cloud"]
        CloudAPI["Cloud Backend API"]
        Ingestor["Ingestor Service"]
    end

    Network -->|"scan / monitor"| EdgeDevice
    HostAgent -->|"prefer LAN"| EdgeDevice
    HostAgent -.->|"fallback"| Ingestor
    EdgeDevice -->|"claim + commands"| CloudAPI
    EdgeDevice -->|"telemetry"| Ingestor

What Edge devices do

Capability	Cloud API	Ingestor
Claim-code registration	POST /v1/devices/announce, claim-status, claim-complete	—
Command polling	GET /api/v1/commands	—
Telemetry / discovery / alerts	—	POST /v1/ingest (various kinds)
Host Agent gateway (planned)	—	Local host_inventory → queue → ingest
OTA (RAUC)	Commands + update APIs	—

Authentication

Credential	How obtained	Used for
claim_token	announce response	Poll claim-status, claim-complete (bootstrap only)
api_key	claim-complete	Commands, Cloud device APIs
X-Device-Key	Same as api_key	Ingestor POST /v1/ingest
mTLS client cert	Optional at claim-complete	Device TLS to Cloud (Devices CA)

Registration uses claim codes — not provisioning/registration keys. See Device Registration.

Software packaging

Edge devices run a RAUC-updatable image with monozu CLI (monozu edge register). Legacy snap/edgezu-tui paths are removed.

Related pages

• Device Registration
• Telemetry
• Commands & OTA
• Host Agents (endpoint inventory via Edge gateway)