# Infuse-IoT Cloud

> Device operations, provisioning, connectivity, commands, and fleet management for Infuse-IoT products.

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](/docs/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

<table>
<thead>
  <tr>
    <th>
      Concept
    </th>
    
    <th>
      What it represents
    </th>
  </tr>
</thead>

<tbody>
  <tr>
    <td>
      Organisation
    </td>
    
    <td>
      The account boundary that owns users, access, linked IoT resources, credentials, marketplace activity, and device operations.
    </td>
  </tr>
  
  <tr>
    <td>
      Linked Infuse IoT organisation
    </td>
    
    <td>
      The Infuse-IoT Cloud organisation connected to the active Infuse platform organisation. Console IoT pages operate inside this linked organisation.
    </td>
  </tr>
  
  <tr>
    <td>
      Board
    </td>
    
    <td>
      A hardware or product profile used to group devices by board type, SoC, and board-specific metadata rules.
    </td>
  </tr>
  
  <tr>
    <td>
      Network
    </td>
    
    <td>
      A device network with a numeric network ID and key used by device connectivity workflows.
    </td>
  </tr>
  
  <tr>
    <td>
      Device
    </td>
    
    <td>
      The registered physical or logical device, identified by Infuse <code>
        deviceId
      </code>
      
      , MCU ID, board, organisation, and metadata.
    </td>
  </tr>
  
  <tr>
    <td>
      Device state
    </td>
    
    <td>
      The latest operational state reported for a device, including last seen time, application version, status, and algorithms.
    </td>
  </tr>
  
  <tr>
    <td>
      Metadata
    </td>
    
    <td>
      Device labels and product-specific fields, including fields required or marked unique by the board profile.
    </td>
  </tr>
  
  <tr>
    <td>
      KV entries
    </td>
    
    <td>
      Device key-value configuration and state entries, including decoded values, raw values, and pending updates.
    </td>
  </tr>
  
  <tr>
    <td>
      Logger state
    </td>
    
    <td>
      Per-logger sync progress and download enablement state for devices that report logged data.
    </td>
  </tr>
  
  <tr>
    <td>
      Applications and releases
    </td>
    
    <td>
      Infuse IoT application metadata, release versions, board compatibility, CoAP file metadata, and device application update state.
    </td>
  </tr>
  
  <tr>
    <td>
      RPC commands
    </td>
    
    <td>
      Command requests sent to devices and the delivery/response state associated with them.
    </td>
  </tr>
  
  <tr>
    <td>
      Definitions
    </td>
    
    <td>
      Versioned RPC, TDF, and KV schemas used to encode, decode, and display device data.
    </td>
  </tr>
  
  <tr>
    <td>
      MQTT token
    </td>
    
    <td>
      A short-lived organisation-scoped token for MQTT connectivity.
    </td>
  </tr>
  
  <tr>
    <td>
      Provisioning keys
    </td>
    
    <td>
      Cryptographic material derived during secure device provisioning and communication.
    </td>
  </tr>
</tbody>
</table>

## 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

<card-group>
<card icon="i-lucide-layout-dashboard" title="Use the console" to="/docs/infuse-iot-cloud/console">

Understand the Infuse IoT console area and what each page is for.

</card>

<card icon="i-lucide-circuit-board" title="Boards" to="/docs/infuse-iot-cloud/boards">

Define hardware profiles, SoCs, and device metadata rules.

</card>

<card icon="i-lucide-router" title="Devices" to="/docs/infuse-iot-cloud/devices">

Search devices, inspect state, update metadata, queue KV updates, and send commands.

</card>

<card icon="i-lucide-package" title="Applications and releases" to="/docs/infuse-iot-cloud/applications-and-releases">

Browse application releases and schedule device application updates.

</card>

<card icon="i-lucide-key-round" title="Provisioning" to="/docs/infuse-iot-cloud/provisioning">

Register devices, derive keys, and automate manufacturing or backend onboarding.

</card>
</card-group>

For endpoint-level request and response schemas, see the [Infuse-IoT Cloud API reference](/api-reference/iot).