What ResolveTrace gives your team
A stack-agnostic browser SDK and support workflow, built around the support-to-engineering handoff. Enough evidence to resolve real customer-reported issues — never more capture than the work requires.
Six things your team can do on day one
Each is on by default with privacy-safe settings. Everything is tunable by your governance reviewer.
Masked replay
Privacy-safe defaults from day one. Mask sensitive inputs, deny-list sensitive routes, redact at source — no broad surveillance capture.
Error and network breadcrumbs
JS errors, API failures, and network activity captured around the moment things went wrong — no guessing what happened before the crash.
Frustration signals
Dead clicks, rage clicks, and stalled interactions surfaced automatically — the things customers can’t describe but can’t ignore.
Per-session support code
Customers share a short code; support pulls up the exact session in seconds. No back-and-forth asking for browser details.
In-app “Report a problem”
One-click widget captures the right context and routes it to your ticketing system with the session attached.
Governance controls
Masking rules, retention policies, role-based access, and audit trails — built for teams whose privacy reviewers say no to broad replay.
From “it didn’t work” to a resolved ticket
Same customer report. Two support workflows. One of them actually resolves the issue.
Support collects a screenshot, asks follow-up questions, opens a ticket with partial information. Engineering starts blind — backend logs show the request happened, but not whether the UI was blocked or what the user saw.
Support gets a support code tied to the affected session. The case shows masked replay, dead-click signals, route history, and the exact moment the interaction stalled. Engineering starts with evidence.
Why privacy and governance teams say yes
- Masked replay by default
- Deny-lists for sensitive routes
- Source-side redaction rules
- Role-based access and full auditability
- Short retention options and regional deployment controls
Built on a public contract you can verify
Hosted or self-hosted, the SDK and wire format are the same — and every deployment is verifiable against the same conformance suite.
resolvetrace-contract
Public source of truth for the ResolveTrace client-to-server boundary: SDK packages, HTTP API spec, JSON schemas, and a conformance harness that verifies any deployment against the same contract.
resolvetrace-core
Single-tenant, self-hosted ResolveTrace server for local development, reference integrations, and teams who need to run everything in their own environment. Converts to Apache 2.0 three years after each release.
See it on a real support case
Bring a customer-reported issue you can’t reproduce. We’ll show you what it looks like with ResolveTrace.
Request a demo →