Appearance
Choose the right Dataplicity agent path #
You should not need to understand Dataplicity's process model before you can connect or support a device. Start with the outcome.
| What you need to do | Start here |
|---|---|
| Build Dataplicity into a Linux product you are shipping now | Integrate the modern agent |
| Understand what runs on the device and why | Modern agent architecture |
| Operate or support devices already using the modern agent | Operate the modern agent |
| Publish product data, receive settings, or run Class Software | Connect your product application |
| Review network, privilege, credential, or storage boundaries | Modern agent security |
| Support an existing device that runs the classic agent | Legacy agent |
| Decide whether an existing fleet should move | Move from legacy to modern |
Which agent is on this device? #
Do not decide from the age of the hardware. Check the services and commands on a representative unit.
A modern full installation normally has:
- a rescue service for identity and remote access;
dataplicity-supervisor.servicefor desired-state and product functions;- state under
/var/lib/dataplicity; - the
prelude-agentcommand.
A modern rescue-only installation deliberately omits the supervisor. It is still the modern agent, not the classic agent.
A classic installation commonly exposes the tuxtunnel program through supervisorctl and does not have the modern supervisor or local product broker. Exact layouts vary across old images, so inspect before changing one.
The practical difference #
| Modern agent | Legacy agent | |
|---|---|---|
| Best fit | New product images and current fleet-management integrations | Existing remote-access fleets that already work |
| Remote Shell and Wormhole | Yes | Yes |
| Product streams, actions, and settings | With the supervisor | No |
| Class Software and desired-state reconciliation | With the supervisor | No |
| Host Python | Python 3 for the supervisor; qualify the exact image | Broad mixed-age support, including Python 2.7 |
| Change policy | Actively developed | Actively supported; compatibility-frozen wire protocol |
| Migration pressure | Use for new integrations | No forced migration; legacy remote access keeps working |
The word supervisor in the modern docs means the Dataplicity management-plane service. It is not the third-party Supervisor process manager used by some classic installations.
One fleet can contain both #
You can keep legacy devices online while introducing the modern agent in new images or a bounded migration cohort. Operators should record agent generation, install mode, OS image and architecture in inventory so a runbook never applies modern commands to a classic device - or the reverse.