Product
A product is the manufacturer’s design — a reusable template, not a physical thing. It bundles:- Commands — the actions the product can perform
- Database schema — tables for the data it stores
- Dashboard — the UI users get out of the box
- Firmware — the code that runs on the hardware
Device
A device is one physical unit running a product’s firmware. It has a unique identifier and connects to the realtime channel with it. A device emits values and receives commands — that’s all that’s required of it.The platform tracks an identifier with a payload. What that device is — a bus,
a sensor, a smart meter — is defined entirely by how the dashboard maps the
payload, not by the platform.
User
A user owns one or more devices. They onboard a device by scanning its QR code, which links the device to their account. From then on they monitor and control it through the manufacturer’s dashboard — or a custom one.Dashboard
A dashboard is a canvas of widgets bound to device data. Two kinds:- Manufacturer dashboard — ships with the product, the same for every user
- Custom dashboard — built by a user or integrator across any devices they own
How they relate
Manufacturer journey
Build the product and its firmware.
The core loop
How values and commands flow.