Scritch vs. an error monitor (like Sentry)
Last updated 3 September 2026
An error monitor and a recovery agent do different jobs. An error monitor like Sentry tells your team that something broke, after the fact: it groups exceptions, alerts an engineer, and shows a stack trace. Scritch, an AI recovery agent, gets the user unblocked in the moment: it reads the failure, asks the one question only they can answer, fixes it with their approval, and proves it worked. They are not alternatives. Scritch reads from your monitor rather than replacing it.
| Error monitor (Sentry) | Scritch | |
|---|---|---|
| Who it serves | Your engineering team | The blocked end user |
| When it acts | After the fact | In the moment the request fails |
| What it produces | A grouped exception, an alert, a stack trace | A resolved session, or a clean escalation |
| Does it change anything | No — it observes | Yes — with the user’s approval, and it verifies the change |
| Pricing shape | By event volume / seats | Per recovery that actually worked, capped |
| Relationship | The source of evidence | Reads that evidence to fix the failure |
Does Scritch replace Sentry?
No. If you want exceptions grouped, alerted, and traced for your team, you already have that, and Scritch reads from it. Scritch is the layer that turns one of those failures into a fix the user can act on, instead of a ticket your team works later. Keep the monitor; add recovery on top.
When would I use each?
Reach for the monitor when the question is “what is breaking, how often, and where in the code” — the team’s view of reliability. Reach for recovery when the question is “this specific user is stuck right now, and the cause is something they can fix” — a bad VAT number, a stale session, a file the endpoint rejected. Most teams that need one eventually want both.
What Scritch does not do
It is not an error monitor, an APM, or a log aggregator. It does not alert your on-call or chart your error rate. It handles a single blocked user, end to end, and hands off anything it cannot fix. For the fuller picture, see what user-facing error recovery is.