What each tier allows on Haiyz Cloud, what a self-hosted instance sets for itself, and what Haiyz can switch off — and what keeps working when it does.
An enterprise's Hyz Assets are sized by its tier:
| Free | Basic | Pro | Max | |
|---|---|---|---|---|
| Asset classes | — | — | 10 | unlimited |
| Sensors | — | — | 50 | 500 |
| Sensor readings a day (UTC, across the enterprise's sensors) | — | — | 100 000 | 200 000 |
| Calls per sensor a minute | — | — | 60 | 60 |
| Each reading kept for | — | — | 30 days | 90 days |
| Readings events keep | — | — | 5 GB | 5 GB |
A tier without asset classes has no Hyz Assets; a tier with classes and no sensors has the core — classes, assets, their hierarchy and status. A class's own layers and services are bounded by the classes row: they do not count against the plan's Hyz Services limit.
Also, for every enterprise:
What the enterprise uses against them is on Hyz Portal › Account › Plan & usage (asset classes, sensors, readings today) and Hyz Console › Usage › Hyz Assets — with the readings on disk, normal and kept, and the kept ones against their 5 GB.
Hyz Assets is an add-on of the licence (assets), issued with publishing. The tiers' table does not
apply: each row is a setting the instance's administrator owns, in Hyz Console › Platform › Settings ›
Hyz Assets — asset classes, sensors, readings a day, calls per sensor a minute, how long each reading
is kept (365 days as shipped) and the hours of history (90 days). An empty value is no limit; 0 is none.
Nothing caps the readings events keep. A dashboard may refresh as often as every 15 seconds there, the
fastest the instance allows (Haiyz Cloud's is 30).
Without the add-on, what exists stays readable — classes, assets, readings, events — and asset layers are
edited as before, but no class or sensor is made or changed and no reading is received
(LICENSE_FEATURE_MISSING); a class or a sensor can still be deleted.
Haiyz's staff can stop parts of an enterprise's Hyz Assets, each with a reason that the enterprise sees. Nothing is deleted by any of them.
| Switched off | What stops | What goes on |
|---|---|---|
| The enterprise's Hyz Assets | no reading is received (ASSETS_HELD); no class or sensor is made or changed; the rules on readings, sensors and service status take no action |
reading everything; editing the asset layers; deleting a class |
| The enterprise's rules | every rule's actions — each firing reads held by Haiyz | events open and close, their readings are kept, alert state follows |
| One sensor | everything it sends (SENSOR_HELD); its enterprise cannot switch it on |
its history and its page |
| One sensor's key | the key, at once (SENSOR_KEY_INVALID) |
the sensor: its enterprise makes a new key |
A suspended enterprise receives nothing from its sensors (ASSETS_SUSPENDED). Deleting an enterprise
removes everything of its Hyz Assets — classes and their layers, sensors and their keys, every reading
kept or not, rules, firings and events.