Skip to content

Commit fe3c9f9

Browse files
authored
Merge pull request #4437 from Blargian/clickpipes_page_split
ClickPipes: split ClickPipes billing page into two separate pages
2 parents 9227f95 + 1b1b733 commit fe3c9f9

File tree

8 files changed

+116
-96
lines changed

8 files changed

+116
-96
lines changed

docs/cloud/reference/03_billing/01_billing_overview.md

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -376,4 +376,4 @@ However, combining two services in a warehouse and idling one of them helps you
376376

377377
## ClickPipes pricing {#clickpipes-pricing}
378378

379-
For information on ClickPipes billing, please see ["ClickPipes billing"](/cloud/reference/billing/clickpipes)
379+
For information on ClickPipes billing, please see the dedicated ["ClickPipes billing" section](/cloud/reference/billing/clickpipes).

docs/cloud/reference/03_billing/02_marketplace/index.md

Lines changed: 2 additions & 2 deletions
Original file line numberDiff line numberDiff line change
@@ -1,7 +1,7 @@
11
---
22
slug: /cloud/manage/marketplace/
3-
title: 'Market Place'
4-
description: 'Market Place Table of Contents page'
3+
title: 'Marketplace'
4+
description: 'Marketplace Table of Contents page'
55
keywords: ['Marketplace Billing', 'AWS', 'GCP']
66
doc_type: 'landing-page'
77
---

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

Lines changed: 8 additions & 91 deletions
Original file line numberDiff line numberDiff line change
@@ -1,86 +1,12 @@
11
---
2-
sidebar_label: 'ClickPipes'
3-
slug: /cloud/reference/billing/clickpipes
4-
title: 'ClickPipes billing'
5-
description: 'Overview of ClickPipes billing'
6-
doc_type: 'guide'
2+
sidebar_label: 'PostgreSQL CDC'
3+
slug: /cloud/reference/billing/clickpipes/postgres-cdc
4+
title: 'ClickPipes for PostgreSQL CDC'
5+
description: 'Overview of billing for PostgreSQL CDC ClickPipes'
6+
doc_type: 'reference'
77
---
88

9-
import ClickPipesFAQ from '../../_snippets/_clickpipes_faq.md'
10-
11-
## ClickPipes for streaming and object storage {#clickpipes-for-streaming-object-storage}
12-
13-
This section outlines the pricing model of ClickPipes for streaming and object storage.
14-
15-
### What does the ClickPipes pricing structure look like? {#what-does-the-clickpipes-pricing-structure-look-like}
16-
17-
It consists of two dimensions:
18-
19-
- **Compute**: Price **per unit per hour**.
20-
Compute represents the cost of running the ClickPipes replica pods whether they actively ingest data or not.
21-
It applies to all ClickPipes types.
22-
- **Ingested data**: Price **per GB**.
23-
The ingested data rate applies to all streaming ClickPipes
24-
(Kafka, Confluent, Amazon MSK, Amazon Kinesis, Redpanda, WarpStream, Azure Event Hubs)
25-
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).
26-
27-
### What are ClickPipes replicas? {#what-are-clickpipes-replicas}
28-
29-
ClickPipes ingests data from remote data sources via a dedicated infrastructure
30-
that runs and scales independently of the ClickHouse Cloud service.
31-
For this reason, it uses dedicated compute replicas.
32-
33-
### What is the default number of replicas and their size? {#what-is-the-default-number-of-replicas-and-their-size}
34-
35-
Each ClickPipe defaults to 1 replica that is provided with 512 MiB of RAM and 0.125 vCPU (XS).
36-
This corresponds to **0.0625** ClickHouse compute units (1 unit = 8 GiB RAM, 2 vCPUs).
37-
38-
### What are the ClickPipes public prices? {#what-are-the-clickpipes-public-prices}
39-
40-
- Compute: \$0.20 per unit per hour (\$0.0125 per replica per hour for the default replica size)
41-
- Ingested data: \$0.04 per GB
42-
43-
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:
44-
45-
| Replica Size | Compute Units | RAM | vCPU | Price per Hour |
46-
|----------------------------|---------------|---------|--------|----------------|
47-
| Extra Small (XS) (default) | 0.0625 | 512 MiB | 0.125. | $0.0125 |
48-
| Small (S) | 0.125 | 1 GiB | 0.25 | $0.025 |
49-
| Medium (M) | 0.25 | 2 GiB | 0.5 | $0.05 |
50-
| Large (L) | 0.5 | 4 GiB | 1.0 | $0.10 |
51-
| Extra Large (XL) | 1.0 | 8 GiB | 2.0 | $0.20 |
52-
53-
### How does it look in an illustrative example? {#how-does-it-look-in-an-illustrative-example}
54-
55-
The following examples assume a single M-sized replica, unless explicitly mentioned.
56-
57-
<table><thead>
58-
<tr>
59-
<th></th>
60-
<th>100 GB over 24h</th>
61-
<th>1 TB over 24h</th>
62-
<th>10 TB over 24h</th>
63-
</tr></thead>
64-
<tbody>
65-
<tr>
66-
<td>Streaming ClickPipe</td>
67-
<td>(0.25 x 0.20 x 24) + (0.04 x 100) = \$5.20</td>
68-
<td>(0.25 x 0.20 x 24) + (0.04 x 1000) = \$41.20</td>
69-
<td>With 4 replicas: <br></br> (0.25 x 0.20 x 24 x 4) + (0.04 x 10000) = \$404.80</td>
70-
</tr>
71-
<tr>
72-
<td>Object Storage ClickPipe $^*$</td>
73-
<td>(0.25 x 0.20 x 24) = \$1.20</td>
74-
<td>(0.25 x 0.20 x 24) = \$1.20</td>
75-
<td>(0.25 x 0.20 x 24) = \$1.20</td>
76-
</tr>
77-
</tbody>
78-
</table>
79-
80-
$^1$ _Only ClickPipes compute for orchestration,
81-
effective data transfer is assumed by the underlying Clickhouse Service_
82-
83-
## ClickPipes for PostgreSQL CDC {#clickpipes-for-postgresql-cdc}
9+
# ClickPipes for PostgreSQL CDC {#clickpipes-for-postgresql-cdc}
8410

