From f39287a76d87be3c365669497da4138521ed5238 Mon Sep 17 00:00:00 2001 From: morsapaes Date: Sun, 21 Sep 2025 14:45:06 +0200 Subject: [PATCH 1/9] Delete original file --- .../03_billing/03_clickpipes_billing.md | 263 ------------------ 1 file changed, 263 deletions(-) delete mode 100644 docs/cloud/reference/03_billing/03_clickpipes_billing.md diff --git a/docs/cloud/reference/03_billing/03_clickpipes_billing.md b/docs/cloud/reference/03_billing/03_clickpipes_billing.md deleted file mode 100644 index 10391a25229..00000000000 --- a/docs/cloud/reference/03_billing/03_clickpipes_billing.md +++ /dev/null @@ -1,263 +0,0 @@ ---- -sidebar_label: 'ClickPipes' -slug: /cloud/reference/billing/clickpipes -title: 'ClickPipes billing' -description: 'Overview of ClickPipes billing' -doc_type: 'guide' ---- - -import ClickPipesFAQ from '../../_snippets/_clickpipes_faq.md' - -## ClickPipes for streaming and object storage {#clickpipes-for-streaming-object-storage} - -This section outlines the pricing model of ClickPipes for streaming and object storage. - -### What does the ClickPipes pricing structure look like? {#what-does-the-clickpipes-pricing-structure-look-like} - -It consists of two dimensions: - -- **Compute**: Price **per unit per hour**. - Compute represents the cost of running the ClickPipes replica pods whether they actively ingest data or not. - It applies to all ClickPipes types. -- **Ingested data**: Price **per GB**. - The ingested data rate applies to all streaming ClickPipes - (Kafka, Confluent, Amazon MSK, Amazon Kinesis, Redpanda, WarpStream, Azure Event Hubs) - for the data transferred via the replica pods. The ingested data size (GB) is charged based on bytes received from the source (uncompressed or compressed). - -### What are ClickPipes replicas? {#what-are-clickpipes-replicas} - -ClickPipes ingests data from remote data sources via a dedicated infrastructure -that runs and scales independently of the ClickHouse Cloud service. -For this reason, it uses dedicated compute replicas. - -### What is the default number of replicas and their size? {#what-is-the-default-number-of-replicas-and-their-size} - -Each ClickPipe defaults to 1 replica that is provided with 512 MiB of RAM and 0.125 vCPU (XS). -This corresponds to **0.0625** ClickHouse compute units (1 unit = 8 GiB RAM, 2 vCPUs). - -### What are the ClickPipes public prices? {#what-are-the-clickpipes-public-prices} - -- Compute: \$0.20 per unit per hour (\$0.0125 per replica per hour for the default replica size) -- Ingested data: \$0.04 per GB - -The price for the Compute dimension depends on the **number** and **size** of replica(s) in a ClickPipe. The default replica size can be adjusted using vertical scaling, and each replica size is priced as follows: - -| Replica Size | Compute Units | RAM | vCPU | Price per Hour | -|----------------------------|---------------|---------|--------|----------------| -| Extra Small (XS) (default) | 0.0625 | 512 MiB | 0.125. | $0.0125 | -| Small (S) | 0.125 | 1 GiB | 0.25 | $0.025 | -| Medium (M) | 0.25 | 2 GiB | 0.5 | $0.05 | -| Large (L) | 0.5 | 4 GiB | 1.0 | $0.10 | -| Extra Large (XL) | 1.0 | 8 GiB | 2.0 | $0.20 | - -### How does it look in an illustrative example? {#how-does-it-look-in-an-illustrative-example} - -The following examples assume a single M-sized replica, unless explicitly mentioned. - - - - - - - - - - - - - - - - - - - - - - -
100 GB over 24h1 TB over 24h10 TB over 24h
Streaming ClickPipe(0.25 x 0.20 x 24) + (0.04 x 100) = \$5.20(0.25 x 0.20 x 24) + (0.04 x 1000) = \$41.20With 4 replicas:

