eosl.ai
About

What EOSL.ai is

EOSL.ai is a source-backed database of hardware end-of-sale and end-of-service-life (EOSL) dates. It answers one question fast and without spin: is this piece of enterprise gear still supported by the vendor — and if not, what are your options?

How the data works

Every date is sourced

End-of-sale and EOSL dates come from the vendor's own end-of-life bulletins. Each record links back to the exact bulletin so you can verify it yourself.

Down to the part number

Coverage is at the SKU / part-number level, not just the product line — lifecycle dates often differ within a single family.

Verified and refreshed

Records carry a last-verified date and are re-checked against the source on a recurring schedule.

Conflicts are surfaced

When two bulletins disagree on a date, both are shown rather than silently picking one.

Vendor coverage standard

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.

Who it's for

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.

Sourcing & accuracy

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.

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.
Using EOSL.ai for an asset review or audit? See Standards Alignment — how the source-linked lifecycle data maps to CIS Control 1, NIST SP 800-53 SA-22, ISO/IEC 27001 and SOC 2 asset-inventory controls.