Your situation, not a product catalog.

Patched builds of RabbitMQ 3.12 and the other 3.x lines, plus the Erlang/OTP runtime under them, with SBOM and VEX attestation for ISVs and auditors on one contract with the rest of your open source stack.

Kafka 4.0 removed ZooKeeper mode. Keep Kafka 3.x on ZooKeeper patched while you plan the KRaft migration, with 24/7 support on your own clusters.

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.

Keep .NET 8 applications patched after Microsoft support ends on 10 November 2026: what extended support covers, how fixes ship, and how to start.

Redis 7.0 is end of life and 6.2 ends 1 April 2027. Compare ElastiCache extended support, a move to Valkey, and patched Redis builds on your own servers.

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

MongoDB 4.4, 5.0 and 6.0 are past end of life. See which CVEs affect them, why AVX-less hardware blocks the upgrade, and how patched builds keep them covered.

Elasticsearch 7.17 is past end of life. Compare upgrading to 8.x, moving to OpenSearch, and patched 7.17 builds with 24/7 support.

ZooKeeper 3.4 to 3.7 get no upstream fixes. Patched, signed builds (3.5 custom) and a written CVE attestation for products that embed ZooKeeper.

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.

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 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.

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.

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 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 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 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'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 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 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.

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 depends on ZooKeeper through Apache Helix. OSSeva supports Pinot 1.x clusters, patches the ZooKeeper ensemble under them, and runs Pinot 24/7.

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.

OSSeva runs your Kafka ZooKeeper-to-KRaft migration and keeps the ZooKeeper ensemble patched until the cutover is final. Also Keeper, etcd and Oxia moves, and patched ZooKeeper for what stays.

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.

Move from Oracle Database to PostgreSQL in phases: assessment, code conversion, dual run and cutover, then 24/7 support on your own servers.

Move SQL Server databases to PostgreSQL in phases, with a T-SQL conversion checklist and 24/7 support on the PostgreSQL you land on.

Support every open-source database you run, including versions past end of life, under one contract with one escalation path and one renewal date.

Keep your binaries and data and change your support. OSSeva takes over open-source database support with a transition plan, a structured onboarding and patched builds.

Move RDS, Aurora, Azure Database or Cloud SQL workloads to self-managed PostgreSQL, MySQL or Valkey you control, with OSSeva support after cutover. And when not to.

MySQL 8.0 support ended on 30 April 2026. Compare upgrading to 8.4 LTS, switching to MariaDB or PostgreSQL, and patched 8.0 builds with support.

Tomcat 9.0 support ends 31 March 2027. OSSeva provides Tomcat extended support and security patching for 8.5 to 11, priced per application server.

Node.js 18 reached end of life in April 2025 and Node.js 20 in April 2026. OSSeva patches Node.js 14 to 20 runtimes now, and Node.js 22 after its end of life on 30 April 2027, while you move to a current LTS line.

MariaDB 10.6 reached end of life on 6 July 2026. Compare upgrading to 10.11, 11.4 or 12.3 LTS with patched 10.6 builds and support from OSSeva.

Migrate MySQL to PostgreSQL in phases, with an incompatibility checklist for types, collations and SQL, then 24/7 support on the cluster you land on.

Managed RabbitMQ for end-of-life 3.8 to 3.13 and current 4.x, with the Erlang/OTP runtime, 24/7 and a 15-minute P1 response, on your own servers, cloud account or Kubernetes. Not a hosted service.

Managed Kafka for end-of-life 2.8 to 3.8, ZooKeeper-mode 3.9 and current 4.x, with a 15-minute P1 response, 24/7, on your own servers, cloud account or Kubernetes. Compared with MSK and Confluent Cloud.

Managed PostgreSQL on bare metal, VMs or your cloud account: Patroni high availability, backups, upgrades and patched builds for 11 to 14 after end of life.

SQL Server 2016 reached end of support on 14 July 2026 and 2019 follows on 8 January 2030. Each version's dates, ESU terms and options, PostgreSQL included.

OSSeva Operate runs PostgreSQL, MySQL, MariaDB, MongoDB and Redis on your servers or cloud account, including versions past end of life, with a 15-minute P1.

What PCI DSS, the EU Cyber Resilience Act, DORA and CMMC ask for on end-of-life open source, and the SBOM, VEX and signed-build evidence OSSeva ships.