Every Limit Is on the Pricing Page
Most software meters something it does not tell you about until you hit it. Why every limit on every AWRA OpsHub plan is a published row on the pricing page, and what actually happens when a workspace reaches one.
Every subscription has limits. The difference between vendors is whether you find them on a pricing page before you sign or in an error message during your busiest week. A limit discovered during a data migration, or on the morning a new branch opens, costs far more than the limit itself — because it arrives at the one moment you have no time to think about it.
The short version
Every usage limit on every plan is a row in the pricing comparison, and Settings › Usage shows where your workspace stands against each one. Reaching a limit never removes anything: count limits stop the next one being added, daily limits reset at midnight UTC, and when AI requests run out the screens keep their figures without the written summary.
What is metered
The limits fall into four kinds, and each behaves differently when it is reached. Knowing which kind you are near tells you how urgent it is.
| Kind | Limits | When you reach it |
|---|---|---|
| Counts | Warehouses and branches, POS counters, API keys, custom fields, customer portal accounts | The next one cannot be added until one is removed or the plan grows. Nothing existing is touched. |
| Daily | Emails sent, exports and PDF reports, developer API calls | Pauses until midnight UTC, then resets. |
| Monthly | AI requests | Screens keep every figure; only the written summary waits for the next month. |
| Per file | Rows in one import file, size of one upload | That file is refused; split it or make it smaller. |
One more sits apart from the rest: how long the audit log and activity history can be kept online. It governs how far you can raise that period, and it never shortens one you already have — there is a separate post on why.
Why publish them
A limit that is written down can be planned around. Two warehouses on a plan that allows one is a conversation to have before the second warehouse opens, not a surprise on its first day. An import file capped at a number of rows is a reason to split the spreadsheet before the migration weekend, not during it.
A limit found during a data load is a limit found at the worst possible moment.
There is also a fairness argument. Every limit exists because the thing it meters costs something each time it is used — an email sent, an AI summary written, a file stored, a server busy answering API calls. Publishing them means a small workspace is not quietly paying for a large one’s usage, and a large one can see exactly what it is buying.
What reaching one looks like
Each limit says which one it is and what to do, in the place you hit it. An attempt to add a fourth warehouse on a plan that allows three says so, with the limit. A developer integration that passes its daily API calls receives a clear error code it can handle, and every key in the workspace shares the one daily total. A workspace already above a count limit when the limits were introduced keeps everything it has; it simply cannot add another until it is back under.
Where to look first
Settings › Usage lists every limit on your plan with how much is in use, so the question “are we close?” has an answer before anyone hits anything.
When the standard limits are the wrong shape
Some workspaces are big in one direction and small in every other. These are the additions we make for them.
Limits agreed in the contract
On Enterprise, each figure is set to how your organisation actually works rather than to a tier.
An early warning before a limit
A notification when a workspace passes a share of any limit you choose.
Capacity without a new tier
Seats, storage and other add-ons that raise one ceiling on the plan you already have.
How it works: tell us which limit is the wrong shape, and we come back with the option that fits.
How add-ons workAsk any vendor before you sign
What is metered on my plan, exactly?
A good answer
A named list with a figure against each.
Why it matters
Anything unnamed is a limit you will meet later.
What happens when I reach one?
A good answer
Whether it pauses, refuses or deletes — per limit.
Why it matters
A limit that deletes anything is a very different risk from one that pauses.
Where do I see how close I am?
A good answer
A page inside the product.
Why it matters
Without one, the first sign is the error.
What AWRA OpsHub does today
- Every usage limit published per plan on the pricing comparison.
- Settings › Usage showing each limit and how much of it is in use.
- Count limits that stop the next addition without touching anything existing.
- Daily limits that reset at midnight UTC, and an AI allowance that falls back to figures.
- A clear error code for a developer integration that passes its daily API calls.
More we can add to your workspace
- An alert when a workspace passes a share of a limit you choose.
- A monthly usage report emailed to the workspace owner.
Where we point you to a specialist
- We set a limit on anything that costs us each time it is used; we would rather publish it than absorb it silently into everyone’s price.
Either of the middle column can be added to your workspace.
Every limit, by plan
The full comparison, with every usage limit listed against every plan.
Compare plansFrequently asked questions
Does AWRA OpsHub have usage limits?
Yes, and every one is published on the pricing comparison: warehouses, POS counters, AI requests, emails, exports, developer API calls, API keys, custom fields, customer portal accounts, import rows, upload size and history kept online.
What happens when a workspace reaches a limit?
Nothing existing is touched. Count limits stop the next one being added, daily limits reset at midnight UTC, and when AI requests run out the screens keep their figures without the written summary.
Where can I see how close my workspace is to its limits?
Settings, then Usage, lists every limit on your plan with how much is in use.
Do all API keys share one daily limit?
Yes. The daily total of developer API calls belongs to the workspace and is shared by all of its keys, on top of a per-minute limit for each key.
