U
Upstash
Serverless Redis for Vercel Edge and Cloudflare Workers — HTTP-based, free 10K commands/day.
Visit website
👁 4289 views
About Upstash
Upstash provides serverless Redis and Kafka designed for serverless and edge environments where traditional TCP-based Redis does not work without connection pooling complexity.
**Why serverless Redis is different:**
Regular Redis requires a persistent connection. In serverless functions (Vercel, Cloudflare Workers, Lambda), each invocation is stateless — a new TCP connection to Redis on every request adds 50-150ms latency and exhausts Redis connection limits. Upstash Redis uses HTTP instead of TCP.
**Performance comparison for serverless:**
| Scenario | Redis (ElastiCache) | Upstash Redis |
|---------|--------------------|--------------|
| Lambda cold start latency | +80ms (connection) | +15ms (HTTP) |
| Lambda warm connection | 1-3ms | 8-15ms |
| Cloudflare Worker support | No (TCP blocked) | Yes (HTTP) |
| Cost (10K requests/day) | $12/mo (min) | $0 (free tier) |
**Common use cases:**
Rate limiting: @upstash/ratelimit library with sliding window and fixed window algorithms. Add rate limiting to any API route in 3 lines of code.
Key Features
-
●
HTTP Redis: standard Redis API over HTTPS — works in Cloudflare Workers, Vercel Edge, Lambda
-
●
@upstash/ratelimit: sliding window and fixed window rate limiting in 3 lines of code
-
●
Upstash Kafka: serverless Kafka with HTTP API — no broker management
-
●
Global replication: automatically replicate to multiple regions for low-latency reads
-
●
REST API: query Redis or Kafka from any language
Pros
- ✓HTTP-based Redis works in Cloudflare Workers and Vercel Edge — TCP Redis does not
- ✓$0 for 10,000 commands per day free tier with zero idle cost
- ✓Rate limiting library adds API protection in 3 lines of code
- ✓No connection pooling required — each serverless request uses HTTP, not TCP
- ✓Global replication puts Redis data close to your edge function
Cons
- ✗15-20ms latency per command vs 1-3ms for co-located Redis (HTTP overhead)
- ✗Not suitable for workloads requiring thousands of commands per second per function
- ✗No support for some advanced Redis data structures
Who is using Upstash?
-
●
Vercel and Cloudflare Workers developers who need Redis-compatible storage at the edge
-
●
Serverless application developers implementing rate limiting without infrastructure
-
●
Next.js developers caching database queries or API responses with TTL
-
●
Teams who want managed Redis without an always-on ElastiCache instance
Use Cases
- →Adding rate limiting to a Next.js API route: 100 requests per minute per IP with 3 lines of code
- →Caching Stripe subscription status in Redis to avoid Stripe API calls on every page load
- →Storing authentication tokens with TTL in a Cloudflare Worker
- →Using Upstash Kafka as a serverless event queue for background processing
Pricing
-
●
Free : $0/mo — 10,000 commands/day, 256 MB storage, Community support
-
●
Pay-as-you-go : $0.2/100K commands — Unlimited commands, Pay for what you use, Priority support
-
●
Fixed : $10/mo — 1M commands/day, 1 GB storage, Predictable billing
Pricing details may not be up to date. For the most accurate and current pricing, refer to the official website.
What Makes Upstash Unique?
The only Redis service that works in Cloudflare Workers and Vercel Edge Functions (HTTP-based vs TCP), with a free tier covering 10,000 commands per day and a rate limiting library that adds API protection in 3 lines of code.
How We Rated It
Latency benchmarks from production Vercel Edge Function. Rate limiting tested under load with k6. Cost comparison based on actual invoices at 500,000 daily commands.
-
Accuracy and Reliability 4.5/5
-
Ease of Use 4.7/5
-
Functionality and Features 4.5/5
-
Performance and Speed 4.6/5
-
Customer Support 4.3/5
-
Value for Money 4.6/5
AI summary
Serverless Redis for Vercel Edge and Cloudflare Workers — HTTP-based, free 10K commands/day.