What the open edition includes
Every stage of the pipeline runs here. Traces arrive over the OTLP (OpenTelemetry Protocol) endpoint, classifiers evaluate them and create findings, triage validates findings into cases, and an agentic root-cause analysis (RCA) run investigates a case. The bundledsandbox-runner service runs the agentic work, and Compose wires it up for you.
What the open edition does not include is the commercially licensed overlay, and Tessary Cloud, the hosted service. Neither is documented here.
Classifiers available out of the box
These five are present and enabled by default on every new project:
The three drift classifiers compare a call site against its own history, so each one needs a stretch of your traffic before it can report anything. A new project sits at the
fitting milestone until they have it. Classifiers and findings covers what fitting a baseline means and what a finding records.
Each of these is switchable per project under Classifiers.
Classifiers that are not currently available
Four classifiers exist in the product and cannot run in the open edition. They are reported as unavailable rather than off, because no setting turns them on here.TESSARY_OBSERVER_ENCODER_URL and TESSARY_OBSERVER_ENCODER_API_KEY ship blank and stay blank in the open edition, so the two encoder-backed classifiers are unavailable rather than merely unconfigured. Configuration covers both variables.
You will not find these four in the Classifiers list. A withheld built-in is filtered out of the listing and returns a 404 if you address it directly, and the capability API refuses an override for one rather than accepting it and doing nothing. The product does not offer a switch that would produce no findings.
Capabilities that require configuration
These are in this build and waiting on something from you.
Replacing the three placeholder secrets is not on this list, because it is not optional. Secure the instance covers it.
Not in service yet
sop_conformance is defined in the product, and it is switched off for every organization in every edition. What holds it back is supply rather than capability: it scores an authored rulebook against the turns a rule applied to, and no per-project artifact bundle has been deployed for it yet.
Treat it as a classifier that does not run today rather than as something the open edition leaves out.
Current product boundaries
These apply to every edition, not only this one.Tessary explains and hands off
Tessary reports what it found, the evidence behind it, and what it believes caused it. It does not open the fix, change your code, or change your agent’s configuration. A case reaches a person through an alert rule and a notification destination you configure. Cases covers what a case carries and how it reaches you.Automatic triage starts off
Triage escalates a finding to a large language model to decide whether it is a real issue. That work runs on the model provider credential you stored, and Tessary applies no ceiling of its own to how much of it runs. Automatic triage is therefore switched off by default, so that turning it on is a decision an operator makes knowingly rather than a default they inherit. Nothing is lost while it is off. Classifiers keep evaluating every trace, findings keep being filed, and the evidence stays on each one. What waits is the escalation that turns a finding into a case.Baselines are per project
The drift classifiers learn what normal looks like from your own traffic, not from a shipped model. A new project cannot report drift until it has enough of its own history to compare against, and moving to a new project starts that history over.Read next
Classifiers and findings
What a classifier is, what fitting a baseline means, and what a finding records.
Cases
How triage turns a finding into a case, and how a case reaches you.
Set up Tessary
First boot, securing the instance, and connecting a trace source.
Configuration reference
Every environment variable a self-hosted deployment reads.