opik
23,482Debug, evaluate, and monitor LLM applications, RAG systems, and agentic workflows.
Activity band details
Activity band A to F: a bin of a score that adds GitHub stars (log scale), a push to the upstream repository in the 12 months before `as_of`, the number of declared integration surfaces and, where the catalogue records them, citing papers and benchmark evaluations. It measures popularity and activity. It is not a level of evidence: no band means a paper cites the tool or that it was measured. Recency is judged as of 2026-11-22.
Computed band: B
(raw score 6.75).
Shown band: B
.
Facets:
documented_in=0evaluated_on=2integration_surfaces=1paper_citations=0recent_push=2stars=1.75
Source of truth: pipeline/maturity/score.py
Measured on SAICA-Bench in this configuration
Each row is one run of opik, set up by us as its run card says, on one labelled set of faulty and clean samples (how we test). It says what that configuration flagged on that set, not how good opik is in general: another model, another input or the tool's own defaults could score differently. J = TPR - FPR, on the answers that carry a verdict. 0% is chance, 100% flags every bad sample and no clean one. J is the sort key within a mode; each row also has false alarms per 100 clean changes and precision at 1%, 5% and 20% prevalence.
| Set | Configuration and run card | J (95% interval) | TPR | FPR | No verdict | Cost per 1,000 reviews |
|---|---|---|---|---|---|---|
|
False 'done' claims
failure mode: Incomplete execution
Real agent output
|
Opik AgentTaskCompletionJudge, score < 0.5 (deepseek-v4-flash)
Catalog tool · Hybrid · own check · judge model deepseek-v4-flash
Rank 6 of 10 ranked rows; no reviewer reaches J 25% on this set.
How this run differs from the tool's defaults
|
+3.6%
−3.3% to +10.6%
|
11.6% | 8.0% | 3 | ~$2.15 |
An answer with no verdict (failed call, blocked request, text cut by the token budget, no verdict in the text) is unreadable: it is left out of the rates and counted beside them, per label. “~” marks an estimated cost. SAICA-Bench results v2.0.0, built 2026-11-22.
Description
Opik is Comet ML's open-source platform for debugging, evaluating, and monitoring LLM applications, RAG pipelines, and multi-agent workflows. Provides trace capture, LLM-as-judge graders, test dataset management, and production monitoring dashboards. Self-hostable alongside a SaaS offering.
Why it's included
Occupies detection × post_generation × full_hitl. Comet-ecosystem-integrated (shared ML experiment-tracking backbone); differentiated from arize-phoenix by its agent-focused trace model.
Addresses failure modes
These tags are the catalog's claim about what opik is built to catch or prevent. A tag is not a test result. The rows under Measured on SAICA-Bench are the evidence, for the sets and the configuration we ran. Not measured here: Context pollution.
- Incomplete execution — Agent claims completion while subtasks are skipped, stubbed, or silently dropped.
- Context pollution — Trajectory drift, hallucination spirals, overlong or off-task context.
Records evidence of
opik can record evidence of these failures (traces, or checks you configure yourself), but it does not detect or prevent them on its own. They are not counted as failure modes it addresses.