What your organisation may do is decided by its plan. This page explains how a plan is put together, the three tiers of the IoT add-on, what each limit means and what happens when you reach it. Prices are on the pricing page of your region; Enterprise plans and on-premises installations are agreed with our sales team (contact us).
How a plan is built
| Part | What it gives |
|---|---|
| Platform plan | The base of every organisation: members, settings, the audit log, API keys, webhooks, notifications. |
| IoT add-on | The IoT modules, such as devices and profiles, telemetry, alarms, commands, firmware updates, provisioning and the device certificate authority, sites and assets, the SCADA designer with its core symbols, cameras with live view, remote access and the ready solutions. It comes in three tiers. |
| Add-ons | Products bought on top, for example the SCADA symbol libraries. |
Your current plan, its tier, your add-ons and the exact list of modules your organisation has are shown on Plan & Billing and My Modules. See Your subscription and entitlements.
The IoT tiers
The tiers differ in size: Growth and Scale raise limits and add no modules of their own.
| Limit | Starter | Growth | Scale |
|---|---|---|---|
| Devices | 43 | 77 | 403 |
| IoT messages per month | 1,150,000 | 4,260,000 | 28,810,000 |
| Telemetry keys | 250 | 400 | 2,050 |
| Telemetry retention | 365 days | 365 days | 365 days |
| Flows | 6 | 12 | 58 |
| Script blocks in deployed flows | 3 | 6 | 29 |
| Messages per second, whole organisation | 10 | 15 | 70 |
| Data points per minute, whole organisation | 6,000 | 9,000 | 42,000 |
The same in every tier:
| Limit | Value |
|---|---|
| Cameras with live view | 12 |
| Camera minutes per month | 10,000 |
| Open router panel sessions | 10 |
| Panel tunnel data per month | 10 GiB |
These are the catalogue values. Your organisation’s plan can differ, for example an Enterprise agreement or a usage pack; Usage and the limit messages always show your own values.
What each limit means
| Limit | Counts | At the limit |
|---|---|---|
| Devices | Every device: quarantined devices, LoRaWAN gateways and sensors, gateway children, polled devices, camera channels. | New devices are refused. Existing devices keep working. See Devices. |
| IoT messages per month | Telemetry and attribute messages your devices send, and poll results. Commands, alarms and connection events do not count. | A soft limit: Hermetry keeps accepting and storing; the overage is billed. Nothing is dropped. See Message quota and usage. |
| Telemetry keys | Distinct telemetry key names in the organisation. | A new key over the cap is not stored; the other keys of the record are. See Telemetry keys. |
| Telemetry retention | How long readings are kept. 365 days puts your data in the 365-day class: raw readings 90 days, minute aggregates 31 days, hourly and daily figures a year. | Older data is removed. See How long data is kept. |
| Flows, Script blocks | Every flow you create; Script blocks in deployed flows. The Default root flow does not count. | New flows or deployments are refused. See Flow limits. |
| Messages per second, Data points per minute | All telemetry and attribute messages of the organisation together, and the keys in them. | Messages over the rate are acknowledged and dropped (HTTP answers 429 with Retry-After). Owners and admins get one notice per hour. Each device profile also has its own, lower per-device limits. |
| Cameras with live view, Camera minutes | See Camera limits and privacy. | |
| Panel sessions, Panel tunnel data | See Remote access limits and audit. |
Choosing a tier: count your devices first, then estimate messages. One device that sends one message a minute uses 43,200 messages in a 30-day month; one every 15 minutes, 2,880. Batch readings to save messages.
Limits of the platform plan
The platform plan can also limit members (seats), open invitations, custom domains, API keys, e-mails and SMS sent per month, and whether some pages (for example reading the audit log) are included. Which of these your plan sets, and their values, are shown on My Modules and Usage. A limit your plan does not state is not a limit.
SCADA symbol libraries
The SCADA designer’s core symbols come with the IoT add-on. The industry libraries are one-time purchases sold beside it: one library at a time (for example SCADA: Factory), SCADA: Industry suite, or SCADA: All pieces with all 13 libraries. If a library ever lapses, symbols you already placed stay. See Symbols and industry packs.
When your plan changes
| Change | Effect |
|---|---|
| A higher tier | The new limits apply within minutes. |
| A lower tier, or a module leaves the plan | Nothing is deleted. New devices are refused while you are at or over the device limit. A module that leaves the plan is switched off, not deleted: its data is kept and comes back with the module. Custom domains the plan no longer covers are paused. |
| A usage pack (where offered) | Adds to one monthly limit for its period. |
In development
Hermetry City, Hermetry Safe and Hermetry Forge are In development and not part of any plan yet.