Fleet structure #

What is this? #

A fleet is the deployed inventory an organisation manages. Dataplicity provides several structures rather than one universal group:

networks for organisation-owned membership and operational statistics
device classes for product lines and durable deployment configuration
tags for lowercase operational labels and selectors
customers and sites for business ownership and location where those modules are enabled

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

Use stable properties and custom tags to search and filter inventory. Fleet monitors and jobs can use supported combinations of class, included tags, excluded tags, and any-or-all matching. Always review the resolved target before an action.

Scheduled HTTP tasks are a separate integration mechanism. Use Fleet jobs for confirmed commands across selected devices.

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 monitor or run a guarded fleet action on an explicitly previewed cohort
You are moving from prototype to production fleet management

Example workflow #

An IoT vendor provisions devices into a product class, associates supported customer and site records after first connection, and applies environment and rollout tags. Engineering previews a selected cohort before a fleet action. Support uses the dedicated customer or site relationship where enabled and operational tags for temporary filtering.