This topic describes how to configure the license for manual deployments of Confluent Platform components. For
information on how to configure licenses in automated deployments of Confluent Platform with Confluent Operator, see
Configure licenses with Confluent Operator.
A developer license allows full use of Confluent Platform features free of charge for an indefinite duration.
However, the license is limited to a single broker configuration per cluster. The developer license
gives developers the freedom to try the Confluent Platform commercial features available in a non-production setting.
The developer license also accommodates multiple single-broker clusters so that developers can try
the Replicator between those instances, or develop failover applications,
for example. Those multiple single-broker clusters share the same license.
Adding a broker starts a trial license that expires in 30 days. You cannot revert from
a trial back to a developer license.
Trial (Evaluation) License
A trial (evaluation) license allows a free trial of commercial features in a production setting.
Expires after 30 days. The trial license is governed by the
Confluent evaluation licenses agreement.
The software ceases to function when the license expires. For details, see
Enterprise (Subscription) License
An enterprise license provides access to all Confluent commercial features for a production environment.
An enterprise license is an annual paid subscription that expires after 365 days. The software ceases
to function after the license expires. For details, see Expired licenses.
The following Confluent Platform components are under the Confluent Enterprise License:
Configure Component Licenses
You must configure a license for each individual Confluent Platform commercial component as
described in the following sections.
Each licensed component requires a valid license key to start up. After the
component starts up, it checks the license topic to use the latest valid license
There are two main topics that store license details of Confluent Platform components.
Confluent Control Center, Connect, and Replicator use the
_confluent-command topic on the
same Confluent Server cluster to store and look up their license.
For example, if you use Control Center to update the license, all other
licensed components that use the same
_confluent-command license topic
will be governed by that new license.
Each of these components have an option to specify a license key in their
respective properties file to be evaluated on startup. See below for the
component properties files. The components store this key on the
Confluent Server brokers use the
_confluent-license topic to store and look up the
When applying an updated license in Confluent Control Center, you must also provide an updated
license key in the Confluent Server configuration file
/etc/kafka/server.properties). The updated license is evaluated against
the current license information that is present in the
topic. If necessary, that original license is updated to the newly submitted
license, and the updated license is applied when the brokers restart.
For more information about managing licenses in Confluent Control Center, see
Managing Confluent Platform Licenses.
Confluent Control Center
For Control Center, the license key can be entered in the Control Center License tab,
or in the
confluent.license parameter in the
Configure the parameter
confluent.license in various Replicator
.properties files. For more
information, see Configure license for Replicator.
Configure the parameter
confluent.license in the
/etc/kafka/server.properties file. For more
information, see Migrate to Confluent Server.
Confluent Schema Registry
A license is required only when using the Schema Registry Security Plugins. For more information, see
Confluent Auto Data Balancer
A license is required only when using multiple broker configurations. Configure the parameter
confluent.license in the Kafka
server.properties file. For more information, see
Configure license for rebalancer.
Confluent MQTT Proxy
Configure the parameter
confluent.license in the MQTT Proxy
etc/confluent-kafka-mqtt/kafka-mqtt-production.properties file. For more information, see
Configure license for MQTT.
Confluent REST Proxy
A license is required only when using the REST Proxy Security Plugins. For more information, see
REST Proxy Authentication.
Add the license key for Operator and Confluent Platform components as described in Operator
Confluent Platform commercial connectors
The Confluent Platform commercial connectors can be used on an unlimited basis with the developer license for
single-broker clusters. Multi-broker clusters can use these commercial connectors for a 30-day trial
without an enterprise license key. After the trial period expires, Confluent Platform software ceases to function.
You must purchase an enterprise license to continue using commercial
connectors in a multi-broker cluster.
Refer to the individual connector documentation for the specific