> ## Documentation Index
> Fetch the complete documentation index at: https://private-7c7dfe99-vortex-format.mintlify.site/llms.txt
> Use this file to discover all available pages before exploring further.

# ClickPipes for CDC

> Overview of billing for Change Data Capture (CDC) ClickPipes

This section outlines the pricing model for Change Data Capture (CDC) connectors in ClickPipes.

<h2 id="cdc-oltp">
  OLTP CDC
</h2>

| Connector        | Feature lifecycle         | Billing status                                                                                                                                                                                                  |
| ---------------- | ------------------------- | --------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
| **Postgres CDC** | General Availability (GA) | Billed according to the listed [pricing dimensions](#pricing-dimensions-oltp).                                                                                                                                  |
| **MySQL CDC**    | Public Beta               | **Free** during Public Beta. Billing will start when the connector is promoted to General Availability (GA) on **September 1st, 2026**, according to the listed [pricing dimensions](#pricing-dimensions-oltp). |
| **MongoDB CDC**  | Public Beta               | **Free** during Public Beta. Billing will start when the connector is promoted to General Availability (GA), according to the listed [pricing dimensions](#pricing-dimensions-oltp).                            |

<h3 id="pricing-dimensions-oltp">
  Pricing dimensions
</h3>

Pricing for OLTP CDC connectors is calculated based on two dimensions: [data volume](#data-volume-oltp) and [compute](#compute-oltp).

<h4 id="data-volume-oltp">
  Data volume
</h4>

The raw, uncompressed bytes read from the database replication stream and ingested into ClickHouse. Pricing depends on the phase of ingestion:

* **Initial load / resync**: In this phase, the connector captures and ingests a consistent snapshot of the tables selected for replication. This happens when a ClickPipe is first created, when a new table is added to an existing ClickPipe, or when there is an irrecoverable error that requires reingesting a consistent snapshot.

* **Continuous Replication (CDC)**: In this phase, the connector captures ongoing changes from the tables selected for replication, such as inserts, updates, and deletes. This happens when the initial load phase is completed and the ClickPipe transitions to a `Running` state.

| Phase                            | Cost        |
| -------------------------------- | ----------- |
| **Initial load / resync**        | \$0.10 / GB |
| **Continuous Replication (CDC)** | \$0.20 / GB |

<h4 id="compute-oltp">
  Compute
</h4>

The compute units provisioned **per service** for CDC ClickPipes, **shared** across all CDC ClickPipes within a service. The compute units provisioned by default depend on the tier of your organization.

| Tier                         | Compute Units (CU)               | Cost          |
| ---------------------------- | -------------------------------- | ------------- |
| **Basic Tier**               | 0.5 CU (1 vCPU, 4GB RAM)/service | \$0.10 / hour |
| **Scale or Enterprise Tier** | 1 CU (2 vCPU, 8 GB RAM)/service  | \$0.20 / hour |

Because compute is shared, this pricing component remains **flat** per service as CDC ClickPipes usage scales. It's possible to provision additional compute units by [scaling the CDC ClickPipes service](https://clickhouse.com/docs/cloud/manage/api/swagger#tag/ClickPipes/operation/clickPipeCdcScalingUpdate), with price scaling linearly.

<h3 id="example-oltp">
  Example
</h3>

<Note>
  This example combines multiple connectors to illustrate the shared-compute pricing model for CDC ClickPipes. Note that [MySQL CDC is free during Public Beta](#cdc-oltp).
</Note>

Consider a service in the **Scale** tier with the following setup:

* 1 **Postgres CDC** ClickPipe replicating 8 tables, with an initial load of 200 GB and 100 GB of changes (CDC) per month.
* 1 **MySQL CDC ClickPipe** replicating 5 tables, with an initial load of 100 GB and 50 GB of changes (CDC) per month.

<h4 id="cost-breakdown-oltp">
  Monthly cost breakdown
</h4>

<h5 id="cost-breakdown-first-month-oltp">
  First month
</h5>

**Initial load** (one-time, charged at the lower rate):

$$(200 + 100) \text{ GB} \times \$0.10/\text{GB} = \$30$$

**Continuous replication (CDC)**:

$$(100 + 50) \text{ GB} \times \$0.20/\text{GB} = \$30$$

**Compute** (shared across both ClickPipes, charged per service):

$$1 \text{ compute unit} \times \$0.20/\text{hr} \times 730 \text{ hours} = \$146$$

**First month total**:

$$\$30 \text{ (initial load)} + \$30 \text{ (CDC)} + \$146 \text{ (compute)} = \$206$$

<h5 id="cost-breakdown-following-months-oltp">
  Following months
</h5>

$$\$30 \text{ (CDC)} + \$146 \text{ (compute)} = \$176 \text{ per month}$$

For CDC ClickPipes, compute is a **fixed cost shared across all CDC ClickPipes** in a service, regardless of the connector type. In this example, adding a MySQL ClickPipe contributed only the cost for **ingested data**, not additional compute — this means your bill grows with the data you ingest rather than the number of ClickPipes you run.

To avoid performance bottlenecks and efficiently reuse the provisioned compute within a service, we recommend replicating all tables from the same upstream database instance via a single ClickPipe until there is a valid reason to split the workload into multiple ClickPipes or scale up.

<h2 id="cdc-dwh">
  Data warehousing CDC
</h2>

Pricing for data warehousing CDC connectors is under development.

| Connector        | Feature lifecycle | Billing status                   |
| ---------------- | ----------------- | -------------------------------- |
| **BigQuery CDC** | Private Preview   | **Free** during Private Preview. |

<h2 id="faq-cdc">
  CDC ClickPipes FAQ
</h2>

<Accordion title="Can I use my ClickHouse Cloud credits for CDC ClickPipes?">
  Yes. ClickPipes pricing is part of the unified ClickHouse Cloud pricing. Any
  platform credits you have will automatically apply to ClickPipes usage as well.
</Accordion>

<Accordion title="How much additional cost should I expect from CDC ClickPipes in my existing monthly ClickHouse Cloud spend?">
  Cost impact varies widely based on your use case, data volume, and organization tier. Most customers see an increase of **5–25%** relative to their baseline ClickHouse Cloud monthly spend, though lower-spend services can exceed this. It's important to note that cost for CDC ClickPipes scales very efficiently: compute is shared across all CDC ClickPipes in the same service, so adding new ClickPipes adds only marginal cost based on ingested data volume.

  For CDC ClickPipes connectors marked as **free** under `Billing Status`, you can estimate future costs based on the data volume metrics provided in the ClickPipes UI (**Metrics** > **CDC bytes** and **Initial load bytes**) and via ClickHouse Cloud's [Prometheus-compatible endpoint](/integrations/clickpipes/monitoring).
</Accordion>

<Accordion title="Where can I see CDC ClickPipes costs in my ClickHouse Cloud bill?">
  CDC ClickPipes costs are listed as separate line items in your ClickHouse Cloud bill with an `Entity Type` of `clickpipe`, broken down by pricing dimension (`ClickPipe Data Transfer ($)`, `ClickPipe Compute ($)`, `ClickPipe Initial Load and Resyncs ($)`).

  For billing reconciliation, you can monitor real-time data volume metrics in the ClickPipes UI (**Metrics** > **CDC bytes** and **Initial load bytes**), or consume these metrics into your existing monitoring stack using ClickHouse Cloud's [Prometheus-compatible endpoint](/integrations/clickpipes/monitoring).
</Accordion>

<Accordion title="Do CDC ClickPipes prevent my ClickHouse Cloud service from idling?">
  No, but due to the continuous nature of CDC, the service is likely to be woken on the configured sync interval. CDC ClickPipes wakes up the service on the configured sync interval **if** there is data to ingest, but the service can otherwise idle normally. If there is no data to ingest on a particular sync run, CDC ClickPipes will **not** wake up the service.
</Accordion>

<Accordion title="Will I be charged if I pause my CDC ClickPipe?">
  Yes. You will be charged for the **compute** resources that are provisioned and shared across all CDC ClickPipes within a service. Data volume charges do not apply while a pipe is paused, since no data is ingested.

  <Note>
    Pausing a CDC ClickPipe for long periods of time is **not recommended**, since it can lead to an irrecoverable state as a result of replication log expiration and/or affect the health of your upstream data source.
  </Note>
</Accordion>

<Accordion title="Can I scale the compute allocated for CDC ClickPipes in my service?">
  The compute resources provisioned by default for CDC ClickPipes are optimized to handle most workloads without the need to scale. If you notice a resource utilization bottleneck, you can [scale the CDC ClickPipes service](https://clickhouse.com/docs/cloud/manage/api/swagger#tag/ClickPipes/operation/clickPipeCdcScalingUpdate). The cost for compute scales linearly with the provisioned compute units.
</Accordion>