Understand CockroachDB Cloud Costs

For CockroachDB Basic, compute cost is usage-based through its consumption of Request Units.

Standard clusters have provisioned compute capacity where customers set a maximum processing capacity for their cluster, measured in vCPUs. This capacity represents the peak processing power the cluster can handle at any given time.

A cluster’s compute charges are based on the cluster’s provisioned capacity in vCPU-hours, with rates that depend on the cluster’s cloud provider and regions. Billing is based on the capacity reserved, not the actual usage. Charges are accumulated throughout the month to determine the total monthly compute charges.

In a multi-region cluster, the price of the most expensive region is applied to the entire cluster’s compute capacity.

For example, consider a three-region Multi-Region GCP cluster provisioned in Iowa (us-central1), St. Ghislain (europe-central1) and Jurong West (asia-southeast1) with 32 vCPUs provisioned compute capacity. The compute cost for the cluster is calculated by multiplying the number of vCPUs provisioned by the highest per vCPU-hour rate amongst Iowa ($0.100), St. Ghislain ($0.113) and Jurong West ($0.121) regions: (32 vCPU * $0.121), which equals $3.872 per hour.

Note: These prices are intended as examples only. For the latest pricing, refer to CockroachDB Pricing.

For an Advanced cluster, each node is provisioned with dedicated compute resources. Users can customize the number of vCPUs per node, which applies to all nodes in the cluster. Compute costs are based on the vCPUs provisioned for each node, with rates depending on the cloud provider, region, and whether a security add-on is enabled.

Compute charges are calculated by multiplying the hourly rate of the provisioned compute by the number of nodes in the cluster. Hourly charges are accumulated throughout the month to determine the total monthly charge.

For example, consider a GCP cluster provisioned in Oregon (us-west1). The cluster consists of three nodes, each with 8vCPU, 32 GiB of RAM. The compute cost for the cluster is determined by multiplying the hourly rate of 8vCPU, 32GiB RAM machine type ($1.062) and the total number of nodes (3), which equals $3.186 per hour.

Note: These prices are intended as examples only. For the latest pricing, refer to CockroachDB Pricing.

IOPS are included as part of request units (RUs).

IOPS are included in storage costs.

For Advanced clusters on AWS, each node will incur charges for the provisioned IOPS, an amount determined based on the allocated storage size (in GiB).

For CockroachDB Basic clusters, storage is automatically provisioned on demand, eliminating the need for manual management. Costs are based on actual usage and adjust dynamically as data is added or removed, starting from zero.

Storage is billed hourly, with rates depending on the cloud provider and the region where the cluster is hosted. Basic plan clusters charge for storage per GiB-hour. These charges are accumulated throughout the month to determine the total monthly storage charges.

For CockroachDB Standard clusters, storage is automatically provisioned on demand, eliminating the need for manual management. Costs are based on actual usage and adjust dynamically as data is added or removed, starting from zero.

Storage is billed hourly, with rates specific to each cloud provider and the region where the cluster is hosted. CockroachDB Cloud measures storage in GiB-hour. These charges are accumulated throughout the month to determine the total monthly storage charges.

A CockroachDB Standard cluster maintains a minimum of three replicas of your data. The second and third replicas are included, with no additional storage charge. If you add further replicas, each will incur a storage cost equal to that of the first replica—the logical database size.

Each Advanced cluster is provisioned with dedicated storage, and users can configure the per-node storage size when setting up their cluster. This storage setting applies to all nodes in the cluster. The storage is billed hourly, with the rate depending on the cloud provider, the region where the cluster is hosted, and whether the Advanced security add-on is enabled. Storage costs are independent of other resources, meaning you can adjust your cluster's storage capacity without altering its compute capacity. For guidance on provisioning compute and storage, refer to Plan Your Cluster.

• For AWS clusters: Storage charge (per hour) is calculated by multiplying the storage size (in GiB) by the per GiB-hour rate for storage, plus any additional charges for IOPS.
  
• For GCP and Azure clusters: Node storage charge (per hour) is determined by multiplying the storage size (in GiB) by the per GiB-hour rate, without additional IOPS fees.

These charges are accumulated throughout the month to determine the total monthly storage charges.

For example, consider a GCP cluster provisioned in Oregon (us-west1). The cluster consists of three nodes, each with 75 GiB of storage. The storage cost for the cluster is determined by multiplying the storage size (75 GiB) by the storage rate ($0.0010338 per GiB) per node. The total storage cost is then calculated by multiplying this figure by the number of nodes: (75 GiB * $0.0010338) * 3, which equals $0.232605 per hour.

Note: These prices are intended as examples only. For the latest pricing, refer to CockroachDB Pricing.

Backups on Basic clusters are included in the Request Unit costs. Managed backups occur daily and are not configurable.

Managed Backups are charged per-GiB storage rates that vary per cloud provider, region, and backup frequency (daily vs. more than daily). The per-GiB unit prices are tiered, based on the amount of backup data stored: Less than 5 GiB-Month, 5 to 100 GiB-Month, 100 to 500 GiB-Month, 500 to 1000 GiB-Month, or 1000 GiB-Month and higher.

Self-Managed Backups to your own object storage are charged a per-GiB fee for the data transferred. This option provides an advanced backup scheduler and additional control over backup storage placement.

