Skip to content

You make the hardware. We provide the SaaS.

Keep your Linux device and product application. Add the fleet software your team operates and the branded product portal your customers use.

Choose one outcome

Your job nowStart hereYou are done when
Prove Dataplicity on one Linux deviceConnect your first deviceThe device is online and you can reach it safely
Turn hardware into a product a customer can useBuild your first connected productA customer signs in to your portal and sees their assigned unit
Run and support devices already in the fieldOperate the installed baseYou can see scope, gather evidence, act, and verify recovery

Already using Remote Shell? Expand beyond remote access without reinstalling devices or starting again.

One product, two separated workspaces

Product layerWhat it does
Your hardware, Linux, and product applicationRuns the physical product you design and ship
Dataplicity agent and device identityConnects the unit outbound and associates it with the correct product and owner
OEM engineering workspaceGives your team fleet operations, software delivery, evidence, and remote support
Customer PortalGives each customer a branded, separated application for their own products
Illustrative OEM device inventory with product classes, tags, and allocation controls
OEM workspace: manage the installed base, product classes, and customer allocation.
Illustrative branded Customer Portal inventory with assigned products and networks
Customer Portal: each customer sees and places only 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:

  • Your engineering and operations team provisions devices, releases software, observes fleets, investigates drift, and uses remote support.
  • Your customer sees only their organisation, locations, assigned products, customer-safe data, and permitted controls in your branded Customer Portal.

Complete product walkthroughs

When you want one article to follow from bench hardware to customer handover, use the worked product closest to your device:

Product shapeComplete walkthrough
Camera or NVRTurn a Linux camera into a product you can sell
Silo, tank, bin, well, or other bounded levelBuild a customer-operated level monitor
Temperature, pressure, flow, signal, or another numeric valueBuild a customer-operated telemetry product

These are deliberately complete articles. Reference pages explain individual parts; a walkthrough is the single URL to send to the person building that kind of product.

Other useful entry points