Effective April 10, 2025, Broadcom requires a minimum order of 72 cores for every core-based product in its portfolio — and Tanzu RabbitMQ is licensed as a core-based product, so it is not exempt. A deployment running on 16 or 24 real cores still licenses 72. The floor moved from 16 cores to 72 in one step, and it applies to new orders and renewals alike.
For a small or mid-size RabbitMQ estate, that is the actual number that matters — not the per-core list price, which is easy to find. What is harder to find is what a deployment under the floor is actually supposed to do about it.
What the 72-core minimum actually says
The rule is an order-size floor, not a per-product carve-out. Broadcom's language covers core-based products broadly: any new order or renewal must be placed for at least 72 cores. It replaced a 16-core minimum that had applied since the VMware acquisition closed.
This did not originate as a RabbitMQ-specific policy — it landed across the commercial catalog Broadcom inherited from VMware, and Tanzu RabbitMQ sits inside that catalog on the same core-based licensing model as the rest of it. If your Tanzu RabbitMQ quote is core-based, which it is, the 72-core floor applies to it the same way it applies to vSphere or Cloud Foundation orders.
Why a floor this high, for a broker license
RabbitMQ clusters are usually small. A production cluster sized for a few thousand messages per second commonly runs on three nodes with single-digit vCPU counts each — nowhere near 72 cores. That is precisely the mismatch: the licensing floor is set at the scale of a large VMware Cloud Foundation deployment, not at the scale of a typical message broker cluster.
The practical effect is a step-function cost. A deployment needing 18 cores of RabbitMQ licensing and a deployment needing 70 cores pay close to the same amount, because both round up to the 72-core minimum. Below that line, core count stops being the variable that drives your bill.
What actually needs the commercial license, and what doesn't
Open-source RabbitMQ, distributed under the Mozilla Public License 2.0, is free to run in production, including commercially. Nothing about the 72-core minimum changes that. What the commercial license buys is specific:
- Patched builds past community end of life — security fixes backported to a version the open-source project has stopped maintaining
- Support SLAs — a defined response-time commitment instead of community forums
- Extended support windows for versions that would otherwise be past end of life, relevant if you are still on 3.13.x or earlier
- Warm standby / disaster recovery tooling for cross-site replication, which is a commercial-only feature
If none of those apply to your deployment yet, the 72-core minimum is a reason to stay on community RabbitMQ longer, not a bill you have to pay regardless.
How smaller deployments actually get licensed
Three paths exist for a deployment under the floor, and they are not equally good:
- License 72 cores anyway. Straightforward, and the right call if you expect to grow into that footprint within the license term, or if you are bundling RabbitMQ into a larger core-based order that already clears 72 on its own.
- Consolidate onto fewer, denser nodes to close the gap. Fewer physical cores licensed at a higher per-node density gets you closer to justifying the floor, though it does not eliminate the mismatch for a genuinely small cluster.
- Take commercial RabbitMQ support from a partner sized to your actual deployment instead of a direct Broadcom core-based order. This gets you patched builds and an SLA without buying 72 cores of licensing for a cluster that needs a fraction of that.
Option three is the one most small-to-mid deployments end up taking, because it decouples "do I need commercial patching and support" from "do I have 72 cores worth of workload." Those are two different questions, and Broadcom's order minimum answers only the second one for you.
Where to get a real number before deciding
Talk to AceMQ about your deployment size
FAQ
Does Broadcom have a 72-core minimum licensing requirement?
Yes. Effective April 10, 2025, every new order or renewal for a core-based Broadcom product must cover at least 72 cores, regardless of how many cores the deployment actually uses. Tanzu RabbitMQ is licensed as a core-based product, so it falls under the same floor.
Is RabbitMQ owned by VMware or Broadcom?
Broadcom, following its 2023 acquisition of VMware. Tanzu RabbitMQ is sold and licensed through Broadcom's enterprise software portfolio, on the same commercial terms as the rest of that catalog.
Is RabbitMQ free for commercial use?
The open-source broker is free under the Mozilla Public License 2.0, including for commercial use. What costs money is the Tanzu RabbitMQ commercial distribution — patched builds, support SLAs, and extended support for versions past community end of life.
What happens if my deployment only needs 20 or 30 cores?
You still license 72. The per-core price does not change with volume below the floor, so a 30-core deployment pays for 72 cores at list price unless it works with a partner who can structure the order differently.
How does AceMQ's RabbitMQ licensing differ from Broadcom's?
AceMQ sells commercial RabbitMQ support and backported security patches sized to the deployment you actually run, without requiring a 72-core minimum order. It is a support and patching relationship, not a resale of Broadcom's minimum order size.
Can I avoid the 72-core minimum entirely?
Only by not buying a direct core-based Broadcom order. Staying on community RabbitMQ with a third-party commercial support arrangement, or consolidating workloads onto fewer, denser nodes to get closer to the floor, are the two practical paths.
