Upstash

What Upstash actually is

Upstash is a serverless data platform built by developers who got tired of provisioning databases for side projects. The company — Upstash, Inc., based in California — was started by Enes Akar, Mehmet and Bilal, raised a $10 million Series A led by Andreessen Horowitz in February 2024 (total disclosed funding about $11.9 million), and has grown from a single Redis product into a small platform: Redis, Vector, Search, QStash (HTTP message queue and scheduler), Workflow (durable multi-step functions), Box (sandboxed containers for AI agents) and Blob (S3-compatible object storage). Every product has a free tier, every product is billed per request, and none of them require you to think about a server.

The Redis product is the reason most people arrive. It is Redis-compatible, reachable over both the Redis protocol and a plain REST API, and runs on a persistent disk-backed store rather than pure RAM — which is the architectural decision that makes per-request pricing possible. Because a command only costs money when you issue one, an app that is idle pays nothing but storage. That model fits serverless functions and edge runtimes (Vercel, Cloudflare Workers, AWS Lambda, Deno, Bun) exactly: no connection pooling headaches over HTTP, no paying for a RAM node that sits idle 22 hours a day.

The free tier deserves correcting up front, because our DB row and half the web still quote an older number. The current free plan is not "10,000 daily commands" — it is 500,000 commands per month with 250 MB of data, 10 GB of bandwidth, a 10,000 commands-per-second ceiling, one database, and no credit card required. There is also a stunt we grudgingly admire: a free Redis instance provisioned by a single POST request to upstash.com/start-redis with no signup at all, aimed at AI coding agents that need scratch state.

Pricing: what you really pay

Three models, and the choice between them is the whole financial decision. Free is $0: 250 MB, 500K commands/month, 10 GB bandwidth. Pay-As-You-Go charges $0.20 per 100K commands, plus $0.25 per GB-month of storage (first 1 GB free), with bandwidth free up to 200 GB/month then $0.03/GB, up to 100 GB of data and 10 databases free before $0.50 per extra database per month. Fixed plans drop per-command billing entirely: $10/mo for 250 MB, $20/mo for 1 GB, $100/mo for 5 GB, $200/mo for 10 GB, $400/mo for 50 GB, $800/mo for 100 GB and $1,500/mo for 500 GB, each with a bandwidth allowance (50 GB to 20 TB) and throughput caps. Read replicas in additional regions cost extra per region — $5 on the 250 MB tier, $10 on 1 GB, $50 on 5 GB and so on. A Prod Pack add-on ($200/mo per database) adds enterprise-ish extras on any paid plan.

Upstash's own comparison blog does the crossover math honestly, and the numbers say it plainly: at 100 million commands a month, Pay-As-You-Go runs $200 while the $20 Fixed 1 GB plan covers the same traffic flat. Conversely, a spiky workload that issues 5 million commands a month costs $10 on Pay-As-You-Go versus $20 on the cheapest Fixed plan that holds a gigabyte. Our practical rule: start Pay-As-You-Go, watch the first two bills, and switch to Fixed the moment command volume is steady. The budget feature helps here — set a monthly budget per database and it rate-limits instead of billing past it, which is a better failure mode than a surprise invoice.

Against the field this is competitive pricing. Upstash's own 2026 round-up prices a small production workload (1 GB data, 5M commands/month) at $10 on Upstash Pay-As-You-Go versus $12.41 for AWS ElastiCache cache.t4g.micro, $15 for a DigitalOcean Valkey 1 GB node, $18 for Redis Cloud Essentials 1 GB and $35.77 for Google Memorystore — and only Upstash, Aiven, Railway and Redis Cloud offer a no-card free tier at all. We would not take a vendor's self-comparison as gospel, but their unit prices are public and the arithmetic checks out from the published rates.

Global databases are billed on the same per-command basis with replication counted as commands: one primary plus one read region means 100K writes cost $0.40 ($0.20 x 2). The free tier can use Global with a maximum of one read region.

Performance & infrastructure

Upstash runs on AWS, GCP, Fly.io and Vercel regions. The documented region list for global databases covers 14 AWS regions — N. Virginia, Ohio, N. California, Oregon, Central Canada, São Paulo, Ireland, London, Frankfurt, Mumbai, Singapore, Tokyo, Sydney and Cape Town — with GCP options (us-central1, us-east4, europe-west1, asia-northeast1) available as primary regions. Reads are served from the nearest replica; writes go to the primary, replicated outward. That is genuinely global coverage for a company this size, and it means EU residency (Ireland, London, Frankfurt) is a dropdown choice rather than a sales call.

