Appearance
Business workflows
Nobody buys features. You buy the ability to ship, support, and improve connected devices as a business.
Most 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. Platform depth provides longer guides to capabilities that become more powerful when they work together.
If your company builds the Linux devices that its own operations use, start with Operate your own Linux fleet. It is the full internal-fleet walkthrough: Device Classes, monitoring, dashboards, Pulse, incident response, remediation, rollout verification, and lifecycle review. It does not require a Customer Portal.
Feature reference stays in Fleet, Project Boards, Operations (including customer surfaces), and Developers. Stories live here.
Stories and screenshots often name illustrative customers - Northstar, Harbor, Polar, Solstice, Amber Field, and Meridian. They are demonstration fleets that make the operating patterns concrete. The methods are real; the companies are illustrative. For a longer screenshot-led OEM tour, see SiloSentry (also fictional) and the screenshot tour.
Choose a path
| Path | Who it is for | Start here |
|---|---|---|
| Operate your own Linux fleet | You build the devices your own organisation operates | Fleet setup → monitoring → incident → verified recovery → lifecycle review |
| Illustrative customers | Recognise your business in the demonstration fleets | Northstar, Harbor, Polar, Solstice, Amber Field, Meridian |
| 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 |
| Silo and tank monitoring | Level-monitor product teams | Turn sensor input into a customer-operated silo product |
| Camera and CCTV product | Linux camera and NVR product teams | Publish a customer-safe camera experience |
| Field advantages | Network, hardware, software-age, and on-call realities in deployed fleets | Starlink vs product, mixed-age images, phone on-call |
| Crafted surfaces | Dashboards, wallboards, and status done with intent | Design the wallboard for who walks past it |
| Platform depth | Operators evaluating how the platform handles evidence, cohorts, control, and poor connectivity | Logging, browser workspace, fleet monitors, and file requests |
Platform thesis
New to the post-shipment framing, or coming from remote shell only? Read After devices ship.
Platform fit
Already have a runtime (Greengrass, balena, systemd, containers, your own supervisor)? Start with Keep your runtime; add the operations layer.