Integrations
Integrations
Rootline works on top of the tracing you already have. Connect Langfuse with an API key pair, send OpenTelemetry traces over OTLP/HTTP, or do both: runs from either source appear in one list.
Which one should I use?
- You already send traces to Langfuse (Cloud, or self-hosted Langfuse v4): connect Langfuse. Nothing changes in your agent.
- Your agent emits OpenTelemetry spans (GenAI or OpenInference conventions, or an instrumentation library that produces them): add Rootline as an OTLP/HTTP exporter destination.
- Both: connect both in the same workspace. Langfuse and OpenTelemetry runs are analysed the same way and shown together.
Other tracing tools are not supported yet.
What is available today
| Integration | Status | Details |
|---|---|---|
| Langfuse Cloud (EU, US, Japan, HIPAA) and self-hosted Langfuse v4 | Available | Read-only: Observations API v2, Viewer keys are enough. Setup |
| OpenTelemetry over OTLP/HTTP (JSON or protobuf) | Available | Traces at /v1/traces, logs at /v1/logs, per-workspace ingest key. Setup |
| OTLP over gRPC | Not supported | Use the HTTP exporter. |
| Other tracing tools | Not supported | No other integration is announced. A tool that can export OTLP/HTTP can use the OpenTelemetry endpoint. |
What each plan includes
| Capability | Free | Team | Agency |
|---|---|---|---|
| Langfuse and OpenTelemetry sources, failure detection, issues, explanations | Yes | Yes | Yes |
| Failed runs explained by AI each month (then rule-based) | 100 | 2,000 | 10,000 |
| Regression tests: view generated cases | Yes | Yes | Yes |
| Regression test export | No | Yes | Yes |
| Cost per customer and feature | No | Yes | Yes |
| Customer view | No | Yes | Yes |
| Email alerts | No | Yes | Yes |
| Price per month | $0 | $49 | $199 |
AI or rule-based? Every failed run gets a rule-based explanation from Rootline's built-in detectors, with no AI involved. AI-written explanations are added on top, up to the monthly allowance above; you can switch them off in Settings and keep rule-based ones only. Full pricing
Data access and trust
- What Rootline can access. Langfuse: one read-only endpoint with the keys you provide; it never creates, changes or deletes anything in Langfuse (details). OpenTelemetry: only the spans and logs your exporter sends with the workspace ingest key (details).
- Keys. The Langfuse secret key is encrypted before storage. Ingest keys are stored only as hashes; regenerating one in Settings revokes the old key at once.
- Retention. Imported trace data, explanations and alert records are deleted automatically after 90 days (privacy policy, section 8).
- AI processing. For an AI explanation, a truncated, redacted excerpt of the failed run (about 2,000 characters of tool inputs and outputs) is sent to an AI provider. Turn it off in Settings to keep everything rule-based (section 5).
- Account deletion. Settings → Danger zone deletes your account and all workspace data immediately (section 8).
- Policies. Privacy policy. Terms of Service.
- Certifications. Rootline holds no security or compliance certifications today.
Start with the traces you have
Free to start, no credit card. Until you connect a source you can explore the labelled sample project (Settings → Use sample project).
Start debugging free creates a free account, no card. Then connect Langfuse or OpenTelemetry.