Documentation

Appearance

SiloSentry ​

What is this? ​

SiloSentry is a made-up grain-bin sensor OEM. It is not a Dataplicity product, not a real customer, and not a separate SaaS offering.

It exists as a worked example: a fictional company whose gateways are managed on Dataplicity, so readers can see post-shipment IoT operations as one coherent business instead of a list of features.

The full screenshot tour lives at silosentry.com.

Why does it exist? ​

Feature pages and API reference describe what Dataplicity can do. They do not always answer the question most OEM readers actually have:

How would it look if my connected-product company used Dataplicity to manage devices after they leave the factory?

SiloSentry answers that with one invented company and one spine of work: device inventory, ops walls, incidents, Device Class Pulse, fleet jobs, Wormhole, and terminal - all attached to the same device records.

Without a setting like this, it is easy to picture Dataplicity as “remote shell plus a few tools.” SiloSentry is there so the product reads as the operations layer for a company that ships Linux devices.

What you will see on the tour ​

The public walkthrough is organised around company questions, not product menus:

  • Devices - classes, Networks, and fleet records that stay useful after install
  • Company ops - dashboards, incidents, and cohort health (including Device Class Pulse)
  • A day - fleet jobs, Wormhole, and terminal when a human needs to act on a unit

Dataplicity remains the real product. SiloSentry is only the tour setting.

When to open it ​

  • You sell (or plan to sell) a Linux-connected product and want a concrete OEM picture
  • Docs stories name demonstration fleets and you want a longer, screenshot-led version of that idea
  • You are evaluating Dataplicity beyond remote access alone

If you want shorter vertical stories instead of a full OEM tour, start with illustrative customers.