Confluent Cloud Cluster Types

The Confluent Cloud cluster type determines the features, usage limits, and price of your cluster.

Basic clusters

Basic clusters are designed for development use-cases. Basic clusters support the following:

  • Up to 100 MB/s of throughput and 5 TB of storage.
  • You only pay for the ingress, egress, and storage. There is no base cluster price.

Standard clusters

Standard clusters are designed for production-ready features and functionality. Standard clusters support the following:

  • 99.95% uptime SLA.
  • Up to 100 MB/s of throughput and 5 TB of storage.
  • Multi-zone availability.
  • Unlimited Connect tasks per connector.
  • Charged an hourly base price in addition to the ingress, egress, and storage.

Dedicated clusters

Dedicated clusters are designed for critical production workloads with high traffic or private networking requirements. Dedicated clusters support the following:

  • Single-tenant deployments with a 99.95% uptime SLA.
  • Up to 100 MB/s of throughput and 5 TB of storage.
  • Multi-zone availability,
  • Unlimited Connect tasks per connector without any capacity limits.
  • Can be scaled to achieve gigabytes per second of ingress.

Dedicated clusters are provisioned and billed in terms of Confluent Unit for Kafka (CKU). CKUs are a unit of horizontal scalability in Confluent Cloud that provide a pre-allocated amount of resources. How much you can ingest and stream per CKU depends on a variety of factors including client application design and partitioning strategy.

Dedicated cluster size

Dedicated clusters can be purchased in any increment of CKUs up to 24. To provision a cluster with more than 24 CKUs, contact your Confluent sales representative.

Dedicated cluster CKUs and limits

CKUs determine the capacity of your cluster. For a Confluent Cloud cluster, the expected performance for any given workload is dependent on a variety of factors, such as message size, number of partitions, number of clients, and ratio of ingress to egress.

Use this table to determine the number of CKUs to use for a given workload. This table shows the benchmarked capacity per CKU using the Confluent Performance Benchmark with 1 KB messages. Values for storage and partition limits are pre-replication.

Dimension Capacity
Ingress 50 MB/s
Egress 150 MB/s
Storage (pre-replication) 10 TB
Partitions (pre-replication) 4500
Total client connections 1000
Connection attempts per second 80
Requests per second 15,000

Dedicated cluster quotas and limits

A dedicated cluster can scale to meet the capacity for your high traffic workloads. However, the limits shown in this table will not change as you increase the number of CKUs.

Dedicated cluster limits per cluster

Feature Limit
Message size 8 MB
Client version Minimum 0.11.0
Request size 100 MB
Fetch bytes 55 MB
Partitions 100,000
API keys 500

Dedicated cluster limits per partition

Feature Limit
Ingress per Partition 5 MB/s
Egress per Partition 15 MB/s
Storage per Partition 250 GB

Dedicated cluster provision time

You can determine the estimated time to provision a dedicated cluster by the size for a cluster.

  • AWS: the expected provisioning times is one hour per CKU. A dedicated 2 CKU cluster on AWS is estimated to complete provisioning in two hours.
  • GCP: the expected provisioning time is one hour per CKU. A dedicated 2 CKU cluster on GCP is estimated to complete provisioning in two hours.
  • Azure: the expected provisioning times is two and a half hours per CKU. A dedicated 2 CKU cluster on Azure is estimated to complete in five hours.