Is RCA turned on by default?

No. RCA ships off, and you turn it on for the org. The default classifiers check traces without a model call; RCA opens an isolated agentic session against a case, reading its evidence and your repo when one is connected. On a self-hosted install, its model calls run on your org’s own provider key.

Turning it on makes the investigation available, not automatic on every finding. A person starts it on a case, so a classifier firing alone does not start spending against that key.

keep reading

More on this.

What happens after Tessary confirms a case?The case reaches a person, and root-cause analysis is theirs to start on it: an isolated investigation over that case's evidence, ending in a report.answer →What is a root-cause report?What Tessary's RCA investigation produces: grounded hypotheses for a case's cause, the checks it ruled out, and the files involved.answer →What is Tessary's root cause analysis?RCA is Tessary's third analysis layer: a strong model in a microVM investigates a confirmed case and returns grounded hypotheses for what changed.answer →Everything on tessary RCAThe definition, and every question answered under tessary RCA.concept →

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
start for free

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