Frontend session replay, backend errors, logs and traces — stitched on a single timeline. One open-source platform replaces the LogRocket + Sentry + log-tool stack you’re quietly outgrowing.
Highlight records every user session — DOM mutations, console output, network calls, redux state — at 60fps with privacy-by-default masking. When you open one, the playhead is already on the error frame. You see what the user saw, three keystrokes before it broke.
rrweb-based capture, <3% CPU overhead, masks every input by default.
Errors, rage clicks, dead clicks and network failures are flagged on the scrub bar.
Server-side PII redaction, domain allowlists, GDPR-compliant retention controls.
Filter by browser, version, A/B variant, custom user trait, or any error message in console.
Sessions on the front end. Errors and traces on the back end. Logs in the middle. Highlight is the only platform that ships all four with a shared trace ID — so the customer’s click and your server’s 500 are the same line on the same timeline.
Watch real users interact with your app. 60fps DOM capture, network & console included, with sub-3% performance overhead and privacy-by-default masking.
Auto-grouped exceptions across web, mobile and backend. Source-mapped stack traces, GitHub PR links, and Slack alerts that already know the offending session.
OpenTelemetry-native distributed tracing and structured logging on ClickHouse. Sub-second queries across billions of rows, with automatic correlation to the originating session.
Highlight is open source — not “source-available marketing.” The full SDK, ingest pipeline, ClickHouse schema and frontend live on GitHub under AGPL-3.0. Run the same code we run in our cloud.
Deploy the entire stack on your own VPC. Customer data never leaves your network. Used by HIPAA, FedRAMP and GDPR-bound teams.
OpenTelemetry-native means Highlight slots into the OTel collector you already run. Native integrations across the rest of your stack.
Highlight’s AI assist surfaces the offending commit, suggests a fix, and pre-fills the GitHub PR description. Available on every session, every error, every trace.
Annual third-party audits. PII redaction at the SDK boundary. EU/US data residency. SSO, SCIM and audit logs on every plan above Free.
A real session. The user reported they couldn’t check out. Highlight already grouped the error, attached the session, captured the slow query and surfaced the failing line. You’re looking at the same panel an on-call engineer sees at 3 a.m.
If you’re running LogRocket for replay, Sentry for errors and Datadog for logs, you’re burning roughly $2,400/mo at 50K MAUs and stitching context manually. Highlight is one timeline, one bill, one open-source codebase.
Predictable usage-based pricing. Unlimited team members on every plan — including Free. Self-host the entire stack for $0, forever.
Side projects, OSS, and the first ten thousand sessions of every startup.
Growing product teams who’ve outgrown the free tier and the legacy stack.
Regulated industries, large teams, and anyone who needs the data inside their own VPC.
Unlimited team seats on every tier · cancel any time · pay-as-you-go beyond included usage
We replaced LogRocket, Sentry and a half-broken in-house log pipeline with Highlight in a single afternoon. The first thing my staff engineer said was ‘why doesn’t every observability tool work like this?’. Our mean time to resolution dropped from 47 minutes to 9.
The session replay alone justified the switch. Watching the customer’s exact click path next to the failing trace is the debugging UX I’ve wanted for a decade.
We’re HIPAA-bound and we self-host the whole stack on our own VPC. Highlight is the only tool in this space that made that path actually pleasant.
OpenTelemetry-native means I’m not locked in. My ingest pipeline already speaks OTel — Highlight slotted in behind it without changing a single line.
The pricing page is the only one I’ve ever read top-to-bottom and not felt like I was being lied to. Usage-based, generous free tier, no per-seat surprise.
Our support team uses Highlight more than the engineers do. They paste a session URL in the ticket and the whole “repro it on my machine” theatre disappears.
Everything an engineering lead asks before greenlighting a new observability vendor. If we missed one, our docs are public — every single line.
Ten thousand sessions, one million errors, unlimited team seats — free, forever. Plug in a single line of code. Watch the next user’s click trip a backend exception. See it in one timeline. Fix it before they email support.