Does Tessary read my Langfuse account?

No. Tessary has no connector for Langfuse or any other vendor, and it never reads an account, an API key, or a dashboard on your behalf. Traces reach Tessary the same way they reach Langfuse in the first place: your agent already emits OpenTelemetry spans, and you add Tessary as a second exporter alongside whatever you have today, pointed at Tessary’s own OTLP endpoint. Langfuse keeps receiving everything it receives now; nothing about your existing setup changes or gets replaced. That also means there’s no export job and no scheduled sync pulling your history out of Langfuse’s database, Tessary only sees what your instrumentation sends it going forward. If you’d rather not touch application code, the same fan-out can happen at an OpenTelemetry Collector instead: one incoming stream, two outgoing exporters.

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