Upstash Redis

HostedDatabase

Serverless Redis in the Cloud

Homepage Docs Pricing

Scanned 15 Oct 2026 · Schema v5 · features v21

From: $10/mo
Per-command PAYG or fixed monthly Redis plans
Free tier: Yes
No card required.
Isolation: Not disclosed
the public docs do not say
Regions: 12
us-east-1 · us-east-2 · us-west-1 · us-west-2 · eu-west-1 · eu-west-2 +6
Capabilities: 14 / 61
3 partial · 44 fail · 0 not assessed
Agent readiness: 9/11 · 9/11
read · drive, pre-login surface

Advertised for

Caching · Session management · Rate limiting · Leaderboards · Redis streams · Full text search · Vector search · Agent state

Built for

Developers, then technical

· HTTP/TCP Redis data API and SDK-first database workflow
· CLI, remote MCP and Redis-specific skills
· Per-command and storage pricing aimed at developers

01 Pricing Per-command PAYG or fixed monthly Redis plans

Tier	EntryRedis Free	Redis Pay as You Go	Redis Fixed 250MB	Redis Fixed 1GB	Redis Fixed 5GB	Redis Fixed 10GB	Redis Fixed 50GB	Redis Fixed 100GB	Redis Fixed 500GB	Enterprise	TopProd Pack add-on
Price	$0/month	$0.20/100K commands	$10/month	$20/month	$100/month	$200/month	$400/month	$800/month	$1500/month	Custom	+$200/month/database
Includes	250 MB data, 500K commands/month, 10 GB bandwidth, 1 DB	Up to 100 GB data, unlimited bandwidth (200 GB free then $0.03/GB), 100 databases	250 MB data, 50 GB bandwidth, 10K cmd/sec	1 GB storage; 100 GB bandwidth; +$10/read region/month	5 GB storage; 500 GB bandwidth; +$50/read region/month	10 GB storage; 1000 GB bandwidth; +$100/read region/month	50 GB storage; 5000 GB bandwidth; +$200/read region/month	100 GB storage; 10000 GB bandwidth; +$400/read region/month	500 GB storage; 20000 GB bandwidth; +$750/read region/month	Custom contracts, VPC peering, HIPAA, SSO, SLA, dedicated support	SLA, multi-zone HA, SOC 2 Type II report, encryption at rest, advanced monitoring and Insights; paid Redis plans only
Transfer	10 GB	—	50 GB	100 GB	500 GB	1000 GB	5000 GB	10000 GB	20000 GB	—	—
Storage	0.25 GB	100 GB	0.25 GB	1 GB	5 GB	10 GB	50 GB	100 GB	500 GB	—	—
Request count	500000	—	—	—	—	—	—	—	—	—	—
Transfer overage	—	$0.03/GB	—	—	—	—	—	—	—	—	—
Storage overage	—	$0.25/GB	—	—	—	—	—	—	—	—	—
Request overage	—	$0.000002 per request	—	—	—	—	—	—	—	—	—

Redis command, GB storage, GB bandwidth, database and additional read region·Card required: No·upstash.com

Overages: PAYG $0.20/100K commands; first 1 GB storage free then $0.25/GB; 200 GB/month bandwidth free then $0.03/GB; first 10 databases free then $0.50/database (up to 100); replicated writes count per region.

02 Website design Desktop public website · assessed 15 Oct 2026

Complete assessment.

Pale mint and white desktop pages use emerald accents, compact navigation and sans-serif typography. A centered gradient Redis hero gives way to rounded pricing cards; docs use a three-column reference layout.

Editorial minimalism
Corporate

Landing page: captured
Pricing: captured
Docs: captured

03 Runtime Each fact carries its source; dots show confidence. Open a row for the evidence.

Isolation & lifecycle

Isolation primitive

Not disclosedthe public docs do not say

Persistence

Yes

Snapshots / forks

Yes

Resources & limits

Storage

Always-persistent Redis data: Free 250 MB; PAYG up to 100 GB; Fixed 250 MB–500 GB; Enterprise up to 10 TB

Limits & quotas

Free 500K commands/month, 10 GB bandwidth, 1 DB; PAYG 100 DB and 10K commands/s; Fixed 10K–16K commands/s; Enterprise custom

GPU

Access

Deploy interface

