Skip to content
Calcrivo

Cloud SQL Cost Calculator

Price a Cloud SQL instance from per-vCPU and per-GB rates, then add high availability, read replicas and backups.

Inputs

vCPU
GB
USD/vCPU-hour

Cloud SQL Enterprise for MySQL lists near $0.0413 per vCPU-hour in us-central1.

USD/GB-hour
hours
GB
USD/GB-month
GB
USD/GB-month

Regional HA runs a standby in a second zone and doubles the compute and storage charge.

replicas
%
%

Monthly Cost

$910.07

Compute Charge

$404.71

Data Storage Charge

$170.00

Read Replica Charge

$287.36

Backup Charge

$48.00

High Availability Premium

$287.36

Commitment Discount

0.0%

Annual Cost

$10,920.82

Step by step

  1. Values used

    vCPUs = 4 vCPU; Memory = 16 GB; Price per vCPU-hour = 0.0413 USD/vCPU-hour; Price per GB-hour = 0.0070 USD/GB-hour; Hours in the billing month = 730 hours; Data storage = 500 GB; SSD storage price per GB = 0.1700 USD/GB-month; Backup storage retained = 600 GB; Backup price per GB = 0.0800 USD/GB-month; Enable regional high availability = Yes; Read replicas = 1 replicas; Commitment term = No commitment; 1-year commitment discount = 25 %; 3-year commitment discount = 52 %

  2. Cloud SQL Cost

    monthly = (vCPU × vCPU rate + GB × GB rate) × hours × HA factor × (1 − commitment discount) + storage GB × storage price × HA factor + replicas × (compute + storage) + backup GB × backup price.

  3. Monthly Cost

    = 910.07

  4. Compute Charge

    = 404.71

  5. Data Storage Charge

    = 170.00

  6. Read Replica Charge

    = 287.36

  7. Backup Charge

    = 48.00

  8. High Availability Premium

    = 287.36

How it works

Cloud SQL bills vCPU and memory separately, then multiplies the compute and data-storage lines by two when regional HA is enabled because the standby is a full second copy. Read replicas are billed as their own instances, and committed use discounts apply only to the compute meter — never to storage or backups. HA plus two read replicas quietly turns one instance into four billable machines, so the topology decision dominates the size decision. Check the current per-vCPU, per-GB and storage rates for your edition and region in the Google Cloud pricing calculator before you size a fleet.

Formula

Cloud SQL Cost

monthly = (vCPU × vCPU rate + GB × GB rate) × hours × HA factor × (1 − commitment discount) + storage GB × storage price × HA factor + replicas × (compute + storage) + backup GB × backup price.

HA factor
2 when regional high availability runs a standby in a second zone
commitment discount
Cloud SQL committed use discount, which covers compute only
replicas
Read replicas, each billed like a standalone instance without the HA standby

Frequently Asked Questions

How is Cloud SQL Cost calculated?

monthly = (vCPU × vCPU rate + GB × GB rate) × hours × HA factor × (1 − commitment discount) + storage GB × storage price × HA factor + replicas × (compute + storage) + backup GB × backup price. Cloud SQL bills vCPU and memory separately, then multiplies the compute and data-storage lines by two when regional HA is enabled because the standby is a full second copy. Read replicas are billed as their own instances, and committed use discounts apply only to the compute meter — never to storage or backups.

Why does Cloud SQL Cost matter?

HA plus two read replicas quietly turns one instance into four billable machines, so the topology decision dominates the size decision. Check the current per-vCPU, per-GB and storage rates for your edition and region in the Google Cloud pricing calculator before you size a fleet.

What values do I need to enter?

This calculator takes 14 inputs: vCPUs, Memory, Price per vCPU-hour, Price per GB-hour, Hours in the billing month, Data storage, SSD storage price per GB, Backup storage retained, Backup price per GB, Enable regional high availability, Read replicas, Commitment term, 1-year commitment discount, 3-year commitment discount. The pre-filled defaults are a realistic starting point — replace them with figures from your own environment for a result you can act on.

Does a read replica also need high availability?

Only if it serves traffic you cannot lose. A replica is already a separate copy in its own zone, so most designs run replicas as zonal instances and reserve regional HA for the primary, which halves the replica bill.

You might also need