OSSeva Blog
OperationsWhat It Costs to Patch Unsupported Node.js: Upgrade vs Extended Support
What does it cost to patch unsupported Node.js?
It costs the sum of your upgrade effort or a support subscription, plus the cost of risk while you wait. No public figure fits every estate, so this guide lists the drivers on each side and the formula to compare them with your own numbers. For the service itself, see OSSeva's Node.js extended support page. Node.js 18 ended on 30 April 2025 and Node.js 20 on 30 April 2026, so every service on them is already making this choice.
Running Node.js in production? OSSeva patches and supports it, end-of-life versions included.
Node.js extended support: what is coveredWhat drives the cost of upgrading?
Native add-ons, deprecated APIs and test coverage drive most of it. The work scales with the number of services, not with the size of Node.js.
| Driver | Why it moves the cost |
|---|---|
| Number of services and base images | Each one needs its runtime and image changed and retested |
| Native add-ons | Compiled for one ABI (115 on Node.js 20, 127 on 22, 137 on 24), so each must be rebuilt or replaced |
| Deprecated or removed APIs | Code that relies on url.parse() or other deprecated calls needs changes before it runs cleanly on 24 |
| Test coverage | Thin tests turn a rebuild into manual retesting |
| Re-certification | A vendor or auditor may need to approve the new runtime |
| Downtime and release windows | A freeze or a maintenance window sets when the work can land |
The upgrade guide lists the changes that break real applications, so you can size the first three rows service by service.
What drives the cost of extended support?
The number of runtimes, the lines they run and the tier set the subscription; your own engineering time adds to it. A subscription does not remove the upgrade, so count the upgrade you still plan to do.
| Vendor | What it publishes about price | Read on 17 November 2026 |
|---|---|---|
| HeroDevs NES | Custom pricing, billed annually, multi-year options | herodevs.com/pricing |
| TuxCare ELS | No price on the Node.js page; "pricing based on your environment" | tuxcare.com Node.js ELS page |
| OSSeva | Priced per application runtime; the tier (Patch, Assure or Operate) sets how much work OSSeva takes on. No price list is published | How pricing works |
Get two or three vendors to quote the same list of runtimes and lines, so the quotes compare. The cost of staying also includes things no vendor invoices: scanner findings that stay open, audit exceptions and the time to explain them.
How do you compare the two?
Compare cost of moving now with cost of staying over the years you plan to stay. The upgrade vs extended support calculator uses these formulas and holds no vendor prices:
- Cost of moving now: (instances x engineer-days per instance x cost of an engineer-day) + (testing and re-certification days x cost of an engineer-day) + your one-off downtime and risk cost.
- Cost of staying: (extended support cost per year + other yearly cost of staying) x years you plan to stay, with the cost of moving added once at the end if you will still have to upgrade.
- Break-even: cost of moving divided by the yearly cost of staying, in years.
If the break-even is longer than the time you would stay, moving is cheaper over that period. If you will stay for years, a service on an ended line collects open findings every security release. The decision framework turns the comparison into a rule per service.
Frequently asked questions
How much does extended support for Node.js cost?
It depends on the vendor, the number of runtimes and the tier, and only the quote shows it. HeroDevs and TuxCare do not publish a Node.js price, and OSSeva prices per application runtime.
Is upgrading always cheaper than extended support?
Not always. A service with an add-on that will not build, or a vendor certification on Node.js 20, can cost more to move than to patch. Most services are cheaper to move than to patch for years.
What costs do people forget?
Re-certification, retesting of base images, the upgrade you still owe at the end of a support contract and the time spent defending open scanner findings.
Does the calculator include OSSeva prices?
No. It holds no vendor prices, OSSeva's included; every money value is one you type in.
How this was checked
Vendor price statements are from herodevs.com/pricing and the TuxCare Node.js page, read on 17 November 2026. The formulas are copied from the calculator page. The ABI numbers and end dates are from the Node.js release schedule and endoflife.date. This guide contains no cost figure on purpose.
Tags
Related articles
Upgrade Node.js or Buy Third-Party Patches? A Decision Framework
November 17, 2026OperationsHow to Choose a Node.js Extended Support Vendor: 12 Questions to Ask
November 17, 2026OperationsNES, ELS and Stay-Put Support for Node.js: How the Models Differ
November 17, 2026SecurityWho Provides Node.js Security Patches After End of Life? (Node 18 and 20)
October 6, 2026MigrationNode.js Version Upgrade: 18 and 20 to 22 or 24, Step by Step
October 5, 2026OperationsHow to Choose a PostgreSQL Extended Support Vendor
November 17, 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?