yamllint checks syntax. We check your schema. That's the difference.

yamllint tells you if your YAML is valid. But "valid YAML" doesn't mean "valid k8s manifest." A missing field, a wrong type, an indentation that silently changes the structure: yamllint passes, Helm crashes, your pipeline fails, you spend 2 hours debugging whitespace. The yamllint maintainer was clear that schema validation is "out of scope." We built the tool that fills that gap.

Every tool today catches syntax but misses semantics

✕yamllint validates YAML syntax, but a file that parses fine can still be a broken k8s manifest, a malformed Ansible playbook, or a silent no-op.

✕Schema validation was explicitly rejected by the yamllint maintainer (github.com/adrienverge/yamllint/issues/37). Nobody mainstream picked it up.

✕You only discover the error in CI, 15 minutes into a pipeline run, or worse, in production (documented 6-hour and 9-hour outages from a single wrong space).

✕No tool handles multi-document --- k8s streams with per-document schema errors. You slice them up manually.

Get on the waitlist

Private beta for devops teams. We'll email when it's ready, and we'll show you a working demo first.

You're on the list. We'll be in touch before we open the beta.

Web tool works locally (no upload). API for CI/CD pipeline gates. Team workspaces for shared schemas and org-wide validation policies.

What we built instead

→Schema validation (JSON Schema 2020-12 & k8s native CRDs): the exact feature yamllint refused to add

→Multi-document --- streams with per-doc schema errors, not a single "line 42 is invalid"

→Works where you work: browser (local processing, no upload), API for CI/CD pipeline gates

→Semantic diff: see what changed structurally, not just text noise

→Clear error messages: "ingress.yaml: spec.rules[0] is missing required field 'host'" instead of "expected block end"