One click records the screen, the console, the network calls and the exact environment — then AI writes the summary, the likely root cause and the steps to reproduce. The ticket lands in Jira before you've finished describing it.
Free forever plan · No credit card · Works on any site, including localhost
AI analysis
Root cause — POST /api/cart/coupon returned 500 after the discount pushed the total below zero. The client reads res.data.total.toFixed() without a null guard, so the cart component throws and unmounts the checkout tree.
✕ TypeError: Cannot read properties of null (reading 'toFixed') at CartTotal (Cart.tsx:118:24)⚠ POST /api/cart/coupon → 500 (412 ms) { code: "NEGATIVE_TOTAL", cartId: "c_9f3a1" }A screenshot in Slack starts a negotiation, not a fix. The developer asks which browser. QA asks which build. Somebody asks for the console. By the time the context exists, the tab is closed and the state is gone.
Without BugCatch
With BugCatch
The reporter clicks once. BugCatch does the interrogation.
BugCatch keeps a rolling buffer of the last two minutes of screen activity in an isolated offscreen document, capped to bound memory. Something breaks, you hit Rewind, and the recording of what led up to it is already there. No "can you do it again?"
Grab the full page or a region, then arrow, box, blur and caption it in place. Sensitive fields blur before the capture ever leaves the browser.
Record a tab, a window or the whole desktop with mic and narration. WebM is transcoded to MP4 on the queue so it plays anywhere your team pastes it.
Errors, warnings, stack traces, failed requests with status codes, timings and payloads — attached to the report automatically, not pasted in by hand.
Browser and version, OS, viewport and device pixel ratio, URL, release build, locale, timezone and the signed-in user — every field a triage engineer checks first.
A ~4 kB browser SDK puts a Report a bug button inside your own product, so customers and non-technical staff file the same complete report — screenshot, console, network and environment — without installing anything. Two lines to initialise, and the widget inherits your theme.
import { BugCatch } from '@bugcatch/sdk'
BugCatch.init({
projectId: 'prj_8f21c',
capture: { console: true, network: true },
redact: ['[data-private]', 'input[type=password]'],
})Every report is analysed the moment it lands. BugCatch writes a one-line summary, proposes a root cause from the stack trace and failed requests, drafts numbered reproduction steps, and suggests a severity — then sorts the queue by it.
Hit the extension or the in-app button. Screenshot, recording or Rewind — plus console, network and environment, collected in the same moment.
Media goes straight to object storage over a presigned URL, so a 60 MB recording never queues behind the API. The report is created the instant the upload lands.
Background workers run AI analysis, redact secrets, transcode the video and push the issue to your tracker. Seconds, not a build step.
It appears in the queue ranked by severity, with the video, the logs and the repro on one screen. Assign, comment, resolve, or share a read-only link.
One internal bug shape maps to every tracker through small per-provider adapters — so the same capture becomes a Jira issue, a GitHub issue and a Slack message with the fields each one expects.
A recording of a checkout flow contains a real cart, a real session and sometimes a real card field. Encryption and redaction are the default, not an enterprise upsell.
On Team and Enterprise, every content column is sealed with AES-256-GCM under a per-workspace data key, itself wrapped by a master key. Ciphertext is self-describing, so a plan change or a half-finished backfill stays readable.
Configurable rules strip tokens, cookies, auth headers, card numbers and anything matching your own patterns out of logs and payloads before the record is written.
Every tenant resource is checked against membership. Projects are public to the workspace or restricted to an explicit member list, enforced inside the guard so no endpoint can ship without the check.
A session is private by default and inherits its project's setting. Share one publicly and the API serves a purpose-built payload at a token URL — never the internal record.
Owner, admin, member and viewer, applied per workspace with an audit trail on every triage action. SSO/SAML and SCIM provisioning on Enterprise.
Retention is enforced per plan, from 7 days on Free to 365 on Enterprise — with custom windows, data residency, and self-hosted or private-cloud deployment available.
Every limit on this page is enforced by the API, not just printed here.
For solo devs and trying things out.
$0/member/mo
Start freeFor product teams shipping every week.
$19/member/mo
Start 14-day trialFor orgs with compliance and scale needs.
Custom
Talk to salesYearly prices are what you pay per member each month when billed annually.
Your team installs the Chrome extension, which works on any site including localhost and staging behind auth. For customers and non-technical staff, drop the ~4 kB SDK into your app and they file the same complete report from a button in your own UI — nothing to install.
Once you enable it, BugCatch continuously records into a rolling in-memory buffer holding the last ~2 minutes, discarding everything older. Nothing is uploaded until you press Rewind. If you never press it, nothing ever leaves the machine.
Two layers. In the browser you can mark elements to blur, and password fields are masked by default. Server-side, redaction rules strip tokens, cookies, auth headers and card patterns from logs and payloads before the record is written — and redaction runs before encryption, so the sealed row never contains the secret.
Yes. Plenty of teams treat BugCatch as the capture and evidence layer only: the issue is created in Jira, GitHub or Linear on ingest, and the BugCatch link carries the video, logs and environment. Status changes sync back so the queue doesn't drift.
Analysis runs on Claude through the API, on a no-training basis. It sees the redacted report — stack traces, failed requests and environment. If you'd rather it saw nothing, AI analysis can be turned off per project and everything else works unchanged.
You keep everything you already have. Limits apply when you create something new, so a workspace over its new plan's cap is simply blocked from adding more rather than losing data. Encryption converts in place and is re-runnable in either direction.
On Enterprise, yes — in your own cloud or a dedicated private instance, with your object storage and your key management. The stack is Postgres, Redis and a Node API, deployable with Docker Compose or your own orchestration.
Install the extension, capture one bug, and see what a complete report looks like. Free forever for solo work — no card, no sales call.
Works in Chrome and Edge · Firefox and Safari support in beta