What each edition holds
Editions are sizes, not feature sets. Every one of them does everything on this page; what changes is how big an operation it is built for. The column that matters most is the one saying what happens when you reach a number.
Ceilings and meters
Two kinds of number, and the difference between them is not a detail. One is enforced when an administrator creates something. The other is counted and never gets in anybody’s way.
| Meter | Single | Multi | Group | On-premise & Custom |
|---|---|---|---|---|
| Work orders / monthMetered | 250 | 1,000 | 4,000 | As agreed |
| FacilitiesLimit | 1 | 4 | 15 | As agreed |
| MachinesLimit | 150 | 750 | 3,000 | As agreed |
| Staff accountsLimit | 3 | 10 | 30 | As agreed |
| Operator accountsLimit | 40 | 200 | 750 | As agreed |
| ProceduresLimit | 25 | 150 | 500 | As agreed |
| Ingested readings / monthMetered | 50k | 500k | 5M | As agreed |
| API calls / dayMetered | 10k | 50k | 250k | As agreed |
A ceiling is refused, and says so. Every enforced ceiling is met by an administrator adding a facility, a machine, a procedure or an account — at a desk, in office hours, as a deliberate act. The refusal names the number you hit, what you have, and which edition holds more. Nothing on the path of doing the work is ever refused.
A meter never refuses anything. Work orders are counted and shown in the app, and that is all. A busy month is not an outage: nothing is blocked, no round is lost, and no operator meets a wall on a tablet at three in the morning. If you run over your edition for 2 months running, we move you at renewal — a conversation, not a surprise invoice. Automated readings and API calls are rate-limited rather than cut off, so a reading is never lost to a quota.
Procedures are counted whole. One number covers every procedure on the account, whether you wrote it in the editor, took it from the library or loaded it from a file. There is no separate allowance and nothing to track — a plant with three hundred procedures is a big plant however they got there.
The two things that are not on every edition
This is the whole of it. Single is not the product with pieces removed — it runs maintenance in full. What it does not have is leverage: the shelf you can take procedures off, and moving a plant’s worth of data in or out in one action.
| Capability | Single | Multi | Group | On-premise & Custom |
|---|---|---|---|---|
| Procedure libraryHundreds of ready-made procedures across trades, each one opening in the editor as yours to change. | — | ✓ | ✓ | ✓ |
| Bulk import and exportEvery procedure or every work order in one file, in or out. Single-record downloads are on every edition. | — | ✓ | ✓ | ✓ |
On every edition, including Single
Not a table, because there is nothing to compare. Everything below is on all four.
- Scheduled and ad-hoc work orders
- Procedure templates and the canvas editor
- Equipment register and asset passport
- Manuals, schematics and certificates per asset
- Multiple facilities, each with its own register
- Teams and assignment
- Operator accounts for the shop floor
- CSV export of reports
- Statutory inspection register
- Readings, downtime, MTBF and failure history
- Company-wide reporting across sites
- REST API and API keys
- Automated readings ingest from PLC or historian
- Cross-organization access for contractors
And what a trial holds
The Single edition with a 3-day clock on it, tightened where a short look could be abused — with one thing deliberately loosened.
Two facilities rather than Single’s one, so you can see reporting across facilities in the 3 days rather than take our word for it. Four sample procedures from the library are yours to install, leaving room to write your own beside them. API keys and bulk export wait until the account is on an edition.