Upstash meters Redis per request and its Kafka page now 404s

The workload

Pricing a serverless data store by the request, rather than by a flat monthly server size, means a founder has to model traffic before predicting cost. Upstash's own pricing page, retrieved 16 September 2026, prices Redis this way: no server to size, only commands to count. Working out whether that is cheaper than a flat-rate instance requires estimating request volume first, which is a modelling task rather than an hours-and-headcount one.

What the documents show

Upstash's pricing page states, verified, that Redis pay-as-you-go costs '$0.2 per 100K commands,' with a few connection-management commands excluded from billing. The free tier, verified, allows 500,000 monthly commands, 256 MB of data, 10 GB of monthly bandwidth, and one database. The Redis pricing documentation adds, verified, that the maximum request size is 10 MB, and requests above that 'are rejected with an exception' rather than truncated. Storage beyond the first free gigabyte costs $0.25 per GB, and bandwidth beyond 200 GB monthly costs $0.03 per GB, both verified. Kafka pricing is a different story: as of this retrieval, both upstash.com/pricing/kafka and upstash.com/docs/kafka return HTTP 404, and Upstash's current documentation lists Redis, Vector, Search, QStash, Workflow, Box and Blob as its products — Kafka is absent. A 29 August 2024 archived capture of that URL, verified as Upstash's own page then, shows it still live, pricing Kafka's free tier at 10,000 messages daily and 1,000 per second, with pay-as-you-go at '$0.6 per 100K messages.' A November 2024 capture already returns 404, so the page's disappearance falls in that window; no dated Upstash announcement of a Kafka discontinuation was found.

The operating cost

Redis cost scales with request volume, not headcount: at $0.20 per 100,000 commands, 10 million monthly commands would cost $20, an editorial estimate using Upstash's published rate and an assumed volume, not a vendor figure. A workload under 500,000 monthly commands pays nothing. Kafka, while priced, billed by message count rather than command count, and its current cost cannot be stated because its pricing page no longer resolves.

The stop condition

Upstash's documents state a hard technical stop condition for Redis: a request larger than 10 MB is rejected outright, so an application generating oversized payloads must resize them before they reach the database. The editorial stop condition for the billing model itself is when request volume becomes predictable enough that a fixed-price plan would cost less than metered pay-as-you-go — fixed plans start at $10 per month, verified, and comparing that flat rate against a rolling command count is the only way to know when to switch.

• Does the workload's monthly command count fit inside the free 500,000, or has it already crossed into billed usage?
• Are any payloads approaching the 10 MB request ceiling, and what happens to the application if one is rejected?
• If this workload used Kafka, is there a migration plan now that its pricing page is gone?

A vendor's own pricing page disappearing without a dated announcement is itself a documented fact, not an assumption: it is evidence the product's availability changed, even where the reason is not stated anywhere this entry could verify.