Skip to content

Commit 9949ff0

Browse files
morsapaesmorsapaes
committed
Rename files
1 parent c8eba39 commit 9949ff0

File tree

3 files changed

+119
-15
lines changed

3 files changed

+119
-15
lines changed

‎docs/cloud/reference/03_billing/03_clickpipes/03_2_clickpipes_for_cdc.md‎ renamed to ‎docs/cloud/reference/03_billing/03_clickpipes/clickpipes_for_cdc.md‎

Lines changed: 94 additions & 13 deletions
Original file line numberDiff line numberDiff line change
@@ -1,14 +1,14 @@
11
---
2-
sidebar_label: 'ClickPipes - PostgreSQL CDC'
2+
sidebar_label: 'PostgreSQL CDC'
33
slug: /cloud/reference/billing/clickpipes/postgres-cdc
44
title: 'ClickPipes for PostgreSQL CDC'
55
description: 'Overview of billing for PostgreSQL CDC ClickPipes'
66
---
77

88
# ClickPipes for PostgreSQL CDC {#clickpipes-for-postgresql-cdc}
99

10-
This section outlines the pricing model for our Postgres Change Data Capture (CDC)
11-
connector in ClickPipes. In designing this model, our goal was to keep pricing
10+
This section outlines the pricing model for the Postgres Change Data Capture (CDC)
11+
connector in ClickPipes. In designing this model, the goal was to keep pricing
1212
highly competitive while staying true to our core vision:
1313

1414
> Making it seamless and
@@ -19,11 +19,8 @@ The connector is over **5x more cost-effective** than external
1919
ETL tools and similar features in other database platforms.
2020

2121
:::note
22-
Pricing will start being metered in monthly bills beginning **September 1st, 2025,**
23-
for all customers (both existing and new) using Postgres CDC ClickPipes. Until
24-
then, usage is free. Customers have a 3-month window starting May 29 (GA announcement)
25-
to review and optimize their costs if needed, although we expect most will not need
26-
to make any changes.
22+
Pricing started being metered in monthly bills on **September 1st, 2025**
23+
for all customers (both existing and new) using Postgres CDC ClickPipes.
2724
:::
2825

2926
## Pricing dimensions {#pricing-dimensions}
@@ -38,7 +35,7 @@ There are two main dimensions to pricing:
3835
to Postgres CDC ClickPipes. Compute is billed at the service level, not per
3936
individual pipe. Each compute unit includes 2 vCPUs and 8 GB of RAM.
4037

41-
## Ingested data {#ingested-data}
38+
### Ingested data {#ingested-data}
4239

4340
The Postgres CDC connector operates in two main phases:
4441

@@ -56,7 +53,7 @@ at once, we offer a lower rate for that phase.
5653
| **Initial load / resync** | $0.10 per GB |
5754
| **Continuous Replication (CDC)** | $0.20 per GB |
5855

59-
## Compute {#compute}
56+
### Compute {#compute}
6057

6158
This dimension covers the compute units provisioned per service just for Postgres
6259
ClickPipes. Compute is shared across all Postgres pipes within a service. **It
@@ -69,15 +66,15 @@ organization's tier:
6966
| **Basic Tier** | 0.5 compute unit per service — $0.10 per hour |
7067
| **Scale or Enterprise Tier** | 1 compute unit per service — $0.20 per hour |
7168

72-
## Example {#example}
69+
### Example {#example}
7370

7471
Let's say your service is in Scale tier and has the following setup:
7572

7673
- 2 Postgres ClickPipes running continuous replication
7774
- Each pipe ingests 500 GB of data changes (CDC) per month
7875
- When the first pipe is kicked off, the service provisions **1 compute unit under the Scale Tier** for Postgres CDC
7976

80-
### Monthly cost breakdown {#cost-breakdown}
77+
#### Monthly cost breakdown {#cost-breakdown}
8178

8279
**Ingested Data (CDC)**:
8380

@@ -95,4 +92,88 @@ Compute is shared across both pipes
9592

9693
**Total Monthly Cost**:
9794

