Built for
- Indie hackers and solo founders on JS/TS
- Small teams who triage outages, not event floods
- Budgets that stay under ~$15/month
- Quiet inbox + AI briefs on every plan
Feature
Triage related crashes as one automatic incident
RetraceKit is incident tracking for JavaScript and TypeScript: related error fingerprints that share a route, release, or session become one outage. Built for indie hackers and small teams who want an incident inbox under about $15/month — not a full APM.
No credit card · ~2 KB SDK · Docs
You get
- Automatic incidents from normal SDK context
- Issues stay the building blocks
- Route, release, and session correlation
- First incidents usually in under three minutes
Stop triaging the same outage five times
Issues fingerprint one crash type. Incidents cluster related failures on one surface — so you resolve the outage once instead of hopping between tickets.
Issue Fingerprint
One crash type, counted many times
An issue is one fingerprint — the same exception message and stack pattern, aggregated across events. Example: TypeError reading .id of undefined on checkout, seen 847 times.
- Same crash type → one issue
- Open / resolved lifecycle per fingerprint
- AI summary on every issue
Incident Cluster
Several issues on one surface
An incident is several different issues that share a route, a release, or a session. You triage one problem instead of a scattered issue list.
- Different fingerprints, same surface
- One AI brief for the cluster
- Resolve the outage; linked issues stay for context
How RetraceKit forms an incident
TypeError: Cannot read 'id' of undefined
214 events
TypeError: Failed to fetch /api/pay
89 events
RangeError: Invalid currency code
31 events
INC-184
Active
High
/checkout
One outage across cart, payment, and currency
- Issues
- 0
- Users
- 0
- Sessions
- 0
- Candidate
- Active
- Investigating
- Resolved
Null cart item, failed payment fetch, and a currency error on /checkout in the same window become one incident — three issues, one unit of work. Full detection rules in docs →
Automatic · ~24 hour window
Opens from the context you already send
No separate incident setup. RetraceKit correlates related issues from page URL, session, and release — then opens one outage when enough distinct fingerprints share a surface.
Route
≥2 different issuesSame page path fails in several ways at once — for example /checkout. Browser apps send the URL by default.
Release
≥3 different issuesA deploy ships a cluster of new failures. Set release in init when you want this surface.
Session
≥2 different issuesOne visit hits a cascade of failures. Session incidents promote to Active as soon as they open.
Thresholds and SDK prerequisites live in the docs. Marketing takeaway: automatic incidents from normal SDK context — no extra incident config. Detection rules →
Statuses that match how you work
Quiet clusters should not sit open forever. Returning errors should reopen the same outage — without you rebuilding context from scratch.
- 01
Candidate
Cluster detected; watching impact (route and release start here).
- 02
Active
Open work — auto-promoted by impact, or immediately for session.
- 03
Investigating
You mark it in the app when you are working the outage.
- 04
Resolved
Cluster handled. Linked issues stay attached for context.
- 05
Reopened
Related errors return within the reopen window (default 24 hours).
Severity (low / medium / high) follows affected users and sessions. When new events stop for a while, the app can suggest resolve so quiet incidents do not linger.
What you open when something breaks
The incident is the unit of work in the dashboard — list, detail, and AI on the cluster and each linked issue.
Incident list
Status, severity, surface, and linked issue count in one inbox.
Detail view
Linked issues, users and sessions affected, environments.
AI on the cluster
Title and summary for the incident, plus AI summaries on each linked issue.
Included on every plan
Automatic incidents and AI summaries are not gated behind a higher tier. Free starts at 100,000 stored events; Plus is $5.99/mo and Pro is $14.99/mo.
- Free, Plus, and Pro all include incidents
- AI briefs on incidents and issues on every plan
- FIFO concurrent storage — not a monthly send quota
- Setup is a two-line SDK init; first issues and incidents usually appear in under three minutes
When to choose RetraceKit
Pick by job, not feature count. RetraceKit stays on issues, incidents, and alerts. Heavier platforms cover APM and multi-product observability.
RetraceKit Incidents inbox
Issue-centric error tracking with automatic incidents by route, release, or session. Quiet inbox under about $15/mo for indie and small JS/TS teams.
See pricing → Sentry Full platform
Errors plus performance, session replay, tracing, and a wide tooling surface. Choose Sentry when your team budgets for that stack every week.
RetraceKit vs Sentry → Bugsnag Errors + performance
Error monitoring plus performance spans and release stability across many platforms. Choose Bugsnag when that breadth matters more than a lightweight incident inbox.
RetraceKit vs Bugsnag →Not shipped yet: Slack/Discord alerts, multi-seat invites, source map upload as a product feature. Live today: Telegram and Bitrix24 integrations.
Try RetraceKit free
100k events. Incidents in under three minutes.
Common questions
What is the difference between an issue and an incident?
An issue is one fingerprint — the same crash type counted many times. An incident is several different issues that share a route, release, or session, so you triage one outage instead of a pile of tickets.
Do I need extra configuration for automatic incidents?
No separate incident config. Correlation uses the page URL (browser default), sessionId from init, and release when you set it in init. Route and session work out of the box for browser apps; set release in production for the release rule.
Are incidents included on the free plan?
Yes. Automatic incidents and AI summaries ship on Free, Plus, and Pro. Free includes 100,000 concurrent stored events with no credit card.
Can RetraceKit replace Sentry or Bugsnag?
For crash triage and automatic incidents on a small JS/TS app, yes — that is the intended job. It does not replace Sentry or Bugsnag when you need session replay, distributed tracing, performance spans, or a multi-product APM every week. See the vs pages for a fit check.
How do I migrate from another error tracker?
Install @retrace-kit/sdk, pass your project API key, and ship. Uncaught errors go out automatically. You can run RetraceKit alongside another tool while you compare inboxes. Setup docs cover browser, Node, and Next.js.
Thresholds and SDK details live in the incidents documentation — this page is the product overview.
Last updated ·
Ready to keep projects stable?
100,000 events free every month. First errors and incidents in under three minutes. No credit card, no platform tax.