rest-apiconsolesdkclimcp

SDK languages

TypeScriptJavaScriptPython

Network & secrets

Egress controls

No customer-programmable outbound egress policy disclosed

Secrets

Database credentials, REST bearer tokens and account Developer API keys

Bring your own cloud

Placement & use

Jurisdiction

US East (N. Virginia) (us-east-1)US East (Ohio) (us-east-2)US West (N. California) (us-west-1)US West (Oregon) (us-west-2)EU West (Ireland) (eu-west-1)EU West (London) (eu-west-2)EU Central (Frankfurt) (eu-central-1)AP South (Mumbai) (ap-south-1)AP Northeast (Tokyo) (ap-northeast-1)AP Southeast (Singapore) (ap-southeast-1)AP Southeast (Sydney) (ap-southeast-2)South America (São Paulo) (sa-east-1)

Advertised workloads

CachingSession managementRate limitingLeaderboardsRedis streamsFull text searchVector searchAgent state

04 Capabilities 14 pass · 3 partial · 44 fail · 61 of 61 assessed

Supported — Documented on the public surface and verified.
Partially supported — Exists with caveats: gated, thin, or enterprise-only.
Not supported — Checked and not offered.
Not assessed — Scanned before this capability was tracked. Not a lack.

Compute & storage 3/11

Persistent diskStorage that survives restart/stop (not ephemeral-only).

Supported

Object storageManaged S3-compatible / blob object store the platform PROVIDES to a user's workloads (buckets, presigned URLs). DISTINCT from persistent-disk (block/volume attached to an instance) and from a self-host dependency (source.self_host.deps[]=["object-storage"] is an infra dep to RUN an OSS tool — the opposite direction). SCOPE varies and matters: native first-class (Railway Buckets, Cloudflare R2) vs a sibling SKU / extension (Fly Tigris, Bunny Storage, DigitalOcean Spaces) — record which in the evidence quote / note. Admitted v15.

Not supported

Snapshots / forkingSnapshot or copy-on-write fork of a running instance (filesystem-only counts). Whether the snapshot also restores memory + running processes is recorded separately by memory-snapshot (v19).

Partially supported

Live-state (memory) snapshotsA snapshot / checkpoint / pause captures a running instance's MEMORY and PROCESS state and restores it, so running processes continue where they left off instead of a freshly booted instance with the same files. Counts whether user-triggered (snapshot, checkpoint, pause-to-storage) or used to restore pre-initialised state (memory snapshots for fast cold starts). Distinct from snapshots-forks (any snapshot or fork, including filesystem-only; a product passing that key may still fail this one) and from scale-to-zero (an idle-cost property; suspension may or may not keep memory). Actor multiplexing (see scale-to-zero) records its live-state half here — only when the suspended actor's MEMORY/process state is what comes back, not a freshly booted worker with the actor's files.

Not supported