98-
$$\$200 \text{ (ingest)} + \$146 \text{ (compute)} = \$346$$
95+
$$\$200 \text{ (ingest)} + \$146 \text{ (compute)} = \$346$$
96+
97+
## FAQ for Postgres CDC ClickPipes {#faq-postgres-cdc-clickpipe}
98+
99+
<details>
100+
101+
<summary>Is the ingested data measured in pricing based on compressed or uncompressed size?</summary>
102+
103+
The ingested data is measured as _uncompressed data_ coming from Postgres—both
104+
during the initial load and CDC (via the replication slot). Postgres does not
105+
compress data during transit by default, and ClickPipe processes the raw,
106+
uncompressed bytes.
107+
108+
</details>
109+
110+
<details>
111+
112+
<summary>When will Postgres CDC pricing start appearing on my bills?</summary>
113+
114+
Postgres CDC ClickPipes pricing began appearing on monthly bills starting
115+
**September 1st, 2025**, for all customers (both existing and new).
116+
117+
</details>
118+
119+
<details>
120+
121+
<summary>Will I be charged if I pause my pipes?</summary>
122+
123+
No data ingestion charges apply while a pipe is paused, since no data is moved.
124+
However, compute charges still apply—either 0.5 or 1 compute unit—based on your
125+
organization's tier. This is a fixed service-level cost and applies across all
126+
pipes within that service.
127+
128+
</details>
129+
130+
<details>
131+
132+
<summary>How can I estimate my pricing?</summary>
133+
134+
The Overview page in ClickPipes provides metrics for both initial load/resync and
135+
CDC data volumes. You can estimate your Postgres CDC costs using these metrics
136+
in conjunction with the ClickPipes pricing.
137+
138+
</details>
139+
140+
<details>
141+
142+
<summary>Can I scale the compute allocated for Postgres CDC in my service?</summary>
143+
144+
By default, compute scaling is not user-configurable. The provisioned resources
145+
are optimized to handle most customer workloads optimally. If your use case
146+
requires more or less compute, please open a support ticket so we can evaluate
147+
your request.
148+
149+
</details>
150+
151+
<details>
152+
153+
<summary>What is the pricing granularity?</summary>
154+
155+
- **Compute**: Billed per hour. Partial hours are rounded up to the next hour.
156+
- **Ingested Data**: Measured and billed per gigabyte (GB) of uncompressed data.
157+
158+
</details>
159+
160+
<details>
161+
162+
<summary>Can I use my ClickHouse Cloud credits for Postgres CDC via ClickPipes?</summary>
163+
164+
Yes. ClickPipes pricing is part of the unified ClickHouse Cloud pricing. Any
165+
platform credits you have will automatically apply to ClickPipes usage as well.
166+
167+
</details>
168+
169+
<details>
170+
171+
<summary>How much additional cost should I expect from Postgres CDC ClickPipes in my existing monthly ClickHouse Cloud spend?</summary>
172+
173+
The cost varies based on your use case, data volume, and organization tier.
174+
That said, most existing customers see an increase of **0–15%** relative to their
175+
existing monthly ClickHouse Cloud spend post trial. Actual costs may vary
176+
depending on your workload—some workloads involve high data volumes with
177+
lesser processing, while others require more processing with less data.
178+
179+
</details>

‎docs/cloud/reference/03_billing/03_clickpipes/03_1_clickpipes_for_streaming_and_object_storage.md‎ renamed to ‎docs/cloud/reference/03_billing/03_clickpipes/clickpipes_for_streaming_and_object_storage.md‎

Lines changed: 8 additions & 2 deletions
Original file line numberDiff line numberDiff line change
@@ -1,10 +1,12 @@
11
---
2-
sidebar_label: 'ClickPipes - streaming and object storage'
2+
sidebar_label: 'Streaming and object storage'
33
slug: /cloud/reference/billing/clickpipes/streaming-and-object-storage
44
title: 'ClickPipes for streaming and object storage'
55
description: 'Overview of billing for streaming and object storage ClickPipes'
66
---
77

8+
import ClickPipesFAQ from '../../../_snippets/_clickpipes_faq.md'
9+
810
# ClickPipes for streaming and object storage {#clickpipes-for-streaming-object-storage}
911

1012
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
7577
</table>
7678

7779
$^1$ _Only ClickPipes compute for orchestration,
78-
effective data transfer is assumed by the underlying Clickhouse Service_
80+
effective data transfer is assumed by the underlying Clickhouse Service_
81+
82+
## FAQ for streaming and object storage ClickPipes {#faq-streaming-and-object-storage}
83+
84+
<ClickPipesFAQ/>

‎docs/cloud/reference/03_billing/03_clickpipes/index.md‎

Lines changed: 17 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,17 @@
1+
---
2+
slug: /cloud/reference/billing/clickpipes
3+
title: 'ClickPipes'
4+
description: 'ClickPipes billing'
5+
keywords: ['ClickPipes Billing']
6+
---
7+
8+
:::note
9+
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.
10+
:::
11+
12+
[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:
13+
14+
| Page | Description |
15+
|---------------------------------------------------------------------------------------------------------------------|------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|
16+
| [ClickPipes for Postgres CDC](/cloud/reference/billing/clickpipes/postgres-cdc) | Pricing for PostgreSQL CDC ClickPipes. |
17+
| [ClickPipes for streaming and object storage](/cloud/reference/billing/clickpipes/streaming-and-object-storage) | Pricing for streaming and object storage ClickPipes. |

0 commit comments

Comments
 (0)