Message Broker pricing
Choose a Community, Pro, or Enterprise node allowance for one Message Broker cluster. Pricing stays predictable without per-message, per-user, per-stream, per-queue, retained-history, or customer-funded-storage charges.
Message Broker pricing is based on broker nodes in one cluster. The product entitlement does not meter messages, users, streams, queues, retained history, or customer-funded storage.
Message Broker
$0
Free, non-expiring entitlement
Included
Expansion
Message Broker
$4,800/year
$400/month equivalent, billed annually
Included
Expansion
Message Broker
$12,000/year
$1,000/month equivalent, billed annually
Included
Expansion
A licensed node is a Message Broker server process in the entitled cluster. Client applications, SDKs, CLIs, and one-shot CI tools are not billable nodes. Paid editions are billed annually; monthly figures are equivalents for comparison, not monthly purchase options.
Paid editions increase the committed node allowance. They do not imply an unverified Kafka listener, cross-site durability outcome, or identity-provider integration that the current product does not yet support.
| Capability | Community | Pro | Enterprise |
|---|---|---|---|
| License shape | Free, non-expiring entitlement for up to 3 nodes in one cluster. | $4,800/year for up to 6 nodes in one cluster. | $12,000/year for up to 12 nodes in one cluster. |
| Streams: publish, fetch, and replay | Included within documented private-beta limits. | Included within documented private-beta limits. | Included within documented private-beta limits. |
| Cursors and consumer groups | Included within documented private-beta limits. | Included within documented private-beta limits. | Included within documented private-beta limits. |
| Shared queues | Claim, renew, acknowledge, nack, retry, and dead-letter workflows are included. | Claim, renew, acknowledge, nack, retry, and dead-letter workflows are included. | Claim, renew, acknowledge, nack, retry, and dead-letter workflows are included. |
| Health, audit, metrics, and diagnostics | Documented routes are included; metrics remain opt-in and route signals are not outcome proof. | Documented routes are included; metrics remain opt-in and route signals are not outcome proof. | Documented routes are included; metrics remain opt-in and route signals are not outcome proof. |
| Configured authentication modes | API-key, mTLS trust-file, and trusted-header modes are available as documented. | API-key, mTLS trust-file, and trusted-header modes are available as documented. | API-key, mTLS trust-file, and trusted-header modes are available as documented. |
| Replication routes | Status, worker polling, and target-apply routes are present; cross-site durability and failover outcomes require confirmation. | Status, worker polling, and target-apply routes are present; cross-site durability and failover outcomes require confirmation. | Status, worker polling, and target-apply routes are present; cross-site durability and failover outcomes require confirmation. |
| Kafka network listener | Not supported; compatibility work is prototype-only. | Not supported; compatibility work is prototype-only. | Not supported; compatibility work is prototype-only. |
| Support path | Self-service documentation; support is licensed separately. | Support is licensed separately from the product entitlement. | Support and rollout coordination are licensed separately. |
Next step