Infuse-IoT Cloud
Infuse-IoT Cloud is the device infrastructure layer for low-power intelligent IoT products. It manages device identity, hardware profiles, networks, operational state, configuration, command delivery, application updates, connectivity credentials, and the cloud contracts used by Infuse-IoT SDK devices.
You can now work with Infuse-IoT Cloud in two ways:
- use the Infuse console for day-to-day fleet operations, boards, networks, device inspection, metadata, KV updates, logger state, application updates, commands, and MQTT token generation,
- use the APIs for automated provisioning, manufacturing flows, backend integrations, device registration, key derivation, bulk operations, and custom workflows.
If you are building device firmware, start with Infuse-IoT SDK. That section covers firmware responsibilities, the Infuse-IoT SDK, generated SDK reference docs, board support, samples, and embedded tooling.
How It Fits Together
| Concept | What it represents |
|---|---|
| Organisation | The account boundary that owns users, access, linked IoT resources, credentials, marketplace activity, and device operations. |
| Linked Infuse IoT organisation | The Infuse-IoT Cloud organisation connected to the active Infuse platform organisation. Console IoT pages operate inside this linked organisation. |
| Board | A hardware or product profile used to group devices by board type, SoC, and board-specific metadata rules. |
| Network | A device network with a numeric network ID and key used by device connectivity workflows. |
| 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 last seen time, application version, status, and algorithms. |
| Metadata | Device labels and product-specific fields, including fields required or marked unique by the board profile. |
| KV entries | Device key-value configuration and state entries, including decoded values, raw values, and pending updates. |
| Logger state | Per-logger sync progress and download enablement state for devices that report logged data. |
| Applications and releases | Infuse IoT application metadata, release versions, board compatibility, CoAP file metadata, and device application update state. |
| RPC commands | 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. |
| Provisioning keys | Cryptographic material derived during secure device provisioning and communication. |
Console Or API
Use the console when an operator or developer needs to inspect or manage a fleet directly:
- create and review boards,
- create and review networks,
- search and inspect devices,
- edit device metadata,
- inspect KV entries and queue KV updates,
- inspect logger sync state,
- inspect applications and releases,
- schedule device application updates,
- send RPC commands,
- generate MQTT tokens for development or trusted operational workflows.
Use the API when the workflow should be automated or kept in a trusted backend:
- create or reconcile devices during manufacturing,
- derive shared or device keys,
- issue credentials from a backend service,
- integrate provisioning with your ERP, test rig, gateway, or fleet-management system,
- perform bulk operations,
- build custom workflows that cannot be completed manually in the console.
Platform Context
Infuse-IoT Cloud is the source of truth for device identity and device communication context. Other Infuse products build on that foundation:
- Infuse Cloud owns organisations, members, roles, permissions, API credentials, and shared platform services.
- Infuse-Marketplace uses device IDs, board compatibility, application releases, and install workflows for apps and algorithms.
- Infuse-DB stores raw and computed device streams for live and historical fleet access.
- Infuse-Analytics turns live and historical device data into operational insight streams.
Start Here
For endpoint-level request and response schemas, see the Infuse-IoT Cloud API reference.