Confluent Cloud Billing

Confluent Cloud bills are based on the consumption of resources within your cloud organization. This includes the total amount of data transferred in and out of your cluster, and request overhead associated with the Kafka protocol. Discounts based on usage are available with annual commitments. For more billing and pricing details, see the PRICING tab in the Cluster Details section of the Pricing page.

Billing for each Confluent Cloud component accrues at hourly intervals. All billing computations are conducted in Coordinated Universal Time (UTC). To view billing information, log into Confluent Cloud and visit the Billing & payment screen.

Confluent Cloud billing integrates with Google Cloud Platform, Microsoft Azure, and Amazon Web Services. Sign up with your cloud provider to pay via your cloud provider billing account.

Annual commitments

Confluent Cloud offers the ability to make a commitment to a minimum amount of spend over a specified time period. This commitment gives you access to discounts and provides the flexibility to use this commitment across the entire Confluent Cloud stack, including any Kafka cluster type, ksqlDB on Confluent Cloud, Connectors, and Support.

With annual commitments you can view the total amount of accrued usage during the commitment term and the amount of time left on your commitment.

If you use more than your committed amount, you can continue using Confluent Cloud without interruption. You will be charged at your discounted rate for usage beyond the committed amount until the end of your commitment term. Commitments are minimums, and there is no negative impact to exceeding your committed usage. If you exceed this minimum, overage charges will be billed to the payment method set for your organization.

Contact Confluent to learn more about annual commitments.

Billing profile

Important

If your organization is using RBAC, then only users who are assigned the OrganizationAdmin role can view the Billing & payment screen. For details, refer to Confluent Cloud RBAC Roles.

To view your billing profile, navigate to the Billing & payment screen and select the Payment details & contacts tab.

Confluent Cloud Payment details page

You can obtain your Cloud Organization ID, edit your billing information, add an address for tax purposes, or claim a Promo Code.

You can use all major credit cards with Confluent Cloud. To switch to invoicing, contact the Confluent sales team. Invoicing requires a minimum annual commitment.

Credit card payment receipts or invoices are emailed to the address that was initially provided during sign up for Confluent Cloud. To change the billing email address, click the Change button next to the email address field under Payment info, or contact your account team.

The invoice can only be sent to a single email address.

Billing Dimensions

Confluent Cloud offers basic, standard, and dedicated Kafka cluster types. The billing dimensions vary by cluster type.

Dimension summary

Clusters are billed based on the dimensions listed in the following tables.

Basic clusters

The following table summarizes the billing dimensions for Basic clusters. The following sections contain more details for some of the billing dimensions.

Dimension Unit of measure
Ingress Cost per GB written per hour
Egress Cost per GB read per hour
Storage Cost per GB stored per hour
Partitions Cost per partition per hour
Kafka Connect Cost per task per hour and throughput
ksqlDB Cost per Confluent Streaming Unit (CSU)
Cluster Linking Cost per hour & data sent/received

Standard clusters

The following table summarizes the billing dimensions for Standard clusters. The following sections contain more details for some of the billing dimensions.

Dimension Unit of measure
Base price Cost per hour
Ingress Cost per GB written per hour
Egress Cost per GB read per hour
Storage Cost per GB stored per hour
Partitions Cost per partition per hour
Kafka Connect Cost per task per hour and throughput
ksqlDB Cost per Confluent Streaming Unit (CSU)
Cluster Linking Cost per hour & data sent/received
Connector events and audit log Cost per GB of data read

Dedicated clusters

The following table summarizes the billing dimensions for Dedicated clusters. The following sections contain more details for some of the billing dimensions.

Dimension Unit of measure
CKU price Cost per CKU per hour
Ingress Cost per GB written per hour
Egress Cost per GB read per hour
Storage Cost per GB stored per hour
Kafka Connect Cost per task per hour and throughput
ksqlDB Cost per Confluent Streaming Unit (CSU)
Cluster Linking Cost per hour & data sent/received
Connector events and audit log Cost per GB of data read

Partitions

Confluent Cloud charges for partitions on Basic and Standard clusters. You are charged for the number of unique partitions that exist on your cluster during a given hour. Basic clusters receive 10 partitions free of charge, and Standard clusters receive 500 partitions free of charge. Dedicated clusters have no partition-based charges.

Internal Kafka topic partitions and storage (for example, __consumer_offsets) are not billable.

Cluster Linking

A cluster link sends data from a “source cluster” to a “destination cluster”. The destination cluster must be a Dedicated Confluent Cloud cluster with internet networking, as described in Supported Cluster Types for Cluster Linking.

Confluent Cloud clusters that use Cluster Linking are charged based on the number of cluster links and the volume of mirroring throughput to or from the cluster. A detailed breakdown for Cluster Linking billing is provided below.

Dimension Unit of measure Description
Cluster link Cost per link per hour

$0.50/hour per cluster link. This charge is split between the Source and Destination clusters; so, each cluster will accrue $0.25/hour per cluster link for which it is the source or destination.

