Is TruLens Open Source and What Does It Integrate With?

TruLens is an open-source, OpenTelemetry-native library for evaluating and tracing AI agents. It instruments your agent so that every step is recorded as a trace span, scores those steps with benchmarked LLM judges, and helps you decide which version to ship. You can use it if you work with LLM agents or RAG pipelines and want per-step visibility into failures, latency, token use, and cost. The project is distributed via GitHub, and the site's "Get started" and "Star on GitHub" links point there. The page does not list pricing, so treat it as an open-source project rather than assuming a paid tier or a free hosted service.

What TruLens actually does

TruLens addresses a specific problem: agents fail differently than normal software, so you need traces and evals to find out why. It provides two connected capabilities.

Tracing: every span understood

TruLens records latency, inputs, outputs, tokens, and cost per step. A bad answer therefore has a traceable cause rather than an unexplained output. The site shows a trace view with tree, timeline, details, and raw attributes for a support agent run, which is the practical shape of the output you get: a per-step record you can inspect.

Evaluation: scores on every step

Each step receives a score, and the judges explain the score so a low result points to what went wrong. TruLens ships benchmarked judges and lets you tune them to your domain with private data by adding a rubric, examples, and an adjusted score range.

Integration model: OpenTelemetry-native

The key integration fact is that TruLens instruments agents with OpenTelemetry. That means tracing follows an open standard rather than a proprietary format, which matters if your stack already collects telemetry. The page describes TruLens as "Open source, OpenTelemetry-native" and frames it for AI agents and RAG pipelines generally; it does not enumerate specific framework connectors, so check the GitHub repository for the current list of supported integrations before committing.

How reliable are the judges?

The site makes several benchmark claims, all attributed to external evaluations:

These are vendor-published claims with cited sources, so they are checkable rather than asserted without support. They are still benchmark results on specific datasets; your domain may behave differently, which is exactly why the customization path exists.

Customizing judges for your domain

The documented approach is to start from the built-in judges and align them to your data. The page shows a code snippet beginning with from trulens.core import Metric, Selector and defining a metric such as f_relevance = Metric(...), indicating that custom metrics are defined in code with a selector choosing what to score. The page excerpt cuts off before the full implementation, so consult the documentation for the complete signature and provider setup.

When TruLens is a good fit

• You need to debug agent failures, not just log outputs. Per-step traces with inputs, outputs, tokens, and cost give you a cause, not just a symptom.
• You want evaluation tied to traces. Scores attached to each span let a low score point to a specific step.
• You prefer open standards. OpenTelemetry-native instrumentation avoids locking tracing into a proprietary format.
• You need domain-specific judges. Rubrics, examples, and score-range adjustments are supported.

If you only need aggregate quality scores without step-level tracing, or if you require a managed hosted service with published pricing, the page does not confirm that TruLens provides it—verify on GitHub and in the docs first.