Pricing

This document explains Cloud Bigtable pricing details. You can also use the Google Cloud Platform Pricing Calculator to estimate the cost of using Cloud Bigtable.

If you pay in a currency other than USD, the prices listed in your currency on Cloud Platform SKUs apply.

Overview

When you use Cloud Bigtable, you are charged for the following:

  1. The type of Cloud Bigtable instance and the total number of nodes in your instance's clusters.
  2. The amount of storage that your tables use.
  3. The amount of network bandwidth that you use.

Storage and bandwidth usage are measured in binary gigabytes (GB), where 1 GB is 230 bytes. This unit of measurement is also known as a gibibyte (GiB).

Storage and bandwidth charges accrue daily. You can view unbilled usage at any time on the Google Cloud Platform Console.

The following sections show the pricing for each component of Cloud Bigtable.

Instance type and nodes

For production instances, Cloud Bigtable keeps track of how many Cloud Bigtable nodes exist in your instance's clusters during each hour. You are charged each hour for the maximum number of nodes that exist during that hour, multiplied by the hourly rate. As a result, any nodes that you provision will be billed for a minimum of one hour.

For development instances, you are billed a flat rate for each hour.

Node charges are for provisioned resources, regardless of node usage. Charges apply even if your cluster is inactive.

Iowa (us-central1) Los Angeles (us-west2) Oregon (us-west1) Northern Virginia (us-east4) South Carolina (us-east1) Montréal (northamerica-northeast1) São Paulo (southamerica-east1) Belgium (europe-west1) Finland (europe-north1) London (europe-west2) Netherlands (europe-west4) Zürich (europe-west6) Mumbai (asia-south1) Singapore (asia-southeast1) Taiwan (asia-east1) Hong Kong (asia-east2) Tokyo (asia-northeast1) Osaka (asia-northeast2) Sydney (australia-southeast1)
Instance type Cost
Production instance
Development instance

For details about the typical performance of a production instance, see Performance for typical workloads.

Development instances are for testing and development. They have no performance or uptime guarantees, and the SLA does not apply.

If you pay in a currency other than USD, the prices listed in your currency on Cloud Platform SKUs apply.

Storage

Cloud Bigtable frequently measures the average amount of data in your Cloud Bigtable tables during a short time interval. For billing purposes, these measurements are combined into an average over a one-month period, and this average is multiplied by the monthly rate.

You are billed only for the storage you use, including overhead for indexing and Cloud Bigtable's internal representation on disk. For instances that contain multiple clusters, Cloud Bigtable keeps a separate copy of your data with every cluster, and you are charged for every copy of your data.

When you delete data from Cloud Bigtable, the data becomes inaccessible immediately; however, you are charged for storage of the data until Cloud Bigtable compacts the table. This process typically takes up to a week.

In addition, if you store multiple versions of a value in a table cell, or if you have set an expiration time for one of your table's column families, you can read the obsolete and expired values until Cloud Bigtable completes garbage collection for the table. You are also charged for the obsolete and expired values prior to garbage collection. This process typically takes up to a week.

Iowa (us-central1) Los Angeles (us-west2) Oregon (us-west1) Northern Virginia (us-east4) South Carolina (us-east1) Montréal (northamerica-northeast1) São Paulo (southamerica-east1) Belgium (europe-west1) Finland (europe-north1) London (europe-west2) Netherlands (europe-west4) Zürich (europe-west6) Mumbai (asia-south1) Singapore (asia-southeast1) Taiwan (asia-east1) Hong Kong (asia-east2) Tokyo (asia-northeast1) Osaka (asia-northeast2) Sydney (australia-southeast1)
SSD storage (GB/mo) HDD storage (GB/mo)
If you pay in a currency other than USD, the prices listed in your currency on Cloud Platform SKUs apply.

Network

Some types of network egress traffic are subject to bandwidth charges, as shown below.

Ingress Free
Egress to the same zone Free
Egress between zones in the same region Free
Egress between regions within the US (per GB) $0.01
Inter-continental egress At Internet egress rate

If you pay in a currency other than USD, the prices listed in your currency on Cloud Platform SKUs apply.

