Memorystore for Valkey pricing
This document explains Memorystore for Valkey pricing details.
Please review our committed use discounts (CUDs) page to learn how you can save 40% with a 3 year commitment or 20% with a 1 year commitment.
Pricing overview
Memorystore for Valkey pricing is based on the following components:
Node type: Determines the node type used for your instance.
Provisioned capacity: Determines how much storage is available to the Valkey instance.
AOF persistence setting: Determines if AOF data is stored, which adds additional cost.
Region: Determines the location where the Valkey instance is provisioned.
Replicas: Determines how many nodes are in the instance. Only applicable for instances that have replicas enabled.
Instance pricing
Pricing depends on the provisioned capacity, node type, and region where the instance is provisioned. You are charged for a Memorystore for Valkey instance in 1-second increments, based on the instance's provisioned capacity in number of nodes. The table below shows the price per node for a full hour (3,600 seconds).
To see pricing, select a region from the drop-down list above the following table:
Charges are incurred as follows:
Pricing is rounded to the nearest second.
Your project starts incurring Memorystore charges when you create an instance. Whether you use the instance or not, you are charged based on the provisioned capacity.
You can change the capacity of a Memorystore instance at any time. You are charged based on the new capacity tier as soon as Memorystore completes the scaling operation.
AOF persistence pricing
Instances that use AOF persistence have an additional charge for storing AOF persistence logs. You are charged based on total instance size and the region where the instance is located. You are charged in 1-second increments, based on the instance's provisioned capacity in total GB. The table below shows the price per GB for a full hour (3,600 seconds) for using AOF.
To see pricing, select a region from the drop-down list above the following table:
Charges are incurred as follows:
Pricing is rounded to the nearest second.
Your project starts incurring AOF charges when you enable AOF based persistence on the instance. Whether you use the instance or not, you are charged based on the provisioned capacity.
You can change the capacity of a Memorystore instance at any time. You are charged based on the new capacity tier as soon as Memorystore completes the scaling operation.
Network pricing
Memorystore supports private and secure networking by default with Private Service Connect. The network pricing for Private Service Connect, when used to access Memorystore, is as follows:
| Resource usage | Price (USD) |
|---|---|
| Private Service Connect endpoint | No hourly charge for Private Service Connect endpoints deployed for Memorystore |
| Intra-zone traffic
(Traffic between a client and Memorystore instance in the same zone) |
No charge for Consumer Consumer Data Processing |
| Inter-zone traffic
(Traffic between a client and Memorystore instance in different zones) |
Consumer Data Processing applies |
| Inter-region traffic
(Traffic between a client and Memorystore instance in different regions) |
Inter-region traffic
(Traffic between a client and Memorystore instance in different regions) |
Pricing example
To calculate the per-hour cost of an instance, sum the number of shards and replica nodes, then multiply by the region price for your node type.
Suppose you provision a 5 shard instance with one replica per shard, using the highmem-medium node type. You want to deploy this instance in Iowa (us-central1), where the price per-node-per-hour is $0.1923. The hourly cost is (5 shards + 5 replica nodes) * $0.1923 = $1.92 total cost per hour.
Networking pricing is dependent on your usage. You are charged $0.01 per GiB of data processed by the PSC endpoints for clients in a different zone than your Memorystore for Valkey instance.