About Ratatosk

Open source projects in the Kubernetes ecosystem release often. Most releases are safe to skip, but every so often a security fix or a breaking change slips quietly into a minor version. If nobody reads the release notes, the upgrade is where it hurts.

Ratatosk reads those release notes. It collects releases from projects across the CNCF landscape (the current list is at /projects) every hour, analyzes them, and surfaces only what needs action.

How it works

1. Collect: official release notes are fetched hourly. When a note is just a pointer to another document, Ratatosk follows the link and reads that too.
2. Extract: verifiable change facts are extracted from the notes with AI. Every fact carries a verbatim quote and a source URL, so you can always check it against the original.
3. Deliver: people get summaries in three languages (English, Korean, Japanese) via web, email, and RSS. Agents get the same data via the REST API and MCP.

Principles

• Silence when nothing needs action. A release that was read and found routine stays marked as exactly that. Nothing is written to fill space.
• Verifiable against the source. Every analysis links to its origin. When a note is too thin to analyze, Ratatosk says so and shows the original instead.
• Your versions stay yours. Even the agent-side version check (check_stack) is designed so running versions never reach the server. See MCP for details.

About the name

Ratatoskr is the squirrel of Norse myth that runs up and down the world tree carrying messages. The job here is the same, and the news it carries is releases.

Data and use

Analyses are AI-generated and provided without warranty. For decisions that matter, verify with the source link that accompanies every item. See the terms of use.