// Competitive Comparison
OSSeva vs. Broadcom Tanzu RabbitMQ
Broadcom employs the RabbitMQ core team and sells Tanzu RabbitMQ with commercial support for 3.13 and the 4.x series. OSSeva supports community RabbitMQ from 3.8 onward, including the 3.10, 3.11 and 3.12 lines whose Broadcom commercial dates have passed, with the Erlang/OTP runtime and managed operations included.
Where OSSeva is stronger
- ✓RabbitMQ 3.8 to 3.12: Broadcom's commercial dates for 3.10, 3.11 and 3.12 have passed, and 3.8 and 3.9 are not on its table
- ✓Patched Erlang/OTP builds paired with each broker version, so the runtime under RabbitMQ is covered as well
- ✓Managed operations on your infrastructure: 24/7 monitoring, a 15-minute P1 response and a named engineer on the Operate tier
- ✓Patches applied to the community RabbitMQ source you already run, delivered through Helm, OCI or Maven
Where Broadcom Tanzu RabbitMQ is stronger
- →Support from the core engineering team that builds and maintains RabbitMQ
- →Commercial dates that run to 31 December 2029 for 3.13 and 30 June 2030 for 4.2
- →Commercial-edition features such as standby-cluster disaster recovery replication and FIPS 140-2 compliant TLS
- →Highest-severity issues receive attention within 30 minutes, 24/7/365, with direct input to the product roadmap
Trusted globally by enterprises
Capability comparison
Comparison based on publicly available product information as of Q3 2026. Verify current coverage with each vendor.
| Capability | OSSeva | Broadcom Tanzu RabbitMQ |
|---|---|---|
| RabbitMQ 3.8 and 3.9 | Not listed (unsupported) | |
| RabbitMQ 3.10, 3.11 and 3.12 | Ended Dec 2023 to Jun 2025 | |
| RabbitMQ 3.13 | To 31 Dec 2029 | |
| RabbitMQ 4.x | 4.0 to 4.3, dates per series | |
| Patched Erlang/OTP runtime | CVE scanning of RabbitMQ and dependencies | |
| Support from the RabbitMQ core engineers | ||
| Highest-severity response | 15 min P1 (Operate) | 30 min, 24/7/365 |
| 24/7 managed operations on your infrastructure | Through partners | |
| Architecture review and upgrade planning | Assure and Operate | Through partners |
| Standby-cluster disaster recovery replication | ||
| FIPS 140-2 TLS and OAuth 2.0 forward proxy | ||
| Intra-cluster compression, AMQP 1.0 over WebSocket | ||
| Signed builds with VEX statements | Patch and Assure | Not stated |
Why teams choose OSSeva
The versions Broadcom's table has closed
Broadcom's published support timeline on rabbitmq.com lists end of commercial support as 31 December 2023 for 3.10, 30 June 2024 for 3.11 and 30 June 2025 for 3.12, and says releases not in the table are unsupported, which leaves out 3.8 and 3.9. Clusters stay on those lines for concrete reasons: mirrored classic queues that RabbitMQ 4.0 removed, or an Erlang/OTP version the rest of the estate is pinned to. OSSeva ships patched, signed builds for 3.8 through 3.13 and 4.x today.
The runtime underneath the broker
Each RabbitMQ series runs on a narrow band of Erlang/OTP releases, and those releases leave Erlang's own support on a separate calendar. A patched broker on an unpatched runtime still fails a scan. OSSeva patches the Erlang/OTP build as well as RabbitMQ and ships them as a tested pair, so the broker and runtime move or stay together.
Operations, not only a support queue
On the Operate tier our engineers monitor your clusters 24/7 on your own infrastructure, respond to P1 incidents within 15 minutes and maintain the runbooks. When you are ready to leave 3.x, the same team plans the move from mirrored classic queues to quorum queues or streams.
Why teams choose Broadcom Tanzu RabbitMQ
Support from the people who write RabbitMQ
Broadcom employs the RabbitMQ core engineering team, and Tanzu RabbitMQ customers get 24/7 support from them. Broadcom states that highest-severity issues receive attention within 30 minutes, 24/7/365, and that enterprise customers have direct access to the product team and can contribute to the roadmap.
Features that exist only in the commercial edition
Tanzu RabbitMQ adds schema and data replication to standby clusters for disaster recovery, FIPS 140-2 compliant TLS, forward proxy support for OAuth 2.0, intra-cluster traffic compression, AMQP 1.0 over WebSocket, distributed shovels, audit logging on Kubernetes and a stream browser. OSSeva patches community RabbitMQ and does not add these features.
Long commercial dates on current series
Broadcom lists commercial support for 3.13 to 31 December 2029 and for 4.2 to 30 June 2030. It describes these dates as indicative, with the official lifecycle kept on the Broadcom support portal. It also supplies an OVA for running RabbitMQ on vSphere.
Which is right for your situation?
Choose OSSeva when…
Your clusters run RabbitMQ 3.8 to 3.12, where Broadcom's commercial dates have passed, or you want the Erlang/OTP runtime patched with the broker and a team that runs the clusters 24/7 on your infrastructure.
Talk to an engineerConsider Broadcom Tanzu RabbitMQ when…
You are on 3.13 or 4.x, rely on commercial-edition features such as standby-cluster replication or FIPS 140-2 TLS, or want support directly from the RabbitMQ core engineers.
Broadcom sells commercial support for RabbitMQ 3.13 and 4.0 to 4.3. OSSeva covers community RabbitMQ 3.8 to 3.13 and 4.x, with the Erlang/OTP runtime underneath.
Frequently asked questions
Does Broadcom still offer commercial support for RabbitMQ 3.12?
Not according to its published timeline. rabbitmq.com lists end of commercial support as 30 June 2025 for 3.12, 30 June 2024 for 3.11 and 31 December 2023 for 3.10, while 3.13 is covered to 31 December 2029. Broadcom notes the dates are indicative and points to its support portal for the official lifecycle. OSSeva ships patched builds for 3.10, 3.11 and 3.12 today.
When does commercial support for RabbitMQ 4.0 end?
Broadcom's table lists 30 September 2026 for 4.0, 30 April 2027 for 4.1, 30 June 2030 for 4.2 and 30 April 2028 for 4.3. Community support for each 4.x series ends much earlier. OSSeva covers the 4.x series as well as 3.x, so a 4.0 cluster that cannot move yet stays patched.
What is the difference between Tanzu RabbitMQ and community RabbitMQ?
Tanzu RabbitMQ is Broadcom's commercial edition. According to rabbitmq.com it adds longer support timelines, 24/7 support from the core engineers, and features such as standby-cluster replication, FIPS 140-2 TLS and intra-cluster compression. Community RabbitMQ is the open source edition, with community support on a best-effort basis. OSSeva patches and supports the community edition.
Can OSSeva provide Tanzu-only features such as standby replication?
No. Those features belong to Broadcom's commercial edition. If your design depends on them, Broadcom is the right vendor for that cluster. On community RabbitMQ, OSSeva designs availability and recovery with quorum queues, streams, shovels and federation.
Can we use Broadcom and OSSeva together?
Yes. A common split keeps Tanzu RabbitMQ on the 3.13 or 4.x clusters that need commercial-edition features, and puts OSSeva on the older 3.x clusters that fell outside Broadcom's dates. The two do not conflict.
How does pricing compare?
We do not publish or estimate Broadcom's pricing. Ask both vendors to quote against the same list of clusters and versions. OSSeva prices per cluster.
Ready to see if OSSeva covers your stack?
Book a 30-minute discovery call. We'll confirm version coverage and scope a proposal within 5 business days.