Business workflows

Nobody buys features. You buy the ability to ship, support, and improve connected devices as a business.

These pages are short stories: recognisable moments for people who build and run Linux IoT devices - either as an internal capability (sites, plant, field assets) or as the product they sell. Each story shows what usually goes wrong, how Dataplicity fits the workflow, and where to go for how-tos.

Feature reference stays in Fleet, Operations, Customers, and Developers. Stories live here.

Choose a path

Path	Who it is for	Start here
Internal IoT operations	Devices that support your business	Fix a remote site without a truck roll
Connected product company	The device is what you sell	Ship the first customer unit you can still support
Field advantages	Hard IoT realities competitors rarely cover	Starlink vs product, mixed-age images, phone on-call, class alignment
Crafted surfaces	Dashboards, wallboards, and status done with intent	Design the wallboard for who walks past it

Platform fit

Already have a runtime (Greengrass, balena, systemd, containers, your own supervisor)? Start with Keep your runtime; add the operations layer.

Start from a moment

Business moment	Story
Remote break/fix without dispatch	Fix a remote site without a truck roll
First commercial ship	Ship the first customer unit you can still support
Warranty / field escalation	Decide dispatch vs remote fix on a warranty call
Fleet looks half offline	Blame Starlink (or not) before you blame your product
On-call away from a desk	Take the incident on the phone without losing the plot
Old and new Linux images together	Keep one ops layer across ancient and brand-new images
Product line silently diverging	Notice when a product line silently splits in the field
Wallboard / TV that nobody trusts	Design the wallboard for who walks past it
“Does this replace our runtime?”	Keep your runtime; add the operations layer