We have not benchmarked Upstash, so no throughput claims from us — but the ceilings are published: 10,000 commands per second on every tier except the two largest Fixed plans (16,000), request sizes from 10 MB up to 100 MB with paid upgrades, and record sizes from 100 MB to 5 GB depending on plan. For caching, session stores, rate limiters and queue state those limits are far above what most apps draw. For anything that would pin a Redis connection at sustained tens of thousands of ops per second, run your own numbers first — this is a serverless-priced product with serverless-shaped limits.

Durability is a design point worth understanding: Upstash's store is disk-backed (their API exposes a Pebble-based type), so data survives restarts without the RAM-tier eviction dynamics of classic Redis. The trade-offs are latency characteristics and a compatibility story that is Redis-protocol-compatible rather than a full Redis drop-in — complex multi-key operations and some edge commands behave differently, and their docs are candid about the gaps. TLS is on by default, and security add-ons (IP allowlisting, VPC peering, PrivateLink, mutual TLS, encryption at rest) appear behind higher tiers.

Where it falls short

First, the compatibility boundary. If your codebase assumes a full Redis — certain Lua semantics, blocking commands, high fan-out pub/sub at scale — validate against Upstash's supported-command list before you migrate. The REST path is the point of the product, and it is also the reason the semantics are not identical.

Second, the throughput ceiling. 10,000 commands per second per database is generous for a web app and inadequate for a hot gaming leaderboard or a real-time fan-out service. The ceiling is per database, so architectures that exceed it must shard across databases — doable, but that is your engineering time.

Third, no public SLA. We found no contractual uptime commitment with credits on the public pages; there is a status page and a support team, but if your compliance regime demands a signed availability commitment, you will be negotiating Enterprise terms. Related: daily backups surface as a toggle in the API and feature in the Prod Pack add-on at $200/mo per database — treat base-plan backups as your own responsibility until confirmed.

Finally, cost predictability has a tail risk: per-request billing plus per-replica command counting means a traffic spike during an incident (retries, thundering herds) multiplies the bill. The per-database budget control is the mitigation; use it.

Who should pick this

Our pick for serverless and edge developers who need caching, session storage, rate limiting, leaderboards, queues or agent state without operating Redis — especially on Vercel, Cloudflare Workers or Lambda, where the HTTP interface sidesteps connection pooling entirely. The free tier is a genuine home for hobby projects (500K commands/month is real usage), and the Pay-As-You-Go model is the cheapest possible way to keep a low-traffic production cache alive. Startups that expect spiky growth benefit from a bill that tracks usage instead of instance hours.

We would look at a managed Redis or Valkey node instead when you need sustained high throughput, full Redis semantics, a signed SLA, or predictable flat pricing at high command volume (Fixed plans exist, but a self-managed node may still win on cost). For relational data, look elsewhere entirely — Upstash is explicit that it is not that. Within our /category/database-hosting picks, Upstash is the one we hand to people building on functions-as-a-service.

Key takeaways

• Serverless data platform (Redis, Vector, Search, QStash, Workflow, Box, Blob) from Upstash, Inc. (California, a16z-backed Series A) — per-request pricing across every product.
• Free tier: 500K commands/month, 250 MB, no credit card — the old "10,000 daily commands" figure in our database was wrong and is corrected here.
• Pay-As-You-Go at $0.20 per 100K commands (first 1 GB storage free); Fixed plans from $10/mo (250 MB) to $1,500/mo (500 GB) with unlimited commands.
• Crossover math matters: 100M commands/month costs $200 on PAYG versus $20 on Fixed 1 GB — switch plans when traffic steadies.
• Global databases replicate across 14 AWS regions (plus GCP primaries); reads served from the nearest replica, writes to the primary.
• Limits to respect: 10,000 commands/sec ceiling, Redis-compatible rather than full Redis, no public SLA, backups tied to the Prod Pack add-on — see alternatives in /category/database-hosting.

Sources

• https://upstash.com/docs/redis/overall/billing
• https://upstash.com/pricing/redis.md
• https://upstash.com/index.md
• https://upstash.com/docs/redis/features/globaldatabase
• https://upstash.com/docs/common/concepts/global-replication
• https://upstash.com/blog/redis-pricing-comparison-every-major-provider-in-2026-with-numbers
• https://upstash.com/about
• https://upstash.com/blog/story-of-upstash
• https://pitchbook.com:8443/profiles/company/462109-96