8511
This section outlines the pricing model for the Postgres Change Data Capture (CDC)
8612
connector in ClickPipes. In designing this model, the goal was to keep pricing
@@ -98,7 +24,7 @@ Pricing started being metered in monthly bills on **September 1st, 2025**
9824
for all customers (both existing and new) using Postgres CDC ClickPipes.
9925
:::
10026

101-
### Pricing dimensions {#pricing-dimensions}
27+
## Pricing dimensions {#pricing-dimensions}
10228

10329
There are two main dimensions to pricing:
10430

@@ -169,11 +95,6 @@ Compute is shared across both pipes
16995

17096
$$\$200 \text{ (ingest)} + \$146 \text{ (compute)} = \$346$$
17197

172-
# ClickPipes pricing FAQ {#clickpipes-pricing-faq}
173-
174-
Below, you will find frequently asked questions about CDC ClickPipes and streaming
175-
and object-based storage ClickPipes.
176-
17798
## FAQ for Postgres CDC ClickPipes {#faq-postgres-cdc-clickpipe}
17899

179100
<details>
@@ -256,8 +177,4 @@ existing monthly ClickHouse Cloud spend post trial. Actual costs may vary
256177
depending on your workload—some workloads involve high data volumes with
257178
lesser processing, while others require more processing with less data.
258179

