Redis
An edge cache for the data that lives for a moment.
A per-tenant key-value store your agent reaches over the Upstash REST API — no sockets, no client to bundle, just commands over HTTP. Keep counters, sessions, rate-limit buckets, and queues hot and close to every request.
speed
Memory-speed, one fetch away
Reads and writes land in memory and answer in a single REST round trip, so the work you do on every request — checking a session, bumping a counter, reading a cached value — never waits on a database. Pipeline a handful of commands together and pay for just one hop.
- Stateless HTTP — nothing to pool or reconnect
- One endpoint for every command
isolation
Your keys, your keyspace
Every tenant gets an automatic key prefix on a shared Upstash database, so you write plain, readable keys and never collide with anyone else. The prefix is applied and stripped for you — isolation you get for free, not infrastructure you have to wire.
- Transparent per-tenant prefixing
- Per-key TTLs for self-cleaning data
pricing
Fluid pricing
Redis runs against your plan's monthly bucket; once it's spent, usage auto-buys from fluid credit. Two numbers set the ceiling:
free plan
500k commands / month
pro plan
25m commands / month
Cohesivity Redis is an edge key-value store your agent provisions once and reaches over the Upstash REST API. There is no socket to keep open and no client library to bundle — every command is a stateless HTTP call. It is built for the hot, short-lived data your app touches constantly: counters, sessions, rate-limit buckets, and lightweight queues.
Related
Key-value, Upstash, REST, Ephemeral, Edge cache
For more information, ask your agent.