Confluent Platform Subscription Definitions and Rules
Catalog row in Vendor License Sources · Cited
- Kind
- Product terms
- Format
- Applies to
- Incorporated into Confluent Platform Orders: licensed components, Node, Flink Node and Confluent Private Cloud Node definitions, environment classes, add-on products and support scope. Applies to Orders entered into after 2025-10-27.
- Evidence
- Confluent Platform is counted per Node, excluding client-only applications
- Confluent Platform is counted per Node, excluding client-only applications (CP D&R, Node note)
- Confluent Platform use may not exceed the purchased quantity
- Hot standby instances count as Production
- Supporting one component pulls the whole cluster under subscription
- Kafka Streams with Confluent Platform requires the Kafka Streams support add-on
- Flink Nodes are sized in vCPUs or hyperthreads, up to 8 per Flink Node
- Flink Nodes are sized in vCPUs or hyperthreads, up to 8 per Flink Node (CP D&R, Flink Node)
- A Confluent Private Cloud Node is capped by cores, drives, capacity and RAM
- A Confluent Private Cloud Node is capped by cores, drives, capacity and RAM (CP D&R, Confluent Private Cloud)
- ksqlDB add-on Nodes cannot be reallocated
- A Connector Pack covers up to five commercial connectors
- CSFLE add-on fees count every Node in the cluster
- Multi-Region Clusters and Tiered Storage are not licensed for Confluent Platform Edge
- Definitions and rules apply by Order date
- A Platform subscription does not narrow Community License rights