Learn
Google Cloud Datastream pricing explained, with examples
How Datastream bills MySQL CDC and backfill per GiB processed, its 2,500, 5,000 and 10,000 GiB tiers, the free backfill allowance, and worked monthly examples.
Google Cloud Datastream charges for the data it processes, 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
Change data capture is tiered per billing account per month, and each tier's price applies only to the GiB inside it (prices in USD, as listed in November 2026):
- 0 to 2,500 GiB: $2.00 per GiB
- 2,500 to 5,000 GiB: $1.50 per GiB
- 5,000 to 10,000 GiB: $1.20 per GiB
- Above 10,000 GiB: $0.80 per GiB (contact sales beyond 10 TB)
Backfill (the initial copy)
Backfill, the historical snapshot of each table, is billed at a flat rate per GiB, and the first 500 GiB each month are free. Re-running a backfill after a schema problem or a broken stream counts again.
The free tier doesn't cover MySQL
Datastream's perpetual free tier (100 GiB of CDC a month) applies only to streams from AlloyDB and Spanner to BigQuery. MySQL, PostgreSQL, Oracle and SQL Server sources pay from the first GiB.
Worked examples
Estimates for CDC only, using Google's 2× to 5× range for processed bytes:
- Small app, 5 GiB of row changes a month: 10 to 25 GiB processed, about $20 to $50 a month.
- Busy app, 200 GiB of changes a month: 400 to 1,000 GiB processed, about $800 to $2,000 a month.
- Large app, 1 TiB of changes a month: 2,048 to 5,120 GiB processed, about $4,100 to $8,900 a month after the tier discounts.
BigQuery bills separately for storing the tables and for the compute that applies changes to them, whichever replication tool you use. See keeping BigQuery costs low.
Estimating your change volume
The binary log is a good proxy for how much a CDC tool will read. 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; that is roughly one day of changes. Multiply by 30 for a month.
Per-GiB vs per-row pricing
Per-GiB pricing grows with row width: a table with large JSON or text columns costs more per change than a narrow one. Quayen prices by monthly active rows instead (distinct rows changed in a month), with initial copies and re-copies free; see pricing and Quayen vs Google Cloud Datastream.