Your hardware and runtime
You retain the board, operating system and application, including physical integration and safety logic.
Keep your product. Add the operating foundation.
Your Linux device and application keep doing their job. Dataplicity supplies the post-shipment layer around them: outbound device connectivity, identity, fleet operations and optional customer-facing software. The agent connects the device to the operating workspace; a branded customer application is optional.
- An outbound agent connection on supported Linux.
- Device context shared across investigation and response.
- Engineering tools and customer access have distinct purposes.
On the device
Install alongside the software you run today.
The Dataplicity agent
Install through an existing local, provisioning or update process. Live remote access requires an online agent and permitted outbound connectivity.
Explore this capabilityFor your engineering and support team
Keep the unit in context from first investigation to follow-up.
One device record
Identity, class, customer and site context help you find and group the right devices.
Explore this capabilityInvestigate and act
Use Pulse, collected logs and diagnostics to investigate. Open a terminal or use the operating capabilities available on your plan.
Explore this capabilityFor your customers, when needed
Keep the application you already have, or build a customer experience on Dataplicity.
Scoped customer access
Give customers their own devices, sites, readings and permitted controls in a branded portal.
Product workflows
Define the records, rules and processes needed for the customer job. Your engineers implement and test the device integration.
Explore this capabilityDecide what to build and what to reuse.
Keep the parts specific to your product. Evaluate the shared services around them as a separate decision.
Dataplicity supplies
Device identity and connectivity, engineering operations, scoped customer access and the application authoring and publishing system. Adopt only the capabilities needed for your product.
Your team configures and integrates
Define Device Classes, product data and Commands, customer boundaries, pages, records and workflows. Connect device code to the local agent interface and test the full customer job.
Your team retains
Hardware, sensing and calibration, the supported Linux image, physical control and safety, commercial terms and the external systems you choose to keep.
Read the technical guideFollow the same product through changes and outages.
Review the mechanism at each boundary before planning a production integration.
Software and OS changes
Coordinate versioned application software and RAUC image delivery without confusing their recovery mechanisms.
Explore this pathDisconnected operation
Place necessary work locally and define buffering, command expiry and reconnect handling explicitly.
Explore this pathCompare an existing stack
Evaluate what you keep, what changes and the operational work left to your team.
Explore this pathRunning inference at the edge?
Edge AI operations are available as an additional path and are not required for the core operating or customer-application journeys.
Explore Edge AI operations
Manage the model and inference workload alongside the Linux fleet and the product workflow it serves.
Explore this pathSee how this fits your current stage.
Start with the operating gap you have today. Expand only where it is useful.