Spanner pricing
This document explains Spanner pricing details.
You can also use the Google Cloud Platform Pricing Calculator to estimate the cost of using Spanner.
If you pay in a currency other than USD, the prices listed in your currency on Cloud Platform SKUs apply.
Spanner pricing overview
Spanner offers editions, a tier-based pricing model that provides greater flexibility, better cost transparency, and opportunities for cost savings. You can choose between the Standard, Enterprise, and Enterprise Plus editions, letting you pick the right set of capabilities to fit your needs and budget. To learn more about Spanner editions, read the overview and blog.
When you use Spanner, you are charged for the following:
The amount of compute capacity in your instance.
Spanner keeps track of the compute capacity (measured in processing units or nodes) of an instance over time. You are charged for the number of nodes multiplied by the hourly rate. Hourly rate may vary by the edition and region.
The amount of storage that your databases use.
Spanner charges you for the average amount of data in your Spanner databases, including for tables, secondary indexes, and metadata over a one-month period, multiplied by the monthly rate.
The amount of storage that your backups use.
Spanner charges you for the average amount of storage used by your Spanner backups over a one-month period, multiplied by the monthly rate.
The amount of data replicated.
Spanner charges cross-region data replication between source and destination regions, multiplied by the amount of data replicated.
The amount of network bandwidth used.
Some types of outbound data transfer traffic, such as application reads of Spanner databases, are subject to network bandwidth charges. There are no bandwidth charges for inbound or intra-region data transfer traffic.
For all base instance configurations (instance configurations with fixed regions and replication topologies), you are charged compute capacity and storage costs for your instance. If you're using a dual-region or multi-region instance configuration, you are also charged for data replication.
If you create a custom instance configuration and add optional read-only replicas to the base instance configuration, Spanner charges you for the amount of compute capacity, data replication, and database storage used by the base instance configuration and by each optional read-only replica added.
For both base instance configurations and custom instance configurations, backup storage charges include all replicas that store the backup.
Project storage usage, replication, and network bandwidth usage are calculated in gigabytes (GiB), where 1 GiB = 230 bytes.
Project storage, replication, and network bandwidth usage charges accrue daily. You can view unbilled usage at any time on the Google Cloud console.
The following sections show the pricing for each component of Spanner.
Compute capacity
Spanner editions
Spanner editions offer tier-based, pay-as-you-use pricing, and optional one-year and three-year committed use discounts (CUDs) for your instances.
You are billed for the number of replicas, which are the physical representation of the node, multiplied by the hourly rate:
- Each node in a base regional instance configuration has three replicas.
- Each node in a base dual-region instance configuration has six replicas and is available in the Enterprise Plus edition.
- Each node in a base multi-region instance configuration has five or more replicas depending on the configuration and is available in the Enterprise Plus edition.
- Each node in an optional read-only replica has one replica, and is available in the Enterprise and Enterprise Plus editions.
Spanner offers granular instances where an instance's compute capacity can be smaller than 1 node (1000 processing units). For example, an instance with compute capacity of 200 processing units that ran for 6 hours will be charged for 1.2 node hours (200 processing units × 6 hours ÷ 1000 processing units per node).
Any compute capacity that you provision will be billed for a minimum of one hour. For example, if you temporarily scale up your instance for only 30 minutes, you will still be charged for one hour.
After the one hour minimum, billing for compute capacity is prorated. For example, if you provision a 5 node instance 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.
Choose a regional configuration from the drop-down in the following table:Choose a dual-region configuration (available in the Enterprise Plus edition) from the drop-down in the following table:
Choose a multi-region configuration (available in the Enterprise Plus edition) from the drop-down in the following table:
Compute capacity pricing for adding optional read-only replicas (available in the Enterprise and Enterprise Plus edition):
You can create a custom instance configuration and add optional read-only replicas to the base regional or multi-region instance configuration. You can't create custom dual-region instance configurations. Spanner charges you for the compute capacity of these read-only replicas in addition to the compute capacity of the base instance configuration.
As an example, if you create a custom instance configuration in the Enterprise edition, add one read-only replica
us-west3
to the base regional instance configuration us-central
, and provision one node to this custom instance configuration, then your total compute capacity cost is as follows:
Base instance configuration
us-central1
: $0.41 / replica hour * 3 replicas = $1.230 per hourAdditional read-only replica
us-west3
: $0.41 * 1.2 (includes regional multiplier) = $0.492 per hour
In total, your compute capacity costs for the custom instance configuration is $1.722 per hour.
Storage
Database storage
You are billed for the amount of data in your read-write and read-only replicas multiplied by the monthly rate. There is no storage cost for witness replicas.
Choose a regional configuration from the drop-down in the following table:Choose a dual-region configuration from the drop-down in the following table:
Choose a multi-region configuration from the drop-down in the following table:
Database storage pricing for adding optional read-only replicas:
You can create a custom instance configuration and add optional read-only replicas to the base regional or multi-region instance configuration. You can't create custom dual-region instance configurations. Spanner charges you for the database storage used by your read-only replicas in addition to the database storage used by your base instance configuration.
As an example, if you create a custom instance configuration with 1000 GiB of storage and add one read-only replica us-west3
to the base multi-region instance configuration us-central1
, then your total database storage cost is as follows:
Base configuration
us-central1
: $0.30 per GiB per month * 1000 GiB = $300 per monthAdditional read-only replica
us-west3
: $0.12 per GiB per month (includes regional multiplier) * 1000 GiB = $120 per month
In total, your database storage cost for the custom instance configuration is $420 per month.
Backup storage
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).
Data replication
Spanner replication is built on top of a custom Paxos implementation, a distributed consensus algorithm that guarantees the consistency of your data across all replicas. This ensures that even in the event of network outages or hardware failures, your data remains accurate and accessible.
Data replication pricing
Intra-region replication is free of charge.
In dual-region, multi-region instance configurations, or regional configuration with optional custom read-only replicas, Spanner automatically replicates your data between regions. When directly writing data (inserts, updates, and deletes) into these configurations, you are charged for the volume of data replicated. You are also charged for any operation that indirectly modifies data, for example, when using TTL, change streams, and secondary indexes.
Inter-region data replication pricing
You are charged for the volume of data replicated across regions. The source of replication is always the leader region.
Source location | Destination location | |||||||
---|---|---|---|---|---|---|---|---|
Northern America | Europe | Asia | Indonesia | Oceania | Middle East | Latin America | Africa | |
Northern America | $0.04/GiB | $0.07/GiB | $0.11/GiB | $0.13/GiB | $0.13/GiB | $0.14/GiB | $0.17/GiB | $0.14/GiB |
Europe | $0.07/GiB | $0.04/GiB | $0.11/GiB | $0.13/GiB | $0.13/GiB | $0.14/GiB | $0.17/GiB | $0.14/GiB |
Asia | $0.11/GiB | $0.11/GiB | $0.11/GiB | $0.13/GiB | $0.13/GiB | $0.14/GiB | $0.17/GiB | $0.14/GiB |
Indonesia | $0.13/GiB | $0.13/GiB | $0.13/GiB | $0.11/GiB | $0.11/GiB | $0.14/GiB | $0.17/GiB | $0.17/GiB |
Oceania | $0.13/GiB | $0.13/GiB | $0.13/GiB | $0.11/GiB | $0.11/GiB | $0.14/GiB | $0.17/GiB | $0.17/GiB | Middle East | $0.14/GiB | $0.14/GiB | $0.14/GiB | $0.14/GiB | $0.14/GiB | $0.11/GiB | $0.17/GiB | $0.14/GiB |
Latin America | $0.17/GiB | $0.17/GiB | $0.17/GiB | $0.17/GiB | $0.17/GiB | $0.17/GiB | $0.17/GiB | $0.17/GiB |
Africa | $0.14/GiB | $0.14/GiB | $0.14/GiB | $0.17/GiB | $0.17/GiB | $0.14/GiB | $0.17/GiB | $0.14/GiB |
You can use the Cross region replicated bytes metric to view the number of bytes that are replicated from your leader replica to the other replicas in your instance configuration. For more information, see Monitor data replication.
Storage for replicated data
Replicated data stored in the destination regional, dual-region, or multi-region instance configuration is charged according to Spanner storage pricing.
Network
Inbound data transfer | Free |
Data transfer within the same region | Free |
Data transfer between regions within the same continent (per GB) | $0.01 |
Inter-continental data transfer | At Internet data transfer rate |
Using the following features may incur network charges:
Outbound internet data transfer rates
For instances in regional configurations, internet data transfer rates are shown in the following table.
For instances in dual-region or multi-region configurations, internet data transfer is charged as follows:
Data transfer from read-write transactions, which consists of the reads and queries in a read-write transaction, is always charged based on the data transfer cost from the leader region.
Data transfer from other reads is charged based on the data transfer cost of the nearest region that has read-write or read-only replicas. For example, assuming that you are using the multi-region configuration
nam-eur-asia1
:- For clients in
us-central1
, data transfer is free, because the region is part of the multi-region configuration. - For clients in
us-west1
, data transfer is charged fromus-central1
, which is the closest region in the multi-region configuration. - For clients in
asia-south1
, data transfer is charged fromasia-east1
, which is the closest region in the multi-region configuration.
- For clients in
Spanner Data Boost pricing
Spanner Data Boost automatically provides on-demand, isolated compute resources to any existing Spanner instance. You can use it to process workloads like federated queries from Google BigQuery (BQ), data exports using Dataflow, or batch queries from your line-of-business applications without impacting your existing Spanner workload. By default, Spanner queries will automatically connect to Data Boost resources in the same region as your active Spanner instance.
Spanner Data Boost measures usage in Serverless Processing Units (SPU) on a per-second basis with a 1-minute minimum charge. SPU represents compute resources required to serve a query. It includes CPU, memory, and local data transfer. There is no fixed cost or resource management needed. You only pay for your actual SPU usage. For more information, see the Spanner Data Boost overview.
Database export and import pricing
There are no additional charges from Spanner for using the export or import tools; you pay the standard rates for data storage and replication when you import a database to 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 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 doesn't overlap with your Cloud Storage bucket configuration, you pay Cloud Storage's standard rates for outbound data transfer. To minimize charges, ensure that you choose a region for your import job that overlaps with your bucket configuration. For more information, see Choosing an import region.
If you run an export job in a region that doesn't overlap with your Spanner instance configuration, you pay the standard rates for outbound data transfer. To minimize charges, ensure that you choose a region for your export job that overlaps with your instance configuration. For more information, see Choosing an export region.
Spanner free trial instances
A Spanner free trial instance lets you learn and explore Spanner features and capabilities at no cost for 90 days. During the 90-day free trial period, you can store up to 10 GiB of data in your free trial instance, which supports Spanner Standard edition features and Spanner Graph. For more details, see Spanner free trial instances. If you are a new Google Cloud customer, you are also eligible for the 90-day Google Cloud free trial that gives you $300 credits to use on Google Cloud products including Spanner. The Spanner free trial instance is in addition to the $300 credits offered by the Google Cloud free trial.
You can upgrade from a free trial instance to a paid, Enterprise instance to continue using your instance beyond the 90-day free trial period and scale beyond the free instance usage limits. If you choose to upgrade your free trial instance to a paid instance, you will be charged according to the pricing on this page.
Pricing for moving an instance to a different configuration
You can move your Spanner instance from any regional, dual-region, or multi-region instance configuration to any other regional, dual-region or multi-region instance configuration.
You can't move a regional (single-region) instance in the Standard or Enterprise edition directly to a dual-region or multi-region instance configuration. You must upgrade the edition of your instance to the Enterprise Plus edition first, then move the instance.
You will be charged for compute capacity and storage usage at both the source and destination instance configurations while the move is in progress. Once the move is complete, you will be charged for compute capacity, storage usage, and replication (applicable only for moves involving optional read-only replica, dual-region, or multi-region instance configuration) at the destination instance configuration. For respective rates, see the compute capacity, storage, and replication pricing sections.
You will be charged a one-time cost for network usage based on the amount of data that you move between the source and destination instance configurations. For network rates, see the network section. If the source and destination instance configurations consist of different regions, you are only charged for data moved to read-write and read-only regions in the destination instance configuration that do not overlap with the regions in the source instance configuration. You aren't charged for the data moved to the witness region.
To illustrate network usage costs, let's say you are moving an instance with 1000GiB data from a source instance configuration to a destination instance configuration. The network rate for “Data transfer between the regions within the same continent” is $0.01 per GiB. “Inbound” and “Outbound within the same region” are free. Let us look at the total network costs in different example scenarios.
If the source instance configuration is us-central1
and the destination instance configuration is us-east1
, your total network usage costs are 1000GiB * $0.01 per GiB * 1 = $10. (In this scenario, the destination instance configuration has one region that does not overlap with any region in the source instance configuration.)
If the source instance configuration is us-central1
and the destination instance configuration is nam8
(which contains read-write regions in us-west2
and us-west1
), your one-time network usage costs are 1000GiB * $0.01 per GiB * 2 = $20. (In this scenario, the destination instance configuration has two regions that do not overlap with any region in the source instance configuration.)
If the source instance configuration is nam7
(which contains read-write regions in us-central1
and us-east4
) and the destination instance configuration is us-central1
, your one-time network usage costs are 1000GiB * $0.01 per GiB * 0 = $0. (In this scenario, the destination instance configuration has zero regions that do not overlap with regions in the source instance configuration.)
If the source instance configuration is nam7
(which contains read-write regions in us-central1
and us-east4
) and the destination instance configuration is eur5
(which contains read-write regions in europe-west2
and europe-west1
), your one-time network usage costs are 1000GiB * $0.12 per GiB * 1 + 1000GiB * $0.01 per GiB * 1 = $130. (In this scenario, destination instance configuration has two regions that do not overlap with the regions in the source instance configuration. Network rates of “Inter-continental data transfer” ($0.12 per GiB for 0-1TB monthly usage) apply once and “Data transfer between the regions within the same continent” ($0.01 per GiB) apply once.)
What's next
- Read the Spanner documentation.
- Get started with Spanner.
- Try the Pricing calculator.
- Learn about Spanner solutions and use cases.