Memorystore for Valkey vs Render Key Value: capacity control and resize downtime

Choose Memorystore for Valkey when you want Google Cloud capacity your team can resize within a selected cluster mode. Render Key Value fits applications already on Render, but upgrades interrupt service and existing instances cannot shrink. New Render instances run Valkey 8.

At a glance

About Google Cloud Memorystore

Google Cloud Memorystore for Valkey is a managed caching service built on Valkey. It offers cluster-enabled and cluster-disabled deployments in Google Cloud, with customers choosing node types, capacity, and topology. Memorystore for Redis and Redis Cluster are separate related offerings.

About Render Key Value

Render Key Value is Render’s hosted key-value service. New instances run Valkey 8, while legacy instances run Redis 6. Customers select a provisioned instance size, which determines its memory and connection limits.

Recent updates

September 24, 2026 - Memorystore’s current Valkey 9 release became generally available. Teams evaluating Valkey 9 can now select that release. The current version table lists that release as the default. Upgrades cannot be downgraded.

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.

June 11, 2026 - Render added configurable persistence for paid instances. Disposable caches can select Off, while other workloads can retain persistence. Mode changes restart the instance, and moving to or from Off loses all data.

Plan capacity changes around service interruptions

Render makes capacity growth an application availability decision. A Key Value upgrade restarts the service with a minute or two of unavailability, and data loss depends on the persistence mode. An existing instance cannot be downgraded.

With Memorystore, your team chooses node types and shard counts. Clustered deployments offer six regular node types with predefined CPU and memory combinations. You can deploy the Memorystore Cluster Autoscaler to adjust shard counts from CPU and memory demand. Your team configures and operates that automation.

Google warns against reducing CPU or memory for workloads that rely on eviction, because memory spikes can block operations. Resharding can increase latency while the service remains available. (Google scaling best practices)

Count the clients and trace their network path

Render’s published plans tie connection limits to memory. The 1 GB plan allows 1,000 connections, and the largest published plan reaches 40,000. A small dataset serving many application instances can therefore need more memory capacity just to accommodate its connections.

Render applications can reach Key Value privately within the same workspace and region. External connections use IP allowlisting and authentication.

Memorystore uses Private Service Connect and has no public endpoint. Applications outside Google Cloud need suitable supported networking to connect.

Try Momento Cache

When a small dataset must serve a growing application fleet, consider Momento Cache and its gateway designed for millions of clients.

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

Can I resize Memorystore after choosing a cluster mode?

Yes. You can resize within the selected mode, but the mode itself cannot change in place. Cluster-enabled deployments use cluster-aware clients. Cluster-disabled deployments use one shard and ordinary clients.

How do their uptime commitments compare?

Memorystore offers a 99.99% uptime SLA. Render’s Key Value uptime percentage is unknown from its public pricing and service information.

Does Render Key Value use Valkey or Redis?

New instances use Valkey 8. Instances created before February 12, 2025 use Redis 6 and continue operating without feature-version upgrades. Render has also scheduled security patches for both Redis and Valkey, as documented on October 8, 2025.