Upstash vs. Redis Cloud vs. Dragonfly · cache providers in 2026
Three providers, three pricing shapes. Upstash bills per request and runs on edge POPs, Redis Cloud bills per provisioned instance, Dragonfly is wire-compatible Redis with multi-threaded internals at a third of the cost.
Default to Upstash for serverless and edge stacks · per-request billing matches the workload, REST API works on Workers and Lambda, and the free tier covers prototyping. Move to Dragonfly Cloud the moment a single instance handles more than ~50k ops/sec or your monthly Redis bill crosses ~$300 · same protocol, same client, half the cost, multi-threaded. Pick Redis Cloud (Redis Inc.) only when you need RedisJSON, RediSearch, or Active-Active geo-replication with vendor support that the others do not match.
When to pick which
Upstash Redis
- 01Vercel / Cloudflare Workers / Lambda where connections are scarce
- 02Bursty, low-average traffic where per-request billing wins
- 03You want a global REST endpoint without a connection pool
- 04Free tier and predictable indie-scale pricing
- 05You only need core Redis primitives (KV, lists, streams, pub/sub)
Redis Cloud / Dragonfly Cloud
- 01Dragonfly: you outgrew Upstash's per-request economics
- 02Dragonfly: single-node throughput beyond what Redis OSS gives you
- 03Dragonfly: snapshotting + memory efficiency on large datasets
- 04Redis Cloud: RedisJSON, RediSearch, RedisTimeSeries modules
- 05Redis Cloud: Active-Active CRDT geo-replication is a hard requirement
Factor-by-factor
| Factors to weigh | Upstash Redis | Redis Cloud / Dragonfly Cloud |
|---|---|---|
| Pricing model | Per request + bandwidth | Dragonfly: per instance · Redis Cloud: per instance + modules |
| Best fit workload | Serverless, edge, bursty | Dragonfly: high-throughput single-node · Redis Cloud: enterprise modules |
| Connection model | REST + native (RESP) · TLS by default | Native Redis protocol · pool required |
| Throughput ceiling per node | ~10k req/s typical for Upstash hot path | Dragonfly: 1M+ ops/s on big nodes · Redis Cloud: 200-300k/s/shard |
| Geo replication | Global database (eventual) | Dragonfly: replica + tiered · Redis Cloud: Active-Active CRDT |
| Module surface | Core Redis only | Dragonfly: core + a subset · Redis Cloud: full modules |
| Wire compatibility | Standard Redis client works | Both speak the Redis protocol · drop-in for most clients |
| We recommend | Default for serverless / edge / indie | Dragonfly for cost-per-throughput · Redis Cloud for modules + Active-Active |
Let's get started.
Send an email or book a 30-minute call.