Skip to main content

Licensing

OSO Kafka Backup Enterprise uses Ed25519-signed license files validated entirely offline. No license server, no phone-home, no network dependency. The license file is self-contained and cryptographically verifiable.

License Model​

TierTargetFeaturesPricing
OSSEveryoneCore backup/restore, PITR, three-phase restore, all storage backends, retention (prune)Free (MIT)
EnterpriseCompliance-driven and multi-cluster platformsAll enterprise features (Schema Registry, Apicurio, Confluent RBAC, CSFLE metadata, MSK KRaft migration, GDPR erasure) and supportAnnual site licence covering all your Kafka clusters — no per-cluster or per-broker count
TrialEvaluationAll enterprise features, 14 days, built into the binaryFree

Licensed Features​

Each license encodes which features are enabled:

Feature FlagDescription
schema_registryConfluent and Apicurio Schema Registry backup & restore
oauthOAuth for Kafka and Schema Registry
rbacMDS RBAC capture and, from 0.8.0, mapped role-binding and Kafka ACL recovery
migrations:msk-kraftAWS MSK ZooKeeper to KRaft migration execution
migrations:msk-kraft:planAWS MSK ZooKeeper to KRaft plan/precheck entitlement
encryptionConfluent CSFLE and DEK Registry metadata backup
maskingData masking for non-production (planned)
auditAudit logging (planned)
wasmWebAssembly plugin system (planned)
erasureGDPR erasure: restore-time key suppression (redaction and crypto-shredding to follow)
supportPriority support SLA entitlement

Obtaining a License​

Free Trial​

The enterprise binary includes a 14-day free trial on first run — no signup, no credit card. Just install the enterprise binary and start using all features immediately.

For licensing questions or a commercial subscription, contact:

Purchase a License​

Buy an Enterprise licence at enterprise.kafkabackup.com or contact sales directly:

The commercial licence is a site licence covering your Kafka clusters. See the portal for current subscription terms.

License File Format​

Licenses are distributed as PEM-encoded files containing a JSON payload signed with Ed25519:

-----BEGIN KAFKA-BACKUP LICENSE-----
eyJsaWNlbnNlX2lkIjoiYWJjZGVmMTItMzQ1Ni03ODkwLWFiY2QtZWYxMjM0
NTY3ODkwIiwiY3VzdG9tZXJfaWQiOiJjdXN0XzEyMzQ1NiIsImN1c3RvbWVy
...
-----END KAFKA-BACKUP LICENSE-----

The license payload contains:

FieldDescription
license_idUnique identifier (UUID)
customer_idCustomer identifier
customer_nameOrganization name
customer_emailContact email
tierstandard or enterprise
featuresList of enabled feature flags
max_clustersMaximum Kafka clusters (optional)
max_nodesMaximum brokers across all clusters (optional)
issued_atIssue date (ISO 8601)
expires_atExpiry date (optional — null = perpetual)
schema_versionLicense format version

License Activation​

Apply from File​

kafka-backup license apply --file /path/to/license.key

This validates and installs the licence file. Check the reported destination and the discovery order below, especially when an explicit licence environment variable is configured.

Output:

License applied successfully.
License ID: abcdef12-3456-7890-abcd-ef1234567890
Customer: Acme Corp
Tier: Enterprise
Saved to: /home/user/.config/kafka-backup/license.key

Verify a License (Without Applying)​

kafka-backup license verify --file /path/to/license.key

Output:

License is valid.
License ID: abcdef12-3456-7890-abcd-ef1234567890
Customer: Acme Corp
Tier: Enterprise
Features: encryption, schema_registry, rbac, audit, support
Expires: 2027-01-15 (285 days remaining)

Check Current License Status​

kafka-backup license info

Output when licensed:

License ID: abcdef12-3456-7890-abcd-ef1234567890
Customer: Acme Corp (acme@example.com)
Tier: Enterprise
Features: encryption, schema_registry, rbac, audit, support
Max clusters: 5
Issued: 2026-01-15
Expires: 2027-01-15 (285 days remaining)
Status: Valid

Output when unlicensed:

No license found. Running in OSS mode.

To activate enterprise features:
kafka-backup license apply --file /path/to/license.key

Get a license at https://enterprise.kafkabackup.com

Upgrade to 0.8.0​

Enterprise 0.8.0 rotates the commercial signing key. A licence issued for 0.7 or earlier must be reissued for the new binary. Download it again from the commercial portal, verify it with the new binary, and install it before relying on Enterprise operations. Reissuance preserves the original paid term and entitlements; it does not extend expiry. New commercial files require 0.8.0 or later, so keep the matching old licence if you must continue using an old binary. The built-in fourteen-day evaluation needs no signed licence file.

License Discovery​

The license is loaded automatically at startup. The tool searches these locations in order:

PrioritySourceDescription
1ENTERPRISE_LICENSE_KEY env varBase64-encoded PEM content (for CI/CD)
2ENTERPRISE_LICENSE_FILE env varPath to license file
3/etc/kafka-backup/license.keyDefault for containers and Kubernetes
4~/.config/kafka-backup/license.keyDefault for CLI users

Kubernetes Secret​

For Kubernetes deployments, mount the license as a secret:

apiVersion: v1
kind: Secret
metadata:
name: kafka-backup-license
namespace: kafka-backup
type: Opaque
stringData:
license.key: |
-----BEGIN KAFKA-BACKUP LICENSE-----
eyJsaWNlbnNlX2lkIjoiYWJjZGVmMTItMzQ1Ni03ODkwLWFiY2QtZWYxMjM0
...
-----END KAFKA-BACKUP LICENSE-----

Mount it in your deployment:

volumes:
- name: license
secret:
secretName: kafka-backup-license
volumeMounts:
- name: license
mountPath: /etc/kafka-backup
readOnly: true

Environment Variable (CI/CD)​

For CI/CD pipelines, pass the license as a base64-encoded environment variable:

export ENTERPRISE_LICENSE_KEY=$(base64 < license.key)
kafka-backup backup --config backup.yaml

Requested features and expiry​

Check the release-specific behaviour before scheduling an Enterprise operation. Enterprise 0.8.0 refuses requested but unlicensed authorization work with exit code 2 before transfer or permission mutation. A successful Kafka data backup alone does not prove that permissions were captured.

At trial expiry, renew before starting another Enterprise operation. Previously created permissions remain in place. Status and licence-file verification remain available. Commercial OAuth has its documented grace period; evaluations do not gain that grace.

See the evaluation guide for persistent state, restart checks and activation commands.

Offline Validation​

License validation is fully offline:

  • The Ed25519 public key is embedded in the binary at compile time
  • No network calls, no license server, no DNS dependency
  • Works in air-gapped environments
  • Validation checks: signature integrity, expiry date, feature flags

Security​

  • The private signing key is held exclusively by OSO DevOps — never distributed
  • The public verification key is embedded in the enterprise binary
  • Licenses cannot be forged or modified without the private key (Ed25519 is 128-bit security)
  • License files contain customer information but no secrets — safe to store in version control or config management

FAQ​

Q: What happens when the license expires? Enterprise features stop activating. The binary continues to work as an OSS-equivalent tool. No data loss, no downtime.

Q: Can I use the same license on multiple machines? Yes. The licence is a site licence: it is not tied to a machine or MAC address and is not limited by the number of clusters or brokers. The max_clusters / max_nodes fields in the payload are informational and not enforced by the binary.

Q: Do I need internet access to validate the license? No. Validation is 100% offline using Ed25519 signature verification.

Q: What if I lose my license file? Contact sales@oso.sh — we can reissue your license from our records.