Platform
Open standards at every boundary. Nothing proprietary in the path.
Telemetry arrives over OTLP from unmodified OpenTelemetry SDKs, lands in an open columnar store queried with standard SQL, and archives to Parquet you can read with anything. No proprietary agent, no bespoke wire format, no query language you can only use here — if you ever leave, your data and your instrumentation come with you.
Data path
- 01
Your services
OTel SDK · any stack
- 02
OTel Collector
OTLP 4317 / 4318
- 03
Columnar store
open · standard SQL
- 04
Clarity API
retrieval + NLP→SQL
- 05
Clarity UI
workspace
Clarity AI
NLP · RCA · advisory
Archive
Parquet · object store
Open at every boundary
- Standard OTLP ingest — gRPC on 4317, HTTP on 4318, nothing custom
- Instrument once with vendor-neutral OpenTelemetry and point it anywhere
- Archive to open Parquet on object storage, readable without us
- Kubernetes and VM targets from a single bootstrap command
Design principles
- The store does the work
- Anywhere a UI computes over a page of rows instead of the match set, the answer is wrong — not approximate. Aggregation belongs in the database.
- Advisory means advisory
- The assistant writes the RCA and the remediation plan; a human runs it. No auto-execution, not behind a flag. That's a product decision, not a missing feature.
- Ambiguity gets an answer
- A malformed or ambiguous question returns a clarifying response. A silent empty result set is the one answer we refuse to give.
- No lock-in, structurally
- Vendor-neutral instrumentation in, standard SQL across, open Parquet out. The exit path is part of the design, not a concession.
See it on your own questions.
Request a login to the live demo with 80M spans, or book a walkthrough on your stack.