(0.25 x 0.20 x 24 x 4) + (0.04 x 10000) = \$404.80
Object Storage ClickPipe $^*$(0.25 x 0.20 x 24) = \$1.20(0.25 x 0.20 x 24) = \$1.20(0.25 x 0.20 x 24) = \$1.20
- -$^1$ _Only ClickPipes compute for orchestration, -effective data transfer is assumed by the underlying Clickhouse Service_ - -## ClickPipes for PostgreSQL CDC {#clickpipes-for-postgresql-cdc} - -This section outlines the pricing model for the Postgres Change Data Capture (CDC) -connector in ClickPipes. In designing this model, the goal was to keep pricing -highly competitive while staying true to our core vision: - -> Making it seamless and -affordable for customers to move data from Postgres to ClickHouse for -real-time analytics. - -The connector is over **5x more cost-effective** than external -ETL tools and similar features in other database platforms. - -:::note -Pricing started being metered in monthly bills on **September 1st, 2025** -for all customers (both existing and new) using Postgres CDC ClickPipes. -::: - -### Pricing dimensions {#pricing-dimensions} - -There are two main dimensions to pricing: - -1. **Ingested Data**: The raw, uncompressed bytes coming from Postgres and - ingested into ClickHouse. -2. **Compute**: The compute units provisioned per service manage multiple - Postgres CDC ClickPipes and are separate from the compute units used by the - ClickHouse Cloud service. This additional compute is dedicated specifically - to Postgres CDC ClickPipes. Compute is billed at the service level, not per - individual pipe. Each compute unit includes 2 vCPUs and 8 GB of RAM. - -### Ingested data {#ingested-data} - -The Postgres CDC connector operates in two main phases: - -- **Initial load / resync**: This captures a full snapshot of Postgres tables - and occurs when a pipe is first created or re-synced. -- **Continuous Replication (CDC)**: Ongoing replication of changes—such as inserts, - updates, deletes, and schema changes—from Postgres to ClickHouse. - -In most use cases, continuous replication accounts for over 90% of a ClickPipe -life cycle. Because initial loads involve transferring a large volume of data all -at once, we offer a lower rate for that phase. - -| Phase | Cost | -|----------------------------------|--------------| -| **Initial load / resync** | $0.10 per GB | -| **Continuous Replication (CDC)** | $0.20 per GB | - -### Compute {#compute} - -This dimension covers the compute units provisioned per service just for Postgres -ClickPipes. Compute is shared across all Postgres pipes within a service. **It -is provisioned when the first Postgres pipe is created and deallocated when no -Postgres CDC pipes remain**. The amount of compute provisioned depends on your -organization's tier: - -| Tier | Cost | -|------------------------------|-----------------------------------------------| -| **Basic Tier** | 0.5 compute unit per service — $0.10 per hour | -| **Scale or Enterprise Tier** | 1 compute unit per service — $0.20 per hour | - -### Example {#example} - -Let's say your service is in Scale tier and has the following setup: - -- 2 Postgres ClickPipes running continuous replication -- Each pipe ingests 500 GB of data changes (CDC) per month -- When the first pipe is kicked off, the service provisions **1 compute unit under the Scale Tier** for Postgres CDC - -#### Monthly cost breakdown {#cost-breakdown} - -**Ingested Data (CDC)**: - -$$ 2 \text{ pipes} \times 500 \text{ GB} = 1,000 \text{ GB per month} $$ - -$$ 1,000 \text{ GB} \times \$0.20/\text{GB} = \$200 $$ - -**Compute**: - -$$1 \text{ compute unit} \times \$0.20/\text{hr} \times 730 \text{ hours (approximate month)} = \$146$$ - -:::note -Compute is shared across both pipes -::: - -**Total Monthly Cost**: - -$$\$200 \text{ (ingest)} + \$146 \text{ (compute)} = \$346$$ - -# ClickPipes pricing FAQ {#clickpipes-pricing-faq} - -Below, you will find frequently asked questions about CDC ClickPipes and streaming -and object-based storage ClickPipes. - -## FAQ for Postgres CDC ClickPipes {#faq-postgres-cdc-clickpipe} - -
- -Is the ingested data measured in pricing based on compressed or uncompressed size? - -The ingested data is measured as _uncompressed data_ coming from Postgres—both -during the initial load and CDC (via the replication slot). Postgres does not -compress data during transit by default, and ClickPipe processes the raw, -uncompressed bytes. - -
- -
- -When will Postgres CDC pricing start appearing on my bills? - -Postgres CDC ClickPipes pricing began appearing on monthly bills starting -**September 1st, 2025**, for all customers (both existing and new). - -
- -
- -Will I be charged if I pause my pipes? - -No data ingestion charges apply while a pipe is paused, since no data is moved. -However, compute charges still apply—either 0.5 or 1 compute unit—based on your -organization's tier. This is a fixed service-level cost and applies across all -pipes within that service. - -
- -
- -How can I estimate my pricing? - -The Overview page in ClickPipes provides metrics for both initial load/resync and -CDC data volumes. You can estimate your Postgres CDC costs using these metrics -in conjunction with the ClickPipes pricing. - -
- -
- -Can I scale the compute allocated for Postgres CDC in my service? - -By default, compute scaling is not user-configurable. The provisioned resources -are optimized to handle most customer workloads optimally. If your use case -requires more or less compute, please open a support ticket so we can evaluate -your request. - -
- -
- -What is the pricing granularity? - -- **Compute**: Billed per hour. Partial hours are rounded up to the next hour. -- **Ingested Data**: Measured and billed per gigabyte (GB) of uncompressed data. - -
- -
- -Can I use my ClickHouse Cloud credits for Postgres CDC via 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. - -
- -
- -How much additional cost should I expect from Postgres CDC ClickPipes in my existing monthly ClickHouse Cloud spend? - -The cost varies based on your use case, data volume, and organization tier. -That said, most existing customers see an increase of **0–15%** relative to their -existing monthly ClickHouse Cloud spend post trial. Actual costs may vary -depending on your workload—some workloads involve high data volumes with -lesser processing, while others require more processing with less data. - -
- -## FAQ for streaming and object storage ClickPipes {#faq-streaming-and-object-storage} - - \ No newline at end of file From 4ec7f4380ba49b3737f3deb733158906b5fe108e Mon Sep 17 00:00:00 2001 From: morsapaes Date: Sun, 21 Sep 2025 15:01:43 +0200 Subject: [PATCH 2/9] Fix typo --- docs/cloud/reference/03_billing/02_marketplace/index.md | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) diff --git a/docs/cloud/reference/03_billing/02_marketplace/index.md b/docs/cloud/reference/03_billing/02_marketplace/index.md index 4d5dc5d88c0..b6261a0e0a0 100644 --- a/docs/cloud/reference/03_billing/02_marketplace/index.md +++ b/docs/cloud/reference/03_billing/02_marketplace/index.md @@ -1,7 +1,7 @@ --- slug: /cloud/manage/marketplace/ -title: 'Market Place' -description: 'Market Place Table of Contents page' +title: 'Marketplace' +description: 'Marketplace Table of Contents page' keywords: ['Marketplace Billing', 'AWS', 'GCP'] doc_type: 'landing-page' --- From c8eba39df2143258ca63cfc1e4f50b75bd5e6f3b Mon Sep 17 00:00:00 2001 From: morsapaes Date: Sun, 21 Sep 2025 15:04:40 +0200 Subject: [PATCH 3/9] Add new files --- ...kpipes_for_streaming_and_object_storage.md | 78 +++++++++++++++ .../03_clickpipes/03_2_clickpipes_for_cdc.md | 98 +++++++++++++++++++ 2 files changed, 176 insertions(+) create mode 100644 docs/cloud/reference/03_billing/03_clickpipes/03_1_clickpipes_for_streaming_and_object_storage.md create mode 100644 docs/cloud/reference/03_billing/03_clickpipes/03_2_clickpipes_for_cdc.md diff --git a/docs/cloud/reference/03_billing/03_clickpipes/03_1_clickpipes_for_streaming_and_object_storage.md b/docs/cloud/reference/03_billing/03_clickpipes/03_1_clickpipes_for_streaming_and_object_storage.md new file mode 100644 index 00000000000..db6776dc4d6 --- /dev/null +++ b/docs/cloud/reference/03_billing/03_clickpipes/03_1_clickpipes_for_streaming_and_object_storage.md @@ -0,0 +1,78 @@ +--- +sidebar_label: 'ClickPipes - streaming and object storage' +slug: /cloud/reference/billing/clickpipes/streaming-and-object-storage +title: 'ClickPipes for streaming and object storage' +description: 'Overview of billing for streaming and object storage ClickPipes' +--- + +# ClickPipes for streaming and object storage {#clickpipes-for-streaming-object-storage} + +This section outlines the pricing model of ClickPipes for streaming and object storage. + +## What does the ClickPipes pricing structure look like? {#what-does-the-clickpipes-pricing-structure-look-like} + +It consists of two dimensions: + +- **Compute**: Price **per unit per hour**. + Compute represents the cost of running the ClickPipes replica pods whether they actively ingest data or not. + It applies to all ClickPipes types. +- **Ingested data**: Price **per GB**. + The ingested data rate applies to all streaming ClickPipes + (Kafka, Confluent, Amazon MSK, Amazon Kinesis, Redpanda, WarpStream, Azure Event Hubs) + for the data transferred via the replica pods. The ingested data size (GB) is charged based on bytes received from the source (uncompressed or compressed). + +## What are ClickPipes replicas? {#what-are-clickpipes-replicas} + +ClickPipes ingests data from remote data sources via a dedicated infrastructure +that runs and scales independently of the ClickHouse Cloud service. +For this reason, it uses dedicated compute replicas. + +## What is the default number of replicas and their size? {#what-is-the-default-number-of-replicas-and-their-size} + +Each ClickPipe defaults to 1 replica that is provided with 512 MiB of RAM and 0.125 vCPU (XS). +This corresponds to **0.0625** ClickHouse compute units (1 unit = 8 GiB RAM, 2 vCPUs). + +## What are the ClickPipes public prices? {#what-are-the-clickpipes-public-prices} + +- Compute: \$0.20 per unit per hour (\$0.0125 per replica per hour for the default replica size) +- Ingested data: \$0.04 per GB + +The price for the Compute dimension depends on the **number** and **size** of replica(s) in a ClickPipe. The default replica size can be adjusted using vertical scaling, and each replica size is priced as follows: + +| Replica Size | Compute Units | RAM | vCPU | Price per Hour | +|----------------------------|---------------|---------|--------|----------------| +| Extra Small (XS) (default) | 0.0625 | 512 MiB | 0.125. | $0.0125 | +| Small (S) | 0.125 | 1 GiB | 0.25 | $0.025 | +| Medium (M) | 0.25 | 2 GiB | 0.5 | $0.05 | +| Large (L) | 0.5 | 4 GiB | 1.0 | $0.10 | +| Extra Large (XL) | 1.0 | 8 GiB | 2.0 | $0.20 | + +## How does it look in an illustrative example? {#how-does-it-look-in-an-illustrative-example} + +The following examples assume a single M-sized replica, unless explicitly mentioned. + + + + + + + + + + + + + + + + + + + + + + +
100 GB over 24h1 TB over 24h10 TB over 24h
Streaming ClickPipe(0.25 x 0.20 x 24) + (0.04 x 100) = \$5.20(0.25 x 0.20 x 24) + (0.04 x 1000) = \$41.20With 4 replicas:

