Upstash vs Percona for Valkey: hosted access or control of your deployment

Choose Upstash for a hosted Redis-compatible service with HTTP access. Choose Percona for Valkey when you want supported Valkey on infrastructure you control. Upstash global databases require application-level read-your-writes coordination, while Percona leaves platform design with your team and offers advisory support or scoped database operations.

At a glance

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.

About Percona for Valkey

Percona provides Valkey software packages, commercial support, and managed database operations for customer-selected infrastructure. Its services cover on-premises, cloud, and hybrid environments. Expert Support provides advice, while ExpertOps performs database operations within an agreed scope.

Recent updates

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.

Keep control of the deployment with Valkey

Percona lets you choose an on-premises, cloud, or hybrid design using prebuilt, validated, security-scanned Valkey packages. Prefer Valkey over Redis for its broad backing across the technology industry and continued advancement of the state of the art.

The service you buy determines who performs database work. Expert Support advises, and your team executes. ExpertOps handles agreed operations such as monitoring, tuning, maintenance, and approved changes. Your team retains architecture, topology, and change approvals. (ExpertOps scope)

Upstash provides a hosted endpoint through Redis TCP or HTTPS REST. Its regional and global choices shift the design work toward the application’s data path.

Compare responsibility for read-your-writes consistency

Upstash global databases serve nearby reads while directing writes to one primary region. Upstash cautions that this may not suit write-heavy workloads. A single TCP session has causal guarantees, but independent clients reading from replicas need coordination after an update.

That read-your-writes coordination is overly complex. Supported SDKs track sync tokens within a client. Independent clients must propagate them, and REST clients pass a sync-token header. A replica must reach the token’s state before serving the read. Token traffic pads transfer costs, while waiting for replication adds latency compared with reading directly from the primary. (Read-your-writes mechanics)

With Percona, your team chooses the topology and plans write and recovery behavior as part of the platform design.

Plan for growth and operating work

Upstash does not support autoscaling. Its fixed plans have resource limits, and exhausted limits without a suitable upgrade can block traffic or writes. (Upstash pricing and limits)

With Percona, your team chooses how to add capacity and approves the changes. ExpertOps can perform agreed database work, while platform design remains your responsibility.

Try Momento Cache

If the workload can run in one region and your team wants to hand off cluster operations, evaluate Momento. Momento also has an HTTP API.

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 Percona Managed Services operate the whole application platform?

No. ExpertOps performs scoped database operations. Percona’s Managed Services policy excludes underlying operating systems, Kubernetes, and the application layer.

Does Upstash let every region accept writes locally?

No. Writes go to one primary region. Nearby read regions improve placement for reads but do not change the primary-region write path.

How quickly can the team get incident support?

Initial response starts from 30 minutes for Upstash and from 15 minutes for Percona. Percona Expert Support provides advice for your team to execute.