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 — evaluation-based guardrails and CI checks now exist, but neither re-executes a captured step or produces 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 | ✗ | ✓ | The OTel GenAI spec standardises what gets emitted, not what happens to it once stored — nothing on the receiving end re-runs a step from it |
| Live policy enforcement — block before it runs | partial | ✓ | Guardrails evaluators can block LLM output in real time — narrower than a tool-call-level policy engine, and evaluation-based rather than a simulated-against-history gate |
| CI release gate | partial | ✓ | A GitHub App runs evals on every PR and posts results — an evaluation-based check, not Runback's simulate-against-production-history gate |
| Signed, tamper-evident audit export | ✗ | ✓ | Spans reach the backend over an open wire format, but nothing seals them afterward — the standard defines transport, not chain-of-custody once stored |
| Regulatory mappings (EU AI Act · CPS 230 · NIST) | ✗ | ✓ |
It's built to get traces out of your stack via standard OTel spans — evaluation-based guardrails and CI checks now exist, but neither re-executes a captured step or produces a signed audit record. Most teams use both — Traceloop for what it's already good at, Runback for the incident replay, CI gate, and signed record it doesn't do.
Compiled from Traceloop's public documentation at https://www.traceloop.com/docs, read on 15 September 2026. Products change; if a row is out of date or wrong, tell us at legal@runback.dev and we will correct it. All product names and trade marks are the property of their respective owners. Runback is not affiliated with, endorsed by, or sponsored by any of them.
No signup. Walk a failing production run step by step and see what the model saw.