Upstash
Upstash · api security · reviewed by Stan K. · Source: data snapshot · data as of 2026-11-13
The DIY rate limiter's meter: $0.20 per 100K Redis commands PAYG, a real free tier (500K commands/mo + 250 MB) — and fixed $10/$20 tiers if you hate meters.
#4 of 8 in Api Security
ToolScore breakdown — why 66/100
10 criteria × 10 points. Low pillars are visible on purpose — that's the point of a score you can audit. Methodology →
What it does well
- ▸A real free tier: 500K commands/mo + 250 MB — a token-bucket check is 1–2 commands per request, so that is roughly 250–500K requests before the meter starts
- ▸The arithmetic stays small at scale: 50M requests ≈ $10–20/mo on PAYG — cheaper than every WAF in this hub except Cloudflare Free
- ▸Fixed tiers if you hate meters: $10/mo (250 MB, 50 GB bandwidth) · $20/mo (1 GB, 100 GB) — a clean escape from per-command anxiety
- ▸Every rate is published: per-command, per-GB, per-tier bandwidth, and the replication multiplier — no quote conversations
- ▸Replication is honest about its shape: additional zones add bandwidth only, not commands — the multiplier does not compound per region
Where it costs you
- ▸Global replication doubles your writes: 1 primary + 1 read region → $0.40/100K — the headline $0.20 quietly doubles the moment you replicate
- ▸The meter is per command, not per request — your bill depends on how many commands your algorithm spends per request (1–2 for a token bucket)
- ▸Rate limiting only — this is a Redis meter, not a WAF: no managed rules, no DDoS absorption, no bot defense
- ▸Nothing published about latency or data handling in our check — the pillars sit at the neutral 5
Hidden traps — the stuff the pricing page doesn't say
Global replication with 1 primary + 1 read region doubles writes → $0.40/100K. The $0.20 headline applies to the un-replicated world; if your limiter must survive a region loss (the usual reason to replicate), budget the doubled rate from day one.
Replicating to additional zones adds bandwidth only, not commands — so the write meter does not triple with a third zone. Good news, but it also means your bandwidth line grows with every zone while the command line does not: the two meters diverge as you scale out.
A token-bucket check is 1–2 commands per request, so 50M requests ≈ $10–20/mo on PAYG after the free 500K. An algorithm that spends 5 commands per request pays 2.5–5× that — the meter prices your code's efficiency, not your traffic.
Know the limits before you pay: read the traps above, then decide with eyes open.
Visit official siteAffiliate link where available — never affects the score.
- official upstash.com/pricing — PAYG, free tier, fixed tiers, replication (official, checked 2026-11-13) verified
Data as of 2026-11-13. Prices and limits change monthly — report anything stale. How we verify: methodology.
Closest alternatives
A free always-on L3/L4 shield for every AWS customer — and a $3,000/mo, 1-year-committed Advanced ti
Pure pay-as-you-go with every cent published — $5/web ACL, $1/rule, $0.60/1M requests — and a meter
The $0 edge stack — unmetered WAF, rate limiting and L3/L4/L7 DDoS on every plan including Free; the
Upstash review
In-depth analysis · last updated 2026-11-13
The DIY limiter's economics
When the rate limiter is not inside a WAF you already pay for, the DIY route moves the meter to Redis — and Upstash is the cleanest published version of that meter: $0.20 per 100K commands PAYG, storage at $0.25/GB with the first 1 GB free, and a real free tier of 500K commands/month plus 250 MB. The unit matters: commands, not requests. A token-bucket check is 1–2 commands per request, so 50M requests ≈ $10–20/mo on PAYG after the free 500K — cheaper than every WAF in this hub except Cloudflare Free, for the narrow job of counting.
The replication double
The one number that bites is replication. Global replication with 1 primary + 1 read region doubles writes → $0.40/100K. If your limiter must survive a region loss — the usual reason to replicate — the headline $0.20 quietly doubles from day one. The shape is at least honest and published: replication is not linear ×N; additional zones add bandwidth only, not commands. So the command meter flattens as you scale out while the bandwidth meter keeps climbing — two lines diverging in opposite directions, both on your bill.
The escape hatch
Upstash uniquely publishes a fixed-tier exit for meter anxiety: $10/mo buys 250 MB and 50 GB bandwidth, $20/mo buys 1 GB and 100 GB. That is the commercial answer to the question every metered product dodges — "what is the worst case?" — and it caps the DIY rate-limiting bill at a number you can put in a spreadsheet before you deploy.
How the pillars land
Price/Value 9: $10–20/mo at 50M requests with a free tier and fixed-tier caps — excellent for the counting job. Request & rate limits 8: the limits are legible (500K free, per-command meter, fixed-tier ceilings), docked because the meter prices your algorithm's commands rather than your traffic. Latency & edge 5, Data handling 5, Self-host 5 and Track record 5: nothing verifiable in this snapshot — the neutral 5 across the board, by rule. Feature set 7: global replication, storage, fixed tiers — a full Redis product, but it is still only a rate limiter in this comparison: no managed rules, no DDoS absorption, no bot defense. Ease of use 8: two clean on-ramps (PAYG or fixed tier) and no quote conversations. Pricing transparency 9: every rate published, including the unflattering replication multiplier. Support & docs 5: neutral — nothing support-related was verifiable from the official pages in this snapshot.
Verdict — FIXED-TIER ESCAPE, 66/100
As a rate limiter, Upstash is the best-priced meter in this hub after $0 — and the only metered vendor here that publishes its own worst case ($10/$20 fixed tiers). Pair it with an edge that absorbs floods (Cloudflare Free is the natural companion), budget the replicated write rate, and keep the limiter's command count per request at 1–2. What it is not, and does not claim to be, is a WAF: buy it for counting, not for protection.