Use case · Sessions
Your session store is read on every request.
Sessions get looked up and refreshed on nearly every authenticated request, so a per-command bill climbs with logins and page views — not with the modest memory the sessions occupy. For a steady, high-traffic app, that is where flat-rate managed Valkey gets cheaper and more predictable. Here is the monthly math.
The shape of it
A session store at 100 req/s over 2 GiB runs about $1,037/mo on Upstash pay-as-you-go versus $34.16/mo on Steada's flat-rate target — predictable regardless of how busy login traffic gets.
Worked monthly cost (2 ops/request, 2 GiB)
| Request rate | Upstash PAYG | Steada target |
|---|---|---|
| 25 req/s 130M commands/mo | $260 | $24.44 $235/mo lower |
| 100 req/s 518M commands/mo | $1,037 | $34.16 $1,003/mo lower |
| 500 req/s 2592M commands/mo | $5,185 | $86.00 $5,099/mo lower |
Steada figures are a controlled-beta target, not a public offer. Assumes 2 Redis ops per request and 2 GiB of session storage. Upstash: $0.20/100,000 commands + $0.25/GiB; Steada target: $19.00/mo + $0.03/1,000,000 commands + $1.10/GiB. Source-checked 2026-06-01. Model your own in the calculator.
Frequently asked questions
- How much does a Redis session store cost?
- It scales with how often sessions are read and written. At 100 requests/second and ~2 ops per request, that is roughly 518M commands a month. On Upstash pay-as-you-go that runs about $1,037; on Steada's flat-rate target it is about $34.16 for the same 2 GiB of sessions.
- Why do sessions get pricey on per-command Redis?
- Sessions are read on nearly every authenticated request and refreshed often, so the command count tracks your traffic. With per-command billing the meter climbs with logins and page views rather than with the modest amount of memory the sessions occupy — so a busy app pays for request volume, not for what it stores.
- Is serverless Redis or flat-rate cheaper for sessions?
- For a small or bursty app, serverless (Upstash) is convenient and can be cheaper. Note that some serverless caches — including ElastiCache Serverless — apply a minimum stored-data charge, so a tiny store can cost more than its size warrants. For a steady, high-traffic session store, flat-rate managed Valkey is usually the cheaper and more predictable option.
- Can I move my session store to Valkey without rewriting it?
- Usually yes. Session libraries built on standard Redis clients (connect-redis, Spring Session, django-redis, and similar) work against Valkey unchanged because it preserves the RESP protocol and Redis 7.2 commands. Confirm your TTL and eviction settings on the new instance, then cut over with a rollback path.
Related & sources
See the full Upstash cost crossover, the Valkey vs Redis explainer, or the other worked workloads: rate limiting · LLM response cache.
Pricing read from Upstash pricing and AWS ElastiCache pricing; client compatibility per the Valkey project. Checked 2026-06-01.
Last reviewed