Quotas & Tiers
Per-organization usage limits for automation runs, tickets, and projects across subscription tiers.
Overview
Every organization in Pomavo belongs to a tier. A tier defines the limits for metered resources, such as how many automation runs an organization may perform within a rolling window, and how many tickets and projects it may have in total. Quotas keep the platform fair and stable for everyone on it.
Tiers
A tier is a named bundle of limits. Higher tiers raise the ceilings. An organization's tier can be changed by a platform administrator from the Admin Dashboard.
| Tier | Intended for |
|---|---|
| Basic | The default tier for most organizations |
| Premium | Teams that need higher limits and heavier automation use |
The exact numeric limits per tier are configured by the platform operator and can be tuned without code changes.
Metered Resources
Quotas are tracked per metric, per organization. Pomavo meters three resources:
- Automation runs: each automation evaluation counts toward a limit measured over a rolling daily window
- Tickets: the total number of tickets an organization may have
- Projects: the total number of projects an organization may have
Limits and Windows
The automation runs limit applies over a rolling window rather than a hard reset. When a run is consumed, it counts against the window; as older usage ages out, capacity returns. This smooths bursts and avoids a single moment where everything resets at once.
The tickets and projects limits are absolute totals rather than windowed, they cap how many of each resource can exist at once.
When the automation run limit is reached, runs are skipped until capacity frees up, and each skip is recorded so you can see it happened.
Checking Usage
Administrators can view current usage against limits for any organization in the Admin Dashboard, making it easy to see how close an organization is to its ceiling and decide whether to raise its tier.
If automations stop running unexpectedly, check the organization's quota usage first, exhausting the automation-run limit causes runs to be skipped rather than failed.