endoflife.ai tracks when software stops being supported: 700+ products and 14,000+ versions, from operating systems and databases to runtimes and network platforms. Every date names its source, the vendor's own lifecycle page where we read it there, and the day it was last verified.

The integration connects that data to your Halo assets. Once a day it reads each asset's operating system and the software rows on its Software tab, matches them to endoflife.ai products and release lines, and writes twelve fields back onto the asset: the product and release matched, end of active support, end of life, a status, the EOL Risk Score and grade, whether the version is on our Exploited & Unpatchable list (actively exploited per CISA, no fix coming), the vendor source, the day it was verified and the day it was checked.

Assets that are past end of life, or exploited and unpatchable, can open a ticket against their customer and site. Upgrade and remediation work then flows through your normal queue, SLAs and billing, and the next daily run never opens the same ticket twice.

Nothing is guessed. A title we do not track is reported as not tracked, and an operating system recorded too loosely to name a release, such as a bare "Windows 10", is reported as needing a more specific version rather than given a date that might be wrong.

The integration uses the public Halo API with a client-credentials application you register, writes only to fields you create and tickets of a type you choose, and stays well under Halo's rate limit so your other integrations keep their headroom. It runs on your own schedule and infrastructure. Only product names and version strings are sent to endoflife.ai; asset names, customers, sites and users stay in your Halo.