Keep your Linux device and product application. Add the connected-product operating layer your team runs and the branded portal your customers use.
| Your job now | Start here | You are done when |
|---|---|---|
| Prove Dataplicity on one Linux device | Connect your first device | The device is online and you can reach it safely |
| Turn hardware into a product a customer can use | Build your first connected product | A customer signs in to your portal and sees their assigned unit |
| Run and support devices already in the field | Operate the installed base | You can see scope, gather evidence, act, and verify recovery |
Already using Remote Shell? Expand beyond remote access without reinstalling devices or starting again.
| Product layer | What it does |
|---|---|
| Your hardware, Linux, and product application | Runs the physical product you design and ship |
| Dataplicity agent and device identity | Connects the unit outbound and associates it with the correct product and owner |
| OEM engineering workspace | Gives your team fleet operations, software delivery, evidence, and remote support |
| Customer Portal | Gives each customer a branded, separated application for their own products |
Your hardware remains your hardware. Dataplicity does not replace its Linux distribution, product application, secure boot, OS hardening, or firmware architecture. It adds a device identity and operating connection, then presents that same product through two deliberately different boundaries:
When you want one article to follow from bench hardware to customer handover, use the worked product closest to your device:
| Product shape | Walkthrough |
|---|---|
| Hardware that does not match a shipped kit | Build your own Product Application |
| Industrial gateway / protocol converter | Build and operate an industrial gateway |
| Camera or NVR | Build a camera and CCTV product |
| Silo, tank, bin, well, or other bounded level | Build a customer-operated level monitor |
| Temperature, pressure, flow, signal, or another numeric value | Build a customer-operated telemetry product |
| Paid access through a Linux gateway | Build a paid Wi-Fi application |
| Bay, site gateway, and offline outload authorisation | Build a silo outload application |
| Customer schedules distributed to controllers | Build an HVAC scheduling application |
| Venue screens and expected content (kit recipe) | Build a remote signage application |
| Metered board with optional generator or solar (kit recipe) | Build an energy site application |
Workshops cover hardware contract through customer verification in depth. Kit recipes apply a native starter and verify the resulting workplace; they are shorter by design. Reference pages explain individual parts; a walkthrough is the single URL to send to the person building that kind of product.
