This document explains Cloud Spanner pricing details.
You can also use the Google Cloud Platform Pricing Calculator to estimate the cost of using Cloud Spanner.If you pay in a currency other than USD, the prices listed in your currency on Cloud Platform SKUs apply.
Cloud Spanner pricing overview
When you use Cloud Spanner, you are charged for the following:
The number of Cloud Spanner nodes in your instance.
Cloud Spanner keeps track of the number of nodes in your instance over time. You are charged for the number of nodes multiplied by the hourly rate. Any nodes that you provision will be billed for a minimum of one hour. For example, if you temporarily scale up the number of nodes in your instance for 30 minutes, you'll be charged for one hour.
After the one hour minimum, billing for nodes is prorated. For example, if you provision 5 nodes at 1:00PM and then at 2:01PM (more than an hour later) you remove one node, the 5th node is billed for 61 minutes.
The amount of storage that your databases use.
Cloud Spanner charges you for the average amount of data in your Cloud Spanner databases, including tables, secondary indexes, and metadata over a one-month period, multiplied by the monthly rate.
The amount of storage that your backups use.
Cloud Spanner charges you for the average amount of storage used by your Cloud Spanner backups over a one-month period, multiplied by the monthly rate.
The amount of network bandwidth used.
Some types of network egress traffic, such as application reads of Cloud Spanner databases, are subject to bandwidth charges, as shown below. There are no bandwidth charges for Cloud Spanner replication or network ingress traffic.
These charges include all of the replicas that Cloud Spanner runs for your instance. You are charged for each instance, not for each replica.
Project storage usage and bandwidth usage are calculated in gigabytes (GB), where 1 GB = 230 bytes.
The following tables show the pricing for each component of Cloud Spanner.
|Regional configuration||Description||Cost per node per hour (including all replications)|
|us-west3||Salt Lake City||$1.08|
|Multi-region configuration||Description||Cost per node per hour|
|nam-eur-asia1||North America, Europe, and Asia||$9.00|
You are billed only for the storage that you use, including tables, secondary indexes, and the overhead for those indexes.
|Regional configuration||Description||Storage per GB per month|
|us-west3||Salt Lake City||$0.36|
|Multi-region configuration||Description||Storage per GB per month|
|nam-eur-asia1||North America, Europe, and Asia||$0.90|
You are billed only for the storage that you use. A backup is billed from the time it is complete until the time it is deleted. A completed backup is billed for a minimum of 24 hours, irrespective of time of deletion (if less than one day).
|Regional configurations||Multi-region configurations|
|$0.10 per GB per month||$0.30 per GB per month|
|Egress within the same region||Free|
|Egress between regions within the US (per GB)||$0.01|
|Inter-continental egress||At Internet egress rate|
Internet egress rates
For instances with regional configurations, internet egress rates are as shown below.
For instances with multi-region configurations, internet egress is charged as follows:
- Egress from read-write transactions, which consists of the reads and queries in a read-write transaction, is always charged based on the egress cost from the default leader region.
Egress from other reads is charged based on the egress cost of the nearest region that has read-write or read-only replicas. For example, assuming that you are using the multi-region configuration
- For clients in
us-central1, egress is free, because the region is part of the multi-region configuration.
- For clients in
us-west1, egress is charged from
us-central1, which is the closest region in the multi-region configuration.
- For clients in
asia-south1, egress is charged from
asia-east1, which is the closest region in the multi-region configuration.
- For clients in
Database export and import pricing
There are no additional charges from Cloud Spanner for use of the export or import tools; you pay the standard rates for data storage when you import a database to Cloud Spanner. However, there are other potential charges associated with importing and exporting databases:
You will be charged the standard rates for Dataflow batch workers when you run an export or import job. The total charge will depend on the amount of data being imported or exported as well as performance factors. For example, if your Cloud Spanner instance is already under heavy load, import and export jobs might take longer, resulting in a larger overall charge for Dataflow workers.
If you run an import job in a region that does not overlap with your Cloud Storage bucket configuration, you pay Cloud Storage's standard rates for network egress. To minimize charges, ensure that you choose a region for your import job that overlaps with your bucket configuration. See Choosing an import region for more details.
If you run an export job in a region that does not overlap with your Cloud Spanner instance configuration, you pay the standard rates for network egress. To minimize charges, ensure that you choose a region for your export job that overlaps with your instance configuration. See Choosing an export region for more details.