Which graders belong on every PR and which belong on a nightly run?

Cheap, deterministic graders belong on every PR; anything that calls a language model belongs on a scheduled run instead. A PR gate fires on every commit from every contributor, so whatever runs there multiplies by your team’s commit volume, and a rule-based check or a distilled classifier costs close to nothing at that frequency.

An LLM judge doesn’t. It’s a paid inference call, and running one on every PR means paying for it at commit frequency instead of once a day. Moving the judge to a nightly run collapses that multiplier: it grades a fixed batch once instead of once per commit. The tradeoff is latency, not accuracy, since a nightly run catches what a PR gate would have caught, just hours later. Reserve the PR tier for checks cheap enough to run at commit frequency, and let volume decide the rest.

keep reading

More on this.

Two ways to run Tessary.

Tessary is an open-source agent reliability platform. Cloud and self-hosted run the same workflow on the OpenTelemetry traces your agent already emits.

Tessary Cloud

We host it for you. Send your first trace with nothing to deploy and no model key.

what's includedper organization
traces
10,000 per calendar month
stored trace data
1 GB
retention
30 days
model credit
$10, one-time, for triage and root-cause analysis
credit card
not required

Self-hosted Tessary

Run the open-source code on your own infrastructure with one command. Add your own model key for triage and root-cause analysis.

Self-host Tessary for me by following https://github.com/tessaryai/tessary/blob/main/setup.md

docker compose -f oci://docker.io/tessaryai/tessary:compose up -d -y