What each plan includes, which ceilings you can meet, and what happens when you reach one.
Your plan caps how much you may hold, not how hard you may work, with one exception: edits to an editable layer are counted per month. Ten things are counted, and each one is counted on its own:
| Counted | What it covers |
|---|---|
| Data items | Items you own at /data/items — not their versions |
| Dashboards | Dashboards you own |
| Field campaigns | Surveys you own |
| Groups | Groups you own |
| Data rooms | Rooms you own |
| Workspaces | Saved workspaces |
| Projects | Work projects at /projects |
| Storage | Total bytes held across your versions |
| Editable layers | Hyz Layers you have switched editing on — see Editable layers |
| Edits per month | Feature changes applied to your editable layers in the calendar month, from every client and from Hyz Field |
Maps are capped too, on their own rules: how many you may publish, how many layers each may carry, and how large a layer may be.
Only what you own counts — something shared with you costs you nothing — and a resource owned by an organization is metered against the organization, not against whoever uploaded it.
The numbers are not written into the product. They live in a table an administrator edits at runtime, per plan and per counted thing — which is why this page describes the model rather than printing values that could be wrong for your instance the day someone changed them.
Any of them can be set to unlimited. On a self-hosted instance, every one of them is — see Haiyz Enclave.
For what each plan costs and what it includes, see Pricing.
You will not hit a silent failure, and nothing you already have is taken away. When a create would take you past a limit it is refused, and you are told which limit, in plain words:
Your [plan] plan allows [limit] [resource].
Alongside it comes the way out: a link to the plans, or — inside an organization — a note that an administrator can raise the limit.
Limits are checked on the way in, not swept afterwards. If your plan changes downward, what you already own stays yours; you simply cannot add more until you are back under the line.
Map styling behaves differently, and deliberately so.
Data-driven symbology — colour or size derived from a field's values, graduated ranges, per-category colours — is an Enterprise capability. Everything else (colour, opacity, size, labels, popups, icons, clustering, flow lines) is available on every plan that can publish a map at all.
If you save a map carrying styling above your plan, the save succeeds and the styling is dropped, with a notice listing exactly what was not kept:
Saved, but your plan does not include this styling, so it was not kept.
This is on purpose. A colleague on a higher plan may have styled a layer you merely renamed; refusing the whole save over symbology you never touched would be worse than naming what will not survive it.
Running a GIS tool is not the same as holding data, and is counted against none of the ten. Tool runs draw on their own allowance, with its own cadence per plan and per-tool caps an administrator can tune.
The full picture — which tools are metered, how the window resets, and what happens when the allowance is spent — is on Tool quotas. Hyz AI has a third, separate daily budget, described in Hyz AI. Edits on editable layers draw on the edits-per-month allowance above, not on tool runs; when it is spent, saves are refused with the limit named and nothing already applied is lost.
Everything above is on one page: Account › Usage in the Portal. It shows your plan, every counted thing against its limit, your storage with the largest data items, tool runs, the Hyz AI budget, this month's requests to your published services, and a 30-day trend taken from a nightly snapshot. The product pages — maps, dashboards, Field, tools, data items — show your work, not meters. Two places keep one line because you need it at that moment: the upload form says how much storage is free, and a tool's page says how many runs you have left in its window.