Error Monitoring
Find out when your app throws an error in production, with the stack trace and context to fix it, before users email you.
Trends
PostHog gained the most ground in package downloads: +91% against the median npm package over a year.
Public counts each month: pull requests on GitHub, package downloads, stars, Product Hunt followers. They show direction, not market share.
- Oct 19 · Adoption 337 more makers' products found using PostHog (now 337).
The real choice
Hosted service or self-hosted tracker. Hosted services give you setup in minutes and pricing by event volume; self-hosting keeps error data on your servers for the cost of running and upgrading it.
Pick by situation
Tap the ones that are you — the tools that fit light up below.Compare the tools
Grouped by the side of the choice they answer, not ranked. Open a row for when to use it, the trade-off and what makers say.
Sentryservice · self-hostable · free tierBroad SDK coverage across languages and frameworks, with performance tracing next to errors.


183+298 open source$29Team33.8M/wk+1% vs npm
Use it whenYou want one tool that covers every language and framework in your stack, frontend to backend.
Trade-offEvent-based billing can jump after a noisy bug; the self-hosted version needs a sizeable server.
llms.txtMCPCLIUsed by Beatoven.ai, Brev.io, Bricks, Central, ChatPal and 178 more · in 298 open-source projects.
Sentry gives us one place to investigate errors across Marqly’s web app and API. The error context is especially useful when tracing a failed save, sync, or AI Organizer run.
Rollbarservice · free tierError grouping tied to releases, with session replays linked to errors.


6+18 open source$29Essentials 50k489.9k/wk−58% vs npm
GlitchTipservice · open source · free tierSelf-hosting error tracking on a small server while using Sentry's SDKs.No evidence yet$15Small
Use it whenYou want error data on your own infrastructure or a lighter stack than self-hosted Sentry.
Trade-offFewer features than Sentry, and you run the upgrades and backups.
CLINo maker's product we track shows it for this yet.
Cost: the cheapest plan that fits errors 50k events, from list prices. Try your own numbers →
Cost as you grow
Each contender's cheapest usable plan as usage rises.
Who switches to what
Public pull requests on GitHub since Oct 2024 whose title says "X to Y" — real code changes, by developers in general rather than makers only. Pick a flow to see its pull requests.
- Switch error monitoring from Rollbar to Sentryneinteractiveliterature/larp_library · 2026-09-03
- refactor: migrate Rollbar to Sentry for error tracking and telemetrydianlight/srat · 2026-05-20
- Convert rollbar to sentrymixpanel/docs-legacy · 2025-07-18
- Migrate from Rollbar to Sentryjetstreamapp/jetstream · 2025-03-30
- ADFA-4751: Rebrand remaining Sentry references to GlitchTipappdevforall/CodeOnTheGo · 2026-07-17
- feat(telemetry): guarded /api/debug/sentry route to verify GlitchTip captureKhourySpecialProjects/video-review-system · 2026-07-17
- ADFA-4397: Migrate crash and log reporting from Sentry to GlitchTipappdevforall/CodeOnTheGo · 2026-07-07
- feat(observability): wire errors-only Sentry SDK to GlitchTipsolid-stats/server-2 · 2026-06-14
Before you choose
Install the SDK on both frontend and backend before launch, upload source maps, and tag each release so you can see which deploy introduced an error. Set alerts for new issues only, not every occurrence, or you will start ignoring them. Filter out noise (bots, browser extensions) early to stay inside your event quota.
- Shipping minified frontend code without uploading source maps, so every stack trace points at one unreadable line.
- Alerting on every occurrence instead of new issues, until the channel is muted and real regressions go unseen.
- Sending request bodies and headers with passwords, tokens or personal data into a third-party error tracker.
Other options
Real choices most makers here won't need to weigh.
Decided alongside
What the 150 makers' products here chose for their other decisions.