259-
</details>
260-
261-
## FAQ for streaming and object storage ClickPipes {#faq-streaming-and-object-storage}
262-
263-
<ClickPipesFAQ/>
180+
</details>
Lines changed: 85 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,85 @@
1+
---
2+
sidebar_label: 'Streaming and object storage'
3+
slug: /cloud/reference/billing/clickpipes/streaming-and-object-storage
4+
title: 'ClickPipes for streaming and object storage'
5+
description: 'Overview of billing for streaming and object storage ClickPipes'
6+
doc_type: 'reference'
7+
---
8+
9+
import ClickPipesFAQ from '../../../_snippets/_clickpipes_faq.md'
10+
11+
# ClickPipes for streaming and object storage {#clickpipes-for-streaming-object-storage}
12+
13+
This section outlines the pricing model of ClickPipes for streaming and object storage.
14+
15+
## What does the ClickPipes pricing structure look like? {#what-does-the-clickpipes-pricing-structure-look-like}
16+
17+
It consists of two dimensions:
18+
19+
- **Compute**: Price **per unit per hour**.
20+
Compute represents the cost of running the ClickPipes replica pods whether they actively ingest data or not.
21+
It applies to all ClickPipes types.
22+
- **Ingested data**: Price **per GB**.
23+
The ingested data rate applies to all streaming ClickPipes
24+
(Kafka, Confluent, Amazon MSK, Amazon Kinesis, Redpanda, WarpStream, Azure Event Hubs)
25+
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).
26+
27+
## What are ClickPipes replicas? {#what-are-clickpipes-replicas}
28+
29+
ClickPipes ingests data from remote data sources via a dedicated infrastructure
30+
that runs and scales independently of the ClickHouse Cloud service.
31+
For this reason, it uses dedicated compute replicas.
32+
33+
## What is the default number of replicas and their size? {#what-is-the-default-number-of-replicas-and-their-size}
34+
35+
Each ClickPipe defaults to 1 replica that is provided with 512 MiB of RAM and 0.125 vCPU (XS).
36+
This corresponds to **0.0625** ClickHouse compute units (1 unit = 8 GiB RAM, 2 vCPUs).
37+
38+
## What are the ClickPipes public prices? {#what-are-the-clickpipes-public-prices}
39+
40+
- Compute: \$0.20 per unit per hour (\$0.0125 per replica per hour for the default replica size)
41+
- Ingested data: \$0.04 per GB
42+
43+
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:
44+
45+
| Replica Size | Compute Units | RAM | vCPU | Price per Hour |
46+
|----------------------------|---------------|---------|--------|----------------|
47+
| Extra Small (XS) (default) | 0.0625 | 512 MiB | 0.125. | $0.0125 |
48+
| Small (S) | 0.125 | 1 GiB | 0.25 | $0.025 |
49+
| Medium (M) | 0.25 | 2 GiB | 0.5 | $0.05 |
50+
| Large (L) | 0.5 | 4 GiB | 1.0 | $0.10 |
51+
| Extra Large (XL) | 1.0 | 8 GiB | 2.0 | $0.20 |
52+
53+
## How does it look in an illustrative example? {#how-does-it-look-in-an-illustrative-example}
54+
55+
The following examples assume a single M-sized replica, unless explicitly mentioned.
56+
57+
<table><thead>
58+
<tr>
59+
<th></th>
60+
<th>100 GB over 24h</th>
61+
<th>1 TB over 24h</th>
62+
<th>10 TB over 24h</th>
63+
</tr></thead>
64+
<tbody>
65+
<tr>
66+
<td>Streaming ClickPipe</td>
67+
<td>(0.25 x 0.20 x 24) + (0.04 x 100) = \$5.20</td>
68+
<td>(0.25 x 0.20 x 24) + (0.04 x 1000) = \$41.20</td>
69+
<td>With 4 replicas: <br></br> (0.25 x 0.20 x 24 x 4) + (0.04 x 10000) = \$404.80</td>
70+
</tr>
71+
<tr>
72+
<td>Object Storage ClickPipe $^*$</td>
73+
<td>(0.25 x 0.20 x 24) = \$1.20</td>
74+
<td>(0.25 x 0.20 x 24) = \$1.20</td>
75+
<td>(0.25 x 0.20 x 24) = \$1.20</td>
76+
</tr>
77+
</tbody>
78+
</table>
79+
80+
$^1$ _Only ClickPipes compute for orchestration,
81+
effective data transfer is assumed by the underlying Clickhouse Service_
82+
83+
## FAQ for streaming and object storage ClickPipes {#faq-streaming-and-object-storage}
84+
85+
<ClickPipesFAQ/>
Lines changed: 18 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,18 @@
1+
---
2+
slug: /cloud/reference/billing/clickpipes
3+
title: 'ClickPipes'
4+
description: 'ClickPipes billing'
5+
keywords: ['ClickPipes Billing']
6+
doc_type: 'reference'
7+
---
8+
9+
:::note
10+
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.
11+
:::
12+
13+
[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:
14+
15+
| Page | Description |
16+
|---------------------------------------------------------------------------------------------------------------------|------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|
17+
| [ClickPipes for Postgres CDC](/cloud/reference/billing/clickpipes/postgres-cdc) | Pricing for PostgreSQL CDC ClickPipes. |
18+
| [ClickPipes for streaming and object storage](/cloud/reference/billing/clickpipes/streaming-and-object-storage) | Pricing for streaming and object storage ClickPipes. |
File renamed without changes.
File renamed without changes.

vercel.json

Lines changed: 2 additions & 2 deletions
Original file line numberDiff line numberDiff line change
@@ -2828,12 +2828,12 @@
28282828
},
28292829
{
28302830
"source": "/docs/cloud/manage/billing/overview#clickpipes-for-postgres-cdc",
2831-
"destination": "/docs/cloud/reference/billing/clickpipes#clickpipes-for-postgresql-cdc",
2831+
"destination": "/docs/cloud/reference/billing/clickpipes/postgresql-cdc",
28322832
"permanent": true
28332833
},
28342834
{
28352835
"source": "/docs/cloud/manage/billing/overview#clickpipes-for-streaming-object-storage",
2836-
"destination": "/docs/cloud/reference/billing/clickpipes#clickpipes-for-streaming-object-storage",
2836+
"destination": "/docs/cloud/reference/billing/clickpipes/streaming-and-object-storage",
28372837
"permanent": true
28382838
},
28392839
{

0 commit comments

Comments
 (0)