// Solutions

Your situation, not a product catalog.

Find the path that matches your migration scenario, your team's role, or your industry compliance requirements.

Trusted globally by enterprises

Henry ScheinEnbridgeGojekMicrosoft

Migration scenarios

End-of-life versions

RabbitMQ 3.x until the 4.x move

EOL version

Patched RabbitMQ 3.8 to 3.13 and the Erlang/OTP runtime under them, kept current until your mirrored queues move to quorum queues on RabbitMQ 4.x.

Kafka 3.x & ZooKeeper extended support

EOL version

Kafka 4.0 removed ZooKeeper and Confluent Platform 7.x support is ending. OSSeva patches Kafka 3.x brokers and ZooKeeper ensembles and runs the move to KRaft.

ActiveMQ Classic extended support

EOL version

ActiveMQ Classic 5.18 is end of life and CVE-2026-34197 is on CISA's exploited list. OSSeva patches 5.x brokers and runs Classic to 6.x or Artemis migrations.

.NET 8 extended support

EOL version

.NET 8 extended support after Microsoft's 10 November 2026 end date: patched runtime builds, VEX attestations and 24/7 operations while you move to .NET 10.

Redis 6 and 7.2 without ElastiCache premiums

EOL version

ElastiCache adds up to 160% for old Redis OSS. OSSeva patches self-managed Redis 6 and 7.2, the last BSD-licensed Redis, and supports a move to Valkey.

Bitnami drop-in images

EOL version

Replace bitnamilegacy images without rewriting Helm charts. Patched, Bitnami-compatible images for EOL PostgreSQL, Redis, Kafka, RabbitMQ, MongoDB and more.

MongoDB 4.2 to 6.0 after end of life

EOL version

MongoDB 4.2 to 6.0 are past end of life, and 4.2 has no fix for the exploited CVE-2025-14847. OSSeva patches these self-managed lines, with or without AVX.

Elasticsearch 7.17 after end of life

EOL version

Elasticsearch 7.17 support ended on 15 January 2026. OSSeva patches 7.17 and 7.10.2 while you choose between an 8.x reindex and an OpenSearch migration.

Apache ZooKeeper extended support

EOL version

Scanner flagged ZooKeeper inside Kafka, Solr, HBase or a vendor product? Get patched drop-in 3.4 to 3.7 builds and a written CVE attestation for your auditor.

Community Consul after the BSL

EOL version

Consul moved to the BSL in 1.17, and 1.15 to 1.20 are out of support. OSSeva patches MPL-licensed community Consul and plans your move to etcd or Kubernetes.

HBase 2.4 and 1.x after end of life

EOL version

The HBase Reference Guide marks 1.x and 2.0 to 2.4 end of maintenance, and 2.4.18 shipped in May 2024. OSSeva ships patched HBase builds and their ZooKeeper.

Hadoop 2.10 to 3.3 support

EOL version

Hadoop 3.2 and older are end of life, and 2.10 and 3.3 have shipped nothing since 2023. OSSeva ships patched HDFS and YARN builds and patches ZooKeeper for HA.

Cloudera CDH extended support

EOL version

CDH 6.3 support ended in March 2022 and CDH 5.16 in December 2020. OSSeva ships patched CDH components today, including the bundled ZooKeeper 3.4.5.

Hortonworks HDP extended support

EOL version

HDP 3.1 support ended in December 2021 and HDP 2.6 in December 2020. OSSeva ships patched HDP components and ZooKeeper 3.4.6 builds for Hortonworks clusters.

Hive 3.1 and 2.3 until Hive 4

EOL version

Hive 2.x reached end of life in May 2024 and 3.x in October 2024. OSSeva patches Hive 3.1 and 2.3, and their ZooKeeper, while your Hive 4 move is planned.

Druid security fixes for older releases

EOL version

Druid has no support window, and its advisories are fixed in the newest release. OSSeva backports CVE fixes to the Druid release you run, ZooKeeper included.

Storm 2.x after end of life

EOL version

