Track hardware and software end-of-sale, end-of-support and end-of-life milestones for every vendor in your estate, matched to the devices actually running each platform or release.
Versus Platform → Inventory → Lifecycle Tracking (/inventory/lifecycle) keeps one table of vendor lifecycle milestones — hardware platforms, software releases and licensable modules — and tells you which of your devices each milestone applies to. It is the place to answer "what in our estate goes out of support next quarter?" without reading twelve vendor bulletins.
Lifecycle dates come from vendor announcements and community feeds. Always verify at the official vendor source (linked on every record) before acting on a date.
Each lifecycle record describes one vendor product:
| Field | Meaning |
|---|---|
| Vendor | F5, Citrix / NetScaler, A10, Radware / Alteon, Kemp, Palo Alto Networks, Fortinet, Check Point, Cisco, Juniper, Arista, VMware / Broadcom, Other |
| Record type | Hardware Platform, Software / Firmware or Software Module / License |
| Product family + model | e.g. BIG-IP iSeries / i5600 / i5800, or IOS XE / 17.16 (for software the model is the release string) |
| Milestones | Announced, Last Order (End of Sale), End of New Development, End of Bug Fix, End of Security Fix, End of SW Maintenance, End of Tech Support, End of Life, End of HW Maintenance, End of RMA, End of Service Contract — all optional |
| Source URL, notes | The official announcement and any internal remarks |
Records can be added, edited and deleted by hand with Add Record; the seeded and feed-synced records are editable too.
Versus derives a status from the dates that are set:
The summary cards at the top count records by status and highlight those whose EoL falls within the next 90 days. Every record also shows its next milestone (the nearest future date) so an "Active" platform that ends sales next month is not mistaken for a safe one.
The matched devices count on each row is the part that turns a vendor bulletin into a work list. Matching depends on the record type:
IOS XE 17.16 record matches a router on 17.16.01a but not one on 17.1.1 or 17.6.4; a BIG-IP 17.1 record matches 17.1.1, not 17.5.1.6. Version strings with a vendor prefix (IOS-XE 17.9) or a build suffix (13.1-49.15, 10.2(5)) are handled.BIG-IP iSeries bulletin lists every F5 device rather than only the iSeries units. Treat that count as "devices to check", not "devices affected".Expand a row and open the matched-devices list to see each device's name, management IP, vendor, type, running version, status and location. The With devices only filter (on by default) hides records that match nothing in your estate; clear it to browse the full catalogue.
The Vendor Data Sources panel lists the official pages the data is curated from and marks which have a live feed:
python manage.py sync_lifecycle_feeds (on demand, or from a scheduled workflow) to upsert the latest release dates; the feed URL is shown and copyable on each card.python manage.py seed_lifecycle_data, each carrying the vendor's official EoL page as its source URL. Update these by editing the record when a vendor publishes a new bulletin.GET /api/device-lifecycle/ — list (filter vendor, record_type; search; ordering), each row with computed_status, days_until_eol, next_milestone, matched_device_count and match_basis (version | vendor | none).POST / PATCH / DELETE /api/device-lifecycle/{id}/ — manage records.GET /api/device-lifecycle/summary/ — the status counts behind the summary cards.GET /api/device-lifecycle/{id}/devices/ — the matched devices for one record.See also: Device Management for the inventory the matching runs against, and Lifecycle Management for the currency and upgrade policy of the Versus platform itself.