Network usage

Dataplicity traffic varies with heartbeat frequency, remote support sessions, logs, diagnostics, monitors, file retrieval, Wormhole services, fleet jobs, and your own application.

Measure data transfer on a representative device and network so your estimate reflects the services, log volume, remote sessions, and update cadence in your deployment.

Measure your workload

Before rollout:

1. Build a staging device with the production image
2. Connect it through a representative customer or cellular network
3. Exercise normal idle operation for several days
4. Run the support, logging, monitoring, and maintenance workflows you expect
5. Record ingress and egress at the network interface or gateway
6. Repeat for each materially different device class

Include peak support sessions and failure conditions, not only idle traffic.

Control avoidable traffic

• Keep debug logging bounded
• Avoid sending repetitive high-volume events
• Set monitor and automation frequency to the operational need
• Use filters and retention appropriate to the fleet
• Schedule large retrieval or maintenance work for suitable network windows

Check your organisation's current usage and service limits in the dashboard. Contact support@dataplicity.com when planning a constrained or high-volume deployment.