Scale to zeroIdle instances suspend at no / negligible cost. ACTOR MULTIPLEXING (many suspended stateful actors sharing a small pool of pre-warmed workers, woken on request — Agent Substrate, AX, kagent; Rivet's hibernating actors) has NO key of its own (proposal REJECTED v20) — score the idle-cost half HERE and the live-state half under memory-snapshot; the oversubscription ratio / density is a performance characteristic the registry does not key.

Supported

GPU computeGPU-backed instances available.

Not supported

Multi-regionCompute placeable in more than one geographic region.

Supported

Sandbox templates / custom imagesBuild reusable sandbox/VM images from an OCI image or Dockerfile (a base you fork instances from).

Not supported

Cloud-init / ignition configCustomise a VM / microVM / instance at boot via cloud-init (or ignition) user-data — the same boot-metadata interface as AWS/Azure/GCP. Inject packages, users, SSH keys, files, and run-commands declaratively at launch. Distinct from sandbox-templates (a PREBUILT image you fork instances from) — this is PER-LAUNCH declarative customisation, not a baked image.

Not supported

Desktop / computer-use sandboxA virtual desktop (GUI) for LLM computer-use — browser + desktop automation, often via noVNC/VNC.

Not supported

Selectable isolation runtimeThe user chooses the isolation runtime per workload / environment / sandbox from more than one option (e.g. microVM vs gVisor vs plain container, native namespaces vs gVisor, gVisor vs VM). Records the CHOICE; the isolation_primitive facet still records the best-evidenced primary. A platform that switches runtime automatically without a user choice (e.g. gVisor forced for GPU) does not pass on that alone.

Not supported

Networking & delivery 0/9

Automatic HTTPSTLS endpoints provisioned automatically per workload.

Not supported

Built-in reverse proxyPlatform routes external traffic to workload services.

Not supported

Custom domainsBring-your-own domain via CNAME/DNS.

Not supported

Public preview URLsShareable per-deploy / per-branch URLs.

Not supported

Direct public IPv6Per-instance stable public IPv6 for raw TCP/UDP (beyond a managed HTTPS proxy) — e.g. mosh / raw sockets.

Not supported

Egress controlsConfigurable OUTBOUND network policy — egress firewall / allowlist / egress proxy on traffic LEAVING a workload. Scoped to OUTBOUND only (v15): private-network REACHABILITY between a user's own services is private-networking, not this. Static-egress-IP belongs here (an outbound concept).

Not supported

Private networkingA platform-internal private network between a user's OWN services — service-to-service connectivity, VPC, service mesh, and/or service discovery, not exposed to the public internet. DISTINCT from egress-controls (OUTBOUND firewall/allowlist), reverse-proxy (PUBLIC inbound ingress), and direct-ipv6 (per-instance PUBLIC addressing). Admitted v15.

Not supported

Email send / receiveSend and/or receive email from the workload.

Not supported

Edge KV storeA globally-replicated key-value store read from WITHIN an edge runtime at the PoP (low-latency, eventually-consistent) — Cloudflare Workers KV, Deno KV, Fastly KV Store, Akamai EdgeKV, Vercel Edge Config. Distinct from first-party-db (a managed DATABASE service you provision and connect to) and from http-query-api (HTTP access to an external store) — edge-kv is colocated with the edge compute and read at the edge.

Not supported

Developer access 5/10

Public APIDocumented programmatic API.

Supported

OpenAPI specMachine-readable OpenAPI / Swagger spec published.

Supported

CLIOfficial command-line tool.

Supported

SDKOfficial client library/libraries.

Supported

SSH accessDirect SSH into workloads.

Not supported

Filesystem APIRemote file operations over the API (list/read/write/watch/copy/upload) without SSH.

Not supported

Git deployDeploy from a Git repo / push-to-deploy.

Not supported

Private container registryHosted private image registry.

Not supported

E2B-compatible APIDrop-in compatibility with the E2B sandbox API/SDKs — existing E2B client code runs against this product by changing the endpoint/domain + key, with no business-code changes. E2B itself passes as the reference implementation. Distinct from public-api / sdk (the product has its own API — this key says it also speaks another vendor's) and from self-host-oss (a self-hosted E2B-compatible server is scored on both).

Not supported

HTTP data APIQuery / read / write the stored DATA over plain HTTP/REST (or GraphQL) WITHOUT the native protocol driver (Postgres wire / Redis RESP) — agent- and edge-friendly data access via fetch(). The DATA plane; distinct from public-api (a control-plane / management API). Auto-generated-from-schema REST/GraphQL (PostgREST, pg_graphql) is a flavour of this.

Supported

AI & agents 2/12

Built-in coding agentShips a first-party AI coding agent in the product.

Not supported

Agent skillsInstallable / declarable agent skills or tools.

Supported

AI app builderPrompt-to-app / vibe-coding generation surface.

Not supported

MCP serverExposes a Model Context Protocol server for agents.

Supported

MCP clientActs as an MCP client / consumes MCP tools.

Not supported

MCP-server hostingRun/host MCP servers as a workload on the platform (distinct from exposing a first-party MCP control server — that is mcp-server).

Not supported

LLM gatewayRoutes LLM API calls through the platform (multi-provider).

Not supported

BYOK for LLMsBring-your-own LLM provider keys.

Not supported

Model inference API (first-party)A FIRST-PARTY hosted LLM/model inference API — the provider serves its OWN catalogue of (usually open-weight) models behind a (typically OpenAI-compatible) endpoint, billed per token. Distinct from llm-gateway (a multi-PROVIDER proxy/router for YOUR calls to external providers like OpenAI/Anthropic) and from byok-llm (bring your own provider keys) — here the platform IS the inference provider, serving its own models.

Not supported

Autonomous QA agentA first-party AUTONOMOUS AI agent that QA-TESTS a running app / implementation — exercising it like a real user (clicking through flows, checking behaviour) and reporting bugs/defects (often back to a coding agent, or before a human review). Distinct from built-in-agent (a code-AUTHORING agent — this one VERIFIES the result, it does not write the feature; a product can ship both), from ai-guided-code-review (organises a diff for a HUMAN to review — not an autonomous tester), and from observability (runtime metrics/logs, not active testing).

Not supported

Credential-injection proxyThe platform holds real secrets OUTSIDE the workload and injects them on the wire (an egress / broker proxy swaps a placeholder or phantom token for the real credential on matching outbound requests), so code running in the sandbox — e.g. an untrusted agent — never sees or can exfiltrate the real key. Distinct from secrets-management (storage + injection INTO the workload as env vars/files — the workload holds the secret) and from egress-controls (outbound allow/deny POLICY; a product can have an allowlist without injecting credentials, and vice versa).

Not supported

Preinstalled coding agentThe platform installs and launches a THIRD-PARTY coding agent (a harnesses.yml entry — Claude Code, Codex, OpenCode, Pi ...) inside a workspace/sandbox it provisions, with the agent's auth wired in (your own account or API key), so you start an agent session rather than an empty box. Distinct from built-in-agent (a FIRST-PARTY agent the vendor ships) and from harnesses[] (which records that a harness CAN target the product, not that the product runs it for you).

Not supported

Data 3/4

First-party databasePlatform-provided managed database.

Supported

Database branchingCopy-on-write branch of a DATABASE (schema + data) as a dev-lifecycle primitive — branch your data like code, usually instant via a metadata operation. Distinct from snapshots-forks (forks a running compute INSTANCE / VM state) and from preview-environments (a full per-PR environment that may USE a DB branch). For a data product a CoW branch maps HERE, not to snapshots-forks.

Not supported

Vector searchFirst-class storage, indexing, and similarity search of vector embeddings — a native vector type/index or a managed vector DB. The data-layer primitive for RAG / semantic retrieval.

Supported

Ephemeral instant DB (no-signup)Provision a working, usable instance via a single command / HTTP call with NO account, signup, or card — typically time-boxed (expires unless claimed). A zero-onboarding path an agent can hit directly.

Supported

Platform & operations 0/6

Scheduled tasksCron / scheduled job primitive.

Not supported

Durable workflowsDurable execution / long-running workflow primitive.

Not supported

Preview environmentsA full EPHEMERAL environment spun up per PR / branch — compute + addons + (often) a DB branch — torn down on merge. More than preview-urls (which is just a shareable URL for one deploy).

Not supported

Built-in observabilityFirst-party metrics / logs / tracing / APM / profiling included in the platform (no third-party stack required to see what a workload is doing).

Partially supported

Managed CI/CD runnersPlatform-hosted, drop-in CI/CD runner VMs (GitHub Actions / GitLab), typically faster and cheaper than the CI vendor's own hosted runners, billed per runner-minute; isolated + ephemeral per job. Distinct from git-deploy (push-to-deploy of an APP) and scheduled-tasks (cron) — this is managed CI COMPUTE you point your existing pipelines at.

Not supported

Project template marketplaceA marketplace / gallery of prebuilt PROJECT STARTER templates (apps or websites) a user clones or launches a new project from and then customises — the "start from a template" surface of a builder / PaaS. Distinct from sandbox-templates (a COMPUTE base IMAGE you fork runtime INSTANCES from — Dockerfile / OCI), from app-builder (the prompt-to-app GENERATION surface — a product can have both), and from one-click OSS-app catalogues / helm-addon-marketplace (deploy a FINISHED app as-is, not a starter you build on).

Not supported

Organisation & security 1/9

Built-in authPlatform-provided authentication / IAM for workloads.

Not supported

SSO / SAMLEnterprise single sign-on.

Partially supported

Secrets managementFirst-class secrets storage / injection.

Not supported

TeamsMulti-user team accounts.

Supported

SharingShare a running workload/resource via link (optionally gated).

Not supported

BYOCRuns inside the customer's own cloud account.

Not supported

Deploy into customers' VPCsA SaaS vendor uses the platform to deploy and operate ITS software inside ITS CUSTOMERS' cloud accounts / VPCs (nested or "customer BYOC"), managed from the vendor's control plane. Distinct from byoc (your own workloads in your own cloud account).

Not supported

Workload identityThe platform gives each workload its own verifiable identity (OIDC token, SPIFFE SVID, cloud IAM federation) that it exchanges for short-lived credentials, so no long-lived static secret is stored or injected. Distinct from secrets-management (stores / injects static secrets) and credential-injection-proxy (swaps real secrets in on the wire).

Not supported

Self-host / OSS coreOpen-source core that can be self-hosted.

Not supported

05 Agent readiness Pre-login surface · counts, not a grade

Can an agent read it?

parse-ability · docs, metadata, machine-readable surfaces

9/11

7 full · 4 partial · 82% of applicable checks

llms.txt
Supported
“Current /llms.txt and /docs/llms.txt are substantive and include Redis; retained.”
llms-full.txt
Supported
“Current /llms-full.txt provides machine-readable brand/product context; not solely Redis.”
robots.txt AI policy
Partially supported
“robots.txt User-agent: * Allow: / plus path exclusions; no explicit AI crawler allowlist.”
JSON-LD
Supported
“Rendered Redis landing contains SoftwareApplication with name, description and USD 0 Offer in organization graph, plus Redis FAQPage.”
Sitemap
Supported
“GET /sitemap.xml 200 valid index; linked sitemap-0.xml has 953 loc entries.”
Meta tags
Supported
“Redis Database | Upstash; description and matching og:title present.”
Markdown negotiation
Partially supported
“Redis docs return markdown with Accept: text/markdown; pricing/redis.md serves detailed markdown; marketing landing returns HTML.”
Content efficiency
Partially supported
“Rendered Redis landing: 7401 readable characters / 164989 HTML bytes = 4.49%; rendered DOM measurement, not raw response.”
Docs discoverable
Supported
“Visible Documentation CTA and first-class Docs navigation link on Redis landing.”
Machine-readable pricing
Supported
“Official /pricing/redis.md has detailed rates, quotas, all Fixed tiers, add-ons and FAQ.”
No anti-bot wall
Partially supported
“Initial Python urllib docs request returned 403; foxcrawl recovered all required sources. No challenge in anonymous Chromium design pages.”

Can an agent drive it?

act-ability · APIs, SDKs, MCP, credentials, webhooks

9/11

8 full · 2 partial · 82% of applicable checks

Public API
Supported
“Redis Developer API introduction documents management and API-key creation.”
OpenAPI spec
Supported
“GET https://upstash.com/openapi.json 200 returns OpenAPI 3.0.4 with Redis endpoints; docs-local and api-host guessed paths returned 404.”
MCP server
Supported
“Official remote MCP supports Redis; URL https://mcp.upstash.com/mcp; OAuth or developer key. Local package remains available.”
SDK packages
Supported
“Official @upstash/redis and upstash-redis; compatibility wrappers for standard Redis clients.”
Auth documented
Supported
“Account email/API key Developer API authentication and database bearer-token REST access documented.”
Self-serve credentials
Supported
“Anonymous /start-redis is documented to return credentials without account/card; not invoked during read-only capture.”
Webhooks
Not supported
“No Redis-native webhook delivery API found. Redis pub/sub and SSE are not HTTP webhook delivery; QStash/Box excluded.”
CLI tool
Supported
“Official upstash CLI; Redis resource management and redis exec documented.”
Error model
Partially supported
“Developer API HTTP-status table and REST error responses documented; status table contains generic kitten-template wording, limiting confidence.”
Rate limits documented
Partially supported
“Pricing documents 10K–16K commands/s and quota-exceed behavior; status table 429; no Redis-specific rate-limit response header contract established.”
Agent config files
Supported
“Official Redis skills and MCP/plugin setup; no user configuration was modified.”

06 Coding harnesses Which agents and IDEs are documented to run here

Advertised integrations 5

Claude Code Anthropic
Supported
“Claude Code, Codex, Cursor, and Gemini CLI get the Upstash plugin (skills plus the remote MCP server). VS Code, GitHub Copilot CLI, and OpenCode get the remote MCP server in their config plus the Upstash skill.”
Source upstash.com
Advertised external agent integration with Redis tooling; not in-database or in-box execution.
Codex CLI OpenAI
Supported
“Claude Code, Codex, Cursor, and Gemini CLI get the Upstash plugin (skills plus the remote MCP server). VS Code, GitHub Copilot CLI, and OpenCode get the remote MCP server in their config plus the Upstash skill.”
Source upstash.com
Advertised external agent integration with Redis tooling; not in-database or in-box execution.
Cursor Anysphere
Supported
“Claude Code, Codex, Cursor, and Gemini CLI get the Upstash plugin (skills plus the remote MCP server). VS Code, GitHub Copilot CLI, and OpenCode get the remote MCP server in their config plus the Upstash skill.”
Source upstash.com
Advertised external agent integration with Redis tooling; not in-database or in-box execution.
Gemini CLI Google
Supported
“Claude Code, Codex, Cursor, and Gemini CLI get the Upstash plugin (skills plus the remote MCP server). VS Code, GitHub Copilot CLI, and OpenCode get the remote MCP server in their config plus the Upstash skill.”
Source upstash.com
Advertised external agent integration with Redis tooling; not in-database or in-box execution.
OpenCode opencode
Supported
“Claude Code, Codex, Cursor, and Gemini CLI get the Upstash plugin (skills plus the remote MCP server). VS Code, GitHub Copilot CLI, and OpenCode get the remote MCP server in their config plus the Upstash skill.”
Source upstash.com
Advertised external agent integration with Redis tooling; not in-database or in-box execution.

Plausible compatibility 0

Derived, not stored: the product passes SSH access, so any CLI coding agent is installable inside it. This is plausible compatibility, not a supported integration.

No general shell access documented, so nothing is derived. Absence is not unsupported.

07 Compliance & regions Standards held, with ordinal rigor; never a score

Certifications held 4

ISO/IEC 27001
in-progresshosted
“We are in process of getting this certification. Contact us ([email protected]) to learn about the expected date.”
Source upstash.com
SOC 2 Type II
certifiedhostedTrust portal held set confirmed rendered. Redis compliance/report access gated to Prod Pack or Enterprise; no report downloaded.
“SOC 2 Type II”
Source trust.upstash.com
HIPAA
enterprise-onlyhostedHIPAA compliance listed under Enterprise features on upstash.com/enterprise. Upstash Redis only; other SKUs in progress.
“Yes. Upstash Redis is HIPAA compliant and we are in process of getting this compliance for our other products.”
Source upstash.com
GDPR
self-attestedhosted
“Yes. For more information, see our Privacy Policy. We acquire DPAs from each subcontractor that we work with.”
Source upstash.com

Regions 12

us-east-1US East (N. Virginia)
us-east-2US East (Ohio)
us-west-1US West (N. California)
us-west-2US West (Oregon)
eu-west-1EU West (Ireland)
eu-west-2EU West (London)
eu-central-1EU Central (Frankfurt)
ap-south-1AP South (Mumbai)
ap-northeast-1AP Northeast (Tokyo)
ap-southeast-1AP Southeast (Singapore)
ap-southeast-2AP Southeast (Sydney)
sa-east-1South America (São Paulo)

Redis global replication docs enumerate 12 AWS read-replica regions including São Paulo; region choice is not a guarantee of cross-border legal residency.

Legal

Privacy notice Terms of service

08 Company & presence Facts only, not scored

Company

Headquarters: California, USA
Founded: —
Team size: Not disclosed
Hiring: yes

Activity

Last release: — upstash.com
Last blog post: 2026-10-14 upstash.com

Presence 6

Links found on the public surface scanned; not an exhaustive search.

09 Sources & method How this entry was produced

Public surface only

Everything here was read from upstash.com's unauthenticated pages, docs, pricing and repository on 15 Oct 2026. Nothing behind a login was used.

Statuses, not scores

Capabilities are pass, partial or fail against a written rubric (features v21). “Not assessed” means the scan predates the key.

Confidence is separate

Each fact carries its own confidence. Low-confidence facts are shown, never hidden, so you can weigh them.

Schema: scan v5
Features registry: v21
Keys tracked today: 61
Assessed on this entry: 61

Something wrong on this page?

Nearby in the atlas

All Database products →