What Needs Redis
Use Redis when you run more than one worker process, either through --num_workers or multiple replicas.
Almost everything the proxy enforces (rate limits, budgets, cooldowns, cache hits, config changes) is coordinated through state. With Redis, that state is shared, so every worker sees the same counters and the same invalidations. Without it, each worker keeps its own copy in memory, so a limit of 100 requests per minute across 4 workers really lets through 400, a revoked key stays usable on the workers that did not process the revocation, and cache hits only land on the worker that happened to store the response.
The Admin UI shows a banner while no Redis is configured. If you deliberately run a single worker, set LITELLM_DISABLE_NO_REDIS_WARNING=true to hide it.
Configure Redis
See Set Up Redis for provisioning and connection settings.
router_settings:
redis_host: os.environ/REDIS_HOST
redis_port: os.environ/REDIS_PORT
redis_password: os.environ/REDIS_PASSWORD
litellm_settings:
cache: True
cache_params:
type: redis
host: os.environ/REDIS_HOST
port: os.environ/REDIS_PORT
password: os.environ/REDIS_PASSWORD
Setting REDIS_HOST and REDIS_PORT in the environment is not enough on its own: the proxy reads them only when the config points at Redis, as above. The router_settings block covers router state (cooldowns, usage and latency based routing), and the cache block covers response caching and everything coordinated proxy-wide (rate limits, budgets, cache invalidation, the pod lock). Configure both. For cluster and sentinel deployments, and for pointing coordination at a different Redis than your response cache with general_settings.coordination_redis, see Redis and Valkey.
What breaks without Redis
| Feature | Without Redis |
|---|---|
| Key, team, user, and end-user rate limits (tpm, rpm, max parallel requests) | Counted per worker, so the effective limit is multiplied by the number of workers. |
| Dynamic rate limits and rate limit tiers | Same per-worker split; a tier's share of capacity is recomputed independently on each worker. |
| Key, team, and user budgets | Spend is reserved and counted per worker, so concurrent requests on different workers can overshoot a hard budget before the database catches up. |
| Provider budget routing and tag budgets | Per-worker spend windows, so a provider or tag can exceed its budget by roughly the worker count. |
usage-based-routing-v2 and latency-based-routing | Routing decisions use only the traffic that worker has seen, so load balancing skews and TPM/RPM-aware placement degrades. |
| Deployment cooldowns | A deployment cooled down after failures on one worker stays in rotation on the others. |
| Response caching | Cache entries stay local to the worker that wrote them, so hit rate drops roughly by the worker count. Semantic caching needs Redis outright. |
| Virtual key and team cache invalidation | Key deletes, budget edits, and team membership changes propagate to other workers only when their local cache entry expires. |
| Config changes stored in the database (models added, deleted, or edited in the UI, and settings changes) | Other workers pick them up on their next periodic reload instead of immediately. |
| Redis transaction buffer for spend writes | Unavailable. Every worker writes spend updates directly to the database, which is the failure mode that buffer exists to prevent at high traffic. |
| Scheduled jobs (budget resets, key rotation, expired session cleanup, database spend flush) | The pod lock that elects a single runner needs Redis, so every worker runs the job and they contend on the same rows. Spend log cleanup is the exception: it coordinates through the LiteLLM_ScheduledJobRun table in Postgres and runs once per schedule with or without Redis. |
| Shared health checks | Every worker runs its own background health checks against every deployment, multiplying provider health traffic. |
| Request prioritization | The priority queue is per worker, so ordering only holds among requests that land on the same worker. |
SSO and litellm login from the CLI | The login flow can fail when the browser redirect lands on a different worker than the one that started it. |
| MCP outbound OAuth credentials | Tokens are cached per worker, so each worker refreshes independently; a provider that rotates refresh tokens on use can invalidate the others. |
| Background responses and polling | A polled response is readable only on the worker that produced it. |