Appearance
Choose a Dataplicity agent generation #
Dataplicity has two device-agent generations. They provide the same basic outbound remote-access path, but their packages, services, state, and product capabilities are different.
| Modern agent | Public legacy agent | |
|---|---|---|
| Choose for | New product integrations and Dataplicity OS | Existing remote-access fleets already using it |
| Distribution | Release wheelhouse from the private Prelude agent project | Public dataplicity 0.5.x source and package |
| Services | Rescue plus optional Dataplicity supervisor | Classic agent, often managed by third-party Supervisor |
| Product runtime | Streams, settings, actions, Class Software, optional RAUC management | Remote Shell, Wormhole, presence, and file access |
| State | Normally /var/lib/dataplicity | Varies by existing installation |
Dataplicity OS currently pins modern agent release 0.1.60. Its image contains the arm64 wheelhouse and creates the runtime under /opt/dataplicity/venv; both the rescue and supervisor services are included in each root filesystem slot. It does not build or install the public legacy 0.5.x source tree.
The lower modern version number does not indicate an older generation. The two projects have independent version histories.
Identify a device #
A modern full installation normally has dataplicity-supervisor.service, the prelude-agent command, and state under /var/lib/dataplicity. A modern rescue-only installation omits the supervisor by design.
A legacy device commonly runs the tuxtunnel process and may expose it through supervisorctl. Inspect a representative unit before applying an upgrade or support runbook.
Use Integrate the modern agent for new products. Keep using the legacy agent guidance for a working classic fleet unless you have a tested migration reason.