Redis Cloud vs Upstash: compare the write path before the global footprint

Choose Redis Cloud if you want to configure capacity and can own scaling decisions and regional application routing. Choose Upstash if usage-based billing and distributed reads fit your workload, with global writes going to one primary. For a global application, the deciding question is what happens between a user’s update and the next read.

At a glance

About Redis Cloud

Redis Cloud is Redis’s managed database service, offered through Essentials and Pro plans. It runs the Redis engine and provides hosted databases with managed client routing. Cloud availability, capacity, and connectivity options depend on the plan.

About Upstash

Upstash is a hosted data service with a proprietary Redis-compatible engine. It provides Redis TCP and HTTPS REST access, with regional and global database options in supported AWS and Google Cloud locations.

Recent updates

September 22, 2026 - Redis announced Smooth Scaling for Cloud Pro. It improves resizing while customers still initiate capacity changes. For this pair, the update changes the resize process rather than who owns growth decisions or how a write reaches another region, so keep those questions separate.

September 2, 2026 - Momento introduced Cluster and Flex capacity for Momento Cache. Both provide dedicated, managed Valkey resources. Cluster exposes topology choices, while Flex selects topology within capacity bounds, giving teams a choice in how they configure capacity while Momento operates the cluster.

Follow an update across regions

Redis Cloud Active-Active is eventually consistent, and your application must handle inter-region connection failover and failback. Redis manages local failover. Active-Active memory requirements can also reach four times the original data size, so regional resilience affects the capacity you buy. (Redis Active-Active documentation)

Upstash Global Database serves reads from nearby regions, but writes travel to one primary. Upstash cautions that this design may not suit write-heavy workloads.

Upstash’s read-your-writes coordination is overly complex. Supported SDKs track sync tokens within a client, independent clients must propagate them, and REST requests pass a token header. A replica waits until it reaches the token’s state before serving the read. Tokens pad transfer costs, and that replication wait adds latency compared with reading directly from the primary. (Upstash read-your-writes guide)

Plan for application and dataset growth

Redis Cloud Essentials tops out at 10,000 concurrent connections, with lower limits on smaller plans. Pro has no fixed database-level connection cap, but infrastructure and workload constrain practical capacity.

With Redis Cloud Pro, your team still initiates capacity changes. More application replicas can therefore require a capacity review even when the dataset remains small.

Upstash fixed plans provide unmetered command counts within resource limits. Its maximum size is 10 TB, compared with 50 TB for Redis Cloud. Dataset growth belongs in the decision alongside the read and write paths.

A spending limit can change application behavior. Upstash pay-as-you-go budgets can rate-limit requests. Fixed-plan upgrades can raise the bill, while exhausted resource limits can block traffic or writes.

Try Momento Cache

For a cache workload that can be served from one region, consider Momento when you want dedicated Valkey capacity with built-in autoscaling and managed client scale.

Momento Cache puts dedicated, high-performance Valkey behind a managed gateway that keeps client integration stable as your application grows. Choose Cluster for direct control over instance types, shards, and replicas, or Flex to set capacity and replication bounds while Momento selects the topology. Both include built-in autoscaling and fully managed cluster operations.

Talk to a Momento solution engineer to evaluate the capacity model and configuration that fit your workload.

Frequently asked questions

Does Redis Cloud’s five-nines SLA apply to one regional endpoint?

No. The 99.999% Active-Active SLA measures failure across all databases in the deployment.

Does Upstash guarantee causal consistency?

A single TCP session has causal guarantees. Independent clients need sync-token propagation for read-your-writes. (Upstash consistency documentation)

Can I use HTTP with Upstash?

Yes. Upstash offers HTTPS REST access alongside Redis TCP. Momento also has an HTTP API.