Solve the problem your product has today.

Support the devices you already ship, investigate a growing fleet, or give customers an application of their own. These worked examples show where to start and what remains yours.

See how the platform works

Follow the evidence through to the result.

Illustrative operating scenarios, not measured customer outcomes. Use the linked playbooks to reproduce the investigation with your own devices.

One gateway has changed

Starting condition
Pulse flags a gateway whose disk usage and packages differ from its peers.
Investigation and action
Review the difference, inspect collected logs and reach the online device to check the service. Decide whether the change is expected before acting.
Evidence to check afterwards
Check fresh logs, disk use and the next health observation. Record what changed and whether further work remains.
Explore the fleet investigation →

A pilot release starts generating errors

Starting condition
Support receives repeated timeout reports after a pilot firmware release.
Investigation and action
Search the signature and compare versions and cohorts. Preserve the evidence and decide whether to pause the rollout or test a corrective change.
Evidence to check afterwards
Compare fresh errors and expected readings in the pilot cohort before expanding. An action being sent is not proof of recovery.
Read the release investigation →

A customer asks for a replacement

Starting condition
A unit is reported as faulty and someone must decide whether to send a technician.
Investigation and action
Identify the unit and customer. Review available coverage and service history, collected evidence and live diagnostics where the device is online.
Evidence to check afterwards
Confirm current device behaviour after any remote action. If a visit or replacement is still needed, leave the findings and remaining work for the next responder.
Read the support investigation →

When customers need an application of their own.

These reference products show possible customer experiences and the responsibility split. Use the application guide to understand the engineering work behind them.

Explore remote access & fleet operations →Explore customer portals & applications →

Cloud camera

Build your own cloud camera.

Ship the Linux camera you already make - including one with a bespoke algorithm the shelf CCTV market does not offer. Time-lapse construction sites, vehicle tracking at a yard gate, plate-based authorisation, or a detector tuned to your process. Dataplicity gives you live video, recording and a branded customer portal so you can sell the camera as a connected product without inventing a full cloud CCTV stack.

You bring
  • Linux camera or gateway hardware
  • Your optics, capture and algorithms
  • Your brand
Dataplicity provides
  • Agent + outbound tunnel
  • Live and recorded video surfaces
  • Sites, cameras and capture events
  • Branded customer portal
Northstar Connected Products customer portal camera detail for Entry Camera with live view controls

Industrial gateway

Operate a mixed-protocol gateway fleet.

Each gateway is a product instance with health, attention state and last reading. Customers see the boxes they own; your team reaches any unit for diagnostics - including protocol capture, traffic charts and debug traces - without asking them to open inbound ports.

You bring
  • Your industrial gateway hardware
  • Protocol interfaces and mappings
  • Your brand
Dataplicity provides
  • Gateway health vs attention
  • Protocol analysis workbench
  • Remote support on the box
  • Branded customer portal
Industrial gateway analysis workbench with traffic chart and Modbus debug trace

Remote signage

Run screens in the field from one portal.

Group screens by venue, manage the media library and review playback events. Customers operate the signage product they bought - without your team handing over the engineering control plane.

You bring
  • Linux signage players
  • Your media and layouts
  • Your brand
Dataplicity provides
  • Screens and venues
  • Media library
  • Playback events
  • Branded customer portal
Remote signage player detail with player state, display state and remote controls

Silo level monitor

Ship a grain silo level monitor as a connected product.

Probes and site gateways on elevators connect outbound. Co-ops see bin levels in your branded portal. Your team keeps fleet ops, incidents and remote support in Dataplicity. SiloSentry is the canonical worked reference for the complete operating model.

You bring
  • Linux probes and site gateways
  • Your grain level sensing stack
  • Your brand
Dataplicity provides
  • Agent + device class
  • Product application
  • Branded customer portal
  • Fleet ops for your team
Silo level monitor detail with current level, history chart and low-level threshold

Connect a device and decide what to add next.

Start with the Linux product on your desk. Fleet operations work without a Customer Portal. Add a portal and Product Applications when buyers need them.