Skip to content

Fleet structure

What is this?

Fleets are collections of devices you manage together. In Dataplicity, fleets are organised using tags - searchable labels attached to devices that let you filter, group, and operate on subsets of your hardware.

Why does it matter after devices ship?

A commercial deployment spans devices across customers, regions, firmware versions, and deployment stages. Fleet organisation helps support teams find the right device quickly and run operations across a group.

How does it work in Dataplicity?

Dataplicity supports:

  • Device property tags - automatically generated from device properties (OS, architecture, etc.)
  • Custom tags - manually set labels such as customer:acme, site:warehouse-3, or firmware:2.1.0

Use device property tags and custom tags to organise, search, and target fleets.

Use tags to search, filter, and scope scheduled tasks and monitors to specific groups.

When should I use it?

  • You manage more than a handful of devices
  • Support needs to find devices by customer, site, or region
  • You want to run a scheduled task on all devices with a specific firmware version
  • You are moving from prototype to production fleet management

Example workflow

An IoT vendor tags devices with customer, site, and deployment-stage during factory imaging. When firmware 2.2.0 is released, engineering filters by firmware:2.1.0 and schedules an upgrade task across matching devices. Support filters by customer:acme to see only that customer's fleet.