01
Lock-In Map
For each commercial platform: the license, the renewal date, the core count, the features in use, and which parts tie you in and which are habit.
Reduce License Costs
Vendor Lock-In: Three Ways to Cut Broadcom, Redis and Confluent License Costs
Vendor lock-in becomes a cost problem at renewal: Broadcom prices VMware and Tanzu per core with a 72-core minimum order, Redis moved off a permissive license after version 7.2, and Confluent is now owned by IBM. AceMQ offers three exits you can combine: independent support on the open-source build, licenses sized to the cores you run, or a planned move such as Redis to Valkey. Send your renewal date and core count for a quote reply within 1 hour.
- core minimum order in Broadcom's standard channel
- 72
- exits: independent support, right-sized licenses, a planned move
- 3
- enterprise customers
- 130+
Is This You?
You probably need this if…
- 01
A Broadcom renewal or quote arrived and the per-core number, or the 72-core minimum, does not match what you run
- 02
A small Tanzu RabbitMQ estate is being quoted as 72 cores
- 03
Your Redis version is 7.4 or later and legal has asked which license applies
- 04
Confluent is up for renewal after the IBM acquisition and nobody has listed which licensed features are actually in use
- 05
You pay a vendor mainly for patches and escalation, and the software underneath is open source
- 06
A budget round asks what it would cost to leave, and nobody can answer
- 07
You want a lower number without starting a migration project this year
Outcomes
Where you are now, and where you end up
Concrete state changes, not deliverable counts. This is what actually differs about your Infrastructure estate when the engagement closes.
Before
A renewal arrives as one number, with no view of how much is rate, how much is the minimum and how much is term.
After
Cores counted the way Broadcom counts them, the two minimums shown, the editions and terms priced side by side.
Before
A small RabbitMQ estate is billed as though it were 72 cores.
After
Commercial RabbitMQ licensed per core through AceMQ at the cores you run, with security patches and CVE backports included.
Before
Support and patches come bundled in a license you would not otherwise buy.
After
The open-source build in production under a support contract with a 15-minute emergency SLA, priced on its own.
Before
Redis and Confluent license terms are argued from headlines.
After
A written stay, support or move recommendation for each platform, based on the features you actually use.
Scope
What's covered
- 02
VMware Renewal Right-Sizing
Physical cores per CPU, the 16-core and 72-core minimums, vSphere Foundation against Cloud Foundation, and term length. Renewal and sizing only.
- 03
Tanzu RabbitMQ Below 72 Cores
Commercial RabbitMQ licensed per core through AceMQ at the size of your estate, quoted per environment and in writing.
- 04
Independent Support on Open Source
Senior-engineer support, patches and escalation for RabbitMQ, Kafka, Valkey and Redis builds you run yourself.
- 05
Redis License and Valkey Decision
Which Redis releases fall under which license, whether Redis 8 or Valkey fits, and a tested migration when the answer is to move.
- 06
Confluent Feature Inventory
The Confluent-licensed features you use today, and what each would need if you moved to Apache Kafka with independent support.
The Engagement
How it actually runs
Every phase has a defined duration and a concrete artifact handed over at the end of it. You always know what stage you're in and what you've received.
- Phase 1Scoped per engagement
Lock-In Inventory
We list each commercial platform with its license, renewal date, core count and the features you use. Delivery is remote and guided by your engineers.
You receive
- Platform and renewal register
- Features in use against features paid for
- Which dependencies are contractual and which are technical
- Phase 2Scoped per engagement
Options and Numbers
For each platform we price the three exits where they apply: stay with right-sized licenses, keep the software and change who supports it, or move.
You receive
- Written quote for each option that applies
- Effort and risk for any move
- A side-by-side view for procurement
- Phase 3Scoped per engagement
Decision Paper
A short paper for engineering, procurement and legal: what to renew, what to re-size, what to move and in what order.
You receive
- Recommendation per platform
- Timeline against renewal dates
- Open questions for the vendor
- Phase 4Scoped per engagement
Execute and Support
Licenses and support contracts put in place, or a migration run with a rehearsed rollback, then the operating model you choose on the support ladder.
You receive
- Licenses or support contract in force
- Migration runbook and cutover, where you move
- Agreed support stage and escalation path
Three ways out of vendor lock-in, and what each leaves in place
Lock-in costs money when a renewal lands and the only price on offer is the vendor's. The way out is rarely one big move. These three exits cover most cases, and many estates use two of them.
| Exit | What changes | What stays the same | Fits when |
|---|---|---|---|
| Independent support on the open-source build | The support contract moves to AceMQ. You run the community build, which is MPL 2.0 for RabbitMQ and Apache 2.0 for Kafka. | The software, the architecture and your team. | You pay mainly for patches and escalation, and you use none of the vendor-only features. |
| License right-sizing | The commercial license stays, priced on the cores you run: Tanzu RabbitMQ below Broadcom's 72-core minimum through AceMQ, VMware renewals sized on a true core count and edition. | The commercial distribution and the vendor features. | You need the commercial build, or a contract requires it, and the quote does not match the estate. |
| A planned move | The platform changes: Redis to Valkey, or Confluent to Apache Kafka with independent support. | The applications, with tested changes to clients and operations. | The license terms rule a version out, or the paid features are not in use. |
This page is one of AceMQ's solutions for common infrastructure problems
For independent support on open source, start with enterprise open source support
Broadcom subscription pricing and the 72-core minimum
Broadcom sells VMware by subscription per physical core. Perpetual licenses are retired. Since April 2025 an order line has to cover at least 72 licensed cores, and every CPU with fewer than 16 cores is billed as 16. For a small estate the minimums move the bill more than the rate does.
| Edition | 1-year term | 3-year term |
|---|---|---|
| vSphere Foundation (VVF) | $117 to $196 | $100 to $160 |
| Cloud Foundation (VCF) | about $344 | $257 to $348 |
These are ranges from real quotes, the same ones published on the VMware licensing page, not a rate card. Two vSphere Foundation quotes for the same 96 cores, issued the same day, came in about 67% apart per core, so your own number depends on your Broadcom account. On the same 2026 one-year quotes, the same core count on VVF came in roughly 43% to 66% below VCF.
| Physical estate | Cores billed | Effect on cost per real core |
|---|---|---|
| Two hosts, 32 physical cores | 72 | More than double the list rate per real core. |
| 24 to 40 physical cores | 72 | About 1.8 to 3 times the list rate per real core. |
| 72 physical cores or more | As counted | The minimum no longer applies; the edition and term decide. |
Count your own cores and see 2026 quote ranges on the VMware licensing and renewals page
The full set of 37 quotes is in State of VMware renewals 2026
For the options at renewal, see VMware renewal options compared
VMware Tanzu pricing for RabbitMQ: license cost below 72 cores
Tanzu RabbitMQ is licensed per core as an annual subscription, so the Tanzu license cost follows the size of the estate, not message volume. Broadcom's standard channel will not quote it below 72 cores, which means a small deployment is billed as though it were far larger. AceMQ licenses beneath that floor, so an 8-core or 20-core estate is priced as 8 or 20 cores. Quotes are per environment and come back in writing. AceMQ does not publish its own prices.
| Cores you run | Broadcom standard channel | Through AceMQ |
|---|---|---|
| 8 | 72 | 8 |
| 20 | 72 | 20 |
| 72 or more | As counted | As counted |
How a RabbitMQ license is quoted, and what it includes: RabbitMQ commercial licensing
Redis and Confluent license changes
Two other platforms changed their terms in ways that now show up in procurement reviews. In both cases the open-source project still exists and can be supported independently.
| Release | License |
|---|---|
| Redis 7.2 and earlier (Redis OSS) | BSD 3-clause |
| Redis 7.4 and later (Community Edition) | RSALv2 or SSPLv1 |
| Redis 8 | RSALv2, SSPLv1 or AGPLv3, your choice |
| Valkey (Linux Foundation, from Redis 7.2.4) | BSD 3-clause |
Valkey is the exit for teams that need a permissive license. It is compatible at the data-file level with Redis 7.2 and earlier, and a move from 7.4 or later needs a different method, so we test before we promise. Teams that depend on Redis 8's integrated modules may be better off staying on Redis, and we say so.
The migration service is Redis to Valkey migration
The decision guide is should you migrate from Redis to Valkey
Confluent after the IBM acquisition
IBM announced its agreement to acquire Confluent on 8 December 2025 and completed the acquisition on 17 March 2026. Apache Kafka itself is unchanged and stays under the Apache 2.0 license. What ties you to Confluent is the license tier of the features you use: Confluent splits its software into three tiers, and the enterprise-licensed pieces such as Control Center, role-based access control, Cluster Linking and the commercial connectors each need a replacement or a decision to go without. The first step is to list the licensed features you use, not the ones you bought.
The options side by side: Confluent alternatives compared
The background and the license tiers: Confluent alternatives after the IBM acquisition
For Kafka under an independent contract, see Kafka support
How to prevent vendor lock-in
Lock-in is cheaper to prevent than to undo. These habits keep an exit available without committing you to take it.
- Keep the license and the support contract separable — If one vendor sells both, ask what each costs alone. The answer shows how much of the bill is the software and how much is the escalation path.
- Prefer open protocols — AMQP, the Kafka protocol and the Redis protocol let you change the server without rewriting every client.
- List the paid features you use — Lock-in sits in the licensed features, not the core product. An inventory, kept current, is the basis of every negotiation.
- Track renewal dates a year ahead — A choice made two months before expiry is a negotiation you have already lost.
- Test the exit before you need it — A compatibility run in staging, such as Redis against Valkey, turns an assumed risk into a measured one.
Is vendor lock-in a risk? It is a risk when the cost of leaving is unknown and the renewal date is close. It is a manageable one when you know both.
What this page does not claim
- Prices are quote ranges — The VMware figures are from AceMQ quotes issued in 2026 and vary by account. They are not a Broadcom rate card and not an offer.
- AceMQ pricing is by quote — We do not publish a price list. Tell us your platforms and cores and we come back with a written quote.
- No savings are promised in advance — What you save depends on your quote, your edition and your term, and we do not state a percentage before seeing them.
- Not legal advice — We explain what each license says in practice. Your legal team decides what it means for your organisation.
FAQ
Questions about Infrastructure license cost reduction
How do we license Tanzu RabbitMQ below Broadcom's 72-core minimum?
Through AceMQ. Broadcom's standard channel applies a 72-core minimum order for Tanzu RabbitMQ, which bills a small estate as though it were far larger. AceMQ is the only RabbitMQ managed service provider globally able to license beneath that floor, so the quantity is set by your estate: a 20-core deployment is priced as 20 cores. Quotes are per environment and returned in writing.
How much does RabbitMQ cost?
RabbitMQ itself is free under the Mozilla Public License 2.0. What is licensed is the commercial distribution, Tanzu RabbitMQ, as an annual subscription per core, so cost follows the cores you run rather than message volume. You can also run the open-source build with an independent support contract. AceMQ prices both by written quote.
Is there a cheaper alternative to a Tanzu RabbitMQ subscription for 8 cores?
There are two Tanzu alternatives, and neither means leaving RabbitMQ. You can license Tanzu RabbitMQ through AceMQ at 8 cores instead of the 72 that Broadcom's standard channel would bill. Or you can run the open-source RabbitMQ build and buy support, patches and escalation separately. Which is cheaper depends on whether you use the commercial features, so we quote both.
What does a VMware vSphere Foundation quote cost per core, for 1 and 3 years?
On AceMQ quotes issued in 2026, vSphere Foundation came in at $117 to $196 per core per year on one-year terms and $100 to $160 on three-year terms. These are ranges and vary by account. Send your host and core count and we return a budgetary one-year and three-year quote within 24 business hours.
Is Redis no longer free?
Redis 7.2 and earlier are BSD-licensed. Redis 7.4 and later moved to RSALv2 or SSPLv1, and Redis 8 added AGPLv3 as a third option. The software can still be downloaded at no charge, but the newer licenses carry conditions your legal team should read. Valkey, the Linux Foundation fork, stays BSD 3-clause.
Redis Enterprise or Valkey with support: what does each cost?
Running Valkey or Redis Community Edition costs no license fee, so the spend is support and operations. Redis Software, the commercial product, is priced by Redis. AceMQ supports Redis Software, Redis Community Edition and Valkey and quotes support in writing, so you can compare it with the vendor's number.
Is vendor lock-in a risk?
It is a risk when the cost of leaving is unknown and a renewal is close. The exposure sits in vendor-only features and in contracts that bundle license and support. A lock-in map, which lists the licensed features you use and the cost of each exit, turns it into a number you can plan around.
How can we prevent vendor lock-in?
Keep the license and the support contract separable, prefer open protocols, list the paid features you use, track renewal dates a year ahead and test the exit in staging before you need it. Independent support on the open-source build is the lowest-effort exit because nothing about the platform changes.
Does the IBM acquisition of Confluent change Apache Kafka?
No. Apache Kafka stays an Apache 2.0 project. The acquisition affects Confluent's own products and license tiers. Teams that use Kafka, the Java clients and Schema Registry can move to other options and keep their schemas and serializers.
Let's talk
Tell Us What You Pay For and When It Renews
Send the platforms, core counts and renewal dates. We will map the lock-in, price the exits that apply and reply to your quote request within 1 hour.
Get in Touch
Talk to an AceMQ Expert
Send us a message and we'll follow up within one business day — or book a free 30-min consultation directly.
305-204-2607info@acemq.com66 W. Flagler St. 9th Floor
Miami, FL 33130
Miami, FL 33130
Prefer to talk now? Call us directly or use the consultation tab to find a time that works.