EOSL.ai tracks hardware end-of-service-life — the physical switches, routers, firewalls and servers in your stack. But that gear runs software that ages on its own clock. When an operating system, runtime or database reaches end of life, the security patches stop — and scanners often miss it.
When a vendor ends support for a physical product: no more firmware fixes, no support, no hardware replacement. Tracked here, source-linked, down to the part number — Cisco and HPE today.
When a vendor stops patching a software release. For software lifecycle dates we point to endoflife.ai — EOL dates for 450+ products, built on the open endoflife.date dataset.
No. EOSL.ai tracks hardware end-of-service-life — physical enterprise gear like switches, routers, firewalls and servers, down to the part number. Software lifecycle (operating systems, runtimes, databases, frameworks) is a separate discipline with its own dates.
Hardware end-of-service-life (EOSL) is when a vendor stops supporting a physical product — no more firmware fixes or hardware replacement. Software end-of-life (EOL) is when a vendor stops patching a software release. A running system can be exposed on either clock: unsupported hardware, unsupported software, or both.
endoflife.ai is a strong free resource for software lifecycle data — end-of-life dates for 450+ products such as Windows, Ubuntu, RHEL, Python, Node.js, PHP, PostgreSQL and Kubernetes, built on the open endoflife.date dataset.
After a release reaches end of life it stops receiving security patches. Vulnerabilities found in still-supported versions often affect the EOL version too, but it is left unpatched — a gap vulnerability scanners frequently miss. Compliance frameworks (SOC 2, PCI DSS, ISO 27001, HIPAA) treat unsupported software as a finding.