RabbitMQ support that keeps you on real RabbitMQ. We patch, architect, and operate it.

No. OSSeva patches are applied to upstream community source code. Your cluster continues to run real RabbitMQ under its open source licence, the Mozilla Public License 2.0. We are not a fork, and there is no proprietary runtime in your stack.

Patches are delivered as signed OCI/Helm packages or Maven artifacts via the OSSeva artifact registry. You pull the patched version the same way you pull upstream today — just from our registry.

Each OSSeva release ships with a validated, tested Erlang/OTP version. The compatibility matrix is published per release. Our Erlang/OTP builds also receive CVE patches independently of the RabbitMQ release cycle.

The migration scope depends on how many Tanzu-specific configuration extensions you've used. For most Tanzu customers, the migration is a configuration change and a cluster migration, planned to avoid downtime. A fixed-price discovery engagement sizes the work before any commitment.

For OSSeva Operate customers, we hold a contractual SLA on critical CVE remediation. For Patch and Assure customers, we publish a quarterly cadence with out-of-cycle patches for CVSS 9+ vulnerabilities.

Yes. OSSeva Operate is a managed service on your infrastructure — your cloud account, your VPC, your on-prem. We provide the operations layer (monitoring, runbooks, incident response) and you retain data sovereignty.

Broadcom sells commercial RabbitMQ through Tanzu RabbitMQ. Cloud providers run managed message broker services inside their own platforms, and third-party support companies cover the community RabbitMQ you run yourself. OSSeva is a third-party provider: one contract can cover RabbitMQ and the rest of your open source stack, community EOL versions back to 3.8.x are included, and OSSeva Operate runs as a managed service on your own infrastructure.

Both. RabbitMQ 4.3.x, the current line, is covered alongside 3.8.x to 3.13.x on extended support and 4.0.x to 4.2.x after community EOL. Every tier includes quarterly CVE patches for all covered versions, Assure adds version upgrade planning and an annual architecture audit, and Operate adds 24/7 monitoring with a 15-minute P1 incident response SLA.

Yes, back to RabbitMQ 3.8.x. The community no longer fixes 3.8.x to 3.13.x or 4.0.x to 4.2.x, and OSSeva ships patched, signed builds for all of those lines together with the Erlang/OTP runtime underneath. Clusters on 3.7.x or earlier are older than the lines OSSeva patches: Assure plans the upgrade to a covered version, and Operate carries it out with your team.

Patched builds for every covered version, delivered through your own repositories, and an escalation path to RabbitMQ core contributors. Assure adds 24/7 reactive support, upgrade planning and an annual architecture audit. Operate adds proactive 24/7 monitoring, a 15-minute P1 response and managed operations on your infrastructure. OSSeva Operate patches Critical CVEs (CVSS ≥ 9.0) within 48 hours and High within 7 days.

OSSeva for RabbitMQ is priced per application cluster, so the price does not change with the size of the hosts underneath. The tier you choose (Patch, Assure or Operate) sets what is included. Book a discovery call for a quote.

Yes. OSSeva delivers patched RabbitMQ builds compatible with the RabbitMQ Cluster Operator for Kubernetes, including signed Helm chart updates and OCI-compliant container images, on OpenShift, EKS, AKS, GKE and other conformant Kubernetes clusters.

Yes. OSSeva Assure includes compliance documentation specifically designed for RabbitMQ audits: CVE patch attestation letters, patch cadence evidence for PCI DSS Requirement 6.3.3, SOC 2 CC6 logical access control evidence templates, and audit narratives for HIPAA §164.312 technical safeguards.

Quorum queues are RabbitMQ's durable, replicated queue type built on the Raft consensus protocol. They replace classic mirrored queues for high-availability workloads. OSSeva supports quorum queue deployments across all covered RabbitMQ versions and includes quorum queue configuration in our reference architectures.