Usage and quotas
The Usage page gathers what your project consumes and the caps that apply: you see where you stand before a limit blocks an operation.
What is measured
Two families of indicators: measured resources (vCPU, RAM, disk) and application counters (API requests this month, Realtime connections, function invocations, database and storage size).
- Resources are measured per project; the Enterprise plan disk covers the whole organisation.
- Counters follow the current month and reset at the start of the cycle.
- A single reading of zero usually means an idle project: read the curve, not one point.
Compare with caps
Each indicator is compared with your plan cap. The page flags thresholds you have reached; when no cap is defined, the indicator stays visible without a target.
History
The last 30 days are plotted: requests, database and storage size, plus vCPU and RAM when measurement is available. If a series is missing, the page says so instead of plotting a misleading zero.
What happens when you go over
A crossed limit slows down or refuses the operation involved — a write, for instance — without ever deleting your data. The affected screens show the reason: reduce the load or change plan to lift the cap.