Show the bug.
Search for it later.
Record the repro in your browser and paste the link into the ticket. What you said while it happened becomes searchable text, so the same bug six months on is a search away.
no install · one flat price · no per-seat fees
The problem
Three paragraphs.
Still needs a demo call.
- Three paragraphs. Still needs a demo call.
- You describe the bug in precise detail. You attach a screenshot. The developer still comes back with "can you just show me?" The written format doesn't carry the context.
- The bug only reproduces under very specific conditions.
- "Click here, then scroll, then open the modal in less than two seconds, then resize." Writing that down accurately is genuinely hard. Showing it takes fifteen seconds.
- Sydney reports it. Amsterdam fixes it. Nobody's awake at the same time.
- Async bug handoffs collapse when the only artifact is a ticket. The developer needs to watch the repro, not reconstruct it from notes.
- The ticket gets reassigned. The context disappears.
- The new person picks up a bug with three sentences of notes and has to start from scratch. The original reporter has moved on.
How it helps
The bug report is the recording.
- Record where the bug lives
- Most bugs are in the browser. The recorder is in the browser. No screen mirroring, no capture software, no extra steps. Reproduce the bug, hit record, show it.
- What you said becomes searchable text
- Every recording is automatically transcribed, published or not. Walk through the bug out loud ("so here I click this, and you can see the state doesn't update") and that becomes a searchable caption alongside the video.
- Paste a link. No account required to watch.
- Publish, copy the link, paste it into Linear or Jira or Notion. The developer opens it in their browser. No searchferret account, no login, no "open in app" prompt. Or keep the recording private and share it with only the people you pick. The choice is yours.
- Recordings save locally first
- The recording saves to your device before anything uploads. You won't lose a repro to a network hiccup or a failed upload. Cloud sync is a separate, retryable step.
Where this pays off
Bugs worth recording.
- Reproducing a bug that only shows under specific user flows
- Cross-timezone handoffs between QA and engineering
- Attaching a repro to a Linear, Jira, or GitHub issue
- Escalating a customer-reported bug with visual proof
- Tagging a repro with its ticket number or bug category so you can find it months later
- Building a library of past bug repros for pattern matching
The call
Twenty minutes, with the person who built it.
- 01
You show us how your team records and shares things today.
Five minutes - 02
We search a real library live, and set up yours if you like.
Ten minutes - 03
You decide. No follow-up sequence, no "checking in".
Five minutes, or less
You'll be talking to Wouter, the founder. Not a sales rep.
Frequently asked questions.
No. Published recordings get a public share link. Anyone with the link can open it in their browser. No sign-up, no app, no login required. Just a link. And you don't have to publish to get one: any recording saved to the cloud can have a magic link that works the same way. No transcoding, no public page, the developer just opens it and watches.
See your repros searchable, on the call.
Twenty minutes with the founder. Bring a bug that was hard to explain in text and we record it together.
Or get started free, no call needed