Do I need my own LLM provider key for Tessary to grade traces?

On a self-hosted install, yes. Your org adds at least one model provider’s own key, and that’s what funds the judgment step.

The five classifiers on by default don’t call a model, so your provider choice doesn’t affect them. Two you switch on yourself work differently. Frustration runs on an OpenRouter or TypeSafe key: every message it scores is a call on that key, and if the key is refused or removed it pauses and says so until one works. Groundedness needs no provider key. It scores answers with a public model you run on a Mac with Apple silicon or a GPU instance on AWS, and while that model is down it pauses, then scores what it missed once the model answers again.

Your model-provider spend is the real cost line here. The LLM judgment that reads what the classifiers flag resolves to whichever provider your org holds a credential for, in a fixed priority order, and on a self-hosted install with none configured that step fails closed.

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