Google Cloud Datastream charges for data processed, not for running streams: an idle stream costs nothing. The catch is how "processed" is measured. Google notes that a processed byte is an internal representation of the source data, and for most workloads it is 2 to 5 times larger than the data itself.
CDC prices (USD, November 2026)
Tiered per billing account per month; each price applies only to the GiB inside its tier:
| Monthly CDC volume | Price per GiB |
|---|---|
| 0 – 2,500 GiB | $2.00 |
| 2,500 – 5,000 GiB | $1.50 |
| 5,000 – 10,000 GiB | $1.20 |
| 10,000+ GiB | $0.80 (contact sales beyond 10 TB) |
Backfill
The initial snapshot is billed at a flat per-GiB rate, with the first 500 GiB each month free. Re-running a backfill counts again.
The free tier doesn't cover MySQL
Datastream's perpetual free tier (100 GiB of CDC a month) applies only to AlloyDB and Spanner sources. MySQL pays from the first GiB.
Worked examples (CDC only, 2×–5× processed bytes)
- 5 GiB of row changes a month: 10–25 GiB processed → about $20–$50/month
- 200 GiB a month: 400–1,000 GiB → about $800–$2,000/month
- 1 TiB a month: 2,048–5,120 GiB → about $4,100–$8,900/month after tier discounts
BigQuery storage and the compute that applies changes are billed separately.
Estimate your change volume
Run SHOW BINARY LOGS; on the primary at the same time on two days and add up File_size for the files created in between: roughly one day of changes. Multiply by 30.
Per-GiB vs per-row
Per-GiB pricing grows with row width: wide JSON or text columns cost more per change. Per-row pricing (monthly active rows) doesn't care how wide the row is.
Disclosure: I work on Quayen, which prices MySQL-to-BigQuery CDC per row. Original article with links: quayen.com/docs/google-cloud-datastream-pricing.
Top comments (0)