Supported products

87 products, each a compiled-in probe (see Concepts). Use the value in Product as product: in a target. Resolver is the lifecycle-data identifier — endoflife:<slug> for endoflife.date (real EOL/support dates), github:<owner/repo> for GitHub Releases (latest version only, no eol/support/lts — GitHub has no opinion on lifecycle policy) — and a — means enodia has version detection for that product but no lifecycle match yet (its patch/branch axes still work; its lifecycle axis stays unknown). Click a product for its exact endpoint, auth requirements, and recorded fields.

This table is generated from enodia products against the currently built binary — re-run it to check for drift before treating this page as gospel if it’s been a while.

Applications and infrastructure services

57 products, probed over HTTP(S) or a raw wire protocol (MySQL, Redis, MongoDB, …) — no SSH involved.

Product	Summary	Resolver
`apache`	Apache HTTP Server	`endoflife:apache-http-server`
`artifactory`	JFrog Artifactory	`endoflife:artifactory`
`bamboo`	Atlassian Bamboo (Data Center)	`endoflife:bamboo`
`bitbucket`	Atlassian Bitbucket (Data Center)	`endoflife:bitbucket`
`bitwarden`	Bitwarden (self-hosted)	`github:bitwarden/server`
`clickhouse`	ClickHouse	`endoflife:clickhouse`
`confluence`	Atlassian Confluence (Data Center)	`endoflife:confluence`
`elasticsearch`	Elasticsearch	`endoflife:elasticsearch`
`esxi`	VMware ESXi	`endoflife:esxi`
`forgejo`	Forgejo	`endoflife:forgejo`
`generic`	Hand-written parser for systems enodia doesn’t know — see Configuration	—
`gitlab`	GitLab	`endoflife:gitlab`
`grafana`	Grafana	`endoflife:grafana`
`graylog`	Graylog	`endoflife:graylog`
`haproxy`	HAProxy	`endoflife:haproxy`
`harbor`	Harbor (container registry)	`endoflife:harbor`
`jaeger`	Jaeger	`endoflife:jaeger`
`jellyfin`	Jellyfin	`github:jellyfin/jellyfin`
`jenkins`	Jenkins	`endoflife:jenkins`
`jira`	Atlassian Jira (Data Center)	`endoflife:jira-software`
`keycloak`	Keycloak	`endoflife:keycloak`
`kibana`	Kibana	`endoflife:kibana`
`kitsu`	Kitsu (CG-Wire / Zou frontend)	`github:cgwire/kitsu`
`logstash`	Logstash	`endoflife:logstash`
`mattermost`	Mattermost	`endoflife:mattermost`
`mongodb`	MongoDB	`endoflife:mongodb`
`mysql`	MySQL Server	`endoflife:mysql`
`nextcloud`	Nextcloud	`endoflife:nextcloud`
`nexus`	Sonatype Nexus Repository	`endoflife:nexus`
`nginx`	nginx	`endoflife:nginx`
`oauth2-proxy`	oauth2-proxy	`github:oauth2-proxy/oauth2-proxy`
`opensearch`	OpenSearch	`endoflife:opensearch`
`owncast`	Owncast	`github:owncast/owncast`
`perforce-swarm`	Perforce Helix Swarm	—
`pgadmin`	pgAdmin	—
`phpmyadmin`	phpMyAdmin	`endoflife:phpmyadmin`
`portainer`	Portainer	`github:portainer/portainer`
`postgres_exporter`	prometheus-community/postgres_exporter	`github:prometheus-community/postgres_exporter`
`postgresql`	PostgreSQL	`endoflife:postgresql`
`proftpd`	ProFTPD	`endoflife:proftpd`
`proxmox`	Proxmox VE	`endoflife:proxmox-ve`
`redis`	Redis	`endoflife:redis`
`routeros`	MikroTik RouterOS	`endoflife:routeros`
`sonarqube`	SonarQube	`endoflife:sonarqube-community`
`ssh`	SSH banner (any implementation)	—
`synology-dsm`	Synology DSM	—
`teamcity`	JetBrains TeamCity	—
`testrail`	TestRail	—
`traefik`	Traefik	`endoflife:traefik`
`truenas`	TrueNAS	`endoflife:truenas`
`vault`	HashiCorp Vault	`endoflife:hashicorp-vault`
`vaultwarden`	Vaultwarden	`github:dani-garcia/vaultwarden`
`vcenter`	VMware vCenter Server	`endoflife:vcenter`
`wordpress`	WordPress	`endoflife:wordpress`
`youtrack`	YouTrack	`endoflife:youtrack`
`zabbix`	Zabbix	`endoflife:zabbix`
`zou`	Zou (CG-Wire API backend)	—

Operating systems

30 products, all identified over SSH rather than HTTP — see SSH-based OS identification for the shared mechanism every one of these uses.

Product	Summary	Resolver
`almalinux`	AlmaLinux	`endoflife:almalinux`
`alpine-linux`	Alpine Linux	`endoflife:alpine-linux`
`amazon-linux`	Amazon Linux	`endoflife:amazon-linux`
`astra-linux`	Astra Linux	—
`centos`	CentOS Linux (legacy, EOL)	`endoflife:centos`
`centos-stream`	CentOS Stream	`endoflife:centos-stream`
`debian`	Debian	`endoflife:debian`
`eurolinux`	EuroLinux	`endoflife:eurolinux`
`fedora`	Fedora Linux	`endoflife:fedora`
`freebsd`	FreeBSD	`endoflife:freebsd`
`gentoo`	Gentoo Linux	—
`kali-linux`	Kali Linux	—
`linuxmint`	Linux Mint	`endoflife:linuxmint`
`macos`	macOS	`endoflife:macos`
`netbsd`	NetBSD	`endoflife:netbsd`
`nixos`	NixOS	`endoflife:nixos`
`openbsd`	OpenBSD	`endoflife:openbsd`
`openeuler`	openEuler	—
`opensuse`	openSUSE	`endoflife:opensuse`
`opnsense`	OPNsense	`endoflife:opnsense`
`oracle-linux`	Oracle Linux	`endoflife:oracle-linux`
`oracle-solaris`	Oracle Solaris	`endoflife:oracle-solaris`
`photon`	VMware Photon OS	`endoflife:photon`
`postmarketos`	postmarketOS	`endoflife:postmarketos`
`redos`	RED OS	—
`rhel`	Red Hat Enterprise Linux	`endoflife:rhel`
`rocky-linux`	Rocky Linux	`endoflife:rocky-linux`
`slackware`	Slackware	`endoflife:slackware`
`steamos`	SteamOS	`endoflife:steamos`
`ubuntu`	Ubuntu	`endoflife:ubuntu`

Atlassian products

Jira, Confluence, Bitbucket, and Bamboo share one manifest endpoint convention. product: is declared explicitly in your config rather than guessed from the response — pointing a Confluence URL at a Jira entry is a real typo that deserves to be caught, not silently recorded as a wrong fact. Bitbucket’s own manifest still reports itself as stash (its former name) — that’s the vendor’s response, not an enodia quirk.

`zou` and `kitsu` — one probe, two products

Both point at the same Zou API backend and answer the same request — they’re registered separately because they need different lifecycle resolvers (Zou’s own GitHub repo publishes no usable Releases). See Zou and Kitsu for the full explanation.

Don’t see your product?

Use product: generic as an escape hatch for anything without a dedicated probe, or open an issue on GitHub — the .github/ISSUE_TEMPLATE/new_product.yml template asks for exactly what a new probe needs.