jan faq 2025

Author: gingerwizard

docs/cloud/manage/jan2025_faq/dimensions.md

@@ -5,6 +5,9 @@ keywords: [new pricing, dimensions]
 description: Pricing dimensions for data transfer and ClickPipes
 ---
 
+import clickpipesPricingFaq1 from '@site/static/images/cloud/manage/jan2025_faq/external_clickpipes_pricing_faq_1.png';
+import clickpipesPricingFaq2 from '@site/static/images/cloud/manage/jan2025_faq/external_clickpipes_pricing_faq_2.png';
+import clickpipesPricingFaq3 from '@site/static/images/cloud/manage/jan2025_faq/external_clickpipes_pricing_faq_3.png';
 import NetworkPricing from '@site/docs/cloud/manage/_snippets/_network_transfer_rates.md';
 
 
@@ -34,60 +37,60 @@ Data transfer prices will **not** be tiered as usage increases. Note that the pr
 ### Why are we introducing a pricing model for ClickPipes now? {#why-are-we-introducing-a-pricing-model-for-clickpipes-now}
 
 We decided to initially launch ClickPipes for free with the idea to gather feedback, refine features,
-and ensure it meets user needs. 
-As the GA platform has grown and effectively stood the test of time by moving trillions of rows, 
-introducing a pricing model allows us to continue improving the service, 
+and ensure it meets user needs.
+As the GA platform has grown and effectively stood the test of time by moving trillions of rows,
+introducing a pricing model allows us to continue improving the service,
 maintaining the infrastructure, and providing dedicated support and new connectors.
 
 ### 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. 
+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.
 The diagrams below show a simplified architecture.
 
-For streaming ClickPipes, ClickPipes replicas access the remote data sources (e.g., a Kafka broker), 
+For streaming ClickPipes, ClickPipes replicas access the remote data sources (e.g., a Kafka broker),
 pull the data, process and ingest it into the destination ClickHouse service.
 
-![ClickPipes Replicas - Streaming ClickPipes](images/external_clickpipes_pricing_faq_1.png)
+<img src={clickpipesPricingFaq1} alt="ClickPipes Replicas - Streaming ClickPipes" />
 
-In the case of object storage ClickPipes, 
-the ClickPipes replica orchestrates the data loading task 
-(identifying files to copy, maintaining the state, and moving partitions), 
+In the case of object storage ClickPipes,
+the ClickPipes replica orchestrates the data loading task
+(identifying files to copy, maintaining the state, and moving partitions),
 while the data is pulled directly from the ClickHouse service.
 
-![ClickPipes Replicas - Object Storage ClickPipes](images/external_clickpipes_pricing_faq_2.png)
+<img src={clickpipesPricingFaq2} alt="ClickPipes Replicas - Object Storage ClickPipes" />
 
 ### 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 2 GiB of RAM and 0.5 vCPU. 
+Each ClickPipe defaults to 1 replica that is provided with 2 GiB of RAM and 0.5 vCPU.
 This corresponds to **0.25** ClickHouse compute units (1 unit = 8 GiB RAM, 2 vCPUs).
 
 ### Can ClickPipes replicas be scaled? {#can-clickpipes-replicas-be-scaled}
 
-Currently, only ClickPipes for streaming can be scaled horizontally 
-by adding more replicas each with a base unit of **0.25** ClickHouse compute units. 
+Currently, only ClickPipes for streaming can be scaled horizontally
+by adding more replicas each with a base unit of **0.25** ClickHouse compute units.
 Vertical scaling is also available on demand for specific use cases (adding more CPU and RAM per replica).
 
 ### How many ClickPipes replicas do I need? {#how-many-clickpipes-replicas-do-i-need}
 
-It depends on the workload throughput and latency requirements. 
-We recommend starting with the default value of 1 replica, measuring your latency, and adding replicas if needed. 
-Keep in mind that for Kafka ClickPipes, you also have to scale the Kafka broker partitions accordingly. 
+It depends on the workload throughput and latency requirements.
+We recommend starting with the default value of 1 replica, measuring your latency, and adding replicas if needed.
+Keep in mind that for Kafka ClickPipes, you also have to scale the Kafka broker partitions accordingly.
 The scaling controls are available under “settings” for each streaming ClickPipe.
 
-![ClickPipes Replicas - How many ClickPipes replicas do I need?](images/external_clickpipes_pricing_faq_3.png)
+<img src={clickpipesPricingFaq3} alt="ClickPipes Replicas - How many ClickPipes replicas do I need?" />
 
 ### 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. 
+- **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  
-  The ingested data rate applies to all streaming ClickPipes 
+- **Ingested data**: per GB pricing
+  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. 
+  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 the ClickPipes public prices? {#what-are-the-clickpipes-public-prices}
@@ -103,8 +106,8 @@ $$
 (0.25 \times 0.20 \times 24) + (0.04 \times 1000) = \$41.2
 $$
 
-For object storage connectors (S3 and GCS), 
-only the ClickPipes compute cost is incurred since the ClickPipes pod is not processing data 
+For object storage connectors (S3 and GCS),
+only the ClickPipes compute cost is incurred since the ClickPipes pod is not processing data
 but only orchestrating the transfer which is operated by the underlying ClickHouse service:
 
 $$
@@ -117,13 +120,11 @@ The new pricing model will take effect for all organizations created after Janua
 
 ### What happens to current users? {#what-happens-to-current-users}
 
-Existing users will have a **60-day grace period** where the ClickPipes service continues to be offered for free. 
+Existing users will have a **60-day grace period** where the ClickPipes service continues to be offered for free.
 Billing will automatically start for ClickPipes for existing users on **March 24th, 2025.**
 
 ### How does ClickPipes pricing compare to the market? {#how-does-clickpipes-pricing-compare-to-the-market}
 
-The philosophy behind ClickPipes pricing is 
-to cover the operating costs of the platform while offering an easy and reliable way to move data to ClickHouse Cloud. 
+The philosophy behind ClickPipes pricing is
+to cover the operating costs of the platform while offering an easy and reliable way to move data to ClickHouse Cloud.
 From that angle, our market analysis revealed that we are positioned competitively.
-
-