Broadcom does not publish a Tanzu RabbitMQ rate card, so every number circulating online is an estimate. What is knowable without a quote is the structure of the cost — and at 50, 100, and 500 cores, three different things end up driving the number: the 72-core minimum order floor, contract term length, and support tier. This is about that structure, not a fabricated price sheet.
Open-source RabbitMQ itself stays free under the Mozilla Public License 2.0 at every one of these sizes. What you're pricing is Tanzu's patched builds, SLA-backed support, and extended support for versions past community end of life.
The variable that dominates below 72 cores
Broadcom's minimum order size for core-based products, RabbitMQ included, is 72 cores per order or renewal. A deployment running 50 cores of real RabbitMQ workload does not license 50 — it licenses 72, because the order floor rounds up regardless of actual usage.
That means the honest way to think about a 50-core deployment's Tanzu cost is: whatever the per-core rate is, multiplied by 72, not by 50. The effective cost per core actually used is meaningfully higher than the list rate implies, because 22 of those 72 licensed cores aren't doing anything.
Where the floor stops mattering
At 100 cores, the math looks different. You're licensing 100 cores for 100 cores of workload — close enough to the floor that the minimum order size isn't costing you meaningfully inflated per-core pricing anymore. This is roughly the size where a direct Tanzu order starts making straightforward sense on its own terms, rather than as a floor you're forced into.
At 500 cores, the 72-core floor is irrelevant — you're an order of magnitude past it. What actually moves the number at this size is contract structure: one-year terms versus three-year fixed-price commitments billed annually, and which support tier you're buying. A three-year fixed-price term protects against list-price increases over the contract but commits you to the spend; a one-year term keeps you flexible but reprices at renewal.
What actually determines the quote
- Core count, rounded to the 72-core floor. Anything under 72 pays for 72. Above it, you pay for what you license.
- Term length. One-year versus multi-year fixed-price commitments trade flexibility for price protection.
- Support tier. Standard versus premium support levels carry different rates, independent of core count.
- Bundling. An order that combines RabbitMQ with other core-based products in the same portfolio sometimes prices differently than a standalone RabbitMQ order — this varies by account and is not published.
None of these are numbers Broadcom puts on a public page. Getting a written quote against your actual core count and preferred term is the only way to get a real figure, and it's worth doing before assuming a specific dollar amount from a forum post or a vendor's sales deck.
The alternative below the floor
FAQ
How much does RabbitMQ license cost?
Open-source RabbitMQ is free under the Mozilla Public License 2.0. Tanzu RabbitMQ, the commercial distribution, is priced per core with no published rate card — the real number depends on core count, term length, and support tier, and requires a quote.
Is RabbitMQ free for commercial use?
Yes, the open-source broker is free for commercial use. What costs money is Broadcom's Tanzu RabbitMQ distribution: patched builds, SLA-backed support, and extended support for versions past community end of life.
Is VMware Tanzu free?
No. Tanzu is Broadcom's commercial portfolio built around VMware's open-source projects, including RabbitMQ. The open-source project underneath it is free; the Tanzu distribution and support are licensed.
Is RabbitMQ owned by VMware?
RabbitMQ is now owned by Broadcom, following its 2023 acquisition of VMware. Broadcom maintains both the open-source project's commercial patching and the Tanzu RabbitMQ distribution.
Why does cost per core change so much between 50, 100, and 500 cores?
The 72-core minimum order floor means a 50-core deployment pays for 72 cores regardless — its effective cost per real core used is inflated. A 100-core deployment pays close to its actual usage. A 500-core deployment is large enough that term length and support tier, not the floor, become the variables that move total cost.
What is the cheapest way to license RabbitMQ below 72 cores?
Stay on open-source RabbitMQ and take commercial support and patching from a partner sized to your deployment, rather than placing a direct Broadcom core-based order that rounds up to 72 cores regardless of actual usage.