One tiny SDK.
The whole loop.
The tiny SDK for in-app feedback, surveys, and crash reports — for the web. Drop in @catch.dev/web once and follow one user problem all the way around the loop.
A bug report users actually send.
One line of JS drops a corner widget into your app. The user types what broke; Catch attaches the screenshot, console, network, URL, and any metadata you pass — so there's no repro hunt waiting for you.
- Screenshot & redact, in-browser
- Console, network & URL auto-attached
- Arbitrary key/value metadata
Crash reports, deminified.
JS errors are symbolicated against your source maps, so production stack traces read like the code you wrote. Catch groups them into issues you can assign, track, and resolve as a team.
- Symbolicated stack traces
- Source maps via CLI or build plugin
- Grouped into issues — assign & track
Know the moment it breaks.
A new issue, a spike, or a regression — Catch alerts the team in Slack or email with the stack trace attached. You fix it before it turns into churn.
- Delivered to Slack and email
- Fire on new, regression, or spike
- Route by app, environment, or severity
Wired into the tools you already use.
Source maps from npm and the CLI, alerts in Slack, errors that connect to GitHub — and your whole team on the same issue: assign, comment, and resolve together, without leaving Catch.
Assign, watch, and comment on every issue together — your whole team, one source of truth.
Add the dependency. Ship in ten.
Three steps, one tiny package. Pick your framework, copy it in, and Catch starts catching on your next deploy.
- 01
Install the package
npm i @catch.dev/web — 4kb gzipped, zero runtime deps.
- 02
Initialize once
Call Catch.init with your project key. Feedback and crashes are on by default.
- 03
Ship it
Deploy. Reports land under App → Issues and App → Feedback.
You've seen the loop.
Now run it.
One tiny SDK — feedback, surveys, crashes, alerts, and integrations, wired together in under ten minutes.