Keep one ops layer across ancient and brand-new images

Connected-product and internal fleets often mix decade-old Linux images with new Ubuntu 24.04 builds. An ops agent that only chases “current Python” breaks half the estate - or forces two control planes.

Without Dataplicity

Legacy units are abandoned or hand-SSH’d. Modern rollouts wait on a rewrite. Nobody shares one inventory.

With Dataplicity

1. Use the dual install path (curl | sudo python) that works when the system python is 2 or 3.
2. Match agent release to the host. Legacy fleets stay on the legacy agent default (0.5.11). Modern hosts - including Ubuntu 24.04 / Python 3.12 - need 0.5.13 or newer. Do not expect 0.5.11 on 3.12.
3. Confirm check-in for both cohorts under one organisation inventory.
4. Treat compatibility as release + system Python, not a promise of every minor version forever (for example 3.8 and 3.13 are not in the certified matrix).

Outcome

One ops layer across mixed-age field reality.

Next

• Connect your first device
• Supported operating systems
• Agent lifecycle

Related: Field advantages, Keep your runtime