Pipeline

How CompatHub works

Collect → normalise → derive. The same architecture for every ecosystem: official source, raw document, parser, normalised facts, lifecycle periods, provenance, and derived status.

Collect

Collectors ingest release schedules, branch maintenance pages, and vendor APIs — Python, Node.js, PHP, PostgreSQL, MySQL, Ubuntu, Debian, .NET, Kubernetes, OpenJDK, Rust, Ruby, and more — and store them as raw documents with fetch metadata.

Normalise

Each source is mapped into products, version lines, releases, lifecycle periods, and support providers. Every fact keeps provenance and an authority tier so a date can be traced back to vendor documentation or a first-party feed.

Derive

CompatHub computes whether a line is in standard support, security maintenance, or end-of-life — with risk and next transition dates derived from periods, never hand-typed spreadsheets.

What you can look up

Product hubs summarise supported and EOL version lines. Version-line pages answer questions such as “is this still supported?”, “when is EOL?”, and “what is the latest release?” — with links to related lines and official sources.

Questions about the pipeline or a missing source: dev@compathub.com.