| Product | Upstash |
| Website | upstash.com |
| Category | Serverless Data / Redis / Kafka |
| Pricing | Free tier, then pay-per-request |
What Is Upstash?
Upstash provides serverless Redis and Kafka. You create a database, get a REST API endpoint, and start making requests. There are no servers to provision, no connection pools to manage, and no monthly minimums. You pay per request, and the free tier gives you 10,000 commands per day.
The serverless model means Upstash works everywhere that HTTP works: edge functions, serverless functions, Cloudflare Workers, Vercel Edge, Deno Deploy. Traditional Redis requires a persistent TCP connection, which doesn’t work in serverless environments where connections are ephemeral. Upstash solves this with a REST API over HTTP.
Key Features
Serverless Redis
Redis-compatible with a REST API. Use it for caching, session storage, rate limiting, feature flags, and real-time leaderboards. The REST API works from any environment; the native Redis protocol is also available for environments that support persistent connections.
QStash (Message Queue)
A serverless message queue and scheduler. Send a message to a URL and QStash delivers it with guaranteed at-least-once delivery, retries, and dead letter queues. Use it for background jobs, scheduled tasks, and event-driven workflows without running a queue server.
Upstash Kafka
Serverless Apache Kafka. Produce and consume messages with per-message pricing. Useful for event streaming, log aggregation, and real-time data pipelines without managing Kafka clusters.
Edge-Compatible
Every Upstash product works over HTTP/REST, which means it works in edge environments where TCP connections aren’t available. This is the primary reason teams choose Upstash: it’s the Redis that works in Cloudflare Workers and Vercel Edge Functions.
Who Is This For?
- Serverless developers who need Redis in edge or serverless functions
- Teams that want Redis without managing infrastructure
- Anyone who needs a message queue (QStash) without running RabbitMQ or SQS
- Projects with unpredictable traffic that benefit from per-request pricing
Pros
- Works in edge/serverless (REST API)
- Pay-per-request pricing
- Generous free tier
- Redis-compatible commands
- QStash for background jobs
- No servers to manage
Cons
- REST adds latency vs native Redis protocol
- Per-request pricing can surprise at scale
- Not suitable for high-throughput Redis workloads
- Vendor lock-in (REST API is not standard Redis)
- Limited data persistence guarantees
Verdict
Upstash fills the gap between “I need Redis” and “I don’t want to manage Redis.” The serverless model, per-request pricing, and edge compatibility make it the obvious choice for Next.js, Vercel, and Cloudflare Workers projects that need caching or rate limiting.
The trade-off is latency and throughput: REST over HTTP adds overhead compared to a native Redis connection. For high-frequency workloads (thousands of operations per second per client), a managed Redis instance is still the better choice. For everything else, Upstash is simpler and cheaper.
Build a database or infrastructure tool?
Get reviewed and linked from our 27-site network.
See Packages