A cluster link must be created by a Confluent Cloud user. It contains a source cluster, a destination cluster, and security credentials. You can have an unlimited number of mirror topics on a cluster link. It is possible to create multiple cluster links with the same source cluster, destination cluster, and security configuration. Confluent does not de-duplicate these links.

Ingress (ClusterLinkingWrite) Cost per GB written per hour

There is a per GB cost for all data that a Confluent Cloud cluster receives over a cluster link. It is charged at the same price as the cluster’s price for Kafka ingress (KafkaNetworkWrite). If you use Cluster Linking between two Confluent Cloud clusters, then you will not be charged by a cloud provider for this ingress.

You are not be charged for Kafka ingress (KafkaNetworkWrite) in addition to the Cluster Linking ingress (ClusterLinkingWrite).

Egress (ClusterLinkingRead) Cost per GB read per hour

$0.25/GB for all data that a Confluent Cloud cluster sends over a cluster link. You are not charged by a cloud provider for this egress; Confluent pays the cloud provider egress.

You are not charged for Kafka egress (KafkaNetworkRead) in addition to the Cluster Linking egress (ClusterLinkingRead).

Note: Volume discounts are available. Contact your Confluent Cloud account team to find out more.

Note

If a source cluster or destination cluster is not a Confluent Cloud cluster, then that cluster will not accrue any charges.

Regional multiplier

Every Confluent Cloud cluster has a regional multiplier depending on its region and cloud provider. This regional multiplier is applied to the base prices. For example, a cluster in AWS in us-east-1 has a 1x regional multiplier, so its Cluster Linking per link price is the base $0.25. A GCP cluster in asia-east2 has a 1.2x regional multiplier, so its Cluster Linking per link price will be $0.25 * 1.2 = $0.30.

Using the Metrics API to monitor billable metrics

Each line item has a corresponding metric in the Confluent Cloud Metrics API:

Line Item Metric
ClusterLinkingPerLink io.confluent.kafka.server/cluster_active_link_count
ClusterLinkRead io.confluent.kafka.server/cluster_link_source_response_bytes
ClusterLinkWrite io.confluent.kafka.server/cluster_link_destination_response_bytes

Examples

Kafka Connect

If you use a dedicated cluster, connectors on Confluent Cloud run on your own dedicated Connect cluster. Confluent Cloud provisions the dedicated Connect cluster when you launch your first connecter. If you use a Basic or Standard Kafka cluster, your connector runs in multi-tenant Kafka Connect clusters. For the connectors running on a multi-tenant Connect cluster, there is no Connect capacity (ConnectCapacity) charge.

The dedicated cluster and fully-managed connectors are billed based on the following dimensions:

Dimension Unit of measure
Dedicated cluster Cost per hour
Task base price Cost per task per hour
Throughput Cost per GB written or read per hour

Fully-managed connector pricing is displayed in the Add Connector screen:

Confluent Cloud Connect Cluster Billing

Dedicated connect cluster hourly pricing is shown on the Review and launch screen the first time you launch a connector.

Confluent Cloud Connect Review and Launch

Dedicated cluster billing is shown as a line item on the Billing & payment > Billing screen.

Self-managed connectors have no billing mechanism themselves. However, note that using self-managed connectors may incur ingress, egress, and storage charges for your Kafka clusters running in Confluent Cloud.

ksqlDB

Fully-managed ksqlDB is billed based on the following dimension:

Dimension Unit of measure
Confluent Streaming Unit Cost per Confluent Streaming Unit per hour

In addition to the per-Confluent Streaming Unit charge, ksqlDB applications may influence Kafka ingress, egress, and storage.

Fully-managed ksqlDB pricing is displayed in the Add an Application screen:

Confluent Cloud |ksql-cloud| Application Billing

Connector events and audit log

Dimension Unit of measure
Confluent Streaming Unit Cost per GB of data read from audit log topics

Connector events and audit logging operate from the Audit Log cluster. Consumption charges for both connector events and audit logging are combined on your bill. For more information, see Confluent Cloud Consumption Metrics for Marketplace Deployments.

Support

Support plans are available for purchase from the Confluent Cloud Console at https://confluent.cloud/support-plans. From this page, you can view your current plan or choose a different plan. If you have an annual commitment, support charges contribute to your total committed spend amount.

Support charges accrue hourly for as long as the support plan is active.

Important

Downgrade restrictions apply to support plan purchases. Your current support level will stay in effect until the end of the current calendar month. However, if you downgrade within the month of purchase, your current support plan level is maintained until the end of the next full calendar month.

View invoices

You can view your current and past monthly invoices by navigating to the Billing tab on the Billing & payment screen. To view invoices from past months, select an option from the dropdown.

Promo codes

If you have a promotional code for Confluent Cloud, you can use one of the following options to claim the code:

  • Navigate to the Payment details & contacts tab on the Billing & payment page and click + Promo code.

    Confluent Cloud Promo Code
  • On the New cluster screen, after you click Continue, enter the promotional code before you click Launch.

    Confluent Cloud Promo Code