For further details, refer to CockroachDB Cloud Pricing.

Managed Backups are charged per-GiB storage rates that vary per cloud provider, region, backup frequency (daily vs. more than daily), and whether the Advanced security add-on is enabled. The per-GiB unit prices are tiered, based on the amount of backup data stored: Less than 5 GiB-Month, 5 to 100 GiB-Month, 100 to 500 GiB-Month, 500 to 1000 GiB-Month, or 1000 GiB-Month and higher.

Self-Managed Backups to your own object storage are charged a per-GiB fee for the data transferred. The rate varies depending on whether the Advanced security add-on is enabled. Self-Managed Backups offer additional control over backup storage placement, and an advanced backup scheduler.

For further details, refer to CockroachDB Cloud Pricing.

For CockroachDB Basic, data transfer is included in the Request Unit price.

For CockroachDB Standard and Advanced, CockroachDB Cloud bills directly to customers based on their usage with a zero-dollar rate during the preview period.

The usage data is based on the volume of data moved (per GiB) and the cloud provider’s identified data transfer type, which CockroachDB categorizes as Same-region data transfer, Cross-Region data transfer, or Public Internet data transfer. Each category is reflected as a line item on your invoice. Within each data transfer category, for a given Cloud provider, rates are consistent across plans: CockroachDB Standard, Advanced, and Advanced with security add-on enabled.

Cloud providers may vary in how they calculate each category and define each region. We recommend consulting the provider’s documentation for details (i.e. AWS, GCP, or Azure).

Same-region

There are no charges for same-region data transfer between CockroachDB cluster nodes. Data egressing the cluster to endpoints in the same region for backups or changefeeds, or using private connectivity, is charged the cloud provider's list price for same-region data transfer.

Cross-region

When data moves between CockroachDB nodes that are in different regions, or from a CockroachDB node to another endpoint in a different region, it is metered as cross-region data transfer.

Cross-region data transfer includes:

• Data transfer required to support queries that involve lookups on nodes in another region.
  
• CockroachDB replication across nodes that are in different regions.
  
• Data egress from the CockroachDB Cloud cluster via supported private connectivity services to a private endpoint in another region.
  
• Managed backup and Self-managed backup data transfer to another region.
  
• Change Data Capture (changefeed) data transfer to another region.

Customers are charged the cloud service provider’s (CSP) list price for metered cross-region data transfer.

Typically, data transfer costs across regions are higher than data transfer costs across AZs (data centers) in a single region.

Public internet

This is the usage for any data leaving CockroachDB such as SQL data being sent to clients, or logs and metrics exported to third-party tools.

For CockroachDB Standard and Advanced, CockroachDB Cloud bills directly to customers based on their usage with a zero-dollar rate during the preview period.

The usage data is based on the volume of data moved (per GiB) and the cloud provider’s identified data transfer type, which CockroachDB categorizes as Same-region data transfer, Cross-Region data transfer, or Public Internet data transfer. Each category is reflected as a line item on your invoice. Within each data transfer category, for a given Cloud provider, rates are consistent across plans: CockroachDB Standard, Advanced, and Advanced with security add-on enabled.

Cloud providers may vary in how they calculate each category and define each region. We recommend consulting the provider’s documentation for details (i.e. AWS, GCP, or Azure).

Same-region

There are no charges for same-region data transfer between CockroachDB cluster nodes. Data egressing the cluster to endpoints in the same region for backups or changefeeds, or using private connectivity, is charged the cloud provider's list price for same-region data transfer.

Cross-region

When data moves between CockroachDB nodes that are in different regions, or from a CockroachDB node to another endpoint in a different region, it is metered as cross-region data transfer.

Cross-region data transfer includes:

• Data transfer required to support queries that involve lookups on nodes in another region.
  
• CockroachDB replication across nodes that are in different regions.
  
• Data egress from the CockroachDB Cloud cluster via supported private connectivity services to a private endpoint in another region.
  
• Managed backup and Self-managed backup data transfer to another region.
  
• Change Data Capture (changefeed) data transfer to another region.

Customers are charged the cloud service provider’s (CSP) list price for metered cross-region data transfer.

Typically, data transfer costs across regions are higher than data transfer costs across AZs (data centers) in a single region.

Public internet

This is the usage for any data leaving CockroachDB such as SQL data being sent to clients, or logs and metrics exported to third-party tools.

In CockroachDB Basic, CDC cost is usage-based via Request Units.

In CockroachDB Standard, CDC is billed monthly based on usage, determined by the total GiB-Month watched across all of a cluster’s changefeeds. The per-GiB unit price is tiered, based on the total watched: Less than 5 GiB-Month, 5 to 100 GiB-Month, 100 to 250 GiB-Month, 250 to 500 GiB-Month, or 500 GiB-Month and higher.

In CockroachDB Advanced, CDC is billed monthly based on usage, determined by the total GiB-Month watched across all of a cluster’s changefeeds and whether the Advanced security add-on is enabled. The per-GiB unit price is tiered, based on the total watched: Less than 5 GiB-Month, 5 to 100 GiB-Month, 100 to 250 GiB-Month, 250 to 500 GiB-Month, or 500 GiB-Month and higher.