Back to blog

OSSeva Blog

Operations

NES, ELS and Stay-Put Support for Node.js: How the Models Differ

7 min read

How do NES, ELS and stay-put support differ for Node.js?

They differ in what you install and where fixes come from. HeroDevs Never-Ending Support (NES) replaces your Node.js with its own build, TuxCare Endless Lifecycle Support (ELS) delivers patches through your package tooling, and stay-put support keeps you on your version with a patched runtime. All three exist because Node.js 18 and 20 no longer get upstream fixes. OSSeva sells the third model: Node.js extended support.

Running Node.js in production? OSSeva patches and supports it, end-of-life versions included.

Node.js extended support: what is covered

The three models side by side

Read each row as what the vendor says on its own page. Facts were read on 17 November 2026.

HeroDevs NESTuxCare ELSOSSeva stay-put support
Node.js lines12, 14, 16, 18, 2012, 14, 16, 18, 20; 22 when it ends14, 16, 18, 20; 22 after 30 April 2027
What you installA drop-in replacement: container images and binaries, installable from a HeroDevs registry mirror (its page shows a version-manager example)Patches pulled through npm and your existing toolchain from TuxCare-hosted repositoriesSigned Docker images (Alpine and Debian), apt and yum packages, binaries
What changes for youThe runtime source or image tagA configuration change, per TuxCareThe image tag
Patch timing published14 days Critical, 30 days High (targets)SLA-backed, no timingsCritical 48 hours, High 7 days
EvidenceOne CVE entry per fixSBOM and VEX per release; SLSA Level 3 "coming soon"Attestation package on Assure
Beyond Node.jsMany JavaScript, Java and .NET productsOperating systems, runtimes and librariesBrokers, databases, Java stack, with Operate for 24/7

How does HeroDevs NES work for Node.js?

NES is a subscription for a maintained build of an ended Node.js version. HeroDevs says it ships container images and binaries as a drop-in replacement, covers fixes for all severity levels and publishes one CVE entry per fix. Its SLA gives fix targets of 14 days for Critical and 30 days for High, counted from the earlier of a verified report or public disclosure. HeroDevs describes its offer as the only one endorsed by the OpenJS Foundation; the Node.js end-of-life page lists three providers.

Does TuxCare patch end-of-life Node.js?

Yes: TuxCare lists Node.js 12, 14, 16, 18 and 20 for ELS. Its page says patches are backported, tested, signed and delivered through npm and your existing toolchain, with SBOM and VEX documents for each patched release and 24/7 expert assistance. The page states an SLA but no timings, and says Node.js 22 is added when it reaches end of life. The page's own data shows it was last modified on 22 October 2026.

What is stay-put support?

It keeps your service on its current version and patches that version. You do not change the Node.js line; you change the image tag or package source. OSSeva patches the runtime, including V8 and libuv fixes, and the Operate tier can run it with a 15-minute P1 response. HeroDevs is the better fit when your exposure is JavaScript and front-end frameworks around Node.js, and TuxCare when you already buy its coverage and want fixes through npm.

How should you choose between them?

Match the delivery model to your pipeline, then compare windows and evidence. The 12 questions in how to choose a Node.js extended support vendor cover that, and who patches Node.js 18 and 20 lists the providers. Whichever model you pick, set the upgrade date: the Node.js project itself calls commercial support for an ended line a temporary solution.

Frequently asked questions

How does HeroDevs NES work?

You swap your end-of-life Node.js for a HeroDevs-maintained build delivered as container images and binaries, and fixes arrive as new builds under an SLA.

Does TuxCare patch EOL Node?

Yes, for Node.js 12, 14, 16, 18 and 20, through npm and your existing toolchain, per its own page.

Is one model more secure than another?

The pages do not say. Compare the patch windows, what is covered beyond the runtime and the evidence you receive.

Can I use more than one?

Yes, per service, but keep each runtime with one provider so a fix is not delivered twice.

How this was checked

Facts come from herodevs.com/support/node-nes, docs.herodevs.com/sla, tuxcare.com/endless-lifecycle-support/nodejs-eol-support and nodejs.org/en/about/eol, read on 17 November 2026. We compared what the vendors publish and did not run their builds.

Tags

Node.jsExtended SupportVendor ComparisonEnd of LifeHeroDevsTuxCare

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

Only your email is required · An engineer replies within 1 business day · No commitment

Prefer to talk or read more first?

Book a call