Redpanda Enterprise unlocks features beyond the community edition by introducing a licensing mechanism that governs access to specific capabilities.
Let’s see Redpanda Enterprise in action, specifically focusing on its tiered features and how a license file dictates what’s available. Imagine you’ve just spun up a new Redpanda cluster. By default, it’s running in community mode.
# Check current Redpanda version and license status
rpk version
rpk cluster info
If you run rpk cluster info without a license, you’ll see something like this:
Cluster ID: <some-uuid>
Brokers: 3
State: running
...
License: Community Edition (Features: community)
Now, let’s say you’ve purchased Redpanda Enterprise and received a license file. This file is a JSON document containing a license_key and an expires_at timestamp, along with a features object that specifies what your license enables. For example, a common enterprise license might look like this:
{
"license_key": "REDPANDA-ENTERPRISE-XXXX-XXXX-XXXX-XXXX",
"expires_at": "2025-12-31T23:59:59Z",
"features": {
"admin_api": true,
"acl": true,
"metrics_v2": true,
"partition_balanceer": true,
"schema_registry": true,
"sasl": true,
"tls": true,
"wasm": true
}
}
To apply this license, you’d typically upload it through the Redpanda Console or use the rpk command-line tool.
# Apply the enterprise license using rpk
rpk license apply --file /path/to/your/redpanda-enterprise.json
After applying the license, if you check rpk cluster info again, you’ll see the change:
Cluster ID: <some-uuid>
Brokers: 3
State: running
...
License: Enterprise Edition (Expires: 2025-12-31T23:59:59Z, Features: admin_api, acl, metrics_v2, partition_balanceer, schema_registry, sasl, tls, wasm)
The key here is that the features object in the license file is a direct mapping to capabilities within Redpanda. When the admin_api is true, you gain access to endpoints for managing topics, configurations, and other cluster-level operations programmatically. If acl is true, you can set Access Control Lists to govern who can produce to or consume from specific topics. The partition_balanceer feature, when enabled, allows Redpanda to automatically redistribute partitions across brokers to ensure even load distribution, a crucial feature for performance and availability in larger clusters. schema_registry enables the built-in schema registry, vital for data governance and evolution in Kafka-compatible applications.
The mental model for Redpanda licensing is straightforward: the license acts as a feature gate. When you start Redpanda, it reads this license file (or fetches it if configured to do so from a license server). Based on the features object, it enables or disables specific internal modules and API endpoints. If a feature is listed as true in your license, that functionality is active. If it’s false or missing from the features object, the corresponding functionality will be unavailable, often resulting in an error if you try to use it. This granular control allows Redpanda to offer different tiers of service, from the free community edition to feature-rich enterprise packages tailored to specific needs.
The license expiration date is also critical. Once the expires_at timestamp passes, Redpanda will revert to community edition features, even if the license key itself remains valid. This is a hard stop; you’ll need to renew your license to regain access to enterprise features.
What most people don’t realize is that the rpk command can directly interact with these features. For instance, if your license doesn’t include acl, attempting to create an ACL using rpk acl create ... will fail with a specific error indicating that the feature is not licensed. Similarly, trying to access certain administrative endpoints via HTTP without the admin_api feature enabled will also result in an authorization error. The system doesn’t just hide the UI elements; it actively prevents the underlying operations from occurring.
Understanding the specific features enabled by your license is the next step to fully leveraging Redpanda Enterprise.