Method: Official documentation and pricing checked September 28, 2026. No benchmarks were run. Recommendations are based on documented features and billing, not hands-on results.
Compare Upstash with a specific Redis deployment, not “Redis” as one universal hosting plan. This page compares Redis Cloud’s published entry plans with Upstash’s hosted Redis offer. Running database software yourself has a different operating cost.
Prices and free allowances
| Offer | Verified entry terms |
|---|---|
| Redis Cloud Free | $0; one database up to 30 MB |
| Redis Cloud Essentials | From $5/month; the page also displays an hourly rate |
| Upstash Free | 256 MB data, 500,000 commands/month and 10 GB monthly bandwidth |
| Upstash pay as you go | $0.20 per 100,000 billable commands, plus applicable storage and network charges |
| Upstash Fixed | Starts at $10/month for 250 MB; additional read regions cost extra |
Sources: Redis Cloud pricing, Upstash pricing. These are entry offers, not equivalent capacity or availability guarantees. Compare the selected region, memory and reliability features before buying.
A command-based budget
Ten million billable commands at $0.20 per 100,000 produce $20 in command charges before other meters. Upstash says paid databases do not retain the Free plan’s command allowance. Global write replication can also add billable commands, so a count of application requests may understate the database work.
The pricing page documents a budget cap that can lead to rate limiting. A capped bill is therefore not a promise that every request continues succeeding during a traffic surge. Decide how your application should behave if the cache is unavailable.
Connection model
Upstash’s REST API allows HTTP access from environments where TCP connections are restricted. It returns JSON and has documented command semantics and error responses. This is a concrete reason to consider it for an edge or serverless runtime.
That does not establish universal command compatibility or identical behavior for every client library. List the commands and operations your app uses, then verify each against the provider documentation. Test the actual library in the target runtime rather than assuming a successful local connection proves deployment compatibility.
Recommendation
Evaluate Upstash when HTTP access or command-based billing matches an intermittent workload. Evaluate Redis Cloud when its particular plan and feature set meet your requirements. For continuous heavy traffic, compare a fixed configuration with a modeled usage bill; this article does not establish a universal break-even point.
Before changing providers, check expiration, eviction, reconnect behavior and what happens when the cache misses. If the data is not disposable, examine persistence and recovery separately. No measured latency, throughput or cost reduction is claimed here.
Sources, checked September 28, 2026: Redis Cloud pricing, Upstash pricing, Upstash REST.