# Platform Overview

> Understand the Infuse product family, who each area is for, and how the areas fit together.

Infuse is a connected-device platform for managing organisations, devices, embedded apps and algorithms, operational data, and analytics.

Most workflows cross product boundaries. For example, a marketplace storefront may use IAM credentials from Infuse Cloud, device IDs from Infuse-IoT Cloud, checkout from Infuse-Marketplace, and insight streams from Infuse-Analytics.

## Product Areas

<table>
<thead>
  <tr>
    <th>
      Area
    </th>
    
    <th>
      Primary audience
    </th>
    
    <th>
      What it covers
    </th>
  </tr>
</thead>

<tbody>
  <tr>
    <td>
      <a href="/docs/infuse-cloud">
        Infuse Cloud
      </a>
    </td>
    
    <td>
      Organisation owners and admins
    </td>
    
    <td>
      Organisation management, profiles, members, invitations, and shared account services.
    </td>
  </tr>
  
  <tr>
    <td>
      <a href="/docs/iam-and-access">
        IAM and Access
      </a>
    </td>
    
    <td>
      Admins and backend developers
    </td>
    
    <td>
      Users, groups, roles, permissions, service accounts, API keys, and token exchange.
    </td>
  </tr>
  
  <tr>
    <td>
      <a href="/docs/infuse-iot-sdk">
        Infuse-IoT SDK
      </a>
    </td>
    
    <td>
      Firmware and device developers
    </td>
    
    <td>
      Infuse-IoT SDK, Zephyr-based firmware guidance, board support, samples, embedded tooling, and generated SDK reference docs.
    </td>
  </tr>
  
  <tr>
    <td>
      <a href="/docs/infuse-iot-cloud">
        Infuse-IoT Cloud
      </a>
    </td>
    
    <td>
      Device-platform developers, backend developers, and fleet operators
    </td>
    
    <td>
      Device identity, boards, networks, console operations, provisioning, device state, configuration, commands, definitions, and connectivity APIs.
    </td>
  </tr>
  
  <tr>
    <td>
      <a href="/docs/infuse-db">
        Infuse-DB
      </a>
    </td>
    
    <td>
      Data and platform engineers
    </td>
    
    <td>
      Ingestion, datasets, querying, and retention for telemetry and operational streams.
    </td>
  </tr>
  
  <tr>
    <td>
      <a href="/docs/marketplace">
        Infuse-Marketplace
      </a>
    </td>
    
    <td>
      App and algorithm developers, providers, and reseller teams
    </td>
    
    <td>
      App and algorithm publishing, provider listings, storefronts, checkout, purchases, releases, and installs for compatible Infuse-IoT SDK devices.
    </td>
  </tr>
  
  <tr>
    <td>
      <a href="/docs/infuse-analytics">
        Infuse-Analytics
      </a>
    </td>
    
    <td>
      Product, operations, and data teams
    </td>
    
    <td>
      Planned operational insight over live and historical device data.
    </td>
  </tr>
</tbody>
</table>

## Infuse-IoT SDK And Infuse-IoT Cloud

Infuse-IoT SDK and Infuse-IoT Cloud are intentionally separate in the docs because they serve different personas.

- **Infuse-IoT SDK** is for code that runs on the device: firmware architecture, SDK usage, board support, samples, and generated embedded reference material.
- **Infuse-IoT Cloud** is for device operations and platform workflows: console-based fleet inspection, boards, networks, device records, provisioning APIs, state lookups, configuration, commands, definitions, and connectivity endpoints.

They meet at shared contracts such as device identity, provisioning material, RPC definitions, TDF definitions, KV definitions, routes, and telemetry context.

## Typical Paths

- **Organisation admin:** [Register a user](/docs/getting-started/register-a-user), [create an organisation](/docs/getting-started/create-an-organisation), invite members, then configure [API access](/docs/infuse-cloud/api-access).
- **Firmware developer:** start with [Infuse-IoT SDK](/docs/infuse-iot-sdk), then review the [Infuse-IoT SDK](/docs/infuse-iot-sdk/sdk-reference) docs.
- **Device platform developer or operator:** start with [Infuse-IoT Cloud](/docs/infuse-iot-cloud), then follow [Console](/docs/infuse-iot-cloud/console), [Boards](/docs/infuse-iot-cloud/boards), [Devices](/docs/infuse-iot-cloud/devices), [Provisioning](/docs/infuse-iot-cloud/provisioning), [Commands](/docs/infuse-iot-cloud/commands), and the [Infuse-IoT Cloud API reference](/api-reference/iot).
- **Data engineer:** start with [Infuse-DB](/docs/infuse-db), then follow [Stream IoT Data to Infuse-DB](/guides/data/stream-iot-data-to-infuse-db).
- **Infuse-Marketplace developer or provider:** start with [Infuse-Marketplace](/docs/marketplace), then choose the developer or provider path and follow [Build a Storefront](/docs/marketplace/providers/build-a-storefront) if you are reselling embedded apps or algorithms through your own site.

## Shared Prerequisites

Most product workflows require a registered user, an organisation, and suitable access before the product-specific steps work.

- If you are new to Infuse, start with [Register a User](/docs/getting-started/register-a-user).
- If you need a workspace, continue with [Create an Organisation](/docs/getting-started/create-an-organisation).
- If you were invited to an existing organisation, register and confirm your user first, then accept the invitation from [Members and Invitations](/docs/infuse-cloud/members-and-invitations).
- If you are integrating APIs, review [API Access](/docs/infuse-cloud/api-access) and [API Keys](/docs/iam-and-access/api-tokens).