Use case · Rate limiting
Rate limiting is where per-command pricing hurts most.
Every rate-limit check is a couple of Redis operations, and it runs on every request, all day. With per-command billing the cost tracks your traffic, not the tiny slice of memory a counter actually uses. That is the workload flat-rate managed Valkey is built for — here is the monthly math, computed from source-checked rates.
The shape of it
A rate limiter at 100 req/s (~518M commands/mo) runs about $1,037/mo on Upstash pay-as-you-go versus$89.00/mo on Steada's selected size tier — and the gap widens as your request rate climbs.
Worked monthly cost (2 ops/request, 0.25 GiB)
| Request rate | Upstash PAYG | Steada live plan |
|---|---|---|
| 25 req/s130M commands/mo | $259 | $89.00$170/mo lower |
| 100 req/s518M commands/mo | $1,037 | $89.00$948/mo lower |
| 500 req/s2592M commands/mo | $5,184 | $89.00$5,095/mo lower |
Steada figures are launch pricing inputs, not an SLA-backed guarantee. Assumes2 Redis ops per rate-limit check and 0.25 GiB of counter storage. Upstash:$0.20/100,000 commands; Steada live plan:$89.00/mo for a tier with 20% memory headroom, without command charges. Source-checked 2026-06-01. Adjust ops-per-request and rate in the calculator.
Frequently asked questions
Upstash Fixed plans also avoid per-command billing and may cost less. These examples compare PAYG only, excluding tax, transfer and add-ons; prices reviewed September 11, 2026. Validate peak load and connection limits before migration.
- Why is rate limiting expensive on per-command Redis pricing?
- A rate-limit check usually costs about 2 Redis operations, and it runs on every request, around the clock. With per-command billing the meter tracks request volume rather than the tiny amount of memory and compute a rate limiter actually uses, so the bill scales with your traffic instead of your cost to serve it.
- How much does a Redis rate limiter cost per month?
- It depends on request rate. At 100 requests/second and ~2 ops per check, that is roughly 518M commands a month. On Upstash pay-as-you-go that is about $1,037; on Steada's selected size tier it is about $89.00 for the same workload. Model your own rate in the calculator.
- Is Upstash good for rate limiting?
- Upstash is worth considering for low-volume, spiky or HTTP/edge workloads. For steady traffic, compare its Fixed plans as well as PAYG with Steada’s capacity tiers. Verify the limiter’s command compatibility and latency from your application region before switching.
- Can I keep my rate-limiting code if I switch?
- A standard TCP Redis client can connect, but check every command or script your limiter needs against Steada’s compatibility documentation. Upstash HTTP clients need adaptation. Test TTLs, reconnects and eviction, and choose explicitly whether your application fails open or closed during an outage.
Related & sources
See the full Upstash cost crossover, the Valkey vs Redis explainer, or the other worked workloads: session store ·LLM response cache.
Per-command rates read from Upstash pricing; client compatibility per the Valkey project. Checked 2026-06-01.
Last reviewed