Skip to content

Commit 642263d

Browse files
BlargianBlargian
authored
Merge pull request #3240 from Blargian/pricing_faq
Add Billing FAQ
2 parents 8e6e6b2 + c882606 commit 642263d

File tree

1 file changed

+300
-0
lines changed

1 file changed

+300
-0
lines changed

‎docs/en/cloud/manage/billing.md‎

Lines changed: 300 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -8,6 +8,170 @@ For pricing information, see the [ClickHouse Cloud Pricing](https://clickhouse.c
88
ClickHouse Cloud bills based on the usage of compute, storage, [data transfer](/en/cloud/manage/network-data-transfer) (egress over the internet and cross-region), and [ClickPipes](/en/integrations/clickpipes).
99
To understand what can affect your bill, and ways that you can manage your spend, keep reading.
1010

11+
## Amazon Web Services (AWS) Example
12+
13+
:::note
14+
- Prices reflect AWS us-east-1 pricing.
15+
- Explore applicable data transfer and ClickPipes charges [here](jan2025_faq/dimensions.md).
16+
:::
17+
18+
### Basic: from $66.52 per month
19+
20+
Best for: Departmental use cases with smaller data volumes that do not have hard reliability guarantees.
21+
22+
**Basic tier service**
23+
- 1 replica x 8 GiB RAM, 2 vCPU
24+
- 500 GB of compressed data
25+
- 500 GB of backup of data
26+
- 10 GB of public internet egress data transfer
27+
- 5 GB of cross-region data transfer
28+
29+
Pricing breakdown for this example:
30+
31+
<table><thead>
32+
<tr>
33+
<th></th>
34+
<th>Active 6 hours a day</th>
35+
<th>Active 12 hours a day</th>
36+
<th>Active 24 hours a day</th>
37+
</tr></thead>
38+
<tbody>
39+
<tr>
40+
<td>Compute</td>
41+
<td>\$39.91</td>
42+
<td>\$79.83</td>
43+
<td>\$159.66</td>
44+
</tr>
45+
<tr>
46+
<td>Storage</td>
47+
<td>\$25.30</td>
48+
<td>\$25.30</td>
49+
<td>\$25.30</td>
50+
</tr>
51+
<tr>
52+
<td>Public internet egress data transfer</td>
53+
<td>\$1.15</td>
54+
<td>\$1.15</td>
55+
<td>\$1.15</td>
56+
</tr>
57+
<tr>
58+
<td>Cross-region data transfer</td>
59+
<td>\$0.16</td>
60+
<td>\$0.16</td>
61+
<td>\$0.16</td>
62+
</tr>
63+
<tr>
64+
<td>Total</td>
65+
<td>\$66.52</td>
66+
<td>\$106.44</td>
67+
<td>\$186.27</td>
68+
</tr>
69+
</tbody>
70+
</table>
71+
72+
### Scale (Always-on, Auto-scaling): From $499.38 per month
73+
74+
Best for: workloads requiring enhanced SLAs (2+ replica services), scalability, and advanced security.
75+
76+
**Scale tier service**
77+
- Active workload ~100% time
78+
- Auto-scaling maximum configurable to prevent runaway bills
79+
- 100 GB of public internet egress data transfer
80+
- 10 GB of cross-region data transfer
81+
82+
Pricing breakdown for this example:
83+
84+
<table><thead>
85+
<tr>
86+
<th></th>
87+
<th>Example 1</th>
88+
<th>Example 2</th>
89+
<th>Example 3</th>
90+
</tr></thead>
91+
<tbody>
92+
<tr>
93+
<td>Compute</td>
94+
<td>2 replicas x 8 GiB RAM, 2 vCPU<br></br>\$436.95</td>
95+
<td>2 replicas x 16 GiB RAM, 4 vCPU<br></br>\$873.89</td>
96+
<td>3 replicas x 16 GiB RAM, 4 vCPU<br></br>\$1,310.84</td>
97+
</tr>
98+
<tr>
99+
<td>Storage</td>
100+
<td>1TB of data + 1 backup<br></br>\$50.60</td>
101+
<td>2TB of data + 1 backup<br></br>\$101.20</td>
102+
<td>3TB of data + 1 backup<br></br>\$151.80</td>
103+
</tr>
104+
<tr>
105+
<td>Public internet egress data transfer</td>
106+
<td>\$11.52</td>
107+
<td>\$11.52</td>
108+
<td>\$11.52</td>
109+
</tr>
110+
<tr>
111+
<td>Cross-region data transfer</td>
112+
<td>\$0.31</td>
113+
<td>\$0.31</td>
114+
<td>\$0.31</td>
115+
</tr>
116+
<tr>
117+
<td>Total</td>
118+
<td>\$499.38</td>
119+
<td>\$986.92</td>
120+
<td>\$1,474.47</td>
121+
</tr>
122+
</tbody>
123+
</table>
124+
125+
### Enterprise: Starting prices vary
126+
127+
Best for: large scale, mission critical deployments that have stringent security and compliance needs
128+
129+
**Enterprise tier service**
130+
- Active workload ~100% time
131+
- 1 TB of public internet egress data transfer
132+
- 500 GB of cross-region data transfer
133+
134+
<table><thead>
135+
<tr>
136+
<th></th>
137+
<th>Example 1</th>
138+
<th>Example 2</th>
139+
<th>Example 3</th>
140+
</tr></thead>
141+
<tbody>
142+
<tr>
143+
<td>Compute</td>
144+
<td>2 replicas x 32 GiB RAM, 8 vCPU<br></br>\$2,285.60</td>
145+
<td>2 replicas x 64 GiB RAM, 16 vCPU<br></br>\$4,571.19</td>
146+
<td>2 x 120 GiB RAM, 30 vCPU<br></br>\$8,570.99</td>
147+
</tr>
148+
<tr>
149+
<td>Storage</td>
150+
<td>5TB + 1 backup<br></br>\$253.00</td>
151+
<td>10TB + 1 backup<br></br>\$506.00</td>
152+
<td>20TB + 1 backup<br></br>\$1,012.00</td>
153+
</tr>
154+
<tr>
155+
<td>Public internet egress data transfer</td>
156+
<td>\$115.20</td>
157+
<td>\$115.20</td>
158+
<td>\$115.20</td>
159+
</tr>
160+
<tr>
161+
<td>Cross-region data transfer</td>
162+
<td>\$15.60</td>
163+
<td>\$15.60</td>
164+
<td>\$15.60</td>
165+
</tr>
166+
<tr>
167+
<td>Total</td>
168+
<td>\$2,669.40</td>
169+
<td>\$5,207.99</td>
170+
<td>\$9,713.79</td>
171+
</tr>
172+
</tbody>
173+
</table>
174+
11175
## FAQs
12176

13177
### How is compute metered?
@@ -111,3 +275,139 @@ Any overages not covered by prepaid credits must be covered by a credit card pay
111275
There is no difference in pricing between marketplace billing and signing up directly with ClickHouse.
112276
In either case, your usage of ClickHouse Cloud is tracked in terms of ClickHouse Cloud Credits (CHCs),
113277
which are metered in the same way and billed accordingly.
278+
279+
### How is compute-compute separation billed?
280+
281+
When creating a service in addition to an existing service,
282+
you can choose if this new service should share the same data with the existing one.
283+
If yes, these two services now form a [warehouse](../reference/warehouses.md).
284+
A warehouse has the data stored in it with multiple compute services accessing this data.
285+
286+
As the data is stored only once, you only pay for one copy of data, though multiple services are accessing it.
287+
You pay for compute as usual — there are no additional fees for compute-compute separation / warehouses.
288+
By leveraging shared storage in this deployment, users benefit from cost savings on both storage and backups.
289+
290+
Compute-compute separation can save you a significant amount of ClickHouse Credits in some cases.
291+
A good example is the following setup:
292+
293+
1. You have ETL jobs that are running 24/7 and ingesting data into the service. These ETL jobs do not require a lot of memory so they can run on a small instance with, for example, 32 GiB of RAM.
294+
295+
2. A data scientist on the same team that has ad hoc reporting requirements, says they need to run a query that requires a significant amount of memory - 236 GiB, however does not need high availability and can wait and rerun queries if the first run fails.
296+
297+
In this example you, as an administrator for the database, can do the following:
298+
299+
1. Create a small service with two replicas 16 GiB each - this will satisfy the ETL jobs and provide high availability.
300+
301+
2. For the data scientist, you can create a second service in the same warehouse with only one replica with 236 GiB. You can enable idling for this service so you will not be paying for this service when the data scientist is not using it.
302+
303+
Cost estimation (per month) for this example on the **Scale Tier**:
304+
- Parent service active 24 hours day: 2 replicas x 16 GiB 4 vCPU per replica
305+
- Child service: 1 replica x 236 GiB 59 vCPU per replica per replica
306+
- 3 TB of compressed data + 1 backup
307+
- 100 GB of public internet egress data transfer
308+
- 50 GB of cross-region data transfer
309+
310+
<table class="nowrap-header"><thead>
311+
<tr>
312+
<th></th>
313+
<th><span>Child service</span><br/><span>active 1 hour/day</span></th>
314+
<th><span>Child service</span><br/><span>active 2 hours/day</span></th>
315+
<th><span>Child service</span><br/><span>active 4 hours/day</span></th>
316+
</tr></thead>
317+
<tbody>
318+
<tr>
319+
<td>Compute</td>
320+
<td>\$1,142.43</td>
321+
<td>\$1,410.97</td>
322+
<td>\$1,948.05</td>
323+
</tr>
324+
<tr>
325+
<td>Storage</td>
326+
<td>\$151.80</td>
327+
<td>\$151.80</td>
328+
<td>\$151.80</td>
329+
</tr>
330+
<tr>
331+
<td>Public internet egress data transfer</td>
332+
<td>\$11.52</td>
333+
<td>\$11.52</td>
334+
<td>\$11.52</td>
335+
</tr>
336+
<tr>
337+
<td>Cross-region data transfer</td>
338+
<td>\$1.56</td>
339+
<td>\$1.56</td>
340+
<td>\$1.56</td>
341+
</tr>
342+
<tr>
343+
<td>Total</td>
344+
<td>\$1,307.31</td>
345+
<td>\$1,575.85</td>
346+
<td>\$2,112.93</td>
347+
</tr>
348+
</tbody>
349+
</table>
350+
351+
Without warehouses, you would have to pay for the amount of memory that the data engineer needs for his queries.
352+
However, combining two services in a warehouse and idling one of them helps you save money.
353+
354+
## ClickPipes Pricing
355+
356+
### What does the ClickPipes pricing structure look like?
357+
358+
It consists of two dimensions
359+
360+
- **Compute**: Price per unit per hour
361+
Compute represents the cost of running the ClickPipes replica pods whether they actively ingest data or not.
362+
It applies to all ClickPipes types.
363+
- **Ingested data**: per GB pricing
364+
The ingested data rate applies to all streaming ClickPipes
365+
(Kafka, Confluent, Amazon MSK, Amazon Kinesis, Redpanda, WarpStream, Azure Event Hubs)
366+
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).
367+
368+
### What are ClickPipes replicas?
369+
370+
ClickPipes ingests data from remote data sources via a dedicated infrastructure
371+
that runs and scales independently of the ClickHouse Cloud service.
372+
For this reason, it uses dedicated compute replicas.
373+
374+
### What is the default number of replicas and their size?
375+
376+
Each ClickPipe defaults to 1 replica that is provided with 2 GiB of RAM and 0.5 vCPU.
377+
This corresponds to **0.25** ClickHouse compute units (1 unit = 8 GiB RAM, 2 vCPUs).
378+
379+
### What are the ClickPipes public prices?
380+
381+
- Compute: \$0.20 per unit per hour (\$0.05 per replica per hour)
382+
- Ingested data: \$0.04 per GB
383+
384+
### How does it look in an illustrative example?
385+
386+
The following examples assume a single replica unless explicitly mentioned.
387+
388+
<table><thead>
389+
<tr>
390+
<th></th>
391+
<th>100 GB over 24h</th>
392+
<th>1 TB over 24h</th>
393+
<th>10 TB over 24h</th>
394+
</tr></thead>
395+
<tbody>
396+
<tr>
397+
<td>Streaming ClickPipe</td>
398+
<td>(0.25 x 0.20 x 24) + (0.04 x 100) = \$5.20</td>
399+
<td>(0.25 x 0.20 x 24) + (0.04 x 1000) = \$41.20</td>
400+
<td>With 4 replicas: <br></br> (0.25 x 0.20 x 24 x 4) + (0.04 x 10000) = \$404.80</td>
401+
</tr>
402+
<tr>
403+
<td>Object Storage ClickPipe $^*$</td>
404+
<td>(0.25 x 0.20 x 24) = \$1.20</td>
405+
<td>(0.25 x 0.20 x 24) = \$1.20</td>
406+
<td>(0.25 x 0.20 x 24) = \$1.20</td>
407+
</tr>
408+
</tbody>
409+
</table>
410+
411+
$^1$ _Only ClickPipes compute for orchestration,
412+
effective data transfer is assumed by the underlying Clickhouse Service_
413+

0 commit comments

Comments
 (0)