What EOSL.ai is

Multiple vendors are live. Additional vendors are added only after their lifecycle data can be collected, normalized, source-linked, and verified to the same standard — never before. The restraint is the point: a lifecycle database is only useful if you can trust every date in it.

IT and infrastructure teams, asset managers, and anyone planning hardware refreshes, budgeting for support renewals, or weighing third-party maintenance against replacement. Public lookup is free and needs no login.

Every end-of-sale and end-of-service-life date on EOSL.ai is taken from the hardware vendor’s own published end-of-life documentation and links back to that source, so you can verify it yourself. Where a vendor does not publish an explicit end-of-service-life date, we compute it from that vendor’s published support-life policy and label it “computed,” with the policy linked — we never present a computed date as a vendor-published one. We do not invent, estimate, or copy dates from third-party databases.

Bulletins read in full, quoted. Where a vendor publishes its dates in a document our column-aware parsers cannot read, the bulletin is read in full and each date is published together with the vendor’s own sentence that states it. Those quotes are re-proven mechanically every time the site is built: a quote that is no longer a verbatim passage of the kept bulletin, or that does not contain the published date, stops the build. On the product page they appear as “the vendor’s words” beside the date they back.

Disclaimer. EOSL.ai is provided for general informational purposes only. Vendor lifecycle dates change, and source documents are occasionally revised or withdrawn, so we make no warranty that every date is complete, current, or error-free. Before any purchase, support-renewal, or migration decision, confirm the dates against the linked vendor bulletin or with the vendor directly.

For an asset review or audit, the source link on every date is the evidence: CIS Control 1, NIST SP 800-53 SA-22, ISO/IEC 27001 and SOC 2 all ask for an inventory that identifies unsupported components, and a vendor bulletin is the citation that shows a component is unsupported. The same applies to an answer from an AI assistant: an end-of-life date with no source is a guess, so check that any date you are given links to the vendor's own bulletin. Every EOSL.ai answer does, including the ones served through the MCP server.