We are at re:Invent 2026Book my merch
Cloud Intelligence™Cloud Intelligence™

Confluent Cloud

Confluent Cloud spend, by cluster and connector.

Cloud Intelligence™ imports your Confluent Cloud billing every six hours: Kafka, Connect and ksqlDB, by environment, resource and billing line type. Right next to the rest of your cloud and data spend.

BillingAdmin API key · Historical billing on connect · Refreshed every 6 hours

Confluent Cloud · October
$72,400
Kafka71%Connect18%ksqlDB11%
Kafka clusters
9
Connector tasks
120
Environments
4
By resource and line type
orders-prod KAFKA_NUM_CKUS$21,300
clickstream KAFKA_NUM_CKUS$14,800
s3-sink CONNECT_NUM_TASKS$7,600
fraud-ksql ksqlDB$5,900
cdc-postgres CONNECT_NUM_TASKS$4,700

Trusted by teams running streaming data on Confluent

Akamai
Blumira
Chess.com
Current
OneFootball
Promptly
Recurly
Lusha
Mux

what we import

Confluent data, in the dimensions you already use.

Every charge maps to standard Cloud Analytics dimensions for organization, resource, product and line type, plus labels for service, category, resource name and environment.

Cloud AnalyticsConfluent CloudExample
ProviderConfluent CloudConfluent Cloud
Billing accountOrganization IDorg-abc12
Project/Account IDResource IDlkc-ab1cd
ServiceProduct nameKafka
SKULine typeKAFKA_NUM_CKUS
Plus Confluent Cloud labels
ServiceCategoryResourceEnvironment
Refreshed every 6 hours · Historical billing on connect

what you can do with it

From the Confluent bill to a decision

Cost by environment

Slice by environment, resource, product or billing line type.

Kafka vs everything else

See how much of the bill is Kafka versus Connect and ksqlDB.

CKUs vs connector tasks

Cluster capacity and connector task spend, side by side.

Next to your clouds

Confluent Cloud in the same reports as your other providers.

Budgets and alerts

Guardrails on streaming spend before the invoice lands.

Allocations

Put Confluent spend on teams by environment or resource.

live in hours

Connect Confluent Cloud in three steps

1

Create a Cloud API key.

Assign a service account the BillingAdmin role, then copy the key and secret.

2

Connect in the catalog.

Enter your organization ID and key:secret, then test the connection.

3

Reports in hours.

Historical billing imported on connect. We email you when it's ready.

Billing data only. Disconnect any time.

Start free

Frequently asked
questions

How do we connect Confluent Cloud?

Search for Confluent Cloud in the integrations catalog, select Connect, and enter your organization ID and Cloud API key. Test the connection, then save.

What credentials do we need?

Your organization ID (for example org-xxxxx) and a Cloud API key, entered as key:secret, for a service account with the BillingAdmin role on the organization. The secret is only shown once, so copy it when you create the key.

How fresh is the data?

We refresh your Confluent Cloud billing data every 6 hours. Data typically becomes available within 48 hours of Confluent generating it.

Do we get historical data?

Yes. We import your historical billing data when you connect, which can take a few hours, and email you when it's ready in Cloud Analytics.

Which dimensions and labels are available?

Organization ID maps to billing account, resource ID (such as a Kafka cluster) to project, product name (Kafka, Connect, ksqlDB) to service, and billing line type to SKU. Service, category, resource and environment labels are also available.

How does Confluent show up next to other providers?

Confluent Cloud appears as its own provider in Cloud Analytics, using the same standard dimensions as your other providers. You can group, filter and compare it in the same reports.

Connect Confluent Cloud. Know what every cluster costs.

Free to start. One API key. Reports in hours.