OSSeva Blog
OperationsHeroDevs vs TuxCare vs OpenLogic: which extended support fits your stack
The short answer
HeroDevs sells Never-Ending Support for named frameworks and libraries, TuxCare sells Endless Lifecycle Support mainly for Linux and a set of language runtimes, and OpenLogic (Perforce) sells long-term support for a short list of Java-stack and other open source, plus technical support for a wider list. Which fits depends on what you run. Every vendor fact below comes from that vendor's own page, read on 14 November 2026. OSSeva sells one of the four options in the tables; the method is at the end.
Running open source in production? OSSeva patches and supports it, end-of-life versions included.
HeroDevs, TuxCare, OpenLogic and OSSeva side by side
| Vendor | Product | What it covers | Pricing as published | Patch window as stated |
|---|---|---|---|---|
| HeroDevs | Never-Ending Support (NES) | Frameworks, libraries and some servers, by product: Node.js, .NET, Spring, Tomcat 8.5, Kafka, PostgreSQL, Angular, React and others | "Custom Pricing", billed annually. Licence based on the number of users who commit code | "Critical fixes are addressed within 14 days of discovery" (support page) |
| TuxCare | Endless Lifecycle Support (ELS) | Linux distributions; runtimes (.NET, Node.js, OpenJDK, PHP, Python, Ruby); an applications list including PostgreSQL 13, MySQL 8.0, Kafka and Tomcat | Checkout showed up to 10 systems at $5,000 a year; larger bands by quote. Pricing page is quote-only | .NET page: 14 days for critical and high (CVSS 7.0+), 60 medium, 90 low. Node.js page: none stated |
| OpenLogic (Perforce) | Long-term support (LTS) and technical support | LTS: AngularJS, Bootstrap, CentOS, Kafka, MySQL, OpenJDK, PHP, Spring Boot and Framework, Tomcat. Technical support list is separate | Not published ("Request LTS Pricing") | LTS page: within 14 days of disclosure for critical (CVSS 9+), 30 days for high (CVSS 7+) |
| OSSeva | Patch, Assure, Operate | Brokers, databases and runtimes: PostgreSQL, MySQL, Kafka, ZooKeeper, RabbitMQ, Redis, MongoDB, Spring, Tomcat, .NET, Node.js and more | Not published. Priced per cluster for most technologies (Tomcat per application server, Spring Boot per application, .NET per application runtime environment, Node.js per runtime). A senior engineer replies within 1 business day with a quote | Critical within 48 hours, High within 7 days |
Windows are not comparable one for one: each vendor counts from a different starting point (discovery, disclosure, or a ticket), and HeroDevs and TuxCare state some windows only on some pages. Extended support pricing compared sets out the pricing bases in more detail, and how OSSeva pricing works explains the units.
How does HeroDevs Never-Ending Support for Node.js work?
HeroDevs lists Node.js versions 12, 14, 16, 18 and 20 on its Node.js NES page (read 14 November 2026), delivered as container images and binaries. The page describes an install through nvm from the HeroDevs registry using an authentication token, and says every patch it ships has a published CVE entry, one CVE per fix.
The licence is a commercial licence for the support services, and the pricing page says it depends on the number of users who commit code, with no figure shown. On timing, the page says response times vary with severity and that a service level agreement is available on request; it states no hours or days. HeroDevs' wider support page gives the 14-day critical-fix target quoted above.
Does TuxCare patch end-of-life Node.js?
Yes: TuxCare's Node.js page (modified 22 October 2026) lists versions 12, 14, 16, 18 and 20 as currently supported, and says Node.js 22 is added when it reaches end of life. Patches arrive through npm and your existing toolchain, as signed packages from TuxCare-hosted repositories, with an SBOM and VEX data. The page mentions a contractual SLA and 24/7 assistance but gives no patch window, and pricing is "based on your environment" through a quote.
Its .NET page (modified 22 September 2026) does give windows, and lists .NET 6, 8 and 10 where HeroDevs lists 6, 8 and 9. Check your exact version against both.
What does OpenLogic cover?
OpenLogic's long-term support table (read 14 November 2026) gives an end date per line, which neither HeroDevs nor TuxCare does on the pages read.
| Technology | Versions | LTS end date |
|---|---|---|
| Spring Boot | 2.7; 3.1 to 3.5 | 31 Oct 2027; 30 Jun 2028 |
| Spring Framework | 5.3; 6.0 to 6.2 | 31 Oct 2027; 30 Jun 2028 |
| Apache Tomcat | 8.5 | 31 Dec 2028 |
| Apache Kafka | 3.8; 3.9 | 30 Nov 2028; 31 Mar 2029 |
| MySQL | 5.7, 8.0 | 30 Sep 2028 |
| OpenJDK | 8, 11 | 30 Nov 2028 |
Tomcat 9 is not in that table. OpenLogic's Spring page describes 1-hour response times under Premium Support and delivery through a private Maven or Gradle repository. Its Tomcat page states no versions, response times or price.
Which vendor covers which technology?
| Technology | HeroDevs | TuxCare | OpenLogic | OSSeva |
|---|---|---|---|---|
| Node.js | 12, 14, 16, 18, 20 | 12, 14, 16, 18, 20 | Not found on its pages | 14 to 20 |
| .NET | 6, 8, 9 | 6, 8, 10 | Not found on its pages | 6 to 9 |
| Spring | Spring Boot 1.x, 2.x, 3.x | Not on its applications list | LTS table above | Boot 2.6 to 3.5; Framework 5.2 to 6.2 |
| Tomcat | 8.5 | 8.5.100+ and specific 9.0 builds | LTS 8.5; technical support | 8.5 to 11 |
| Java / OpenJDK builds | Not listed | OpenJDK, under runtimes | LTS 8 and 11 | No: OSSeva does not patch the JVM |
| PostgreSQL | Listed | 13 | Technical support only (20 Oct) | 11 and later lines |
| MySQL | Connector/J only | 8.0 | LTS 5.7, 8.0 | 5.7 and 8.0 |
| Kafka | Listed | 3.2.3, 3.5.2 | LTS 3.8, 3.9 | Brokers 2.8 to 3.9 |
| ZooKeeper | Not listed | Not on its lists (20 Oct) | Technical support only (20 Oct) | 3.4, 3.6, 3.7; 3.5 on request |
| RabbitMQ | Java client only | Not on its lists (20 Oct) | Technical support only (20 Oct) | 3.8 to 4.2 with Erlang/OTP |
| Redis | Not listed | Not on its lists (20 Oct) | Technical support only (20 Oct) | 6.2 and 7.0 |
| Linux OS | Not listed | 70+ distribution versions | CentOS 7 and 8 LTS | No |
"Not listed" and "not found" mean the vendor's own pages did not show it on 14 November 2026, except rows marked 20 Oct, which come from the dated pages OSSeva vs HeroDevs, OSSeva vs TuxCare and OSSeva vs OpenLogic. They are not a statement that a vendor cannot do it: TuxCare says it will add open source that is not on its list if asked. Listed does not mean every version: check yours.
How we compared
We read each vendor's own pages on 14 November 2026: HeroDevs' support, Node.js and pricing pages; TuxCare's Endless Lifecycle Support, Node.js, .NET and applications pages and its checkout; OpenLogic's long-term support, solutions, Spring and Tomcat pages. We copied only what a page states, with the date, and left a cell as "not stated" where it says nothing. OSSeva sells one of these four options, so read its column as a vendor's own statement. OSSeva is not a fit for Linux operating systems, front-end frameworks such as Angular or Vue, PHP, Python, or the Java runtime itself.
Which should you choose?
- A Linux estate or a runtime such as PHP, Python or Ruby: TuxCare lists it; HeroDevs and OSSeva do not cover Linux.
- Front-end frameworks such as Angular, Vue 2 or React: HeroDevs.
- A Java stack already on Perforce, or a need for a dated LTS end per line: OpenLogic.
- Data, messaging and runtime middleware past end of life (Kafka, ZooKeeper, RabbitMQ, Redis, PostgreSQL, MySQL, Node.js, Spring, Tomcat): OSSeva. See open source extended support vendors for a wider list.
- A mixed estate: one vendor per layer is common.
Frequently asked questions
Does HeroDevs publish prices?
Not on the pages read on 14 November 2026: its pricing page shows "Custom Pricing, billed annually" on each product, and says the licence depends on the number of users who commit code. That is why no HeroDevs price is compared here.
Which of these covers end-of-life Kafka or RabbitMQ?
For Kafka: HeroDevs lists Apache Kafka, TuxCare lists versions 3.2.3 and 3.5.2, OpenLogic's LTS table lists 3.8 and 3.9, and OSSeva patches brokers 2.8 to 3.9. For RabbitMQ the servers are not on the HeroDevs list (only a Java client), and TuxCare's and OpenLogic's lists were last checked on 20 October 2026; OSSeva patches RabbitMQ 3.8 to 4.2.
Can I combine providers?
Yes. Coverage is per technology, so an estate can use one vendor for Linux, another for a framework layer and a third for brokers and databases. Keep each component with a single vendor so that fixes are not delivered twice.
Tags
Related articles
Who Provides Support for Apache Hadoop 2.x and 3.x After End of Life?
October 7, 2026OperationsWho Provides Support for Apache HBase 1.x and 2.x After End of Maintenance?
October 7, 2026OperationsWho Provides Support for Apache Flink 1.x and 2.x?
October 7, 2026OperationsWho Provides ClickHouse Support for Releases Outside the LTS Window?
October 7, 2026OperationsWho Provides Support for Hazelcast IMDG 3.x, 4.x and Older 5.x Releases?
October 7, 2026OperationsWho Provides Support for Erlang/OTP 25 and 26 After End of Life?
October 7, 2026Get a quote
Ready to get your open source under control?
Tell us what you run. An OSSeva engineer replies within 1 business day with CVE coverage and a price for your stack.
Prefer to talk or read more first?