Overview

Keryx investigates Kubernetes incidents. An alert fires, Keryx gathers evidence over read-only tools, and posts a finding whose every claim is tied to the exact tool call that produced it.

It is deliberately narrow. Keryx does not page anyone, run your on-call schedule, write your postmortem, or route your alerts. Those are solved by products that do them well, and none of them feed the loop Keryx cares about: getting better at the next incident because of this one.

The claim, stated precisely

Keryx's only write surface is Git PRs that a human reviews and merges; the cluster changes only through your existing GitOps pipeline.

The short version — "never touches your cluster" — is what people say, and it overclaims. Two planned features open pull requests: the learning loop drafts runbooks, and remediation proposes fixes. In a Flux shop a merged PR becomes a cluster change. So the sentence above is the one to hold us to.

Mechanically: the Kubernetes access is a read-only ServiceAccount, the GitHub integration is mounted read-only, and an execution-layer denylist test covers every mounted MCP server's write-capable tools — not just kubectl verbs.

What a finding contains

• A root cause, or an explicit "insufficient evidence" panel. Never a headline with nothing behind it.
• A conviction rung, spelled out: speculation, pattern match, supported by context, validated by system state, alternatives ruled out. Computed in code from the structure of the evidence. The model may argue a rung down, never up. There is no percentage, because a number nobody calibrated is theater.
• Numbered claims, each with the verbatim excerpt it rests on and the exact query to replay it yourself.
• What was checked and ruled out, with reasons.
• Honest-uncertainty lines — claims dropped for lacking a citation, and any PR or commit named in the prose that no cited excerpt supports.

Status

Keryx is pre-launch. The release gate scores 6 of 10 and we publish that number with its failures — see Eval methodology. Container images are not public yet, so the quickstart is currently for people with access to the private registry.