Internet egress rates

Iowa (us-central1) Los Angeles (us-west2) Oregon (us-west1) Northern Virginia (us-east4) South Carolina (us-east1) Montréal (northamerica-northeast1) São Paulo (southamerica-east1) Belgium (europe-west1) Finland (europe-north1) London (europe-west2) Netherlands (europe-west4) Zürich (europe-west6) Mumbai (asia-south1) Singapore (asia-southeast1) Taiwan (asia-east1) Hong Kong (asia-east2) Tokyo (asia-northeast1) Osaka (asia-northeast2) Sydney (australia-southeast1)
Monthly Usage Egress to Worldwide Destinations (excluding Asia & Australia)
(per GB)
Egress to Asia Destinations (excluding China, but including Hong Kong)
(per GB)
Egress to China Destinations (excluding Hong Kong)
(per GB)
Egress to Australia Destinations
(per GB)
Ingress
0-1 TB $0.23 $0.19 Free
1-10 TB $0.22 $0.18 Free
10+ TB $0.20 $0.15 Free
If you pay in a currency other than USD, the prices listed in your currency on Cloud Platform SKUs apply.

One-time, initial replication traffic

Each instance's clusters are located in zones, and each zone is located in a region. If you add a new cluster in a region, and none of the instance's existing clusters are in that region, you are charged a one-time cost for the initial data copy to the new cluster. For this initial copy, you are charged the network egress rate for the existing cluster that is geographically closest to the new cluster, multiplied by the amount of data in your tables. There is no charge for replication between clusters in a single region.

For example, let's say your instance has 9 TB of data, and its clusters are in us-east1 (South Carolina) and europe-west1 (Belgium). If you add a new cluster to the instance in the us-central1 (Iowa) region, your data is copied to the new cluster from the existing cluster in us-east1, which is the closest cluster in the instance. You are charged a rate of $0.01 per GB, which is the network egress rate for traffic between regions within the US. As a result, the initial replication cost is $92.16:

9 TB * 1,024 GB/TB * $0.01 per GB = $92.16

In another example, let's say your instance has 9 TB of data, and its clusters are in us-east1 (South Carolina) and europe-west1(Belgium). If you add a new cluster in europe-west2 (London), your data is copied to the new cluster from the existing cluster in europe-west1, which is the closest cluster in the instance. You are charged a rate of $0.11 per GB, which is the network cost for replication of 1 TB to 10 TB within Europe. In this example, the initial replication cost is $1,013.76:

9 TB * 1,024 GB/TB * $0.11 per GB = $1,013.76

Ongoing replication traffic

When you write to a cluster, Cloud Bigtable automatically replicates the write from that cluster (the "source cluster") to all of the other clusters in the instance (the "destination clusters"). If a destination cluster is in a different region than the source cluster, you are charged to replicate the write to the destination cluster. The charge is equal to the network egress rate to the destination cluster, multiplied by the amount of data that you wrote to the source cluster. You incur a separate charge for every destination cluster that is in a different region than the source cluster.

For example, let's say you have a 3-cluster instance with clusters in us-east1 (South Carolina), europe-west1 (Belgium), and australia-southeast1 (Sydney). Over the course of a month, if your application writes 5 TB of data to the cluster in us-east1, that 5 TB of data is replicated from us-east1 to europe-west1 at the rate of $0.11 per GB, which is the network cost for replication of 1 TB to 10 TB from the US to Europe. The data is also replicated from us-east1 to australia-southeast1 at the rate of $0.18 per GB, which is the network cost for replication of 1 TB to 10 TB from the US to Australia. In this example, the 30-day replication cost for the 5 TB of data originally written to the cluster in us-east1 is $1,484.80:

(5 TB * 1,024 GB/TB * $0.11 per GB) + (5 TB * 1,024 GB/TB * $0.18 per GB) = $1,484.80

Pricing example: single cluster