(0.25 x 0.20 x 24 x 4) + (0.04 x 10000) = \$404.80
Object Storage ClickPipe $^*$(0.25 x 0.20 x 24) = \$1.20(0.25 x 0.20 x 24) = \$1.20(0.25 x 0.20 x 24) = \$1.20
+ +$^1$ _Only ClickPipes compute for orchestration, +effective data transfer is assumed by the underlying Clickhouse Service_ \ No newline at end of file diff --git a/docs/cloud/reference/03_billing/03_clickpipes/03_2_clickpipes_for_cdc.md b/docs/cloud/reference/03_billing/03_clickpipes/03_2_clickpipes_for_cdc.md new file mode 100644 index 00000000000..ea2b5dd11af --- /dev/null +++ b/docs/cloud/reference/03_billing/03_clickpipes/03_2_clickpipes_for_cdc.md @@ -0,0 +1,98 @@ +--- +sidebar_label: 'ClickPipes - PostgreSQL CDC' +slug: /cloud/reference/billing/clickpipes/postgres-cdc +title: 'ClickPipes for PostgreSQL CDC' +description: 'Overview of billing for PostgreSQL CDC ClickPipes' +--- + +# ClickPipes for PostgreSQL CDC {#clickpipes-for-postgresql-cdc} + +This section outlines the pricing model for our Postgres Change Data Capture (CDC) +connector in ClickPipes. In designing this model, our goal was to keep pricing +highly competitive while staying true to our core vision: + +> Making it seamless and +affordable for customers to move data from Postgres to ClickHouse for +real-time analytics. + +The connector is over **5x more cost-effective** than external +ETL tools and similar features in other database platforms. + +:::note +Pricing will start being metered in monthly bills beginning **September 1st, 2025,** +for all customers (both existing and new) using Postgres CDC ClickPipes. Until +then, usage is free. Customers have a 3-month window starting May 29 (GA announcement) +to review and optimize their costs if needed, although we expect most will not need +to make any changes. +::: + +## Pricing dimensions {#pricing-dimensions} + +There are two main dimensions to pricing: + +1. **Ingested Data**: The raw, uncompressed bytes coming from Postgres and + ingested into ClickHouse. +2. **Compute**: The compute units provisioned per service manage multiple + Postgres CDC ClickPipes and are separate from the compute units used by the + ClickHouse Cloud service. This additional compute is dedicated specifically + to Postgres CDC ClickPipes. Compute is billed at the service level, not per + individual pipe. Each compute unit includes 2 vCPUs and 8 GB of RAM. + +## Ingested data {#ingested-data} + +The Postgres CDC connector operates in two main phases: + +- **Initial load / resync**: This captures a full snapshot of Postgres tables + and occurs when a pipe is first created or re-synced. +- **Continuous Replication (CDC)**: Ongoing replication of changes—such as inserts, + updates, deletes, and schema changes—from Postgres to ClickHouse. + +In most use cases, continuous replication accounts for over 90% of a ClickPipe +life cycle. Because initial loads involve transferring a large volume of data all +at once, we offer a lower rate for that phase. + +| Phase | Cost | +|----------------------------------|--------------| +| **Initial load / resync** | $0.10 per GB | +| **Continuous Replication (CDC)** | $0.20 per GB | + +## Compute {#compute} + +This dimension covers the compute units provisioned per service just for Postgres +ClickPipes. Compute is shared across all Postgres pipes within a service. **It +is provisioned when the first Postgres pipe is created and deallocated when no +Postgres CDC pipes remain**. The amount of compute provisioned depends on your +organization's tier: + +| Tier | Cost | +|------------------------------|-----------------------------------------------| +| **Basic Tier** | 0.5 compute unit per service — $0.10 per hour | +| **Scale or Enterprise Tier** | 1 compute unit per service — $0.20 per hour | + +## Example {#example} + +Let's say your service is in Scale tier and has the following setup: + +- 2 Postgres ClickPipes running continuous replication +- Each pipe ingests 500 GB of data changes (CDC) per month +- When the first pipe is kicked off, the service provisions **1 compute unit under the Scale Tier** for Postgres CDC + +### Monthly cost breakdown {#cost-breakdown} + +**Ingested Data (CDC)**: + +$$ 2 \text{ pipes} \times 500 \text{ GB} = 1,000 \text{ GB per month} $$ + +$$ 1,000 \text{ GB} \times \$0.20/\text{GB} = \$200 $$ + +**Compute**: + +$$1 \text{ compute unit} \times \$0.20/\text{hr} \times 730 \text{ hours (approximate month)} = \$146$$ + +:::note +Compute is shared across both pipes +::: + +**Total Monthly Cost**: + +$$\$200 \text{ (ingest)} + \$146 \text{ (compute)} = \$346$$ \ No newline at end of file From 9949ff051cfb67928dd8ee898572a7d36c6dfff5 Mon Sep 17 00:00:00 2001 From: morsapaes Date: Sun, 21 Sep 2025 15:09:01 +0200 Subject: [PATCH 4/9] Rename files --- ...pipes_for_cdc.md => clickpipes_for_cdc.md} | 107 +++++++++++++++--- ...pipes_for_streaming_and_object_storage.md} | 10 +- .../03_billing/03_clickpipes/index.md | 17 +++ 3 files changed, 119 insertions(+), 15 deletions(-) rename docs/cloud/reference/03_billing/03_clickpipes/{03_2_clickpipes_for_cdc.md => clickpipes_for_cdc.md} (51%) rename docs/cloud/reference/03_billing/03_clickpipes/{03_1_clickpipes_for_streaming_and_object_storage.md => clickpipes_for_streaming_and_object_storage.md} (93%) create mode 100644 docs/cloud/reference/03_billing/03_clickpipes/index.md diff --git a/docs/cloud/reference/03_billing/03_clickpipes/03_2_clickpipes_for_cdc.md b/docs/cloud/reference/03_billing/03_clickpipes/clickpipes_for_cdc.md similarity index 51% rename from docs/cloud/reference/03_billing/03_clickpipes/03_2_clickpipes_for_cdc.md rename to docs/cloud/reference/03_billing/03_clickpipes/clickpipes_for_cdc.md index ea2b5dd11af..3ce7c15ad37 100644 --- a/docs/cloud/reference/03_billing/03_clickpipes/03_2_clickpipes_for_cdc.md +++ b/docs/cloud/reference/03_billing/03_clickpipes/clickpipes_for_cdc.md @@ -1,5 +1,5 @@ --- -sidebar_label: 'ClickPipes - PostgreSQL CDC' +sidebar_label: 'PostgreSQL CDC' slug: /cloud/reference/billing/clickpipes/postgres-cdc title: 'ClickPipes for PostgreSQL CDC' description: 'Overview of billing for PostgreSQL CDC ClickPipes' @@ -7,8 +7,8 @@ description: 'Overview of billing for PostgreSQL CDC ClickPipes' # ClickPipes for PostgreSQL CDC {#clickpipes-for-postgresql-cdc} -This section outlines the pricing model for our Postgres Change Data Capture (CDC) -connector in ClickPipes. In designing this model, our goal was to keep pricing +This section outlines the pricing model for the Postgres Change Data Capture (CDC) +connector in ClickPipes. In designing this model, the goal was to keep pricing highly competitive while staying true to our core vision: > Making it seamless and @@ -19,11 +19,8 @@ The connector is over **5x more cost-effective** than external ETL tools and similar features in other database platforms. :::note -Pricing will start being metered in monthly bills beginning **September 1st, 2025,** -for all customers (both existing and new) using Postgres CDC ClickPipes. Until -then, usage is free. Customers have a 3-month window starting May 29 (GA announcement) -to review and optimize their costs if needed, although we expect most will not need -to make any changes. +Pricing started being metered in monthly bills on **September 1st, 2025** +for all customers (both existing and new) using Postgres CDC ClickPipes. ::: ## Pricing dimensions {#pricing-dimensions} @@ -38,7 +35,7 @@ There are two main dimensions to pricing: to Postgres CDC ClickPipes. Compute is billed at the service level, not per individual pipe. Each compute unit includes 2 vCPUs and 8 GB of RAM. -## Ingested data {#ingested-data} +### Ingested data {#ingested-data} The Postgres CDC connector operates in two main phases: @@ -56,7 +53,7 @@ at once, we offer a lower rate for that phase. | **Initial load / resync** | $0.10 per GB | | **Continuous Replication (CDC)** | $0.20 per GB | -## Compute {#compute} +### Compute {#compute} This dimension covers the compute units provisioned per service just for Postgres ClickPipes. Compute is shared across all Postgres pipes within a service. **It @@ -69,7 +66,7 @@ organization's tier: | **Basic Tier** | 0.5 compute unit per service — $0.10 per hour | | **Scale or Enterprise Tier** | 1 compute unit per service — $0.20 per hour | -## Example {#example} +### Example {#example} Let's say your service is in Scale tier and has the following setup: @@ -77,7 +74,7 @@ Let's say your service is in Scale tier and has the following setup: - Each pipe ingests 500 GB of data changes (CDC) per month - When the first pipe is kicked off, the service provisions **1 compute unit under the Scale Tier** for Postgres CDC -### Monthly cost breakdown {#cost-breakdown} +#### Monthly cost breakdown {#cost-breakdown} **Ingested Data (CDC)**: @@ -95,4 +92,88 @@ Compute is shared across both pipes **Total Monthly Cost**: -$$\$200 \text{ (ingest)} + \$146 \text{ (compute)} = \$346$$ \ No newline at end of file +$$\$200 \text{ (ingest)} + \$146 \text{ (compute)} = \$346$$ + +## FAQ for Postgres CDC ClickPipes {#faq-postgres-cdc-clickpipe} + +
+ +Is the ingested data measured in pricing based on compressed or uncompressed size? + +The ingested data is measured as _uncompressed data_ coming from Postgres—both +during the initial load and CDC (via the replication slot). Postgres does not +compress data during transit by default, and ClickPipe processes the raw, +uncompressed bytes. + +
+ +
+ +When will Postgres CDC pricing start appearing on my bills? + +Postgres CDC ClickPipes pricing began appearing on monthly bills starting +**September 1st, 2025**, for all customers (both existing and new). + +
+ +
+ +Will I be charged if I pause my pipes? + +No data ingestion charges apply while a pipe is paused, since no data is moved. +However, compute charges still apply—either 0.5 or 1 compute unit—based on your +organization's tier. This is a fixed service-level cost and applies across all +pipes within that service. + +
+ +
+ +How can I estimate my pricing? + +The Overview page in ClickPipes provides metrics for both initial load/resync and +CDC data volumes. You can estimate your Postgres CDC costs using these metrics +in conjunction with the ClickPipes pricing. + +
+ +
+ +Can I scale the compute allocated for Postgres CDC in my service? + +By default, compute scaling is not user-configurable. The provisioned resources +are optimized to handle most customer workloads optimally. If your use case +requires more or less compute, please open a support ticket so we can evaluate +your request. + +
+ +
+ +What is the pricing granularity? + +- **Compute**: Billed per hour. Partial hours are rounded up to the next hour. +- **Ingested Data**: Measured and billed per gigabyte (GB) of uncompressed data. + +
+ +
+ +Can I use my ClickHouse Cloud credits for Postgres CDC via 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. + +
+ +
+ +How much additional cost should I expect from Postgres CDC ClickPipes in my existing monthly ClickHouse Cloud spend? + +The cost varies based on your use case, data volume, and organization tier. +That said, most existing customers see an increase of **0–15%** relative to their +existing monthly ClickHouse Cloud spend post trial. Actual costs may vary +depending on your workload—some workloads involve high data volumes with +lesser processing, while others require more processing with less data. + +
\ No newline at end of file diff --git a/docs/cloud/reference/03_billing/03_clickpipes/03_1_clickpipes_for_streaming_and_object_storage.md b/docs/cloud/reference/03_billing/03_clickpipes/clickpipes_for_streaming_and_object_storage.md similarity index 93% rename from docs/cloud/reference/03_billing/03_clickpipes/03_1_clickpipes_for_streaming_and_object_storage.md rename to docs/cloud/reference/03_billing/03_clickpipes/clickpipes_for_streaming_and_object_storage.md index db6776dc4d6..40a4f92f19e 100644 --- a/docs/cloud/reference/03_billing/03_clickpipes/03_1_clickpipes_for_streaming_and_object_storage.md +++ b/docs/cloud/reference/03_billing/03_clickpipes/clickpipes_for_streaming_and_object_storage.md @@ -1,10 +1,12 @@ --- -sidebar_label: 'ClickPipes - streaming and object storage' +sidebar_label: 'Streaming and object storage' slug: /cloud/reference/billing/clickpipes/streaming-and-object-storage title: 'ClickPipes for streaming and object storage' description: 'Overview of billing for streaming and object storage ClickPipes' --- +import ClickPipesFAQ from '../../../_snippets/_clickpipes_faq.md' + # ClickPipes for streaming and object storage {#clickpipes-for-streaming-object-storage} This section outlines the pricing model of ClickPipes for streaming and object storage. @@ -75,4 +77,8 @@ The following examples assume a single M-sized replica, unless explicitly mentio $^1$ _Only ClickPipes compute for orchestration, -effective data transfer is assumed by the underlying Clickhouse Service_ \ No newline at end of file +effective data transfer is assumed by the underlying Clickhouse Service_ + +## FAQ for streaming and object storage ClickPipes {#faq-streaming-and-object-storage} + + \ No newline at end of file diff --git a/docs/cloud/reference/03_billing/03_clickpipes/index.md b/docs/cloud/reference/03_billing/03_clickpipes/index.md new file mode 100644 index 00000000000..16bb2afbbf3 --- /dev/null +++ b/docs/cloud/reference/03_billing/03_clickpipes/index.md @@ -0,0 +1,17 @@ +--- +slug: /cloud/reference/billing/clickpipes +title: 'ClickPipes' +description: 'ClickPipes billing' +keywords: ['ClickPipes Billing'] +--- + +:::note +Usage is free for MySQL and MongoDB CDC ClickPipes before reaching General Availability (GA). Customers will be notified ahead of GA launches to review and optimize their ClickPipes usage. +::: + +[ClickPipes](/integrations/clickpipes) billing is based on **compute usage** and **ingested data**. For more information on the pricing model for each category, see the dedicated billing pages: + +| Page | Description | +|---------------------------------------------------------------------------------------------------------------------|------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| [ClickPipes for Postgres CDC](/cloud/reference/billing/clickpipes/postgres-cdc) | Pricing for PostgreSQL CDC ClickPipes. | +| [ClickPipes for streaming and object storage](/cloud/reference/billing/clickpipes/streaming-and-object-storage) | Pricing for streaming and object storage ClickPipes. | \ No newline at end of file From adaa017d2f1759ca3651030bcd693fb23352de43 Mon Sep 17 00:00:00 2001 From: Shaun Struwig <41984034+Blargian@users.noreply.github.com> Date: Tue, 16 Sep 2025 15:45:47 +0200 Subject: [PATCH 5/9] change ordering of menu items --- ...{05_network-data-transfer.mdx => 04_network-data-transfer.mdx} | 0 .../{04_payment-thresholds.md => 05_payment-thresholds.md} | 0 2 files changed, 0 insertions(+), 0 deletions(-) rename docs/cloud/reference/03_billing/{05_network-data-transfer.mdx => 04_network-data-transfer.mdx} (100%) rename docs/cloud/reference/03_billing/{04_payment-thresholds.md => 05_payment-thresholds.md} (100%) diff --git a/docs/cloud/reference/03_billing/05_network-data-transfer.mdx b/docs/cloud/reference/03_billing/04_network-data-transfer.mdx similarity index 100% rename from docs/cloud/reference/03_billing/05_network-data-transfer.mdx rename to docs/cloud/reference/03_billing/04_network-data-transfer.mdx diff --git a/docs/cloud/reference/03_billing/04_payment-thresholds.md b/docs/cloud/reference/03_billing/05_payment-thresholds.md similarity index 100% rename from docs/cloud/reference/03_billing/04_payment-thresholds.md rename to docs/cloud/reference/03_billing/05_payment-thresholds.md From bb38fc4170121699c5e965c3612870e58117f101 Mon Sep 17 00:00:00 2001 From: morsapaes Date: Fri, 19 Sep 2025 13:04:53 +0200 Subject: [PATCH 6/9] Minor patches --- docs/cloud/reference/03_billing/01_billing_overview.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/docs/cloud/reference/03_billing/01_billing_overview.md b/docs/cloud/reference/03_billing/01_billing_overview.md index 64235e6f9ad..7ce4bceae26 100644 --- a/docs/cloud/reference/03_billing/01_billing_overview.md +++ b/docs/cloud/reference/03_billing/01_billing_overview.md @@ -376,4 +376,4 @@ However, combining two services in a warehouse and idling one of them helps you ## ClickPipes pricing {#clickpipes-pricing} -For information on ClickPipes billing, please see ["ClickPipes billing"](/cloud/reference/billing/clickpipes) +For information on ClickPipes billing, please see the dedicated ["ClickPipes billing" section](/cloud/reference/billing/clickpipes). From 44224b710034bddd23877bacc86ec4b240297896 Mon Sep 17 00:00:00 2001 From: morsapaes Date: Fri, 19 Sep 2025 13:06:58 +0200 Subject: [PATCH 7/9] Make ClickPipes section collapsible --- docs/cloud/reference/03_billing/03_clickpipes/index.md | 2 +- vercel.json | 4 ++-- 2 files changed, 3 insertions(+), 3 deletions(-) diff --git a/docs/cloud/reference/03_billing/03_clickpipes/index.md b/docs/cloud/reference/03_billing/03_clickpipes/index.md index 16bb2afbbf3..19b40ca8772 100644 --- a/docs/cloud/reference/03_billing/03_clickpipes/index.md +++ b/docs/cloud/reference/03_billing/03_clickpipes/index.md @@ -14,4 +14,4 @@ Usage is free for MySQL and MongoDB CDC ClickPipes before reaching General Avail | Page | Description | |---------------------------------------------------------------------------------------------------------------------|------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| | [ClickPipes for Postgres CDC](/cloud/reference/billing/clickpipes/postgres-cdc) | Pricing for PostgreSQL CDC ClickPipes. | -| [ClickPipes for streaming and object storage](/cloud/reference/billing/clickpipes/streaming-and-object-storage) | Pricing for streaming and object storage ClickPipes. | \ No newline at end of file +| [ClickPipes for streaming and object storage](/cloud/reference/billing/clickpipes/streaming-and-object-storage) | Pricing for streaming and object storage ClickPipes. | diff --git a/vercel.json b/vercel.json index 3c60347cb72..ee9b783ef10 100644 --- a/vercel.json +++ b/vercel.json @@ -2828,12 +2828,12 @@ }, { "source": "/docs/cloud/manage/billing/overview#clickpipes-for-postgres-cdc", - "destination": "/docs/cloud/reference/billing/clickpipes#clickpipes-for-postgresql-cdc", + "destination": "/docs/cloud/reference/billing/clickpipes/postgresql-cdc", "permanent": true }, { "source": "/docs/cloud/manage/billing/overview#clickpipes-for-streaming-object-storage", - "destination": "/docs/cloud/reference/billing/clickpipes#clickpipes-for-streaming-object-storage", + "destination": "/docs/cloud/reference/billing/clickpipes/streaming-and-object-storage", "permanent": true }, { From 84c04b6a7e62af91408ff2ff53ef2219477940a8 Mon Sep 17 00:00:00 2001 From: morsapaes Date: Sun, 21 Sep 2025 15:39:28 +0200 Subject: [PATCH 8/9] Add doc_type to frontmatter --- .../reference/03_billing/03_clickpipes/clickpipes_for_cdc.md | 1 + .../03_clickpipes/clickpipes_for_streaming_and_object_storage.md | 1 + docs/cloud/reference/03_billing/03_clickpipes/index.md | 1 + 3 files changed, 3 insertions(+) diff --git a/docs/cloud/reference/03_billing/03_clickpipes/clickpipes_for_cdc.md b/docs/cloud/reference/03_billing/03_clickpipes/clickpipes_for_cdc.md index 3ce7c15ad37..ab30a5bfca3 100644 --- a/docs/cloud/reference/03_billing/03_clickpipes/clickpipes_for_cdc.md +++ b/docs/cloud/reference/03_billing/03_clickpipes/clickpipes_for_cdc.md @@ -3,6 +3,7 @@ sidebar_label: 'PostgreSQL CDC' slug: /cloud/reference/billing/clickpipes/postgres-cdc title: 'ClickPipes for PostgreSQL CDC' description: 'Overview of billing for PostgreSQL CDC ClickPipes' +doc_type: reference --- # ClickPipes for PostgreSQL CDC {#clickpipes-for-postgresql-cdc} diff --git a/docs/cloud/reference/03_billing/03_clickpipes/clickpipes_for_streaming_and_object_storage.md b/docs/cloud/reference/03_billing/03_clickpipes/clickpipes_for_streaming_and_object_storage.md index 40a4f92f19e..6c5beced49d 100644 --- a/docs/cloud/reference/03_billing/03_clickpipes/clickpipes_for_streaming_and_object_storage.md +++ b/docs/cloud/reference/03_billing/03_clickpipes/clickpipes_for_streaming_and_object_storage.md @@ -3,6 +3,7 @@ sidebar_label: 'Streaming and object storage' slug: /cloud/reference/billing/clickpipes/streaming-and-object-storage title: 'ClickPipes for streaming and object storage' description: 'Overview of billing for streaming and object storage ClickPipes' +doc_type: reference --- import ClickPipesFAQ from '../../../_snippets/_clickpipes_faq.md' diff --git a/docs/cloud/reference/03_billing/03_clickpipes/index.md b/docs/cloud/reference/03_billing/03_clickpipes/index.md index 19b40ca8772..ec44874153d 100644 --- a/docs/cloud/reference/03_billing/03_clickpipes/index.md +++ b/docs/cloud/reference/03_billing/03_clickpipes/index.md @@ -3,6 +3,7 @@ slug: /cloud/reference/billing/clickpipes title: 'ClickPipes' description: 'ClickPipes billing' keywords: ['ClickPipes Billing'] +doc_type: reference --- :::note From 1b1b733f797237997f2a5e3698e5bb99b76e0cbf Mon Sep 17 00:00:00 2001 From: morsapaes Date: Sun, 21 Sep 2025 16:02:19 +0200 Subject: [PATCH 9/9] Fix linting --- .../reference/03_billing/03_clickpipes/clickpipes_for_cdc.md | 2 +- .../clickpipes_for_streaming_and_object_storage.md | 2 +- docs/cloud/reference/03_billing/03_clickpipes/index.md | 2 +- 3 files changed, 3 insertions(+), 3 deletions(-) diff --git a/docs/cloud/reference/03_billing/03_clickpipes/clickpipes_for_cdc.md b/docs/cloud/reference/03_billing/03_clickpipes/clickpipes_for_cdc.md index ab30a5bfca3..a61deb2863d 100644 --- a/docs/cloud/reference/03_billing/03_clickpipes/clickpipes_for_cdc.md +++ b/docs/cloud/reference/03_billing/03_clickpipes/clickpipes_for_cdc.md @@ -3,7 +3,7 @@ sidebar_label: 'PostgreSQL CDC' slug: /cloud/reference/billing/clickpipes/postgres-cdc title: 'ClickPipes for PostgreSQL CDC' description: 'Overview of billing for PostgreSQL CDC ClickPipes' -doc_type: reference +doc_type: 'reference' --- # ClickPipes for PostgreSQL CDC {#clickpipes-for-postgresql-cdc} diff --git a/docs/cloud/reference/03_billing/03_clickpipes/clickpipes_for_streaming_and_object_storage.md b/docs/cloud/reference/03_billing/03_clickpipes/clickpipes_for_streaming_and_object_storage.md index 6c5beced49d..fab2fa5e37c 100644 --- a/docs/cloud/reference/03_billing/03_clickpipes/clickpipes_for_streaming_and_object_storage.md +++ b/docs/cloud/reference/03_billing/03_clickpipes/clickpipes_for_streaming_and_object_storage.md @@ -3,7 +3,7 @@ sidebar_label: 'Streaming and object storage' slug: /cloud/reference/billing/clickpipes/streaming-and-object-storage title: 'ClickPipes for streaming and object storage' description: 'Overview of billing for streaming and object storage ClickPipes' -doc_type: reference +doc_type: 'reference' --- import ClickPipesFAQ from '../../../_snippets/_clickpipes_faq.md' diff --git a/docs/cloud/reference/03_billing/03_clickpipes/index.md b/docs/cloud/reference/03_billing/03_clickpipes/index.md index ec44874153d..cb3da587a4a 100644 --- a/docs/cloud/reference/03_billing/03_clickpipes/index.md +++ b/docs/cloud/reference/03_billing/03_clickpipes/index.md @@ -3,7 +3,7 @@ slug: /cloud/reference/billing/clickpipes title: 'ClickPipes' description: 'ClickPipes billing' keywords: ['ClickPipes Billing'] -doc_type: reference +doc_type: 'reference' --- :::note