Editions

Tessary comes in two editions. Open Source is free: you self-host it, or you use Tessary Cloud, the hosted service. Paid adds custom classifiers, higher limits, longer retention, and support over a dedicated Slack channel, and you self-host it or use managed hosting.

​

Compare the editions

Talk to us about the Paid edition to get its price for your team. The pricing section of the website compares the two editions.

​

How Tessary Cloud and self-hosting differ

The Open Source edition runs two ways. Tessary Cloud is the hosted service: Tessary runs it, and you sign up at app.tessary.ai. The open edition is the code in the tessary repository, released under the Apache License 2.0, and it is the build you get when you self-host. Every stage of the pipeline runs on both. Traces arrive over the OTLP (OpenTelemetry Protocol) endpoint, classifiers evaluate them and create findings, triage validates findings into cases (a high-confidence secret leak and a frustration finding open their case without it), and an agentic RCA (root-cause analysis) run investigates a case. What differs is who runs the stack, what pays for the model work, and what is switched on from the start. Tessary Cloud’s usage limits and model credit are not part of the repository. The pages under Tessary Cloud document how they behave. To raise a limit on Tessary Cloud, see Get higher limits.

​

Classifiers available out of the box

These five are present and enabled by default on every new project, on Tessary Cloud and self-hosted alike: On Tessary Cloud, groundedness is also on from the start. 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. These are the built-in classifiers. Custom classifiers, which you build for failures specific to your own agent, are available only in the Paid edition.

​

Capabilities that require configuration

These wait on something from you. A requirement marked self-hosted applies only to a self-hosted instance. Self-hosted, replacing the three placeholder secrets is not on this list, because it is not optional. Secure the instance covers it.

​

Current product boundaries

These apply to Tessary Cloud and self-hosted alike.

​

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. New cases are listed on Triage. Tessary does not send notifications yet. Cases covers what a case carries.

​

Automatic triage starts off

Triage escalates a finding to a large language model to decide whether it is a real issue. Self-hosted, 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. On Tessary Cloud, automatic triage is not available. Triage runs when a person selects Run triage on a finding. 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