eosl.ai
FAQ

Frequently asked questions

How EOSL.ai works, where the data comes from, and what it can do for you.

Questions & answers

What does EOSL (end of service life) mean?

End of Service Life — also called Last Date of Support — is the date after which the vendor no longer provides support, software fixes, or hardware replacement for a product. After EOSL the hardware still runs, but it is unsupported by the manufacturer.

What is the difference between end-of-sale and end-of-service-life?

End-of-sale is the last date you can buy the product new from the vendor. End-of-service-life (EOSL) is the later date when vendor support ends entirely. The gap between them is usually several years.

Where do your dates come from, and how are they verified?

Every end-of-sale date is taken from the vendor's own published end-of-life bulletin, and each record links back to that bulletin so you can confirm it at the source. Where a vendor does not publish a per-model end-of-service-life date, EOSL is computed from the vendor's published support-life policy, which is also linked. Records show when they were last verified.

Is EOSL.ai free?

Yes — public lookup, the bulk checker and Stack Monitor are all free and need no login. Stack Monitor keeps a saved local inventory with evidence fields and CSV/JSON/PDF export in your browser.

Which vendors are covered?

Coverage spans major enterprise networking, server, and storage hardware vendors — see the homepage for the current vendor list. We add a vendor only once its lifecycle data can be collected, normalized, source-linked, and verified to the same standard.

Can I check a whole list of part numbers at once?

Yes. The bulk checker lets you paste or upload a list of part numbers and returns each one's support status, end-of-sale and EOSL dates, and source bulletin — in one report. Matching runs in your browser; matched parts are counted as anonymous sightings so coverage follows demand, and unmatched text stays on your machine.

What does Action Priority mean?

Action Priority is a plain-language label for how urgently a part needs attention: Immediate (past EOSL), Soon (support ends within 12 months), Plan (within 36 months), or Monitor (supported, with a known timeline).

My hardware is past EOSL — what are my options?

Common paths are third-party maintenance (independent support past the vendor cutoff), pre-stocking spares, scheduling a migration, or running to failure on low-criticality gear. The right choice depends on how critical the hardware is.

Does EOSL.ai store the part numbers I check?

Matched part numbers only, as anonymous sightings — the tracked identifier with no IP, no identity, and no record of which parts were checked together, so your list cannot be reconstructed. Text that matches nothing never leaves your browser; each tool offers an email link if you want an untracked part added. That demand signal is how missing hardware gets prioritised and is used internally only.