What you can do with EOSL.ai
EOSL.ai is a source-backed hardware end-of-life database — 2,443 products, 10,823 part numbers, 17 manufacturers, every date linked to the bulletin it came from. Around that sits a set of free tools for looking hardware up, planning a refresh, getting told when something changes, and building on the data. All 27 of them are listed below. Nothing here needs an account, and the tools that take an inventory never send it anywhere.
Look something up
You have a part number, or a pile of them, and need the answer now.
Every tracked product in one filterable, sortable table — by vendor, category, status or how soon support ends. Export what you filter.
Bulk checker →Paste or upload a list of part numbers and get every status in one report, with a refresh-horizon chart you can download as an image.
Compare models →Line up to six models side by side — end-of-sale, EOSL, remaining runway and source — in one shareable link.
Plan and budget
You know what you have. Now you need a decision, a number, or something to send upward.
Paste an inventory, get a dated plan grouped by budget year, with the manufacturer’s own named replacement for each item. Share it, print it, export it.
Stack Monitor →Keep your inventory in one place and attach the evidence an audit asks for — owner, criticality, exceptions, replacement target, review dates. Stays in your browser.
Support outlook →For hardware with no end-of-life announced: what each vendor’s published track record says about how much warning you actually get.
Replacements →The successor each manufacturer named in its own end-of-life bulletin, with per-part mappings where published.
Ending soon →Everything losing vendor support in the next 18 months.
EOL by year →Browse what ends in any given year — the shape of your next few budget cycles.
Unsupported hardware →Everything already past its last date of support.
What to do after end of support →Third-party maintenance, OEM extensions, spares, migration — the trade-offs, without a sales pitch.
Get told when something changes
So you find out before an auditor or an outage does.
Subscribe in Outlook, Google or Apple Calendar — whole database, one vendor, or a single model. Dates land in the calendar you already read.
Lifecycle change ledger →What moved in the data and when, with an RSS feed. Vendors revise dates; this is the record.
Status badges →A live badge for a wiki, README or runbook that updates itself when the vendor date changes.
Build on the data
Machine surfaces, all free, no key, no login.
CORS-open endpoints for the family index and full per-family detail; a one-line-per-part endpoint built for =IMPORTDATA in Google Sheets and =WEBSERVICE in Excel; and published NetBox, Ansible and Snipe-IT integrations that read the inventory you already have. Every record carries its source URL.
MCP server →A live Model Context Protocol endpoint. Connect Claude, Cursor or any agent and it can check hardware lifecycle status directly — with the vendor bulletin attached to every answer.
Open dataset →The whole database as CSV and JSON under CC BY 4.0. Reproduce any figure on this site independently.
Understand the data
What the terms mean, where the numbers come from, and where the limits are.
One adapter per vendor, read from the manufacturer’s own bulletins, re-checked weekly, with the safeguards that stop bad data publishing.
EOL vs EOSL vs end of sale →The milestones people mix up, and which one actually ends your support.
Glossary →Every lifecycle term this site uses, defined.
Support Runway Score →A transparent 0–100 lifecycle-timing indicator, with its inputs shown. Not a risk or compliance rating.
Research: the 60-month rule →Two decades of support tails. Original analysis, recomputed on every refresh.
Support tail by vendor →How long each manufacturer keeps supporting hardware after it stops selling it. Measurements, not grades.
EOL data report →The state of enterprise hardware end-of-life, from this database.
Audit and compliance →How this maps to CIS Control 1, NIST SA-22, ISO 27001 and SOC 2 evidence.
CISA BOD 26-02 →What the directive requires on end-of-support edge devices, and how to find yours.
Can you trust an AI with EOL dates? →Why these answers need a source link, written for people asking a chatbot instead.
Questions
Is any of this paid, or behind a login?
No. Every tool, page, feed and endpoint listed here is free and open, with no account and no key. EOSL.ai sells no hardware and no maintenance. The tools that take an inventory — the refresh plan, the bulk checker and Stack Monitor — run entirely in your browser and never upload what you paste.
Which tool should I use for what?
They differ by how long the answer needs to live. The bulk checker is for triage — paste a list, read the report, close the tab. The refresh plan produces a document you send to somebody, grouped by budget year and shareable as a link. Stack Monitor is a record you come back to: it saves your inventory in your browser, re-checks it every time you open it, and holds the audit evidence.
Can I use EOSL.ai data in my own tools?
Yes. There is a CORS-open JSON API, a live MCP server for AI agents, the whole database as CSV and JSON under CC BY 4.0, a one-line-per-part endpoint for spreadsheet formulas, and published integrations for NetBox, Ansible and Snipe-IT. Attribute EOSL.ai and link back so your users can reach the vendor bulletin behind each date.
Where do the dates come from?
Each one is read from the manufacturer's own end-of-life bulletin, and the link to that bulletin is on the page. Where a vendor publishes no per-model date but does publish a support-life policy, the date is computed from that policy and labelled as computed. Nothing is estimated, and EOSL.ai does not predict future end-of-life dates.