Skip to content

ClickPipes Benchmarks, Vertical Scaling FAQs, and additional pricing information #4162

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Merged
merged 10 commits into from
Jul 29, 2025
Merged
30 changes: 15 additions & 15 deletions docs/cloud/manage/billing.md
Original file line number Diff line number Diff line change
Expand Up @@ -454,12 +454,12 @@

#### What does the ClickPipes pricing structure look like? {#what-does-the-clickpipes-pricing-structure-look-like}

It consists of two dimensions
It consists of two dimensions:

- **Compute**: Price per unit per hour
- **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**: per GB pricing
- **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).
Expand All @@ -472,27 +472,27 @@

#### 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.
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}

**Vertical Replica Sizes and Pricing:**
- Compute: \$0.20 per unit per hour (\$0.0125 per replica per hour for the default replica size)
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

@tpanetti: we can keep this as is to make the OOTB price clear and then include the pricing table (❤️) with the per-size price in case a user chooses to scale.

- Ingested data: \$0.04 per GB

| Replica Size | Compute Units | RAM | vCPU | Price per Hour |
|---------------|---------------|-----|------|----------------|
| Extra Small | 0.0625 | 512 MiB | 0.125| $0.0125 |
| Small | 0.125 | 1 GiB | 0.25 | $0.025 |
| Medium | 0.25 | 2 GiB | 0.5 | $0.05 |
| Large | 0.5 | 4 GiB | 1.0 | $0.10 |
| Extra Large | 1.0 | 8 GiB | 2.0 | $0.20 |
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:

Check warning on line 483 in docs/cloud/manage/billing.md

View workflow job for this annotation

GitHub Actions / vale

ClickHouse.BadPlurals

Rewrite '(s)' to be plural without parentheses.

**Additional Pricing:**
- Ingested data: \$0.04 per GB
| 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 medium size replica unless explicitly mentioned.
The following examples assume a single M-sized replica, unless explicitly mentioned.

<table><thead>
<tr>
Expand Down
Loading