Quotas

Monthly request/cost budgets and tenant request-rate limits.

Monthly request/cost budgets and tenant request-rate limits.

This screen belongs to the Router deployment operator, not an ordinary hosted customer. Hosted customers have a separate account page with their own keys and limits; policy and service settings are not exposed there. Contact the operator to change protection. In the operator console, open the route listed above; a report tenant filter does not automatically scope a global setting.

Examples use educational data. Use your own authorized tenant in real integrations. Each screenshot shows the actual frontend, with the source and educational/demo mode stated below it.

Step-by-step actions

  1. Quotas → Add quota: enter docs-demo, 10000 requests, USD 50 and warning 80%, then Add.
  2. For an existing tenant, Edit quota → Save and verify the reloaded row.
  3. Under Tenant limits, Add or edit → docs-demo, RPS 10, Burst 20 → Save.
  4. The separate Add override form uses tenant-id, RPS, Burst → OK; its zero semantics differ.
  5. Save zero to remove a monthly cap. Delete an RPS override to restore the global limit.

Every control and its meaning

Control / parameterValues, units and effect
Tenant IDMonthly quota tenant; * denotes the global default. Tenant ID cannot change during editing.
max_requests / max_cost_usdMonthly UTC requests as an integer ≥ 0 and USD ≥ 0. Zero removes the corresponding cap; example: 10000 and 50.00.
warn_at_pctForm: 0–100%; 80% is saved as 0.8. Backend zero means the 80% default, not off; a negative API/file value belongs to the operator contract.
Лимиты по тенантам: RPS / BurstRPS integer 1–1000; Burst ≥ 0, zero auto-selects RPS × 2. This form does not change monthly quotas.
Лимиты запросов тенантов (RPS)Separate form: RPS = 0 removes the restriction; positive values limit traffic. Deleting an override restores the global value, which differs from unlimited.
Сброс использования / Reset usageResets current-period consumption, not the limit. Allows spending again; unnecessary when editing a cap.

Verify the result

Check PostgreSQL active, reread quota and compare usage. On staging, exceeding rate should produce 429 and exceeding budget a quota error. Refresh does not reset consumption.

Errors, disabling and reverting changes

File-only permits reading but quota writes require PostgreSQL recovery. Restore previous monthly and RPS/Burst values to revert. Cancel discards the draft.

Saved test tenant quota · actual staging
Saved test tenant quota · actual staging
2026-10-15 · Actual staging application and an existing operator session. Synthetic data or non-personal configuration only; credentials and the operator profile are excluded. A form alone does not establish persistence or replica consistency.
  1. Monthly requests
  2. Monthly cost
  3. Warning threshold
  4. Save
Dynamic RPS limit form · actual staging
Dynamic RPS limit form · actual staging
2026-10-15 · Actual staging application and an existing operator session. Synthetic data or non-personal configuration only; credentials and the operator profile are excluded. A form alone does not establish persistence or replica consistency.
  1. Tenant ID
  2. RPS
  3. Burst
  4. Save

Detailed security settings · Traffic analysis · FAQ · All application sections