Source: LiteLLM docs: budgets and rate limits (proxy users, teams, keys)
LiteLLM proxy's budget hierarchy (global, team, team member, internal user, virtual key, end user, per model) and rpm/tpm/parallel-request limits, with reset windows and fail-open/fail-closed behaviour.
Contents
- What: official documentation page (“Budgets, Rate Limits”)
- Publisher: BerriAI (LiteLLM)
- Date: living docs, read 2026-11-14 (mentions behaviour changes in v1.94.0 and v1.95.0)
- Original: docs.litellm.ai/docs/proxy/users
Summary
The proxy can cap spend (in USD, priced from its model cost map) and request/token rates at several levels of an org hierarchy. Everything except the global budget depends on Postgres, and enforcement details (which budget wins, when windows reset, what happens when the database or Redis is down) are configurable and easy to get wrong.
Key claims
- Postgres is required. Without it, budgets fail open: requests keep being served.
- Levels: global (
litellm_settings.max_budget+budget_duration), team, team member (max_budget_in_team), internal user, virtual key, end user / customer (via/budget/newandmax_end_user_budget_id), and per-model budgets on keys/users (model_max_budget, Enterprise). - A key that belongs to a team is checked against team and team-member budgets only, not its owner’s personal budget (briefly enforced in v1.94.0, reverted in v1.95.0).
- Durations are written like
30s,30m,30h,30d; a key can hold several windows viabudget_limits.24hresets at midnight UTC,7don Monday,30don the 1st of the month. A background job checks resets about every 10 minutes by default. - Over-budget errors include
ExceededTokenBudget(key) andExceededBudget(team member, end user). rpm_limit,tpm_limitandmax_parallel_requestscan be set on keys, users and teams;model_rpm_limit/model_tpm_limitper model, with key values overriding team values.token_rate_limit_typecounts input, output or total (default) tokens.- Budget reservation is on by default (it reserves estimated cost before the call);
fail_closed_budget_enforcementchecks the database before admitting a request;fail_closed_rate_limit_enforcementreturns 503 when Redis cannot confirm counters. - Agents can carry per-session token/request limits,
max_iterationsandmax_budget_per_session, returning 429 when exceeded. - Models priced at zero input and output cost skip budget checks.