Traceloop observes.
Runback re-executes.
Traceloop maintains OpenLLMetry, the open-source OpenTelemetry standard for LLM instrumentation, plus a hosted monitoring platform on top of it. It's built to get traces out of your stack via standard OTel spans — not to re-execute a step, enforce policy live, or produce a signed audit record.
| Capability | Traceloop | Runback | Note |
|---|---|---|---|
| Broad auto-instrumentation via OpenTelemetry | ✓ | partial | Runback ingests standard GenAI OTel spans too |
| Read and search traces | ✓ | ✓ | |
| Open-source instrumentation layer | ✓ | partial | Runback's OTel ingestion is open; the replay/audit core is not |
| Re-execute any step from captured inputs | ✗ | ✓ | |
| Live policy enforcement — block before it runs | ✗ | ✓ | |
| CI release gate | ✗ | ✓ | |
| Signed, tamper-evident audit export | ✗ | ✓ | |
| Regulatory mappings (EU AI Act · CPS 230 · NIST) | ✗ | ✓ |
Most teams use both — Traceloop for day-to-day trace browsing, Runback for incident replay, CI gating, and the compliance artifact. The two don't overlap until the moment an agent misbehaves in production and someone asks you to prove it.
Try the replay on a real incident.
No signup. Walk a failing production run step by step and see what the model saw.