Get a Quote for Licensing or Support
Tell us the platform, the rough size of the estate and the response time you need, and you get a written quote with the SLA and scope stated in it — priced for the cores you actually run. AceMQ is the only RabbitMQ managed-service provider globally that licenses commercial RabbitMQ below Broadcom’s standard 72-core minimum, and a Broadcom Partner of the Year for VMware licensing and renewals.
130+ enterprise customers · 26+ countries · 24/7 coverage with a 15-minute emergency SLA
Trusted for mission-critical messaging by teams in finance, healthcare, defense and telecom
The Featured Authorized Partner for RabbitMQ — named by the engineers who build it
AceMQ is the Featured Authorized Partner for RabbitMQ, named by the RabbitMQ Core Engineering Team — the people who write and maintain the broker. That recognition covers RabbitMQ support, licensing and professional services, and it makes AceMQ the only RabbitMQ partner with a direct line to the core team. When an escalation needs an answer that is not in the documentation, it does not stop at a support tier.
You do not have to take our word for it — RabbitMQ lists AceMQ on its own site.
See AceMQ listed on rabbitmq.comWhat to have ready
None of this is required to send the form — we can work it out on the call. Having it to hand just means the quote comes back accurate the first time.
Which technology, and which edition
RabbitMQ, Kafka, Redis, IBM MQ, VMware or one of the 40+ other platforms we support — and whether you are on the open-source distribution or a commercial one.
Core or node count, across every environment
Licensing is counted on production, pre-production, staging and QA together, not production alone. An approximate number is enough to quote from.
The response time you actually need
A 15-minute emergency SLA and next-business-day cover are priced very differently. Tell us what downtime costs you and we will tell you which tier is honest for your case.
Your renewal or go-live date
Renewals concentrated near a vendor deadline take longer to turn around. The earlier we know the date, the more room there is to compare options.
What you get back
Line-item pricing, per core
Not a range and not a “starting from”. The actual number for the core count you give us, itemised so procurement can read it without a follow-up call.
The SLA in writing
Response commitments and coverage hours stated in the document, along with what is explicitly not covered — the part most support quotes leave you to discover later.
Term options
One, two and three-year pricing side by side, so you can see whether a longer commitment is actually cheaper for your estate rather than being told it is.
An honest scope
If you do not need what you asked for — a licence when the answer is extended support, or nothing at all because your version is current — the quote says so.
How the quote process works
Send the form
Two minutes. No sales sequence attached to it.
A short scoping call
A senior engineer, not an SDR, confirms the sizing and the coverage you need.
Written quote
Line-item pricing with the SLA and scope stated in writing, so it can go straight to procurement.
Looking for detail before you ask? RabbitMQ licensing, VMware licensing and renewals, and enterprise support each cover pricing structure and what is included.
Before you send it
Do I have to know my exact core count?
No. An approximate number is enough to produce a quote you can plan against, and the sizing call exists to firm it up. The one thing worth checking beforehand is whether you have counted non-production — staging, QA and DR all count toward licensing, and leaving them out is the usual reason a first number moves.
Is this going to put me into a sales sequence?
No. A senior engineer responds, not an SDR, and there is no automated follow-up attached to the form. If the answer is that you do not need what you asked for, that is what you will be told.
How fast does the quote come back?
Within 24 hours of an agreed core count. The delay in most licensing conversations is establishing that count across environments rather than producing the pricing, which is why the questions above matter more than the form does.
What if my version is end of life?
Then a licence is probably the wrong purchase. Commercial licensing reaches back to 3.13.x; AceMQ support reaches back to 3.8.x. If you sit between those, extended support is the entitlement you need, and the quote will reflect that rather than selling you a licence that does not cover you.