The real product
Dataplicity
Software for IoT product companies: remote access, fleet monitoring, incidents, and fixes after devices leave the factory, without VPN or inbound ports on every site.
Worked example
How would it look if I ran my IoT product company using Dataplicity to manage devices after they ship?
Screenshots from a SiloSentry demo org on Dataplicity: devices, ops dashboards, incidents, fleet fixes. Use them to picture your own company in that seat.
Two names on this page. Here’s who they are.
The made-up company
SiloSentry
Not real. A grain-bin sensor OEM we invented so the product isn’t abstract. Their customer cloud is separate. Dataplicity is how they support the gateways.
This whole site is that fiction, used as a tour.
Why this isn’t tool salad
Not “PagerDuty + Geckoboard + a VPN spreadsheet.”
Those products each do a job. An IoT OEM needs those jobs attached to the same device records, from install through monitoring, paging, fixes, warranty, and RMA.
Scattered tools
A wallboard here, an on-call pager there, remote shells somewhere else, RMA in another system. Every incident starts with “which box was that?”
One spine (Dataplicity)
The device is the unit of work. Dashboards, incidents, terminals, and fleet jobs all point at the same fleet, including commercial lifecycle (licences, warranty, RMA).
1 · After devices ship
SiloSentry’s gateways land in Dataplicity, and stay reachable.
This is the foundation. Everything else (dashboards, pages, jobs) hangs off these records.
- Install outbound A first-boot command. Outbound only. Works on LTE and farm routers.
- It shows up The gateway appears in the SiloSentry org, tagged by site and hardware type.
- Reach it Open the device’s local web UI, or a browser terminal, without a truck roll.
- Act on many Alerts, drift detection, and fleet commands, still keyed to those devices.
What you’d see
The supported fleet
Gateways named for bins and sites. Classes for SKUs (Probe GW, Site Gateway). This list is what SiloSentry’s support team opens when a co-op calls.
When one box needs a human
Terminal on that same record
You’re not jumping to a separate VPN tool. The shell is on the device page, next to the same identity dashboards and incidents will refer to.
2 · Running the company
Ops wall, incidents, progression, remediations. Same account.
This is the “what would my company look like?” part: not a feature dump, the shapes SiloSentry would actually use day to day.
Ops center
A monitoring wall fed by your devices
Not a generic KPI collage. SiloSentry’s “Plains elevators” display is built from their Dataplicity fleet: check-ins, heartbeats, and open incidents.
Fleet monitors
Watch the fleet, not one box at a time
“Any Probe GW offline,” “too many Site Gateways dark,” rules SiloSentry would keep on the same devices that show up in the list and on the wall.
Incidents
Page people about things that already exist here
A tower’s probe service down. Customer-cloud latency. Ack, own, escalate, publish, with the device or endpoint named on the incident.
On-call
Who gets woken
Escalation paths and mobile alerts live beside those incidents, not a separate vendor login your team forgets the password to.
Fleet progression
Online isn’t always “healthy”
Device Class Pulse watches whether gateways still look like their peers over time (a missing service, climbing disk, and so on), so ops sees change, not just up/down.
Fixes at scale
Run a command across many gateways
Harvest readiness checks, restarts, cleanups, run as fleet jobs with per-device results. The same place that paged you also runs the remediation.
3 · A day in the seat
If you were SiloSentry ops on Dataplicity.
See what needs you
Operations overview, the ops wall, Pulse on the Probe GW class.
Page → fix
Acknowledge the Tower 2 incident. Run a fleet job. Check per-device results.
Finish the leftover
Terminal or Wormhole on the one box that didn’t clear. Alerts for anything still quiet.
Lifecycle stays attached
Customers, licences, warranty, and RMA stay in the same product. Hardware support didn’t end at install day.
Takeaway
That’s the picture of an IoT company on Dataplicity.
Replace grain bins with your hardware. The shape stays: devices you can reach, ops you can see, incidents you can page, fixes you can run, lifecycle you can keep, all in one place.
Dataplicity = post-ship device ops. SiloSentry = the example setting. Your product = the real story.
Next step: dataplicity.com