Storm 2.x ended with 2.8.9 on 22 July 2026, and Storm 3 needs Java 25. OSSeva keeps Storm 2.x and its ZooKeeper patched until the Java work is done.

ClickHouse 25.x and older

EOL version

ClickHouse's security policy lists every 25.x release and older as unsupported. OSSeva ships signed, patched builds for them and moves you to ClickHouse Keeper.

Etcd 3.4 under Kubernetes

EOL version

etcd 3.4 ended with 3.4.45 on 1 June 2026. OSSeva patches etcd 3.4 under self-managed Kubernetes control planes, Patroni and Vitess, with tested restores.

Flink 1.19 and older

EOL version

Flink fixes its two newest minors and 1.20 LTS, which leaves 1.19 and older 1.x lines out. OSSeva patches those and the ZooKeeper 3.7.1 behind Flink HA.

Apache Accumulo extended support

EOL version

Accumulo 1.10 reached end of life with 1.10.4 in November 2023 and builds on ZooKeeper 3.4.14. OSSeva ships patched Accumulo 1.10 and patched ZooKeeper 3.4.

Apache Pinot support

EOL version

Apache Pinot depends on ZooKeeper through Apache Helix. OSSeva supports Pinot 1.x clusters, patches the ZooKeeper ensemble under them, and runs Pinot 24/7.

Patroni support

EOL version

Patroni runs PostgreSQL HA on ZooKeeper, etcd, Consul or Kubernetes. OSSeva patches the ZooKeeper, etcd or Consul under Patroni and migrates the DCS when ready.

ZooKeeper to Raft migration

EOL version

Move coordination off ZooKeeper where the product allows: Kafka to KRaft, ClickHouse to Keeper, Patroni to etcd, Pulsar to Oxia. Patched ZooKeeper for the rest.

Apache Pulsar extended support

EOL version

Pulsar 4.0 LTS leaves active support on 21 Oct 2026 and 3.0 LTS lost security fixes in May. OSSeva ships patched, signed Pulsar 2.10 to 3.2 builds.

By role

By industry

Frequently asked questions

What is the Broadcom Tanzu exit and why are companies doing it?

Broadcom acquired VMware in 2023 and restructured the Tanzu licensing model around per-core pricing with minimum commitments. Many enterprises found their RabbitMQ, Spring, and GemFire support costs increase 5–10x. The Broadcom Tanzu exit is the process of migrating from Tanzu-packaged commercial software to OSSeva-supported community OSS equivalents, eliminating the license cost while maintaining security coverage and compliance documentation.

What does OSSeva's Confluent exit program cover?

OSSeva's Confluent exit program replaces Confluent Platform with OSSeva-supported community Apache Kafka, including: broker migration, Schema Registry replacement (Apicurio Registry or community Schema Registry), connector migration from Confluent connectors to community alternatives, removal of Confluent-specific configurations, and post-migration monitoring setup. Most Confluent exits reduce annual licensing costs by 60–80%.

Can OSSeva support PostgreSQL 11, 12, or 13 after community EOL?

Yes. PostgreSQL 11 (EOL November 2023), 12 (EOL November 2024), and 13 (EOL November 2025) are all covered under OSSeva's PostgreSQL extended lifecycle support. OSSeva delivers backported security patches with compliance attestation, allowing teams to continue running these versions securely while planning a major-version migration at their own pace.

Is there a supported migration path from Spring Boot 2.x to Spring Boot 3.x?

Yes. OSSeva offers a Spring Boot 2.x-to-3.x migration toolkit covering: Spring Framework 5.x to 6.x upgrade, Jakarta EE namespace migration (javax.* to jakarta.*), Spring Security 5.x to 6.x configuration changes, Spring Data query method updates, and integration testing. OSSeva can also continue patching Spring Boot 2.7.x in parallel while the migration is in progress, giving teams a definitive security backstop.

Don't see your exact scenario?

Most enterprise OSS situations are variations on a theme. Book a discovery call and we'll map your situation to the right path.