// Migration Scenario
You decided to leave Tanzu Spring, RabbitMQ or GemFire.
Now what?
You need to keep running Spring, RabbitMQ and GemFire workloads without Broadcom. OSSeva provides CVE-patched community versions, migration design and managed operations under a single contract.
Trusted globally by enterprises
The Broadcom Tanzu situation, plainly
Per-core licensing with minimum commitments
Broadcom restructured Tanzu RabbitMQ licensing around per-core pricing with minimum commitments, so the invoice tracks the size of the cluster rather than the support you consume. Teams running modest brokers on large hosts pay for cores the workload never uses.
Tanzu Spring support now sits inside TrueSource
Broadcom sells commercial Spring support as Spring Enterprise, which became part of its TrueSource portfolio on 31 August 2026. Open source support for Spring Boot 3.5 ended on 30 June 2026, so every Spring Boot 3.x line now gets fixes only through a paid contract.
GemFire pricing and support uncertainty
VMware/Broadcom GemFire customers are facing unclear roadmaps and escalating support costs. Many are evaluating Apache Geode (the upstream community project) as the exit path.
Tanzu Spring and Spring Boot: TrueSource or independent support
Broadcom's commercial Spring support, long sold under the Tanzu name, became part of TrueSource on 31 August 2026. TrueSource bundles it with Trusted Artifacts and with Data Services for PostgreSQL, RabbitMQ, MySQL and Valkey, sold as tiered site licences. It patches the release lines Broadcom still supports: commercial support for Spring Boot 3.4 ends on 31 December 2026, and for 3.0 to 3.3 it has already ended.
Independent support takes the other route. OSSeva patches the Spring Boot 2.6 to 3.5 and Spring Framework 5.2 to 6.2 lines you already run, with no Broadcom subscription. If Spring is the only Tanzu product you use, compare Spring 5 and Spring Boot 2 support options before you renew. For the broker, see Broadcom RabbitMQ support compared, and for the whole portfolio, Broadcom TrueSource explained.
How OSSeva closes the gap
CVE-patched community versions
OSSeva ships patched community RabbitMQ, Apache Geode, Spring Boot and Spring Framework: the same upstream code, with active CVE remediation. No Broadcom subscription required.
Migration design
A fixed migration playbook: licence exit, cluster migration, runtime validation and a cutover planned for zero downtime.
Single contract going forward
Replace three Broadcom support contracts with one OSSeva contract: patches, architecture reviews, managed operations, and compliance documentation.
Pricing model: per cluster, not per core
OSSeva for RabbitMQ is priced per application cluster — not per core, not per broker, so a modest broker on a large host does not pay for cores the workload never uses. We'll price your estate on the discovery call.
Frequently asked questions
What is Broadcom Tanzu and why are enterprises leaving it?
Broadcom Tanzu is Broadcom's commercial packaging of VMware's enterprise open-source portfolio, including RabbitMQ, Spring Framework, GemFire, and other middleware. After Broadcom's acquisition of VMware, the licensing model was restructured around per-core licensing with minimum commitments, so the invoice tracks cluster size rather than support consumed. We do not publish other vendors' pricing — the relevant comparison is your own renewal quote against a per-cluster model, for software that has an open-source equivalent available at no license cost.
What will I lose by leaving Broadcom Tanzu for OSS RabbitMQ?
Functionally, very little. The open-source RabbitMQ is the same codebase as Tanzu RabbitMQ — Broadcom does not add proprietary features that are not available in the community version. What you give up is Broadcom's commercial support contract, which OSSeva replaces with equivalent CVE patching, compliance documentation, and optional managed operations at a fraction of the cost.
How long does a Tanzu to OSS RabbitMQ migration take?
A standard Tanzu-to-OSS-RabbitMQ migration takes 4–8 weeks for most enterprise deployments. This includes: vhost and topology export, new cluster deployment (via RabbitMQ Cluster Operator on Kubernetes or manual clustering), policy and federation recreation, parallel validation, and production cutover. Complex deployments with custom plugins or large numbers of vhosts may take 8–12 weeks.
Can OSSeva handle GemFire and Spring as part of a Tanzu exit?
Yes. OSSeva covers the Tanzu portfolio: RabbitMQ, Spring Framework 5.2 to 6.2, Spring Boot 2.6 to 3.5, Spring Security 5.6 to 6.5, and VMware GemFire. A Tanzu exit engagement covers all of these technologies under a single contract, with a migration roadmap and interim extended lifecycle support while migrations are in progress.
Let's plan your Tanzu exit.
A discovery call, then a migration plan and proposal for your Spring, RabbitMQ and GemFire estate.