Uncia
FR / EN Demo

Glossary

Software obsolescence

Software obsolescence is the state of software its vendor no longer maintains: it stops receiving fixes, security patches included, and support. It is dated version by version, from the end-of-support dates vendors publish.

Updated

What is software obsolescence?

Software obsolescence is the state of software its vendor no longer maintains, or no longer maintains fully: no more security patches, no more bug fixes, no more support. The software runs exactly as it did the day before. But nobody will repair it.

IT obsolescence management is the recurring work that follows from this: knowing which versions are running, until when they are maintained, and what replaces them. End of life software tracking is the same job seen from the calendar side. When hardware is included, people simply say IT obsolescence.

It matters for practical reasons. Security: a flaw found after support ends gets no patch, and Microsoft itself writes that it may be unable to provide security updates for older products. Compatibility: sooner or later an unsupported system is refused by the vendor of the application it runs, by the backup agent or by the next hypervisor release. Accountability: an auditor or an insurer may ask for the list of unsupported systems and the plan for them, and you need to be able to produce it.

End of sale, end of support and end of life: what is the difference?

Vendors do not use the same words, and that is the first source of error in an obsolescence table. Four milestones keep coming back.

End of sale: the vendor stops selling the version, which is still maintained. End of standard support: the vendor stops feature work and non-security fixes. End of extended support, where it exists: security patches stop. This is the date that matters for risk, and the one most often called end of support or end of life. Paid extended coverage: some vendors sell security patches for a limited time after that date.

Microsoft offers a readable example of end of support vs end of life. Its Fixed Lifecycle Policy provides at least five years of Mainstream Support, then, for some products, Extended Support during which security updates continue with no design changes or non-security updates. For Windows Server 2016, Mainstream Support ended on January 11, 2022 and Extended Support ends on January 12, 2027, according to Microsoft's lifecycle page and endoflife.date, both checked on November 17, 2026. After that, the Extended Security Updates program supplies critical and important security updates for up to three years. Microsoft describes it as a last resort paid option that does not extend the product's lifecycle and does not include technical support.

So a column headed "end of support" should say which milestone it holds: confusing the end of standard support with end of life throws the replacement calendar off.

How do you date an end of support?

The authoritative source is the vendor's lifecycle page. Each vendor publishes its dates in its own format and vocabulary. With fifty products in an estate, collecting them one by one takes time, and the collection goes stale.

The endoflife.date project addresses that. It describes itself as a site that documents end-of-life dates and support lifecycles for various products, aggregating data from various sources, and it makes the data available through an API. It is open to contributions, and its GitHub repository is published under the MIT license. It makes dates comparable across vendors, which no vendor page does.

Two precautions. endoflife.date is an aggregation kept by contributors: for a decision with consequences (a migration budget, an answer to an auditor), check the date on the vendor's page and note the day you checked. And a date only holds for an exact version. "Windows Server" is not enough: you need the version, sometimes the edition or the servicing channel. An inventory that records only the name of the operating system cannot be dated.

How do you run an obsolescence review?

An obsolescence review fits in five columns, filled in order.

Inventory: the list of machines and products, taken from tools and not from memory. A hypervisor export gives the declared operating system of each virtual machine, and the cloud provider gives its images and managed services (what an IT asset inventory should contain). Versions: the operating system, but also the database, the application server, the middleware. This is the column most often left empty. Dates: for each product and version, the end of support, which milestone it is, the source and the day it was checked. Criticality: what the machine carries, which is what an impact analysis establishes. An unsupported server hosting a test tool and an unsupported server running invoicing do not belong in the same quarter. Plan: for each line, a decision (upgrade, replace, isolate in the meantime, accept the risk in writing), an owner and a deadline.

The report for a committee does not repeat that table. It says what is already out of support, with the applications concerned, what will be within the coming year, which is about the time it takes to budget and run a migration, and which decisions are requested. Every date carries its source. A committee that cannot verify a date will debate it, and the meeting goes to that.

What is the difference between obsolescence and technical debt?

