What runs today.
Operating systems, runtimes, databases and agreed Windows/Linux applications. Track the release and the support that actually applies.
Software lifecycle intelligence
Know what’s
running out
of support.
From servers to dependencies, turn your software inventory into clear deadlines, affected systems and the next action to take.
Pilot preview · For IT, platform, security teams and MSPs
Your next actions
Less noise. A clearer plan.
Customer portal runtimeBase image + 12 deployments
Plan upgradeDistribution-maintained packageUpstream ended · distro support continues
MonitorInternal npm dependencyNo published support policy
UnknownOne connected view.WINDOWS + LINUXGOLDEN + CONTAINER IMAGESJAVASCRIPT DEPENDENCIES
01 / The whole picture
Software doesn’t live
in one place.
Neither should your lifecycle planning. Start with the inventories you already have, across three connected areas.
What ships next.
Track components in golden and container images. Link them to deployments when your inventory supplies the relationship.
What sits underneath.
Include JavaScript dependencies from your inventory. Where a package has no documented support policy, its status stays explicitly unknown.
02 / Context changes the answer
An old version.
Not always an
unsupported version.
Distribution backports and extended support can change the answer. We keep those support paths separate, with evidence and scope attached.
See the matching rules ↗Source-backed support status
Record the maintainer, release, source and date checked. A customer-claimed entitlement stays unverified until reviewed.
Priorities with context
Exposure, service importance and customer policy guide the next action. End-of-life alone is not a critical vulnerability.
Exceptions that stay visible
Track the owner, reason and review date. Accepted risk does not change an unsupported product into a supported one.
03 / Start with an export
Your inventory in.
A useful plan out.
For larger estates, use a central inventory export. Our Linux collector gives you a simple starting point on individual machines.
LINUX COLLECTORREAD-ONLY · LOCAL OUTPUT
# Run without sudo
python3 lifecycle_inventory.py \
--asset-id server-01 \
--output inventory
# Produces inventory.json + inventory.csv
# Nothing uploaded automatically
Collector covers dpkg/RPM packages, OS and kernel. It does not scan images or discover all manually installed software.
01
Agree your coverage
Confirm products, support entitlements and the inventory format before onboarding.
02
Review the evidence
Match releases to support information. Resolve ambiguity and identify affected systems.
03
Receive the next actions
Get an initial review, followed by weekly reports and agreed deadline alerts during the pilot.
04 / A focused first step
Start small.
Prove the value.
A proposed four-week pilot with one organisation, up to 500 component records and a clearly agreed product scope.
A reviewed first report.
Support deadlines, affected systems, priorities, sources and unknowns. Confirm the findings with your team.
Weekly updates.
Compare refreshed inventories and lifecycle information. Keep accepted exceptions and stale inventory visible.
Continue if it helps.
Evaluate useful findings and review effort. Agree pricing and ongoing coverage before committing.
Know the deadline. Own the next step.
Bring your inventory.
Leave with a plan.
See the proposed pilot and prepare your enquiry.
A few practical answers
Clear from the start.
Do we need a collector on every machine?
No. A central inventory export can cover your estate. The Linux collector is an additional option for machines where it is useful. The first pilot uses an agreed CSV format.
Does every dependency have an end-of-life date?
No. Without a documented support policy, a package remains “support status unknown”. Age, deprecation and release activity provide context, not an invented expiry date.
Will Lifecycle change our systems?
No. The pilot works from customer-supplied exports. The collector reads local inventory and writes files; it does not install, upgrade or upload anything automatically.
Is the monitoring service already live?
This is the pilot website preview. The collector and sample report are available now. Secure customer onboarding, automated monitoring and a customer portal are being developed; this site does not accept real inventory uploads or payments.