Your product stays yours
Keep your hardware, supported Linux distribution and application. Your team owns sensing, control logic and the safety checks that run on the device.
Keep the product you have. Add the software to operate it.
Install one agent alongside your existing Linux application. Give your team remote access, fleet health and logs. Add a branded customer application when it serves your product.
Get the install command by email. Remote access is free on one device. Pricing
One agent on your device. One workspace for your team.
Dataplicity connects your Linux equipment to the people who operate it. Start with remote access, then add the capabilities your product needs.
The agent connects the device
Install the Dataplicity agent through a local command, your factory setup or an existing update process. It runs alongside your application and connects outbound.
Your team works from the device record
Find the unit, see its health and collected logs, and open a remote terminal. Keep customer and site context with the equipment you support.
Installation needs access to the device. Live remote access begins once the agent is online and able to reach Dataplicity; outbound network policies still apply.
Explore the architecture
Dataplicity fleet workspace: device inventory and a live Linux terminal.
Example customer application: silo levels, reading history and device controls.
Keep your product. Add the capabilities it needs.
Start with the problem you have today. Operate an existing fleet, release software, keep essential work local or build a customer application. You do not need to adopt everything.
Reach and support devices
Reach Linux devices behind customer networks. Investigate with Pulse, diagnostics and collected logs without replacing the application you already run.
Manage releases when you want to
Fleet operations works with the software and updater you already have. If useful, add managed application releases or RAUC fleet rollouts later.
Keep essential work local
Use explicit Edge execution, selected local data and bounded buffering for products that must tolerate unreliable connectivity.
Give customers an application
Provide scoped device views, records, controls and workflows in your brand while keeping engineering tools with your team.
Add the tools for the next job.
Use these capabilities together around the same devices. Check plan availability before choosing your rollout.
Find the right device
Organise equipment by product type, customer and site. Keep the context your support team needs.
Device inventory and ownershipBring the next batch online
Define a Device Class for a product type and use the right installation settings across a batch.
Device provisioningUnderstand a fault
Compare device health, search collected logs and reach an online device to investigate.
Fleet operationsRepeat a maintenance task
Schedule recurring jobs and review execution history. Use the controls appropriate to the devices you target.
Scripts and schedulesGive customers their own application
Show customers their equipment, data and permitted actions under your brand. Your engineers define and test the product workflow.
Customer applicationsControl and review access
Use team roles, identity controls and security activity to understand who accessed the system.
Security and audit scopeA prototype, a production batch or an existing fleet?
Choose a starting point that matches how you can reach your devices today. Prove the connection and one useful task before expanding.