If you've started researching commercial RabbitMQ licensing, you've probably run into the term "per-core pricing" and walked away more confused than when you started. What counts as a core? What's included in the license? How does the MSP model differ from buying direct?
This post answers all of it — with the same directness we use on sales calls with real clients.
How is RabbitMQ commercial licensing structured?
Commercial RabbitMQ — the Tanzu RabbitMQ distribution from Broadcom — is licensed by vCPU core count. Not by users, not by messages, not by throughput. By the number of virtual CPU cores your RabbitMQ brokers run on across all environments.
That includes production and non-production. If you're running RabbitMQ on a 12-core VM in production and a 4-core VM in QA, you're licensing for 16 vCPUs in total. There's no production-only option through Broadcom.
Two vCPUs count as one physical core for licensing purposes — a nuance that often surprises teams when they first price out a quote.
What does the license actually include?
A commercial RabbitMQ license unlocks several things that aren't available in the open-source distribution:
- LTS release access. Commercial subscribers can stay on a major version for approximately two years with continued security patches and bug fixes.
- Patched commercial builds. Broadcom releases commercial-only iterations of each version with CVE fixes available only to licensed users.
- Repository access. Licensed customers receive access to a hosted repository (via JFrog) containing all commercial package formats. Downloads are self-service and persistent.
- Included product support. Basic licensing includes product support with ticket access covering product-level issues — bugs, configuration guidance, and escalation.
What is Broadcom's minimum licensing threshold?
This is where smaller deployments run into a wall. Broadcom goes to market with a minimum purchase of 72 cores. If you have a 12-core production deployment, you're still purchasing 72 cores of licensing under Broadcom's direct model.
That's a significant cost floor — and it's the primary reason most sub-72-core organizations either stay on open source or look for an alternative path.
"Broadcom requires a minimum of 72 cores licensed... technically you guys would require 15 cores, but because Broadcom minimums are 72 cores, you guys would be required to procure 72 cores of licensing as opposed to 15."
— Tyler Eastridge, Stark Engagement Call, June 2026
How does AceMQ's licensing model differ from buying direct?
AceMQ is the only RabbitMQ MSP (Managed Service Provider) globally. Through a purpose-built partnership with Broadcom, AceMQ pre-purchased a block of commercial licenses and can resell them independently — which means we're not bound by Broadcom's 72-core floor.
AceMQ's minimum licensing threshold is substantially lower than Broadcom's direct minimum. This structure was specifically designed for the reality that the vast majority of RabbitMQ deployments — roughly 90% of the customers we work with — are sub-72-core environments.
Your contract is with AceMQ, not Broadcom. You get the same commercial builds, the same patched repositories, the same Broadcom-maintained release line — but sized and priced for your actual deployment.
Can I lock in pricing for a multi-year term or public tender?
Yes. Multi-year commitments — typically one-year or three-year terms — are standard, and the per-year cost decreases with longer commitment terms. For public-sector tenders and procurement processes that require price certainty through a specific end date, we can include committed pricing language appropriate for those RFPs.
If your organization is on a procurement cycle or using a preferred reseller/integrator, we can also work through those channels. AceMQ regularly structures deals where a customer's existing approved vendor is the primary contracting party and we supply the license and support behind the scenes.
How do I figure out how many cores I actually need to license?
Start with a count of every environment where RabbitMQ runs: production, staging, QA, UAT, and development if RabbitMQ is deployed there. For each environment, count the vCPU cores allocated to RabbitMQ broker nodes.
A few things to keep in mind:
- All environments count. Production-only licensing isn't available through Broadcom or AceMQ on the commercial path.
- vCPUs, not physical cores. If you're on virtual infrastructure, count your virtual CPUs.
- Right-sizing matters. We work with clients to review whether their RabbitMQ nodes are over-provisioned. Reducing core counts before licensing reduces cost.
"Because it is a per-core basis, that's really the only way that you could save some money on this quote — downsize the environments."
— Tyler Eastridge, Press Ganey call, May 2026
What's the difference between licensing support and managed support?
This distinction matters and often gets blurred. The support included with a commercial RabbitMQ license covers product-level issues — bugs, configuration questions, and escalation for confirmed RabbitMQ defects. It's not designed for emergency incident management, proactive performance tuning, architecture review, or RabbitMQ operations outside the product boundary.
If your team needs that — fast P1 response, architectural guidance, hands-on operational support — that's managed support, and it's a separate engagement layered on top of licensing. AceMQ offers both, and many clients carry both: a commercial license for the compliant builds plus a managed support retainer for operational coverage.
"Most of our licensing customers don't really raise tickets. They just really want the compliance. Our open-source support is more for customers that don't really need the compliance, but they want more of that high-touch, low-response-time, operational, incident-management-style support."
— Tyler Eastridge, Press Ganey call, May 2026
Ready to price out your deployment?
Every organization's licensing math is different. If you want a clear-eyed view of what commercial RabbitMQ licensing would actually cost for your deployment — including a comparison of one-year versus multi-year terms and how AceMQ pricing compares to Broadcom's direct model — contact our RabbitMQ support team and we'll put a real number in front of you.
Where a partner changes the outcome: how partner escalation works with Broadcom.
Go deeper on RabbitMQ
- GuideThe RabbitMQ Performance Tuning GuideRead the guide
- GuideThe RabbitMQ Streams GuideRead the guide
- GuideThe RabbitMQ Reliability Guide: Ten Failure Patterns and Their FixesRead the guide
- GuideThe RabbitMQ Disaster Recovery GuideRead the guide
- GuideThe RabbitMQ Clustering and Sizing GuideRead the guide
- GuideThe RabbitMQ on Kubernetes GuideRead the guide
- GuideThe RabbitMQ Migration GuideRead the guide
- GuideThe RabbitMQ Security and Hardening GuideRead the guide
- GuideThe RabbitMQ Monitoring and Alerting GuideRead the guide
- ComparisonManaged RabbitMQ Options ComparedSee the comparison
- ComparisonMessage Broker Support Options ComparedSee the comparison
- ResearchWhat Breaks in Production RabbitMQ: 145 Support Tickets, 2023 to 2026Read the research
- ResearchRabbitMQ in Production 2026: What 22 Assessed Estates Actually RunRead the research
- ResearchThe RabbitMQ CVE Register, 2026 EditionRead the research