Back to blog

OSSeva Blog

Operations

What to Look for in a .NET Extended Support Provider

7 min read

What to look for in a .NET extended support provider

Check five things before you buy: which .NET versions it patches, which operating systems, how fixes are delivered, how fast it commits to patch, and what it states in writing. Microsoft ended .NET 8 and .NET 9 on 10 November 2026 and sells no extension, so a provider is now the only source of fixes for them. Our .NET 8 extended support page sets out what OSSeva offers; this guide is for judging any provider, including us.

QuestionWhy it mattersWhat to ask for
Which versions?Lists differ: one covers 6, 8 and 9, another 6, 8 and 10Your exact versions in writing, including .NET 9 if you run it
Which platforms?Windows hosts, Linux hosts and containers need different packagingEach OS and architecture you run, named
Which components?Runtime, ASP.NET Core, Entity Framework Core, SDK, desktop runtimesThe component list, and whether container base images are patched
How are fixes delivered?Installer, script, package feed or container image decides your rollout effortSigned builds that fit your repository manager and pipeline
How fast?Time to patch sets your exposure windowPublished days by severity, counted from disclosure
What is committed?"Targets" and "where possible" are not commitmentsAn SLA, and which severity scale it uses
Which pricing basis?Per user, per server and per application differ widely for the same estateA quote on your inventory, not a list price
How do you leave?The goal is to move to .NET 10, not to stayTerm length and what you keep if you stop

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

.NET extended support: what is covered

What providers publish about .NET 8

Published terms vary more than the marketing suggests. The table uses only what each vendor states on its own pages, read 17 November 2026; a blank means the page does not say.

HeroDevs NESTuxCare ELSOSSeva
.NET versions6, 8 and 91.1, 2.0, 2.2, 6, 8 and 10 on its docs page; 9 is not listed6, 7, 8 and 9
PlatformsWindows and Linux (its .NET 8 announcement)Windows list on its docs page; its product page says Linux and Windows without naming distributionsWindows installers; Linux apt, yum, Docker and binaries
ResponseSame-day resolution where possible; its SLA documentation sets targets of 14 days for Critical and 30 for HighProduct page: 14 days from disclosure for CVSS 7.0 and above, 60 for medium, 90 for lowCritical within 48 hours, High within 7 days
DeliveryInstaller, PowerShell script or manual setup filesSigned with GPG and Sigstore

Where each is the better fit: HeroDevs suits a team that already buys end-of-life support for other frameworks from it and runs .NET 9. TuxCare suits a Windows-heavy estate that wants a published patch window. OSSeva suits Linux containers and teams that want patches and 24/7 operations from one vendor. The full provider comparison has the detail and the sources.

Red flags

Walk away from vague scope, unstated version lists and fixes you cannot verify.

  • "All .NET versions" without a list.
  • No answer on .NET Framework: OSSeva's patched builds cover .NET (Core and 5 and later), and Framework follows its Windows lifecycle, so any provider claiming otherwise should say how.
  • Patches you cannot check: ask how builds are signed and whether an SBOM ships.
  • No exit plan. Extended support is a bridge to .NET 10; see upgrade or stay.

How we chose these criteria

We read each vendor's own .NET page and published SLA or docs page on 17 November 2026 and Microsoft's .NET support policy the same day. OSSeva is one of the providers compared, so treat the list as a method, not a ranking. We did not run any provider's builds.

Frequently asked questions

Does Microsoft offer a .NET extended support option?

No. See whether Microsoft offers ESU for .NET.

Should the provider cover .NET 9 as well as .NET 8?

If you run .NET 9, yes: it ended on the same day as .NET 8. Not every provider lists it.

Is a published SLA better than a "same-day" promise?

Yes. A number of days by severity, counted from disclosure, is something you can audit. A target is not a commitment.

How long should I plan to stay on extended support?

Until the move to .NET 10 is done. Set a date per application when you sign.

Where OSSeva fits

OSSeva is one of the providers above. Its published terms are on the .NET 8 extended support page, including where it is not the right fit: .NET Framework, and applications that can move to .NET 10 this quarter.

Sources

Read 17 November 2026: HeroDevs NES for .NET and its SLA, TuxCare ELS for .NET docs and product page, and Microsoft's .NET support policy. OSSeva facts: the .NET support page.

Tags

.NET.NET 8.NET 9Extended SupportVendor ComparisonBuyer's Guide

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