# Infuse-DB

> Scalable IoT time-series data layer for live and historical device data.

Infuse-DB is the scalable IoT time-series data layer for Infuse. It stores high-volume device telemetry, keeps raw and computed device streams aligned with Infuse-IoT Cloud, and gives teams fast access to live and historical fleet data.

Use Infuse-DB when your product needs to store, query, and retain timestamped telemetry without designing a custom database or data pipeline for every deployment.

Infuse-DB is designed for teams that need to:

- deploy telemetry storage quickly,
- scale to millions of timestamped records,
- query devices by customer, environment, location, or asset group,
- store both raw and computed device streams,
- choose cloud-managed, private, or on-prem hosting for data control.

## How Infuse-DB Fits Together

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

<tbody>
  <tr>
    <td>
      Dataset
    </td>
    
    <td>
      A logical grouping for related device or product data.
    </td>
  </tr>
  
  <tr>
    <td>
      Telemetry stream
    </td>
    
    <td>
      A sequence of timestamped records from devices, gateways, jobs, or integrations.
    </td>
  </tr>
  
  <tr>
    <td>
      Raw stream
    </td>
    
    <td>
      Source telemetry as received or normalized by the ingestion path.
    </td>
  </tr>
  
  <tr>
    <td>
      Computed stream
    </td>
    
    <td>
      Derived values created from raw telemetry, such as summaries, signals, or enriched records.
    </td>
  </tr>
  
  <tr>
    <td>
      Timestamped record
    </td>
    
    <td>
      A data point with an event time and associated device or operational fields.
    </td>
  </tr>
  
  <tr>
    <td>
      Device dimensions
    </td>
    
    <td>
      Fields such as device, customer, environment, location, board, or asset group used to filter and segment data.
    </td>
  </tr>
  
  <tr>
    <td>
      Ingestion
    </td>
    
    <td>
      The workflow that writes records into Infuse-DB.
    </td>
  </tr>
  
  <tr>
    <td>
      Querying
    </td>
    
    <td>
      The workflow that retrieves live or historical fleet data.
    </td>
  </tr>
  
  <tr>
    <td>
      Retention
    </td>
    
    <td>
      The policy for how long data remains available for operational and historical access.
    </td>
  </tr>
  
  <tr>
    <td>
      Hosting model
    </td>
    
    <td>
      The deployment option for data control: cloud-managed, private, or on-prem.
    </td>
  </tr>
</tbody>
</table>

## Where Infuse-DB Fits In The Platform

- **Infuse-IoT Cloud** manages device identity, provisioning, communication state, definitions, commands, and telemetry context.
- **Infuse-DB** stores raw and computed device streams for live and historical access.
- **Infuse-Analytics** can use live and historical device data to create decision-ready insight streams.

For a cross-product ingestion flow, see [Stream IoT Data to Infuse-DB](/guides/data/stream-iot-data-to-infuse-db).