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, flat-rate managed Valkey is worth comparing with both PAYG and Fixed plans. Here is the monthly math.

Worked monthly cost (2 ops/request, 0.35 GiB)

Steada figures are launch pricing inputs, not an SLA-backed guarantee. Assumes2 Redis ops per request and 0.35 GiB of session storage. Upstash:$0.20/100,000 commands +$0.25/GB above the free first GB; Steada live plan: $89.00/mo with 20% memory headroom and no command charge. Model your own in the calculator.

Frequently asked questions

Cache-mode sessions can disappear on restart or eviction: your application must tolerate reauthentication. Upstash Fixed plans may cost less than Steada. These PAYG-only examples exclude tax, transfer and add-ons; prices reviewed September 11, 2026.

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 selected size tier it is about $89.00 for the same 0.35 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?

It depends on size, traffic and operational requirements. Compare Upstash PAYG and its Fixed plans against the Steada size tier that fits with headroom. Fixed pricing is not unique to Steada, and a lower bill does not establish equivalent availability or throughput.

Can I move my session store to Valkey without rewriting it?

Standard TCP Redis clients can connect, but validate the exact commands your library uses against Steada’s compatibility documentation. Test TTLs, eviction and reconnect behavior before cutting over. Cache-mode session loss can sign users out; do not use it for irreplaceable session data.