Docs

Your Linux devices.
Connected, operated, supported.

Remote access, Pulse fleet health and logging, from the first prototype to equipment already in the field. Keep your hardware and application. Give customers an application of their own when your product needs one.

OEM fleet viewSiloSentry worked reference · Pulse attention

Your team needs control. Your customers may need an application.

Operate your Linux devices, build a customer application, or do both.

For your team

Operate your Linux devices

Reach devices remotely. Spot unexpected changes with Pulse. Search logs and investigate problems with the device context in front of you.

From the prototype on your desk to equipment already in the field. Keep your existing application and use Dataplicity to operate it.

Explore remote access & fleet operations
Dataplicity terminal cockpit with fleet device list and a live device shell session

Dataplicity fleet workspace: device inventory and a live Linux terminal.

For your customers

Give customers an application of their own

Give customers their devices, data and controls in your brand. Add records, rules and workflows when your product needs them.

Your team keeps the engineering tools. Your customers get an application built around the job they need to do.

Explore customer portals & applications
Silo level monitor detail with current level, history chart and low-level threshold

Example customer application: silo levels, reading history and device controls.

Use either independently, or combine them around the same connected devices.

Where are you starting?

A prototype, a first batch or an established fleet. Start where the work is.

On your desk

Prove remote access on a development device, or investigate a fault with Device Check.

Start with one device →

Preparing a production run

Make installation and device identity repeatable before the first batch goes out.

Prepare the first batch →

Already in the field

Use your existing installation or update process to connect a reachable cohort. Keep your customer application.

Operate an existing fleet →
Explore the full product lifecycle →

Bring the product you already make.

Dataplicity starts with the Linux device inside it. You keep the hardware, software, data and brand that make the product yours. SiloSentry shows how fleet operations and a customer application can work together.

SiloSentry visuals on this site are a worked reference-product scenario, clearly labelled as such — not a claim of an unrelated third-party customer deployment.

What the OEM brings

  • Linux level-monitor or gateway hardware
  • Sensing method and calibration
  • Product runtime and field install
  • SiloSentry brand and customers

What Dataplicity adds

Fleet operations for your teamOutbound connection, durable identity, Device Class, Pulse, diagnostics, logs and Remote Shell — with no Customer Portal required.
Optional portal and workflowsBranded Customer Portal, Product Application records and customer-isolated Product Instances when buyers need them.

See the fleet. Then get all the way into a device.

Open a live terminal from any device record, investigate the problem and make the fix. The same system handles the work around it, from fleet-wide jobs and monitoring to incidents, customers, warranties and returns.

Dataplicity showing a fleet device list, a selected device and its live Linux terminal in one workspace
Work on the deviceLive terminal, remote access, logs and diagnostics.
Work across the fleetMonitoring, releases and guarded jobs across groups.
Handle the incidentAlerts, on-call, ownership and a complete audit history.
Manage the installed baseCustomers, licences, warranty and RMA tied to the hardware.

Fleets diverge. You shouldn’t have to invent a gold image.

IoT devices are not homogeneous, and they never stay identical. Chasing a gold design is a mug’s game.

Pulse learns normal from the whole Device Class — with no prior knowledge, no coding, and no baseline from you — then flags the ones that stop looking like their peers.

No prior knowledgeTurn Pulse on. It fingerprints the class as devices run.
Peer-learned normalThe baseline is what the fleet actually looks like, not a manifesto.
Divergence, flaggedWhen units stop matching their peers, you hear about it first.

Know when the fleet crosses the line.

Set thresholds on impaired devices — offline, unreachable, or failing checks. When enough of the fleet is affected, Dataplicity opens an incident, pages on-call, and escalates until someone owns it.

Fleet-wide thresholdsAlert when a share of devices goes offline, stops checking in, or fails monitored signals — not one device at a time.
Wake the right peopleOn-call schedules, push to mobile apps, and escalation if nobody acknowledges in time.
Owned through resolutionIncidents carry device context, notes, and audit history so the next engineer picks up where you left off.

The job starts when the hardware ships.

Devices need managing whether or not customers need a portal. Dataplicity provides fleet operations first, then an optional customer application and product workflows when the product requires them.

See a complete product journey

Start with the complete SiloSentry walkthrough, then explore how the same foundation supports five more connected-product journeys.

Featured walkthrough

SiloSentry level monitoring

OEM attention path and customer site view on one shared model

You bringProbes, gateways, sensing stack and SiloSentry brand
Dataplicity suppliesDevice Class, OEM fleet view, branded portal and Product Application workflow
You keepSensing method, calibration and physical install
Read the guideOpen SiloSentry

More product journeys

Existing Linux product, no portal

A supportable installed base without a Customer Portal

You keepHardware, OS, calibration and field qualification

See the responsibility split
You bring
Your Linux device and application
Dataplicity supplies
Identity, Remote Shell, diagnostics, monitoring and fleet ops
Read the guide

Industrial gateway

Mixed-protocol fleets stay operable behind customer networks

You keepProtocol correctness and field wiring

See the responsibility split
You bring
Gateway hardware and protocol mappings
Dataplicity supplies
Health vs attention, protocol workbench, remote support and portal
Read the guide

CCTV

Sell a camera as a connected product without inventing a full CCTV cloud

You keepCapture pipeline and detection models

See the responsibility split
You bring
Linux camera hardware, optics and algorithms
Dataplicity supplies
Live and recorded video surfaces plus branded Customer Portal
Read the guide

Offline silo outload

Customer workflow continues when connectivity is intermittent

You keepWeighbridge and yard process rules

See the responsibility split
You bring
Site process, tickets and driver workflow
Dataplicity supplies
Product Application records, offline datasets and reconnect handling
Read the guide

HVAC scheduling

Multi-device site workflow around existing controllers

You keepController integration and building safety logic

See the responsibility split
You bring
Controllers and zone model
Dataplicity supplies
Schedules, applied-state records and Customer Portal workplace
Read the guide

Start with the device on your desk.

Keep your hardwareNo Dataplicity board or replacement Linux distribution.

Install one agentOutbound only, so it works behind NAT, LTE and customer firewalls.

Prove it before rolloutConnect one device, reach it remotely and build from there.

Not ready to install the agent? Try Device Check — free, no account

Connect your first device.

Enter your email to get the install command. Run it on your Linux device and watch it appear in Dataplicity.