Documentation

Appearance

Build the customer product ​

Use this section when the Linux device is something you sell or provide to a customer. Dataplicity adds the product definition, fleet software, support workspace, and customer application around the hardware and product software you already own.

Illustrative Northstar Customer Portal inventory listing assigned Linux products by name, serial, status, network, and Device Class
The destination is a customer product application, not a view of the OEM engineering console. Northstar is an illustrative demonstration fleet.

Choose the path ​

Your starting pointOpen
You need the generic device-to-customer activation pathBuild your first connected product
Your devices already use Dataplicity Remote ShellExpand beyond remote access
You need to understand the customer-facing applicationCustomer Portal
You need one complete vertical walkthroughChoose a worked product

Define the product once ​

  1. Device Classes define the hardware and product model.
  2. Streams, actions, and settings define its stable product contract.
  3. Product UI designer turns that contract into the customer page.
  4. Software and examples let you prove or release the device-side publisher.
  5. Customer Portal creates the downstream customer boundary and operating application.
Illustrative Dataplicity Device Classes list with Edge Gateway, Retail Controller, and Environmental Sensor product models
Device Classes keep distinct hardware products separate before software, data, controls, and customer layout are added.

Complete walkthroughs ​

These long-form articles are designed to be sent to one implementer. Each keeps the complete path from representative hardware to customer verification on one URL.

Use the generic activation and reference pages for other product shapes. Add another complete walkthrough only when a repeated customer need or campaign justifies it.

Product and engineering boundaries ​

Your customer sees assigned products, locations, product data, video, and permitted controls. Your OEM team keeps logs, diagnostics, Remote Shell, software delivery, fleet jobs, and peer drift in the separate engineering workspace.

Dataplicity does not replace your Linux distribution, product application, secure boot, OS hardening, sensor calibration, physical safety logic, or firmware-update architecture.