# RetraceKit

> Incident tracking for JavaScript, TypeScript, Python, and Java: related crashes correlate by route, release, or session into one outage. Issues remain the building blocks. Hosted SDKs (JS/TS ~3.5 KB gzipped ESM; Python `retrace-kit` on PyPI; JVM `cloud.retracekit:sdk`), AI summaries — without a full APM or self-hosted Sentry stack.

RetraceKit is a managed SaaS product at https://retracekit.cloud. Best when you want production error awareness and automatic incident correlation under about $15/mo, not distributed tracing or session replay.

Start free (no card): https://app.retracekit.cloud · Upgrade (manual email billing): support@retracekit.cloud

## Who it is for

- Indie hackers and solo founders shipping JS/TS apps, Python backends (FastAPI, Django, asyncio), or JVM services (Java 17+, Kotlin)
- Small product teams that want an incident inbox for outages, not a data lake
- Teams leaving heavier tools because of noise, price, or setup cost

Skip when you need session replay, tracing, profiling, source map upload, Slack/Discord alerts, multi-seat invites, or self-serve card checkout only.

## Product

- [Full content for LLMs](https://retracekit.cloud/llms-full.txt): Product brief — pricing, incidents, setup, constraints, vs Sentry / self-host.
- [Home](https://retracekit.cloud/): Landing — incident-centric positioning.
- [Incidents](https://retracekit.cloud/features/incidents/): Automatic incident tracking — correlate related crashes by route, release, or session.
- [Pricing](https://retracekit.cloud/pricing/): Free (100k stored events), Plus ($5.99), Pro ($14.99). Incidents + AI on every plan. FIFO storage, not monthly send quota.
- [vs Sentry](https://retracekit.cloud/vs/sentry/): Comparison for indie hackers and small teams.
- [Sentry alternative](https://retracekit.cloud/alternatives/sentry/): 301 → /vs/sentry/.
- [vs Bugsnag](https://retracekit.cloud/vs/bugsnag/): Bugsnag alternative for indie hackers and small teams — incidents under ~$15/mo.
- [Bugsnag alternative](https://retracekit.cloud/alternatives/bugsnag/): 301 → /vs/bugsnag/.
- [About](https://retracekit.cloud/about/): Independent / bootstrapped project by founder Ildar Timerbaev.
- [Privacy](https://retracekit.cloud/privacy/): Data handling; retention follows the project plan.
- [Blog](https://retracekit.cloud/blog/): Notes on incident tracking and error correlation.
- [Blog: Python error tracking](https://retracekit.cloud/blog/python-error-tracking/): Python SDK — exceptions become events; FastAPI and Django.
- [Blog: Java error tracking](https://retracekit.cloud/blog/java-error-tracking/): Java SDK — exceptions become events; Java 17+ and Kotlin.
- [Blog: Remote MCP](https://retracekit.cloud/blog/remote-mcp/): RetraceKit remote MCP — triage from your IDE (Cursor, Claude, Codex, VS Code).
- [App](https://app.retracekit.cloud): Dashboard (issues, incidents, releases, integrations).

## Documentation

- [Overview](https://retracekit.cloud/docs/): Quick start.
- [Setup](https://retracekit.cloud/docs/setup/): Install and API key.
- [MCP](https://retracekit.cloud/docs/mcp/): Remote MCP for Cursor, Claude Code, Codex, VS Code — triage with the project API key.
- [Incidents](https://retracekit.cloud/docs/features/incidents/): Related issues correlated by route, release, or session (docs).
- [Incidents (product)](https://retracekit.cloud/features/incidents/): Marketing overview — automatic incidents for indie teams.
- [Breadcrumbs](https://retracekit.cloud/docs/features/breadcrumbs/): Trail before an error (product).
- [Current user](https://retracekit.cloud/docs/features/current-user/): User id on issues (product).
- [Session](https://retracekit.cloud/docs/features/session/): Visits and EFU (product).
- [Release](https://retracekit.cloud/docs/features/release/): Version labels and Releases view (product).
- [Capture](https://retracekit.cloud/docs/sdk/capture/): Auto vs manual capture, payload.
- [SDK Breadcrumbs](https://retracekit.cloud/docs/sdk/breadcrumbs/): addBreadcrumb, network, routers.
- [SDK Current user](https://retracekit.cloud/docs/sdk/current-user/): setUser.
- [SDK Session](https://retracekit.cloud/docs/sdk/session/): sessionId and pings.
- [SDK Release](https://retracekit.cloud/docs/sdk/release/): version from package.json / metadata.
- [Browser](https://retracekit.cloud/docs/environments/browser/): Frontend hooks, URL, network.
- [Node.js](https://retracekit.cloud/docs/environments/node/): Server init; pass url on captureException.
- [Python](https://retracekit.cloud/docs/environments/python/): pip install retrace-kit; FastAPI and Django; asyncio auto-capture.
- [Java](https://retracekit.cloud/docs/environments/java/): cloud.retracekit:sdk; Java 17+ and Kotlin; uncaught handler.
- [Next.js](https://retracekit.cloud/docs/platforms/nextjs/): App Router client + server setup.
- [Plans](https://retracekit.cloud/docs/plans/): Retention and storage limits.

## Key facts

- Package `@retrace-kit/sdk` (JS/TS) — `init({ apiKey })`; ~3.5 KB gzipped ESM (measured)
- Package `retrace-kit` (Python 3.10+) — `pip install retrace-kit`; `init(api_key=...)`; FastAPI and Django extras; zero core runtime deps
- Package `cloud.retracekit:sdk` (Java 17+) — `RetraceKit.init(Config)`; Kotlin source, Java bytecode; runtime dep `kotlin-stdlib`
- Remote MCP at `https://api.retracekit.cloud/mcp` — same project API key as the SDK; list/get/update issues and incidents, AI explain
- Automatic incidents: cluster distinct issues by route, release, or session
- Auto-grouping of identical crashes into issues; AI summaries on all plans
- Stack traces, breadcrumbs, EFU (error-free users)
- Alerts live: Telegram, Bitrix24. Email: coming soon. Slack/Discord: not shipped
- Free: 100,000 concurrent stored events (FIFO); Plus $5.99; Pro $14.99
- Not included: session replay, distributed tracing, source map upload, multi-seat invites, self-serve card checkout

## Incidents (summary)

An issue is one fingerprint (the same crash type). An incident is several different issues that share a surface — the same URL path, the same release you shipped, or the same browser session — so a solo developer or small team triages one outage instead of a pile of open tickets. Product overview: https://retracekit.cloud/features/incidents/ · Docs: https://retracekit.cloud/docs/features/incidents/

## Compared to heavier platforms

- [RetraceKit vs Sentry](https://retracekit.cloud/vs/sentry/): Head-to-head — incidents vs alerts, pricing, fit.
- [Sentry alternative](https://retracekit.cloud/alternatives/sentry/): 301 → /vs/sentry/.
- [RetraceKit vs Bugsnag](https://retracekit.cloud/vs/bugsnag/): Bugsnag alternative for indie hackers and small teams.
- [Bugsnag alternative](https://retracekit.cloud/alternatives/bugsnag/): 301 → /vs/bugsnag/.
- [Blog: RetraceKit vs Bugsnag](https://retracekit.cloud/blog/retracekit-vs-bugsnag/): Long-form pricing, fit, and FAQ.
- [Blog: Python error tracking](https://retracekit.cloud/blog/python-error-tracking/): Python SDK announce and setup.
- [Blog: Java error tracking](https://retracekit.cloud/blog/java-error-tracking/): Java SDK announce and setup.
- [Blog: Remote MCP](https://retracekit.cloud/blog/remote-mcp/): RetraceKit remote MCP announce and tool examples.

Choose RetraceKit when you want a quiet JS/TS, Python, or JVM tracker with automatic incidents and predictable indie pricing. Choose Sentry when you want one vendor for errors plus performance, session replay, and the wider monitoring stack. Choose Bugsnag when you want errors plus performance spans and release stability across many platforms. Prefer self-hosted GlitchTip/Sentry when you want zero SaaS cost and accept the ops.