Documentation

Appearance

Dataplicity in your operations stack ​

Dataplicity brings post-shipment operations together around each device, customer, fleet, and support workflow. Your teams can move from fleet status to logs, remote access, monitoring, and customer context without rebuilding that relationship in every tool.

One operational context ​

Dataplicity provides:

  • outbound Remote Shell, Wormhole, and resilient file retrieval
  • device inventory with online status and properties
  • tags, groups, and customer or site context
  • logs and monitors linked to devices
  • alerts, scheduled operations, roles, permissions, and audit history
  • status pages for customer-facing service visibility

Connect specialist systems ​

Use Dataplicity as the device operations layer alongside the systems your organisation already relies on:

  • Observability: keep fleet and application analytics in your chosen platform while Dataplicity provides device-level access and context
  • ITSM: keep ticket workflows in your service desk and link responders to the affected device
  • Corporate networking: use your network controls for internal infrastructure while Dataplicity reaches devices on customer networks through outbound connections
  • Engineering access: use direct local tools in the lab and Dataplicity for consistent access after deployment

Reduce operational glue ​

Dataplicity keeps device identity, customer context, access, logs, monitors, and support workflows together. This gives support and engineering teams a shared operational view as a fleet grows.

Next steps ​