Infuse IoT
Infuse IoT is the maintained device infrastructure layer for low-power intelligent IoT products. It combines an open, maintained firmware codebase built on Zephyr RTOS with cloud APIs for device identity, provisioning, cryptographic key workflows, telemetry state, command delivery, and device-side definitions.
Infuse IoT does not currently have a dedicated dashboard UI. Treat the current product surface as API-led infrastructure: backend services create and manage device records, provision credentials, issue MQTT access, read operational state, send RPC commands, and connect device data into the rest of Infuse.
Use Infuse IoT when you want to stop rebuilding the IoT foundations for every product:
- ship from a hardened Zephyr-based base instead of starting from scratch,
- get device infrastructure to market faster and cheaper,
- keep security, compliance, and operational patterns built into the foundation,
- connect device identity and state to Marketplace, Infuse DB, and Infuse Analytics insight streams.
How Infuse IoT Fits Together
| Concept | What it represents |
|---|---|
| Organisation | The account boundary that owns boards, networks, devices, credentials, and API access. |
| Board | A hardware or product board profile used to group devices and define board-specific metadata. |
| Network | A connectivity or deployment grouping for devices. |
| Device | The registered physical or logical device, identified by Infuse deviceId, MCU ID, board, organisation, and metadata. |
| Device state | The latest operational state reported for a device, including timestamps and route context. |
| Route | The last known communication path for a device, used when sending downlink work such as RPC messages. |
| Logger state | Per-logger download progress and enablement state for devices that report logged data. |
| KV entries | Device key-value configuration and state entries, including pending updates. |
| RPC messages | Command requests sent to devices and the delivery/response state associated with them. |
| Definitions | Versioned RPC, TDF, and KV schemas used to encode, decode, and display device data. |
| MQTT token | A short-lived organisation-scoped token for MQTT connectivity. |
| Shared and device keys | Cryptographic material derived during secure provisioning and device communication. |
Where Infuse IoT Fits In The Platform
Infuse IoT is the source of truth for device identity and device communication context. Other Infuse products build on that foundation:
- Infuse Cloud owns organisations, access, and shared platform services.
- Marketplace uses device IDs when customers buy and install products for specific devices.
- Infuse DB stores raw and computed device streams for live and historical fleet access.
- Infuse Analytics turns live and historical device data into decision-ready insight streams for analytics, ML, and AI use cases.
Current Integration Surface
Start with Devices to understand the registry model, then follow Provisioning to create device records and credentials. Use Telemetry and State for operational state workflows, Commands and RPC for device actions, Definitions for schema registries, and Connectivity for MQTT and CoAP support.
For endpoint-level request and response schemas, see the Infuse IoT API reference.