Platform - Fleet identity

Device identity, ownership, and inventory in one model.

Dataplicity keeps devices, customers, and firmware tied to the same record so ops never loses context.

  • Inventory stays tied to customer and warranty data.
  • Groups and tags drive rollout cohorts.
  • Device classes define provisioning defaults per SKU.
  • Fleet search uses the same metadata across modules.
Dataplicity device inventory for the Northstar demo fleet with tagged devices across customer sites

Inventory model

Every device record carries ownership, firmware, and health metadata.

Devices

Devices view

Track last check-in, firmware, tags, and status in one table.

Customers

Customer accounts

Bind devices to customer accounts and entitlements without spreadsheets.

Cohorts

Groups + tags

Saved cohorts for lab, pilot, and field rollouts.

Ownership

Customer metadata

Keep customer records attached to every deployed unit.

Cohorts and segmentation

Inventory metadata becomes a control plane for firmware and ops.

  • Cohorts drive firmware targeting and alert routing.
  • Customer segmentation stays consistent across ops views.
  • Entitlements and warranty context follow the cohort.

Filters

Saved cohort filters

Reuse the same tag logic across alerts, rollouts, and ops.

Ownership

Customer scoping

Slice fleets by customer without exporting data.

Lifecycle

Warranty windows

Warranty and license context stays visible in ops workflows.

Lifecycle context

Provisioning, ownership, and licensing stay tied to inventory from day one.

Provisioning

Device classes

Standardize metadata and config per device SKU.

Ownership

Customer accounts

Bind devices to customer accounts without spreadsheets.

Licensing

License bundles

Track entitlements and coverage windows inside Dataplicity.

Ready to validate the workflow?

Install the agent and see inventory and logs in one place.