Deltz docs

Garboard is now Deltz. The garboard CLI, GARBOARD_* settings, package names and existing integration URLs remain compatible.

Deltz is a review gate for infrastructure pull requests. It learns your repository’s own conventions by parsing it — facts with file-and-line evidence, never a model’s guess — reviews every infrastructure pull request against them, and never touches your cloud.

Start wherever you actually are.

Evaluating it

• What Deltz is — the shape of the thing, in one page.
• How a review actually works — webhook to comment, every step.
• The six invariants — what it will not do, and the test that enforces each.
• When Deltz says nothing — the most surprising property, and the one most worth understanding.
• What it writes, and what it never writes — the precise version, not the flattering one.

Getting going

• Quickstart: scan a repo offline — no key, no network, about a minute.
• Supported stacks and git hosts — including where support is thin.
• Plans, quotas and limits.

Running it

• Self-hosting — one binary plus Postgres with pgvector.
• Deltz for coding agents — the envelope an agent reads, the pre-push hook, garboard init per harness, and what the Check Run gives it afterwards.
• The MCP server — the four tools, and why the server is read-only by contract.

Reference

Generated from the source tree, so it cannot disagree with the binary.

• CLI — every command and flag.
• Environment variables — every setting a install reads.
• Built-in rules — the rules that ship in the binary.
• Rule catalog — the opt-in curated catalog.

Anything else

The fastest route to a real answer is [email protected] or a walkthrough. See also the changelog, the security overview, and the gauntlet — where we publish our own false positives.