Migration Scenario
You decided to leave Broadcom Tanzu.
Now what?
You need to keep running RabbitMQ, GemFire, and Spring Commercial workloads — without Broadcom. OSSeva provides CVE-patched community versions, migration design, and managed operations under a single contract.
Scope my Tanzu exit →The Broadcom Tanzu situation, plainly
50/72-core minimums on Tanzu RabbitMQ
Broadcom restructured Tanzu RabbitMQ licensing to require minimum core counts that have increased costs 10–30× for most enterprise workloads. You're paying for cores you don't use.
Spring Commercial is now a commercial product
Broadcom commercialized Spring Commercial (Spring Boot, Spring Framework, Spring Security) with explicit subscription requirements. Community EOL moved earlier than expected.
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.
How OSSeva closes the gap
CVE-patched community versions
OSSeva ships patched community RabbitMQ, Apache Geode, and Spring 5.x — the same upstream code, with active CVE remediation. No Broadcom subscription required.
Migration design
Our architects have run Tanzu-exit programs for Global 2000 customers. Fixed-scope migration playbook: license exit, cluster migration, runtime validation, 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. For most Tanzu customers, the savings are 60–80% versus Tanzu renewal. We'll scope your specific situation 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 2023 acquisition of VMware, the licensing model shifted to a 72-core minimum, dramatically increasing costs for most enterprise deployments. Many customers are now paying $200,000–$1,000,000+ annually 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 full Tanzu portfolio: RabbitMQ, Spring Framework 5.3.x, Spring Boot 2.7.x, Spring Security 5.8.x, and VMware GemFire. A Tanzu exit engagement can be scoped to cover all of these technologies under a single contract, with a migration roadmap and interim extended lifecycle support while migrations are in progress.
Let's scope your Tanzu exit.
Discovery call → migration scope → proposal within 5 days. Most Tanzu exits complete within one quarter.