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.
Let's scope your Tanzu exit.
Discovery call → migration scope → proposal within 5 days. Most Tanzu exits complete within one quarter.