documentation / operate
Usage and limits
Four meters measure what an application uses and what it costs.
| Meter | How it accumulates | Excess rate |
|---|---|---|
| Storage | Time-weighted live GB above the allowance | Temporarily unavailable |
| Downloads | Observed successful delivery bytes | Temporarily unavailable |
| Live files | Time-weighted file count above the allowance | Temporarily unavailable |
| Request units | Weighted authorized operations | Temporarily unavailable |
- Opening a file session costs 4 units, and each accepted part costs 1 more, so a normal single-part upload costs 5 units.
- An upload with 100 accepted parts costs 104 units.
- A successful delivery GET, HEAD, or 304 costs 1 unit. Each Range request counts separately.
- File management and list operations cost 1 unit per file, with a minimum of one.
- Deletion, cancellation, cleanup, dashboard activity, sign-in, and billing actions cost nothing.
- Repeating an idempotent operation doesn't charge twice, and backend retries never add charges.
Uploadfile integrates storage and file excess over the actual billing period. If 10 excess GB remains for half of the period, it contributes 5 GB-months. A higher allowance starts once Uploadfile confirms the paid upgrade, and excess accrued before then still counts.
Downloads and request units count up over the period. An upgrade adds only the remaining fraction of the period's allowance. Changing plans or disabling overages doesn't reset what you already used.
To enable overages, accept the rates, set all four quantity limits, and set a monthly USD overage alert. Without that consent Uploadfile charges no extra usage, including usage reported late.
You can disable overages once live storage, file count, and outstanding reservations fit the included capacity. Cleanup stays available. Delivery reports arrive late, so the quantity limits don't stop spending instantly.