The building blocks of Hermetry and how they connect: organisations, devices and profiles, readings, sites, boards, alarms, rules and flows.
This page explains the main parts of Hermetry and how they work together. Each part has its own section in these docs; the links take you there.
The picture in one paragraph
Your organisation lives in one region. Its devices send telemetry (time-stamped readings) and keep attributes (values that are not time series). Every device follows a device profile, which says how it connects, which keys it sends and which alarm rules apply to it. You place devices on sites and other assets, show them on boards (dashboards) and SCADA drawings, and react to what they send with alarms, the Rules card and flows. Programs reach the same data through the REST API, webhooks and AI assistants (MCP).
Organisation, members and region
Concept
What it is
Read more
Organisation
Your company’s own space in Hermetry, with its members, devices and data. Some messages call it a tenant or a workspace.
The template of a kind of device: how it connects, its keys, limits, alarm rules, commands and firmware settings. Change the profile and every device that uses it follows.
Time-stamped readings, such as a temperature every minute. Kept for the retention your plan allows, with minute, hour and day summaries for long time ranges.
A named value on a device that is not a time series. Client attributes come from the device, shared attributes are set in Hermetry and sent to the device, server attributes are only for the platform and people.
A record that a condition on a device is abnormal, with a severity, a status (open, acknowledged, resolved) and a timeline. One active alarm per device and type.
A program of connected blocks that reacts to device messages, schedules or webhooks. Every device message enters the root flow, which stores the data and runs the alarm rules.