Check us before you rely on us.

This page is the short route through everything we publish about our own data. Each section says one thing and links to the proof.

Of the 17,995 dates we serve for the 367 products with a paid-support market, 80.6% are vendor-sourced: read from, or checked against, the vendor's own lifecycle source. The rest come from the open endoflife.date dataset and are labelled as such. 123 vendor feeds are read on every run and 536 vendor statements are re-checked at every build. How these are counted.

Where the dates come from

Every lifecycle date we serve carries a label that says where it came from: set from the vendor's own publication, read from the vendor's lifecycle page, cross-checked by a person, from our own catalogue curated from the vendor, or from the open endoflife.date dataset only. For products with a paid-support market we read the vendor's own lifecycle page or API twice a day.

The scoreboard and the labels →

How a date changes

A date on this site changes only when the vendor's own page says so. Before we change a served date by hand, we read the vendor's page twice and the two reads must agree. A blog post, a mirror or an AI answer is never a source. When the community dataset moves a date by a year or more, drops a date or removes a version, that change is held until a person has read the vendor's page.

Corrections policy →

What we corrected

Every correction is published with the day it was made, the value we served before, the value we serve now and the vendor page it came from. The change record lists the last 180 days.

Change record →

What we do not know

Some dates cannot be confirmed at the vendor, and some products we do not cover. We list both rather than guess.

Dates we could not confirm →  ·  What we do not cover, and why →

What is ours and what is open data

endoflife.ai and endoflife.date are separate projects. endoflife.date is an open source dataset under the MIT License. We build on it, contribute to it, and label every date that comes from it alone. The EOL Risk Score™ is our own method, with its four factors published and a section on what the score is not.

How the two projects relate →  ·  How the score is calculated →

Check the record yourself

The provenance behind the scoreboard is published as a machine-readable file, so anyone can inspect it without asking us. The API and the MCP server are documented.

verification.json →  ·  API docs →  ·  MCP server →

Report an error

If a date here disagrees with the vendor, tell us. The correction form asks for the product, the version, what we show, what the vendor says and the vendor's page.

Report a correction →  ·  partners@endoflife.ai

Privacy and terms

What we collect, the third parties we use, how long we keep data and your rights are set out in the privacy policy.

Privacy →  ·  Terms →

Who we are

EndofLife AI Inc., Taber, Alberta, Canada. One email reaches the team.

About →  ·  Press kit →  ·  Contact →