EvalGlass

Local-first

It runs on your machine. Your repo stays the source of truth.

EvalGlass is local-first: the vendored runtime runs on your machine and in CI, your repo stays the source of truth, and nothing is sent to a hosted EvalGlass service.

EvalGlass runs entirely on your machine and in your CI. There is no hosted tier, no keys to buy, and nothing phones home. Local-first isn’t a feature — it’s the design.

The three honest “no”s

Why local-first matters

There are no servers to keep running on the project’s behalf. A tool that runs entirely from vendored source in your repo does not switch off when a bill goes unpaid — it keeps working as long as your machine and your CI do.

What runs where — who owns the truth

The runtime outlives the tooling.

Because authority lives in host-owned files and the managed runtime is plain vendored code, the evaluation keeps working after the plugin and any coding-agent context are removed. Local-first means there is no cost centre to monetise and no place to insert a meter — EvalGlass measures what your evidence supports and reports only what it can honestly claim. Host ownership, in detail →

Related

Security
data handling & reporting
Trust model
the six structural promises
No false green
what a pass can’t claim
Get the plugin
two commands in Claude Code