> ## 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.

# Introduction

> What Relnx does and who it's for.

**Relnx is a release-tracking platform for cloud-native and DevOps tools.** It
watches the tools your stack depends on — Kubernetes, ArgoCD, Helm charts,
Prometheus, Istio, and 100+ others — and turns every new release into a clear,
human-readable summary of *what actually changed*.

## The problem

A typical platform team runs dozens of cloud-native tools. Each one ships
releases on its own cadence with release notes that are often:

* A wall of auto-generated commit messages.
* Lacking a clear breaking-changes section.
* Buried in a GitHub release page nobody is watching.

When a security patch lands or a breaking change ships, you find out *after*
something breaks.

## What Relnx does

For each release Relnx tracks, it:

1. **Pulls the raw release notes** from GitHub, Helm charts, or the tool's
   official site.
2. **Parses them into structured features** (Bug Fix, Security Fix, Breaking
   Change, Enhancement, Deprecation, etc.).
3. **Uses AI to generate plain-language explanations** — what the change does,
   why it matters, how to act on it.
4. **Notifies you** via email and (for Enterprise) Slack when a tool you follow
   ships a new release.
5. **Opens an upgrade pull request for you** — for tools in a connected GitHub
   or GitLab repository, Relnx can raise a PR that bumps the version (in your
   `Chart.yaml`, `terragrunt.hcl`, or `versions.json`). The PR description
   includes a **Breaking Changes** section summarising what changed between your
   current and target versions, with links back to the full details — so the
   review context lives right where you approve the upgrade.

It also plugs into where your team already works (Enterprise):

* **Catches drift in CI** — the [`relnx/check-outdated` GitHub Action](./how-to/check-tools-in-ci)
  fails a build when a tool is behind or has unacknowledged security / breaking
  changes, so missed upgrades surface like a failing test.
* **Turns a release into a ticket** — [open a Jira or Linear ticket](./how-to/create-tickets)
  from any release in one click, pre-filled with what changed.

So a new release doesn't just sit in your inbox — it lands in your CI, your pull
requests, and your team's board.

Free tools — the [Kubernetes EOL tracker](./how-to/track-k8s-eol) and the
[version comparison page](./how-to/compare-versions) — don't even require
sign-in.

## Who Relnx is for

* **Platform engineering leads** — keep the whole org informed without writing
  an internal newsletter.
* **SREs and DevOps engineers** — never miss a security patch or breaking
  change.
* **Engineering managers** — track upgrade work with release acknowledgments
  and the stack health score (Enterprise).

If your team runs Kubernetes and a stack of CNCF tooling, Relnx is built for
you.

## Next steps

* **Try it without an account**: visit [www.relnx.io/eol](https://www.relnx.io/eol) or
  [www.relnx.io/compare](https://www.relnx.io/compare).
* **Sign up and follow your first tool**: [Getting started](./getting-started).
* **See what each plan includes**: [Plans and limits](./reference/plans).