Vendor comparison, 2026
The best open source extended support vendors for end-of-life versions
10 vendors compared, listed alphabetically (2026)
The best open source extended support vendor depends on which layer has gone end of life. HeroDevs covers end-of-life application frameworks, especially JavaScript. TuxCare covers end-of-life Linux, runtimes and libraries. OpenLogic by Perforce offers one contract across 400+ technologies, with patched LTS builds for a short list. Red Hat, SUSE and Canonical cover their own operating systems. Percona covers multi-database estates and Command Prompt covers PostgreSQL alone. Chainguard supplies hardened images for current versions. OSSeva covers the data and messaging stack, end-of-life versions included, and published this page.
By the OSSeva team. Last reviewed 22 October 2026; next review by 22 January 2027.
Trusted globally by enterprises





Which vendor fits which situation
Find the layer your end-of-life version sits in, then read that vendor's row below.
| Your situation | Start with | Why |
|---|---|---|
| An end-of-life JavaScript or Java web framework in your code (AngularJS, Vue 2, Struts) | HeroDevs | The longest published list of end-of-life application frameworks, delivered as drop-in packages |
| End-of-life Linux, runtimes and a long tail of libraries | TuxCare | Distributions, OpenJDK, PHP, Python, .NET and kernel patching without a reboot |
| One support contract across hundreds of technologies | OpenLogic by Perforce | Technical support for 400+ technologies, plus LTS builds for a short list with published end dates |
| The operating system itself: RHEL, SLES or Ubuntu | Red Hat, SUSE or Canonical | The OS vendor's own extended lifecycle add-on; Ubuntu Pro also covers packaged applications |
| A multi-engine database estate | Percona | MySQL, PostgreSQL, MongoDB, Valkey and Redis, with ExpertOps and post-EOL support for MySQL 5.7 and 8.0 |
| PostgreSQL only | Command Prompt | PgLTS supports end-of-life PostgreSQL 12 and up, with 24x7x365 support |
| Current versions that need low-CVE images | Chainguard | Minimal images rebuilt daily; the EOL grace period is up to six months and does not fix the end-of-life package |
| Databases, brokers and the runtimes under them on one contract, end-of-life versions included | OSSeva | Signed patched builds of the version you run for PostgreSQL, MySQL, MongoDB, Kafka, RabbitMQ, ZooKeeper and more, with 24/7 operations available |
Commercial support for end-of-life open source software
Commercial support for end-of-life open source software is a paid contract that keeps delivering security fixes for versions the community no longer patches. HeroDevs, TuxCare, OpenLogic, Percona, Command Prompt and OSSeva sell it for applications, runtimes, databases and brokers. Red Hat, SUSE and Canonical sell it for their own operating systems.
Check that the vendor ships new fixes for your exact version, not only advice on running it. The four options for end-of-life software set extended support beside upgrading, cloud-provider support and building the fixes yourself. For three vendors head to head, read HeroDevs vs TuxCare vs OpenLogic compared.
Enterprise support for unsupported open source versions
Enterprise support for unsupported open source versions depends on which layer is unsupported. Operating systems go to the OS vendor, application frameworks to HeroDevs or TuxCare, databases to Percona or Command Prompt, and the data and messaging stack to OSSeva. OpenLogic suits a wide estate. Ask each vendor for patched builds of your exact versions.
Every vendor named here is listed in the tables below with its sources. OSSeva's Assure tier adds architecture review, audit evidence and 24/7 reactive support to patched builds, and the supported versions page lists every line it patches.
Patch SLA, price model and fit, as of 22 October 2026
What each vendor publishes about technologies covered, patch timing and how it prices. “Not published” means the linked pages do not say. Prices are never estimated: the column shows the pricing unit where one is stated. “Not a fit for” is our reading of each vendor's published scope, not a claim that it cannot do the work.
| Vendor | Technologies covered | Patch SLA (as published) | Price model (as published) | Not a fit for | Sources |
|---|---|---|---|---|---|
| Canonical | Ubuntu LTS and the applications packaged in the Ubuntu archive, such as PostgreSQL, Redis, MongoDB and Kafka. | Not published. The page states scope (critical, high and selected medium vulnerabilities for 10 years) and 24/7 support, with no patch or response time. | Free for personal use on up to 5 machines; 30-day enterprise trial. Enterprise price and unit not on the page. Cloud marketplace billing scales with usage. | Estates not running Ubuntu, and end-of-life application versions that are not packaged in the Ubuntu archive. | ubuntu.com/pro |
| Chainguard | More than 3,000 container images and a library catalogue for Python, Java, JavaScript, Go and .NET, on current versions. | A 1-day SLA for vulnerabilities on the Known Exploited Vulnerabilities (KEV) list. Times for other severities are not on the home page. | Not published. | Keeping an end-of-life version patched. The EOL grace period is up to six months and does not fix the end-of-life package itself. | chainguard.devChainguard EOL grace period |
| Command Prompt | PostgreSQL 12 and up, including end-of-life versions (PgLTS), with 24x7x365 support and managed services. | Not published. | Not published. | Estates that also need Kafka, RabbitMQ, MySQL or MongoDB covered; none are listed. | commandprompt.com |
| HeroDevs | 36 product lines of end-of-life frameworks and libraries: AngularJS, Vue 2, Spring, Struts, Tomcat, .NET, Django, PHP, Rails, Node.js and others, plus PostgreSQL 14, 16 and 18. | Published targets of 14 days for Critical and 30 days for High security issues. The SLA page words them as effort-based targets rather than guarantees. | Annual licence per user, counted as anyone committing code to the project repository, with no charge for extra environments. No prices published; custom pricing. | Operating systems, and message brokers or databases beyond the PostgreSQL versions and the Kafka client library it lists. | HeroDevs SLAHeroDevs pricingHeroDevs support |
| OpenLogic by Perforce | Technical support for 400+ technologies. Patched LTS builds for a short list: AngularJS, Bootstrap, CentOS 7 and 8, Kafka 3.8 and 3.9, MySQL 5.7 and 8.0, PHP, Spring Boot and Framework, Tomcat 8.5. | Critical (CVSS 9 and above) within 14 days and High (CVSS 7 and above) within 30 days. A contractual SLA applies only to CentOS 7 and AngularJS; other products have service level objectives. | Custom quote on request. No price or pricing unit published. | Patched builds for products that are not on the LTS list, or for versions past a listed end date; for those it sells technical support only. | OpenLogic LTS |
| OSSeva | PostgreSQL, MySQL, MariaDB, MongoDB, Redis and Valkey, Elasticsearch, Kafka, RabbitMQ with Erlang/OTP, ActiveMQ and ZooKeeper, with Spring, Tomcat, Node.js and .NET. Current and end-of-life versions. | On Patch, Critical CVEs (CVSS 9.0 and above) within 48 hours and High within 7 days. On Operate, a 15-minute P1 incident response. | Per cluster for most technologies; per application server for Tomcat, per application for Spring Boot, per application runtime environment for .NET. No price list published; quote on a discovery call. | Operating systems, front-end frameworks, Microsoft SQL Server, Oracle Database, hosted databases and training courses. | OSSeva PatchOSSeva OperateOSSeva pricingOSSeva supported versions |
| Percona | MySQL, PostgreSQL, MongoDB, Valkey, Redis and MariaDB. Post-EOL support for MySQL 5.7 and 8.0 for up to three years after Percona Server's end of life. | Response times as fast as 15 minutes on the Advanced and Premium tiers. No patch-time commitment published. | Tiered support (Advanced, Premium). Pricing unit and prices not published. | Message brokers, runtimes, frameworks and operating systems; none are listed. | Percona supportPercona MySQL 5.7 post-EOL |
| Red Hat | RHEL 7 and RHEL 6 while in the Extended Life phase, through the ELS Add-on. | Not published. Scope is certain critical-impact security fixes and selected urgent bug fixes for the last minor release. | Add-on subscription to a Standard or Premium RHEL subscription. Unit and price not stated on the datasheet. | Anything that is not RHEL: databases, brokers and application frameworks. RHEL Desktop and Workstation subscriptions are not eligible. | Red Hat ELS datasheet |
| SUSE | SLES 11, 12 and 15 (LTSS); RHEL 6 to 9 and CentOS 7 and later (Multi-Linux Support). | No patch time published. Response: Priority 24x7 with 1 hour for critical issues; Standard 12x5 with 2 hours. | LTSS is an extension to an existing SLES subscription, bought through a SUSE representative. Unit and price not published. | Databases, brokers and application frameworks; none are listed. | SUSE LTSS |
| TuxCare | End-of-life Linux distributions, runtimes (OpenJDK, PHP, Python, .NET, Ruby, Node.js), language libraries including Spring, and named versions of PostgreSQL, MySQL, MariaDB, Kafka, Tomcat and others. | Describes its patches as SLA-backed with guaranteed timelines, but states no hours or days. | Custom quote based on your infrastructure and use case. No unit or prices published. | Spring Boot 2.7, which its Spring page does not list, and brokers beyond the named Kafka versions. Check its list against your exact versions. | TuxCare ELSTuxCare pricingTuxCare ELS for Spring |
How this list was made
- Who wrote it. OSSeva, which sells extended support. That is a conflict of interest, so the order is alphabetical and OSSeva has its own row like everyone else.
- Who is on it. Vendors a buyer with an end-of-life version is likely to be offered: extended support specialists, operating system vendors, database specialists and an image vendor. A dependency-governance vendor was dropped because its pages could not be verified on the review date.
- Sources. Only the vendor's own public pages, linked per row. No analyst reports, review sites or customer claims. A cell says “Not listed” when the linked pages do not list it; that is not a claim the vendor cannot do it.
- Selection criteria. Each vendor is judged on the same questions: which layers and exact versions it lists, whether it ships patched builds of your version, how fixes reach you, what it commits to in writing by severity, and where it runs. The checklist is under how to choose.
- What is left out. Price figures (the table shows each vendor's published pricing model only), speed or quality claims, and anything we could not verify on a vendor page.
- Dates. The patch SLA and price model table was checked on 22 October 2026, and each row of the feature table shows its own check date. If a vendor fact here is out of date, tell us and we will recheck it against the vendor's page.
Feature table, as of 20 October 2026
What each vendor lists by layer. Rows show the date they were last checked against the vendor's own pages.
| Vendor | Operating systems | Runtimes, frameworks, libraries | Databases | Message brokers | Container images | Support hours | Checked |
|---|---|---|---|---|---|---|---|
| Canonical | Ubuntu LTS | Packages in the Ubuntu archive | PostgreSQL, Redis, Valkey, MongoDB, Cassandra (archive packages) | Kafka (archive package) | Not listed | Separate Ubuntu Pro + Support tier, 24/7 | 20 Oct 2026 |
| Chainguard | Not listed | Python, Java, JavaScript, Go and .NET libraries | In images, current versions | In images, current versions | 3,000+ images; up to 6 months of EOL grace | Not listed | 20 Oct 2026 |
| Command Prompt | Not listed | Not listed | PostgreSQL 12 and up, including end-of-life (PgLTS) | Not listed | Not listed | 24x7x365 support, 24/7/365 managed services | 20 Oct 2026 |
| HeroDevs | Not listed | JavaScript, Java (Spring, Tomcat, Struts), .NET, Python and PHP frameworks and libraries | PostgreSQL 14, 16, 18 | Kafka client library 3.1 only | Not listed | Fix targets of 14 and 30 days | 20 Oct 2026 |
| OpenLogic by Perforce | CentOS 7 and 8 | AngularJS, Bootstrap, PHP, Spring Boot and Framework, Tomcat 8.5 (LTS list) | MySQL 5.7 and 8.0 (LTS list) | Kafka 3.8 and 3.9 (LTS list) | Not listed | Up to 24/7/365 | 20 Oct 2026 |
| OSSeva | Not covered | Spring, Tomcat, Node.js, .NET | PostgreSQL, MySQL, MariaDB, MongoDB, Redis and Valkey, Elasticsearch | Kafka, RabbitMQ and Erlang/OTP, ActiveMQ, ZooKeeper | Bitnami-layout images for seven data and messaging families | 24/7 reactive on Assure; 24/7 managed with 15-minute P1 on Operate | 20 Oct 2026 |
| Percona | Not listed | Not listed | MySQL, PostgreSQL, MongoDB, Valkey and Redis, MariaDB; MySQL 5.7 and 8.0 post-EOL | Not listed | Not listed | 24x7 incident response (Advanced, Premium) | 20 Oct 2026 |
| Red Hat | RHEL 7 and 6 (Extended Life phase) | Not listed | Not listed | Not listed | Not listed | Per RHEL subscription | 20 Oct 2026 |
| SUSE | SLES 11, 12, 15; RHEL 6 to 9; CentOS 7 and later | Not listed | Not listed | Not listed | Not listed | Priority 24x7; Standard 12x5 | 20 Oct 2026 |
| TuxCare | CentOS, RHEL 7, Oracle Linux, Ubuntu, Debian, Amazon Linux 2 | OpenJDK, PHP, Python, .NET, Ruby, Node.js, Perl, Spring and other libraries | PostgreSQL 13, MySQL 8.0, MariaDB 10.6 | Kafka 3.2.3 and 3.5.2 | Not listed | 24/7 support | 20 Oct 2026 |
Extended support vendors compared
Vendors are listed alphabetically. Coverage is what each vendor publishes, not a judgement of what it could support if asked.
| Vendor | What they cover | Delivery | Best for | Source |
|---|---|---|---|---|
| CanonicalUbuntu Pro | Ubuntu LTS releases. Expanded Security Maintenance covers the whole Ubuntu archive (Main and Universe) for 10 years, or 15 with the Legacy add-on, for critical, high and selected medium vulnerabilities. Covered applications include PostgreSQL, Redis, Valkey, MongoDB, Kafka, OpenSearch, Cassandra, Spark and etcd. | Security updates through the Ubuntu archive, Livepatch for kernel fixes without a reboot and Landscape for fleet management. 24/7 break-fix support for infrastructure and applications is a separate Ubuntu Pro + Support tier. | Fleets on Ubuntu LTS that want the OS and its packaged applications patched together. | ubuntu.com/pro |
| ChainguardChainguard Containers and Libraries | More than 3,000 container images rebuilt from source daily, and Chainguard Libraries, a catalogue of Python, Java, JavaScript, Go and .NET packages. | Images and packages from Chainguard's registry. When an image's primary package reaches end of life, an EOL grace period keeps rebuilding the image for up to six months. It fixes vulnerabilities in the image's other packages, not the end-of-life primary package itself. | Teams on current versions that want minimal, low-CVE base images and a vetted dependency source. | chainguard.devChainguard EOL grace period |
| Command PromptPostgreSQL support, PgLTS and managed services | PostgreSQL support, consulting and managed services. Its PgLTS distribution supports end-of-life PostgreSQL version 12 and up and keeps deployments running until you are ready to upgrade. | Enterprise-wide 24x7x365 support for Postgres and the full stack, and 24/7/365 managed services, per its site. The home page names no support tiers. | PostgreSQL-only estates that want a specialist for end-of-life versions, with managed services available. | commandprompt.com |
| HeroDevsNever-Ending Support (NES) | End-of-life application frameworks and libraries, 36 product lines in all: AngularJS, Angular, Vue 2, React, Next.js, Node.js, Express and other JavaScript packages; Spring, Struts, Tomcat, Jetty, Hibernate and Quarkus on Java; .NET, Django, PHP, Rails and Drupal 7; and PostgreSQL 14, 16 and 18. | Drop-in replacements on the same version line, pulled from the NES registry through your package manager or a repository manager such as Nexus or Artifactory. Each release comes with a VEX statement and a signed attestation. Published fix targets are 14 and 30 days. | Application teams with an end-of-life framework in their code, especially JavaScript front ends and Java web frameworks. | herodevs.com/supportherodevs.com/pricing |
| OpenLogic by PerforceLong-Term Support (LTS) and Technical Support | Technical support for more than 400 open source technologies. LTS builds cover AngularJS, Bootstrap, CentOS 7 and 8, Kafka 3.8 and 3.9, MySQL 5.7 and 8.0, PHP, Spring Boot and Spring Framework, and Tomcat 8.5, each with a published end date. Spring Boot 2.7 and Spring Framework 5.3 run to 31 October 2027. | Tested, signed LTS packages from OpenLogic's private repository. Published patch timings (critical, CVSS 9 and above, within 14 days of disclosure; high, CVSS 7 and above, within 30 days) are a contractual SLA only for CentOS 7 and AngularJS; every other product has service level objectives. Technical support up to 24/7/365, plus consulting, migrations and training. | One support contract across a very wide estate, with patched builds for the products on the LTS list. | openlogic.com/products/long-term-support |
| OSSevaOSSeva Patch, Assure and Operate | The data and messaging stack, current and end-of-life versions on one contract: PostgreSQL, MySQL, MariaDB, MongoDB, Redis and Valkey, Elasticsearch, Kafka, RabbitMQ with its Erlang/OTP runtime, ActiveMQ and ZooKeeper, with Spring, Tomcat, Node.js and .NET alongside. End-of-life lines include PostgreSQL 11 to 13, MySQL 5.7 and 8.0, MariaDB 10.4 to 10.6, MongoDB 4.2 to 6.0, Kafka 2.8 to 3.9, RabbitMQ 3.8 to 3.13 and Spring Boot 2.6 and 2.7 with Spring Framework 5.2 and 5.3. | Signed patched builds of the version you already run, as packages, tarballs, container images, Helm charts and Maven artifacts (Patch: Critical within 48 hours, High within 7 days). Architecture review, audit evidence and 24/7 reactive support (Assure). 24/7 managed operations with a 15-minute P1 response (Operate). Runs on bare metal, VMs, your Kubernetes clusters or your cloud account. | One contract for databases, brokers and the runtimes under them, end-of-life versions included. | OSSeva supported versionsOSSeva services |
| PerconaPercona Support, ExpertOps and post-EOL support for MySQL 5.7 and 8.0 | MySQL, PostgreSQL, MongoDB, Valkey and Redis, and MariaDB under a single contract, on premises, in the cloud, hybrid or on Kubernetes. MySQL 5.7 and 8.0 have post-EOL support for up to three years after Percona Server's end of life. | 24x7 incident response and troubleshooting with response times as fast as 15 minutes, in Advanced and Premium tiers. ExpertOps adds hands-on operations: monitoring, tuning, patching and backup validation. For MySQL 5.7 and 8.0, Percona provides fixes for detected, reproducible CVEs after end of life. | Database estates that want deep database expertise across several engines, with operations available. | Percona supportPercona MySQL 5.7 post-EOLPercona MySQL 8.0 post-EOL |
| Red HatRHEL Extended Life Cycle Support (ELS) Add-on | Red Hat Enterprise Linux. The ELS Add-on extends the RHEL version in its Extended Life phase (the datasheet lists RHEL 7 and RHEL 6) beyond the standard 10-year lifecycle. | Certain critical-impact security fixes, selected urgent priority bug fixes and troubleshooting for the last minor release of the version. It is an add-on to a Standard or Premium RHEL subscription. | RHEL estates that need more time on a major version before they upgrade. | Red Hat ELS Add-on datasheet |
| SUSELong Term Service Pack Support (LTSS) and Multi-Linux Support | SUSE Linux Enterprise Server 11, 12 and 15: LTSS adds 3 years after general support, and LTSS Core adds 3 more for a core set of packages. Multi-Linux Support covers RHEL 6 to 9 and CentOS 7 and later. | Critical and important security patches and fixes for severity 1 and 2 defects. Priority support is 24x7 with a 1-hour response for critical issues; Standard is 12x5. LTSS extends an existing SLES subscription. Multi-Linux Support patches the RHEL or CentOS systems you already run, without a migration. | SLES estates, and RHEL or CentOS fleets that want another source of OS patches. | SUSE LTSSSUSE Multi-Linux Support |
| TuxCareEndless Lifecycle Support (ELS) | End-of-life Linux distributions (CentOS 6 to 8, RHEL 7, Oracle Linux 6 and 7, Ubuntu 16.04 to 20.04, Debian 10 and 11, Amazon Linux 2 and more), runtimes (OpenJDK, PHP, Python, .NET 6, 8 and 10, Ruby, Node.js, Perl), language libraries including Spring, and named application versions such as PostgreSQL 13, MySQL 8.0, MariaDB 10.6, Kafka 3.2.3 and 3.5.2, Tomcat, Jetty and WildFly. | Signed packages from TuxCare-hosted repositories, installed through yum, apt, pip, Maven, Gradle, npm and other tools, with 24/7 support. KernelCare adds kernel patching without a reboot. TuxCare's pages read on 20 October 2026 state no patch-time figure. | Linux fleets with end-of-life operating systems, runtimes and a long tail of libraries. | TuxCare ELSTuxCare ELS for applicationsTuxCare ELS for Spring |
Worked example: who covers Spring Boot 2.7?
Take one application on Spring Boot 2.7, which left open-source support on 30 June 2023. OSSeva's CVE directory records 6 advisories that affect it since then, 5 scoring 7.0 or higher, and the upstream fix for each exists only in a commercial build. Which vendors list it? The Spring extended support page lists each advisory and its fixed version.
| Vendor | Lists Spring Boot 2.7? | Source and end date |
|---|---|---|
| Broadcom (Tanzu Spring) | Yes | Commercial support to 30 Jun 2029 (spring.io); 24x7 support for over 50 Spring projects (enterprise.spring.io) |
| HeroDevs | Yes | Boot 2.7 with Framework 5.3 and Security 5.7 and 5.8 (herodevs.com/support/spring-nes); no end date stated on the page |
| OpenLogic by Perforce | Yes | LTS to 31 Oct 2027 (openlogic.com/products/long-term-support) |
| TuxCare | No | Its Spring page lists Boot 2.4, 2.6, 3.1 and 3.5, and Framework 5.2 and 5.3 |
| OSSeva | Yes | Spring Boot 2.6 and 2.7 patched builds; Critical within 48 hours and High within 7 days |
Where each vendor is the better fit
OSSeva does not patch operating systems or front-end frameworks. These are the cases where another vendor on this list is the stronger choice.
Canonical: Ubuntu Pro
If your servers run Ubuntu and you install your databases from the Ubuntu archive, Ubuntu Pro patches the OS and those packages under one subscription, for up to 15 years with the Legacy add-on. OSSeva does not patch operating systems.
Chainguard: Chainguard Containers and Libraries
If you can stay on current upstream versions, Chainguard's images and libraries remove most base-image CVE noise. Treat the grace period as a short bridge for end-of-life versions: Chainguard's documentation says it makes no exceptions to the six-month limit.
Command Prompt: PostgreSQL support, PgLTS and managed services
If your end-of-life problem is PostgreSQL alone, Command Prompt's PgLTS is built for that and adds managed services. OSSeva fits better when one contract must also cover MySQL, MongoDB, Kafka, RabbitMQ or ZooKeeper.
HeroDevs: Never-Ending Support (NES)
HeroDevs publishes the longest list of end-of-life JavaScript frameworks of any vendor here, and OSSeva does not cover front-end frameworks. For an AngularJS, Vue 2 or Struts application, start with HeroDevs.
OSSeva vs HeroDevsOpenLogic by Perforce: Long-Term Support (LTS) and Technical Support
If your estate spans hundreds of open source technologies and your end-of-life versions are on the LTS list, OpenLogic gives you one vendor for both. Its CentOS and PHP coverage is outside OSSeva's scope.
OSSeva vs OpenLogicPercona: Percona Support, ExpertOps and post-EOL support for MySQL 5.7 and 8.0
If your estate is databases only, Percona's database depth, its own software and ExpertOps are a strong fit, and it offers post-EOL support for MySQL 5.7 and 8.0. OSSeva fits better when the same contract must also cover Kafka, RabbitMQ, Elasticsearch or ZooKeeper.
OSSeva vs PerconaRed Hat: RHEL Extended Life Cycle Support (ELS) Add-on
For RHEL 7 or another RHEL release past its 10 years, the ELS Add-on keeps support with the company that builds the OS. OSSeva does not patch operating systems.
SUSE: Long Term Service Pack Support (LTSS) and Multi-Linux Support
If the end-of-life problem is a SLES service pack, or CentOS 7 and RHEL systems you cannot move yet, SUSE covers the operating system. OSSeva does not.
TuxCare: Endless Lifecycle Support (ELS)
For an end-of-life Linux distribution, rebootless kernel patching or a long tail of language libraries, TuxCare covers ground OSSeva does not. It also lists some database and Kafka versions, so check its list against the exact versions you run.
OSSeva vs TuxCareWhere not to pick OSSeva
We would rather lose a deal than sell coverage we do not have. Choose another route in these cases.
Your end-of-life problem is the operating system
OSSeva does not patch Linux distributions or kernels. For CentOS, RHEL, SLES or Ubuntu, use the OS vendor's extended support, or TuxCare or OpenLogic.
Your end-of-life problem is a front-end framework
OSSeva has no AngularJS, Vue 2, React or jQuery coverage. HeroDevs publishes the longest list of those.
You run Microsoft SQL Server or Oracle Database
Both are closed source and out of scope. OSSeva supports neither, though it does help teams move from Oracle Database to PostgreSQL.
You want a vendor to host the database
OSSeva does not host databases. Operate puts our engineers on clusters you run; if you want the data in a vendor's platform, pick a managed database service.
You can stay on current upstream versions
If an upgrade is already planned, extended support is a bridge you may not need. Current versions of most of this stack are supported by their communities, and hardened images such as Chainguard's reduce base-image CVEs.
You want Spring fixes from the Spring maintainers, or Spring Data and Spring Cloud
Broadcom sells commercial Spring support from the project's owner, with day-zero patches and 24x7 support for over 50 Spring projects. OSSeva's published Spring coverage is Framework, Boot and Security.
Your end-of-life problem is PostgreSQL alone
Command Prompt's PgLTS supports end-of-life PostgreSQL 12 and up, and HeroDevs lists PostgreSQL 14, 16 and 18. If PostgreSQL is the only gap, a PostgreSQL specialist is a reasonable first call.
You need training or one contract across hundreds of technologies
OpenLogic sells training and technical support across 400+ open source technologies. OSSeva covers the data and messaging stack and does not offer training courses.
Where OSSeva fits
OSSeva provides extended support for the data and messaging stack: one contract, one renewal date and one escalation path across PostgreSQL, MySQL, MariaDB, MongoDB, Redis and Valkey, Elasticsearch, Kafka, RabbitMQ, ActiveMQ and ZooKeeper.
- End-of-life versions are included, so consolidating support does not force an upgrade first. Every line OSSeva patches is on the supported versions page.
- It runs where you run: bare metal, VMs, your Kubernetes clusters or your cloud account. Patched builds ship as packages, tarballs, container images and Helm charts.
- Three tiers: Patch for signed builds, Assure for architecture review, audit evidence and 24/7 reactive support, and Operate for 24/7 managed operations with a 15-minute P1 response.
- On Patch, Critical CVEs (CVSS 9.0 and above) are fixed within 48 hours and High within 7 days.
- Priced per cluster for data and messaging, and per application for Spring. Book a discovery call for a quote, or see how pricing works.
How to choose an extended support vendor
Start from an inventory. endoflife.date and the OSSeva EOL tracker show which versions are already past end of life. Then put the same questions to every vendor on your shortlist.
- 01List the exact versions you runInclude the components inside other products: the ZooKeeper under Kafka, the Erlang/OTP under RabbitMQ, the base image under a Helm chart. Coverage is sold per version line, so a product name alone is not enough.
- 02Match each version to its layerOperating system, language runtime, application framework, database or broker, container image. Most vendors here are strong in one or two layers.
- 03Ask for patched builds, not only adviceConfirm the vendor ships new security fixes for your exact version. Help running an old version and a fixed build of it are different services.
- 04Check how fixes reach youPackage repository, artifact registry, container image, or engineers who apply them in your maintenance windows. Pick the route your change process already accepts.
- 05Read the patch commitment by severityLook for a written time to fix for critical and high CVEs, and check which tier carries it.
- 06Ask what an auditor will receiveSigned builds, SBOMs, VEX statements and CVE remediation records are the usual evidence.
- 07Confirm where it runsYour own servers, VMs, Kubernetes or cloud account, or only on the vendor's own operating system or platform.
- 08Count contracts and renewalsEach vendor adds a contract, a renewal date and an escalation path. Ask how each one prices: per cluster, per node, per environment or per package.
Who provides open source extended support for end-of-life software?
The main vendors are HeroDevs (application frameworks), TuxCare (Linux, runtimes, libraries and some applications), OpenLogic by Perforce (broad support plus LTS builds for a short list), Red Hat, SUSE and Canonical (their own operating systems and, for Ubuntu Pro, packaged applications), Percona (databases), Command Prompt (PostgreSQL), Chainguard (hardened images with a six-month EOL grace period) and OSSeva (one contract for the data and messaging stack, end-of-life versions included). Pick by the layer your end-of-life versions sit in.
Which vendors provide extended support for .NET 8 after 10 November 2026?
Microsoft ends support for .NET 8 on 10 November 2026. HeroDevs lists Never-Ending Support for .NET 6, 8 and 9. TuxCare lists .NET 6, 8 and 10 on its runtimes page. OSSeva ships patched .NET runtimes, ASP.NET Core and container images for the period after Microsoft support ends. The differences are the Windows and Linux matrix, the patch commitment and whether you want operations.
Who sells security patches for PostgreSQL 14 after end of life?
Community support for PostgreSQL 14 ends on 12 November 2026. After that date HeroDevs lists PostgreSQL 14, 16 and 18, Command Prompt's PgLTS supports end-of-life PostgreSQL 12 and up, and OSSeva ships patched PostgreSQL 14 builds, as it does for 11 to 13. TuxCare lists PostgreSQL 13, Ubuntu Pro covers PostgreSQL as packaged in Ubuntu, and OpenLogic sells technical support for PostgreSQL but lists no patched builds for it.
What are the best HeroDevs alternatives?
It depends on the layer. For Spring, Tomcat and Node.js, OpenLogic's LTS list and TuxCare's libraries and runtimes overlap with HeroDevs, and OSSeva covers Spring, Tomcat, Node.js and .NET. For databases and brokers such as MySQL, MongoDB, Kafka, RabbitMQ and ZooKeeper, OSSeva is the closer fit. For end-of-life JavaScript front ends, HeroDevs has the longest list; TuxCare lists Angular among its libraries and OpenLogic sells LTS for AngularJS and Bootstrap. OSSeva does not cover front-end frameworks.
TuxCare vs HeroDevs: which should I choose?
Choose TuxCare when the end-of-life problem includes the operating system, the kernel or language runtimes across a Linux fleet, delivered through yum, apt and other package managers. Choose HeroDevs when it sits in application code, especially JavaScript frameworks, delivered as drop-in packages with a VEX statement and signed attestation per release. Many estates use one of them for applications and another vendor for the infrastructure underneath.
Who provides open source stack maintenance?
For the data and messaging layer, OSSeva patches and can operate PostgreSQL, MySQL, MariaDB, MongoDB, Redis, Elasticsearch, Kafka, RabbitMQ, ActiveMQ and ZooKeeper on your infrastructure. Percona does the same for several databases, and OpenLogic sells technical support across more than 400 technologies. Operating systems are the OS vendors' job, and application frameworks are HeroDevs' and TuxCare's.
Where can I compare ZooKeeper support packages?
Four vendors are worth asking. OSSeva patches ZooKeeper 3.4, 3.6 and 3.7, with 3.5 as custom support, and ships it with the products that embed it. OpenLogic lists ZooKeeper under technical support, with no LTS builds listed. TuxCare's all-products list does not include ZooKeeper, and HeroDevs' product list does not either. Confirm the exact version with each vendor.
Is there extended support for MySQL 5.7 and 8.0?
Yes. OSSeva ships patched builds for MySQL 5.7 and 8.0 from the Community Edition you already run. OpenLogic's LTS covers 5.7 and 8.0, TuxCare's ELS lists 8.0, and Percona offers post-EOL support for 5.7 and 8.0 for up to three years after Percona Server's end of life.
Who sells extended support for Spring Boot 2.7?
Broadcom (to 30 June 2029), HeroDevs, OpenLogic (to 31 October 2027) and OSSeva list Spring Boot 2.7. TuxCare's Spring page lists Boot 2.4, 2.6, 3.1 and 3.5 but not 2.7. The worked example above sets them side by side.
Is there extended support for Kafka and RabbitMQ?
For Kafka, OSSeva covers 2.8 to 3.9, OpenLogic's LTS covers 3.8 and 3.9, and TuxCare lists 3.2.3 and 3.5.2. For RabbitMQ, OSSeva ships patched builds for 3.8 to 3.13 and 4.0 to 4.2, with the Erlang/OTP runtime underneath.
Can I use more than one extended support vendor?
Yes, and large estates often do: one vendor for the operating system, one for application frameworks and one for databases and brokers. Each one adds a contract and an escalation path, so keep the count as low as your version list allows.
How much does extended support cost?
Most vendors here quote per customer, and this page does not estimate other companies' prices. The patch SLA and price model table shows each vendor's published pricing unit, such as HeroDevs per user or OSSeva per cluster, and where none is published. Ask each one for a quote against the same version list. Book a discovery call for an OSSeva quote.
Get a quote
Bring your version list.
We will tell you which parts are ours.
One contract for your databases, brokers and the runtimes under them, end-of-life versions included.
Prefer to talk or read more first?