Open its terminal remotely
Connect one device and open its Linux terminal through the outbound agent connection.
Explore this capabilityStart with a prototype, a batch or an existing fleet.
You can start with a prototype, a production run or equipment already in the field. Choose the problem you need to solve. Keep the hardware, application and customer relationships you already have.
- Join at any stage.
- Operate devices for as long as you need, with no customer portal required.
- Add customer applications only when they serve your product.
A device on your desk
First prove you can reach and investigate a real device.
Investigate a fault first
Use public Device Check for a temporary diagnostic report without an account. You need a way to run its command on the device.
Explore this capabilityYour first pilot or production batch
Make support repeatable before each unit becomes a special case.
Repeat the installation
Use an organisation-specific installation process and Device Classes. Verify identity and first check-in on a representative batch.
Explore this capabilityCheck the pilot before expanding
Compare collected errors across a firmware cohort and investigate a suspect release before proceeding.
Explore this capabilityEquipment already in the field
Improve operations alongside the software and management process you already use.
Start with a reachable cohort
Install the agent through your existing remote access, update system or a planned site visit. Dataplicity access begins once that agent connects.
Explore this capabilityKeep your existing application
Your device runtime and customer application can stay. See where the agent, operating workspace and optional customer application fit.
Explore this capabilitySupport is becoming harder to manage
Give the next engineer the device context and evidence needed to pick up the work.
Investigate fleet-wide trouble
Scope affected devices, compare cohorts and use the available evidence to decide the next action.
Explore this capabilityDecide whether a site visit is needed
Bring device evidence and customer context into the support decision before dispatch or replacement.
Explore this capabilityCustomers need their own application
Build the customer job on the connected-device foundation.
Provide their devices, data and controls
Add a branded portal and scoped access. Extend it with records and workflows where the customer task requires them.
Explore this capabilityProducts change hands, need replacing or reach end of service
Keep service decisions tied to the equipment. Your team defines the handover and retirement process.
Preserve the service context
Keep customer, site and available service history in view when investigating an ageing or replacement unit.
Explore this capabilityMake the handover reviewable
Track replacement or retirement work with links to devices and incidents. Include ownership checks and access review in your process.
Explore this capabilityThe product is deployed. Now it has to keep working.
Start with the next operating gap rather than rebuilding the product around a platform.
Release the next software version
Target a bounded cohort and verify application or RAUC-image outcomes before expanding.
Explore this pathHandle an unreliable connection
Design local work, stored data and recovery around the essential customer job.
Explore this pathChoose what to replace
Compare the parts your existing tools already cover with the responsibilities Dataplicity can take on.
Explore this pathChoose one useful result to prove.
Start with remote access to a device you can reach, or inspect a complete customer application. Neither commits you to adopting everything.