Technical debt is broader. It covers everything that will have to be reworked one day: code that is hard to maintain, workarounds in the architecture, scripts with no author, missing documentation. Obsolescence is the part of it you can date: it has a deadline published by a third party, and it is not negotiable. That makes it easier to present to management, and a good way into the rest.

The pitfalls of a review are nearly all inventory blind spots. Firmware on servers, storage arrays and switches has its own lifecycle, seldom tracked. Appliances (firewalls, load balancers, backup devices) embed a system their vendor maintains at its own pace. Middleware ages under an application that is itself current: an application server, a Java version, a database engine. The cloud is no exception. AWS Lambda, for one, deprecates a runtime when one of its components no longer receives security updates, and warns that it may then stop applying patches to it. A system on paid extended coverage still needs handling too: it has to be replaced before that program ends.

Which tools track software obsolescence?

A spreadsheet suits a small estate: one line per product and version, a date, a source. It has to be re-entered at every review and cannot say which machines run a given version.

A CMDB or an asset management tool ties versions to machines and to support contracts. Its value depends on how fresh the entered or discovered versions are (what a CMDB is).

Agent-based inventory tools and scanners record what is installed in fine detail, down to libraries. They cover machines where the agent is deployed well, and appliances, network equipment and forgotten machines less well.

endoflife.date and its API supply the dates: you have to bring the list of products and versions.

A map derived from the sources starts from existing exports (hypervisor, cloud, CMDB), picks up the versions in them and matches them to published dates, keeping track of what each machine carries. It only sees what the exports contain: middleware absent from every source still has to be collected another way (what to do with an RVTools export).

What Uncia brings, and what it does not do

Uncia reads, read-only, the operating system and product versions in your sources (connectors and the exports you drop in), then dates each end of support from endoflife.date. Each end-of-support date carries its source, per product and per machine, cloud included, with the applications and flows that depend on them (dated end-of-support across the estate). The obsolescence report is written from those facts: each sentence points to its fact, and the Word or PDF export keeps the sources as notes. Uncia also matches the products in your estate against published vulnerabilities (NVD, CERT-FR) and reads your scanner reports (Tenable, Qualys, Cyberwatch): each vulnerability is tied to the machines, applications and flows it affects, next to their end-of-support date.

Uncia only knows the versions present in the sources it has read. A version missing from an export is reported as undetermined, not assumed. Uncia upgrades nothing and changes nothing, the replacement plan remains your teams' decision, and its knowledge updates with each collection.

Sources

Frequently asked questions

What is the difference between end of support and end of life?

Vendors use the terms differently. In practice the date that matters is the one when security patches stop: the end of Extended Support at Microsoft, often called end of life elsewhere. An obsolescence table should state which milestone each date refers to.

When does Windows Server 2016 support end?

Mainstream Support ended on January 11, 2022 and Extended Support ends on January 12, 2027, according to Microsoft's lifecycle page and endoflife.date (checked on November 17, 2026). Microsoft then offers paid Extended Security Updates for up to three years.

What is endoflife.date?

An open project that documents end-of-life dates and support lifecycles for various products, from various sources, and exposes them through an API. Its GitHub repository is under the MIT license. For a decision with consequences, check the date on the vendor's page.

Can you keep running software after its end of support?

Technically yes, it keeps working. It no longer receives security patches, unless the vendor sells a paid program. Keeping it is a risk decision: put it in writing, with an owner, isolation measures and a replacement deadline.

Does obsolescence apply to the cloud too?

Yes. Virtual machines in the cloud run operating systems that have an end of support, and managed services follow their own calendar. AWS Lambda, for example, publishes deprecation dates for its runtimes.

Every week, an article to know your IT estate better

Architecture documents, end of support, NIS2, CMDB, migrations: methods you can apply with or without Uncia.

Get a call from our team

Thirty minutes with a member of our team, remote or on site: Uncia on a demonstration instance, then on part of your own estate if you wish. We reply within 48 hours.

Request received

Thank you. A member of our team will reply within 48 hours to set a date.