Suppose you have a Cloud Bigtable instance that has 1 cluster, with no replication. During a 30-day billing cycle, you use the following Cloud Bigtable resources:

  • 1 production instance in us-central1 (Iowa) with a single cluster, which has 18 nodes during days 1-10 and 25 nodes during days 11-30
  • Average of 30 TB of data stored on SSD drives in us-central1
  • 10 TB of network ingress to us-central1
  • 50 GB of network egress to us-central1
  • 25 GB of network egress to europe-west1

Assuming that you are billed in USD, your Cloud Bigtable bill for the billing cycle is broken down as follows. Additional fees would apply for any other GCP services used during the billing cycle, such as Compute Engine instances.

Cloud Bigtable nodes

Days 1-10

  • 1 cluster * 18 nodes * 10 days * 24 hours/day * $0.65 per node per hour in us-central1: $2,808.00

Days 11-30

  • 1 cluster * 25 nodes * 20 days * 24 hours/day * $0.65 per node per hour in us-central1: $7,800.00

Storage

1 cluster * 30 TB * 1,024 GB/TB * $0.17 per GB in us-central1: $5,222.40

Network

  • 10 TB of ingress to us-central1: No charge
  • 50 GB of egress to us-central1: No charge
  • 25 GB of egress to europe-north1 * $0.12 per GB: $3.00

Monthly total

In this example, the total monthly bill for Cloud Bigtable is $15,833.40.

Pricing example: 2 clusters in the same region

Suppose you have a Cloud Bigtable instance that has 2 clusters, which means that replication is enabled. The clusters are in different zones in the same region. During a 30-day billing cycle, you use the following Cloud Bigtable resources:

  • 1 production instance in us-central1 (Iowa) with 2 clusters; each cluster has 18 nodes during days 1-10 and 25 nodes during days 11-30
  • Average of 30 TB of data stored on SSD drives in us-central1
  • 10 TB of network ingress to us-central1
  • 50 GB of network egress to us-central1
  • 25 GB of network egress to europe-north1

Assuming that you are billed in USD, your Cloud Bigtable bill for the billing cycle is broken down as follows. Additional fees would apply for any other GCP services used during the billing cycle, such as Compute Engine instances.

Cloud Bigtable nodes

Days 1-10

  • 2 clusters * 18 nodes * 10 days * 24 hours/day * $0.65 per node per hour in us-central1: $5,616.00

Days 11-30

  • 2 clusters * 25 nodes * 20 days * 24 hours/day * $0.65 per node per hour in us-central1: $15,600.00

Storage

2 clusters * 30 TB * 1,024 GB/TB * $0.17 per GB in us-central1: $10,444.80

Network

  • 10 TB of ingress to us-central1: No charge
  • 50 GB of egress to us-central1: No charge
  • 25 GB of egress to europe-north1 * $0.12 per GB: $3.00

Monthly total

In this example, the total monthly bill for Cloud Bigtable is $31,663.80.

Pricing example: 2 clusters in different regions

Suppose you have a Cloud Bigtable instance that has 2 clusters, each in a different Cloud Bigtable region. During a 30-day billing cycle, you use the following Cloud Bigtable resources:

  • 1 production instance with 1 cluster in us-central1 (Iowa) and 1 cluster in asia-south1 (Mumbai); each cluster has 18 nodes during days 1-10 and 25 nodes during days 11-30
  • Average of 30 TB of data stored on SSD drives for each cluster
  • 10 TB of network ingress to us-central1
  • 2 TB of network ingress to asia-south1
  • 50 GB of network egress to us-central1
  • 25 GB of network egress to europe-north1
  • 10 TB of writes replicated from us-central1 to asia-south1
  • 2 TB of writes replicated from asia-south1 to us-central1

Assuming that you are billed in USD, your Cloud Bigtable bill for the billing cycle is broken down as follows. Additional fees would apply for any other GCP services used during the billing cycle, such as Compute Engine instances.

Cloud Bigtable nodes

Days 1-10

  • 1 cluster * 18 nodes * 10 days * 24 hours/day * $0.65 per node per hour in us-central1: $2,808.00
  • 1 cluster * 18 nodes * 10 days * 24 hours/day * $0.748 per node per hour in asia-south1: $3,231.36

