> ## Documentation Index
> Fetch the complete documentation index at: https://docs.relnx.io/llms.txt
> Use this file to discover all available pages before exploring further.

# Supported tools

> Categories of tools Relnx tracks, plus how to add custom tools.

Relnx tracks **100+** cloud-native tools out of the box. This page is a
high-level taxonomy — for the authoritative, always-current list, browse
[www.relnx.io/tools](https://www.relnx.io/tools).

## Categories

* **Container Orchestration** — Kubernetes, Karmada, KubeVirt, OpenYurt
* **GitOps / CD** — ArgoCD, ArgoCD Image Updater, Flux, Argo Workflows
* **Service Mesh / Networking** — Istio, Linkerd, Cilium, Ingress NGINX,
  Traefik, Contour
* **Observability** — Prometheus (server + operator + kube-stack), Grafana,
  OpenTelemetry (collector, contrib, eBPF, SDKs), Jaeger, Tempo, Fluentd,
  Datadog Agent, OpenCost
* **Security** — Falco, Kyverno, OPA, Kubescape, cert-manager, TUF, in-toto
* **Storage** — Rook, Longhorn, Dragonfly, MinIO, Vitess
* **Container Runtime** — CRI-O, containerd, Flatcar Container Linux
* **Packaging** — Helm, Kustomize, Skaffold, Tilt
* **Identity / API** — Keycloak, OpenFGA, Dex
* **CNCF & ecosystem** — CloudEvents, KEDA, KEDA HTTP, Knative, NATS, Tekton,
  CoreDNS, Crossplane, KubeFed, KubeVela, Strimzi, etcd
* **K8s clients & tooling** — k9s, kubectl, kubectx, Lens, Stern, OpenLens

## How tools enter Relnx

* **Built-in** (the list above): added by Relnx, parsers tuned, ready to
  follow.
* **Custom** (Enterprise only): your organisation can register its own
  open-source or internal tools with a GitHub repo or Helm chart URL.
  Releases sync the same way as built-in tools and only your org sees them.
  See [Bring your own tool](../how-to/bring-your-own-tool).

## Don't see what you want?

* Browse [www.relnx.io/tools](https://www.relnx.io/tools) — the list grows.
* Free/Starter/Pro: open a support ticket with the tool name + GitHub repo.
* Enterprise: just add it yourself via the org admin page.

## How releases are sourced

For each tool Relnx tracks the most appropriate source:

* **GitHub Releases** — most CNCF tools.
* **Helm chart repositories** — for tools where the chart cadence differs
  from the binary (e.g. Argo CD's official chart).
* **Tool-specific changelog pages** — for projects that don't ship via
  GitHub Releases (rare).

A dedicated parser per tool turns the raw notes into structured features.
For tools without a dedicated parser, a generic parser handles the standard
formats (commit-style changelog, "What's Changed", Conventional Commits).

## Related

* [Feature types](./feature-types)
* [Compare two versions](../how-to/compare-versions)