LLM-as-judge is a prompt that grades an agent's output by reasoning over it against one or more specific intents, the things the agent was supposed to do. The judge reads the output, works through whether each intent was met, and returns a verdict. It exists because many of the qualities that matter, like tone, helpfulness, or whether an answer actually addresses the question, need judgment to assess, and human judgment is too slow and expensive to apply to every output.
A judge's verdicts come from the model its prompt runs on, so they carry that model's properties. They're stochastic: run the judge twice on the same input and it can disagree with itself. And they depend on the model version: change the model and the verdicts change meaning, even with the prompt held fixed.
LLM-as-judge fits checks that need judgment: whether an answer is grounded in the retrieved context, whether the agent followed a policy, whether the tone fits. Because it costs the most per verdict of any grader, it usually runs on a subset rather than every output: against a fixed dataset in evals before a change ships, and in production on traces that were sampled or flagged by cheaper checks.
17 questions
Answered, plainly.
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.
- 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