Days 11-30

  • 1 clusters * 25 nodes * 20 days * 24 hours/day * $0.65 per node per hour in us-central1: $7,800.00
  • 1 clusters * 25 nodes * 20 days * 24 hours/day * $0.748 per node per hour in asia-south1: $8,976.00

Storage

  • 1 cluster * 30 TB * 1,024 GB/TB * $0.17 per GB in us-central1: $5,222.40
  • 1 cluster * 30 TB * 1,024 GB/TB * $0.196 per GB in asia-south1: $6,021.12

Network

  • 10 TB of ingress to us-central1: No charge
  • 2 TB of ingress to asia-south1: No charge
  • 50 GB of egress to us-central1: No charge
  • 25 GB of egress to europe-north1 * $0.12 per GB: $3.00

Replication

  • 10 TB of writes replicated from us-central1 toasia-south1` * 1,024 GB/TB * $0.12 per GB: $1,228.80
  • 2 TB of writes replicated from asia-south1 to us-central1 * 1,024 GB/TB * $0.12 per GB: $245.76

Monthly total

In this example, the total monthly bill for Cloud Bigtable is $35,536.44.

Pricing example: 3 clusters in different regions

Suppose you have a Cloud Bigtable instance that has 3 clusters, each in a different Cloud Bigtable region. During a 30-day billing cycle, you use the following Cloud Bigtable resources:

  • 1 production instance with 1 cluster in us-central1 (Iowa), 1 cluster in asia-south1 (Mumbai), and 1 cluster in europe-west2 (London); each cluster has 15 nodes on every day of the 30-day month
  • Average of 50 TB of data stored on SSD drives for each cluster
  • 10 TB of writes to each cluster; writes are then replicated to the other 2 clusters
  • 25 GB of network egress to asia-northeast1

Assuming that you are billed in USD, your Cloud Bigtable bill for the billing cycle is broken down as follows. Additional fees would apply for any other GCP services used during the billing cycle, such as Compute Engine instances.

Cloud Bigtable nodes

  • 1 cluster * 15 nodes * 30 days * 24 hours/day * $0.65 per node per hour in us-central1: $7,020.00
  • 1 cluster * 15 nodes * 30 days * 24 hours/day * $0.748 per node per hour in asia-south1: $8,078.40
  • 1 cluster * 15 nodes * 30 days * 24 hours/day * $0.78 per node per hour in europe-west2: $8,424.00

Storage

  • 1 cluster * 50 TB * 1,024 GB/TB * $0.17 per GB in us-central1: $8,704.00
  • 1 cluster * 50 TB * 1,024 GB/TB * $0.196 per GB in asia-south1: $10,035.20
  • 1 cluster * 50 TB * 1,024 GB/TB * $0.20 per GB in europe-west2: $10,240.00

Network

  • 10 TB of ingress to us-central1: No charge
  • 10 TB of ingress to asia-south1: No charge
  • 10 TB of ingress to europe-west2: No charge
  • 50 GB of egress to us-central1: No charge
  • 25 GB of egress to asia-northeast1 * $0.12 per GB: $3.00

Replication

  • 10 TB of writes replicated from us-central1 to asia-south1 * 1,024 GB/TB * $0.11 per GB: $1,126.40
  • 10 TB of writes replicated from us-central1 to europe-west2 * 1,024 GB/TB * $0.11 per GB: $1,126.40
  • 10 TB of writes replicated from asia-south1 to us-central1 * 1,024 GB/TB * $0.11 per GB: $1,126.40
  • 10 TB of writes replicated from asia-south1 to europe-west2 * 1,024 GB/TB * $0.11 per GB: $1,126.40
  • 10 TB of writes replicated from europe-west2 to us-central1 * 1,024 GB/TB * $0.0.11 per GB: $1,126.40
  • 10 TB of writes replicated from europe-west2 to asia-south1 * 1,024 GB/TB * $0.0.11 per GB: $1,126.40

Monthly total

In this example, the total monthly bill for Cloud Bigtable is $59,263.00.

Was this page helpful? Let us know how we did:

Send feedback about...

Cloud Bigtable Documentation