About

Why it exists

The warehouse code and the reports that read it are one pipeline, and the tools treat them as two. A Dataform change is only correct when the Looker side still works, and nothing you can install today looks at both — so the failure surfaces later, in a dashboard, in front of someone who didn't make the change.

Graver is the tool that looks at both. It came out of doing this work rather than out of a product plan, which is why the parts that exist are the parts that were annoying enough to build.

Where it came from

Graver is forked from Incise, a native Mac text editor by the same author, and inherits its editor, terminal and agent integration. Incise remains a separate product with its own releases; Graver isn't a rebrand of it, and changes don't flow back.

That lineage is the reason a workbench this specific could exist at all — the editor underneath it was already written and already shipping.

Also built here

• Incise — a native Mac text editor. Fast, precise, and the foundation Graver is built on.
• SQLAnvil — an open-source SQL workflow engine with first-class Postgres, Supabase and MySQL adapters. Graver targets vanilla Dataform and does not require it; they're separate projects that happen to share an author.
• ListAnvil — a reseller data foundry: cross-marketplace listing and relay automation.
• Checklists.io — runbooks that AI agents execute and humans approve, with evidence attached to every step.

Getting in touch

Graver is young and private. If something is broken or missing, the log at Help ▸ Show Log in Finder usually says why, and that's the most useful thing to have to hand when reporting it.