Use cases

Not just a bug reporter.
A consent-gated capture tool.

The thing we built isn't "report a bug." It's let the person on the other side of the screen show you exactly what happened, with their consent, while everything sensitive stays in their browser. That primitive solves a handful of jobs-to-be-done equally well. Here's where it fits.

For engineering orgs

Internal QA

Your QA testers click Record on staging. Engineering gets the rrweb replay, the failing API call, the actual console TypeError — not "the button didn't work."

See the QA workflow →
For agencies + freelancers

Client feedback

Client clicks Record on the staging URL, walks through their feedback with audio, draws on the page. No more "the button on the page" in Slack DMs.

See the agency workflow →
For support + CS teams

Customer support

Stop asking customers to "screenshot the error." Send a capture invitation; get back a real replay with network log and console attached to the ticket.

See the support workflow →
Also a clean fit for UX research, beta-feedback collection, incident reproduction, accessibility audits, and compliance audit trails. If your workflow involves "can you show me what happened?", the primitive is the same. Pitch yours →

Same product. Different default.

All four use cases run on the same SDK + dashboard. Pricing's on the pricing page. Free covers the first 10 captures a month — enough to feel whether it fits.

Start free How it works →