GlitchTip vs Sentry
Of the 191 makers' products we know the error monitoring of, 183 chose Sentry (96%) and 0 GlitchTip (0%). Among the 34 launched in 2026, GlitchTip is in 0% and Sentry in 100%. At our calculator's default usage, GlitchTip comes to $15 a month and Sentry $29, at list prices. On GitHub, 0 public pull requests moved projects from GlitchTip to Sentry, and 4 the other way.
Two sides of the error monitoring decision: self-hosted tracker and hosted service. When each fits, what it costs, who moves from one to the other, and what makers who chose it say.
Which fits you
- Your error data must stay on your own servers
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.
- You want the widest SDK coverage and tracing next to errors
- Your product is a mobile app and crash-free rates per release matter
- Your error data must stay on your own servers
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.
At a glance
| Used by | No maker's product yet | 183 makers' products · 298 open-source projects |
|---|---|---|
| Cost at default usageerrors 50k events | $15/mo Small | $29/mo Team |
| Moved to it on GitHubpull requests since Oct 2024 | 4 from Sentry | fewer than 3 |
| Downloads | 33.8M/wk+1% vs npm | |
| Pricing | Free tier (1,000 events/month) on hosted plan; paid hosted tiers by volume; free if self-hosted. · paid from $15/mo | Free tier; usage-based paid plans by event volume; self-hosted option available. · paid from $26/mo |
| Free tier | Yes | Yes |
| Open source | Yes · self-hostable | No · self-hostable |
| Incidents, 90 daysfrom its status page | no public status feed | 21 (13 major) |
Which makers on your framework pick
Makers' products built with each framework that chose either one, for error monitoring.
| Framework | |||
|---|---|---|---|
| 0 | 56 | All 57 Next.js products' picks → |
New launches vs older products
A tool that came first has products from every year since, so its total runs ahead. Here is what products launched each year chose, as a share of those that made the error monitoring decision (by the year they launched on Product Hunt).
| Launched | Products | ||
|---|---|---|---|
| 2024 | 0% 0 | 96% 27 | 28 |
| 2025 | 0% 0 | 100% 35 | 35 |
| 2026 | 0% 0 | 100% 34 | 34 |
Cost as you grow
Both cost $0 up to 1k events; from 5k events Sentry costs less ($0 vs $15); from about 10k events GlitchTip does ($15 vs $29); from about 1M events Sentry does ($228 vs $250). They're different kinds of tool — self-hosted tracker and hosted service — so the prices don't buy the same thing.
The numbers, plan by plan
| Errors per month | GlitchTip | Sentry |
|---|---|---|
| 1,000 | $0 Free | $0 Developer |
| 5,000 | $15 Small | $0 Developer |
| 10,000 | $15 Small | $29 Team |
| 50,000 | $15 Small | $29 Team |
| 100,000 | $15 Small | $47 Team |
| 500,000 | $50 Medium | $135 Team |
| 1,000,000 | $250 Large | $228 Team |
| 5,000,000 | over plan limits | $978 Team |
Who moves from one to the other
Public pull requests on GitHub since Oct 2024 whose title says "GlitchTip to Sentry" or the reverse — real code changes, by developers in general rather than makers only.
- 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
What makers say
Makers on using it for error monitoring, from Product Hunt and Starter Story interviews, each linked to the source. Products with a page of their own and fuller notes first.
No maker quote about GlitchTip for error monitoring yet.
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.
…e - Payments Google reCAPTCHA v3 - Spam protection Amazon Web Services - Platform hosting Sentry - Bug tracking Additionally, the following communities have been an invaluable support gr…
Sentry helped us monitor errors and debug issues quickly while shipping Greta Marketplace. Real-time visibility into crashes and performance made it easier to move fast without breaking things.
Loved and watch-outs
Themes that recur in makers' words and Hacker News comments, each linked to what it summarises.
- It accepts Sentry SDKs, so switching from Sentry is mostly a DSN change. HNHN 2HN 3
- It is far lighter to self-host than modern Sentry, needing a few containers rather than a large server, while covering what small teams need. HNHN 2HN 3HN 4
- It is MIT-licensed open source, unlike Sentry's source-available license. HNHN 2
- Real-time alerts with full stack traces and user context flag production errors before users report them, which matters most for solo builders without QA. PHPH 2PH 3PH 4
- Issue grouping, release tracking and regression detection, plus links to commits, PRs and issue trackers, turn raw errors into actionable work. PHHNHN 2HN 3
- Setup is quick, and framework integrations like Next.js trace one error across server, edge and client. PHPH 2PH 3PH 4
- Self-hosting the full suite needs around 16GB of RAM, and some teams gave up on running it themselves. HNHN 2HN 3
- For simple projects it feels like overkill, with a steep price and an overwhelming dashboard. PHHNHN 2
- Frontend projects get flooded with noise from browser extensions and vague errors that need manual filtering. HNHN 2HN 3
Who uses each
What makers pair each with
Not enough makers' products to say yet.
Neither quite right?
See the whole error monitoring decision →Questions
GlitchTip or Sentry: which do makers choose?
Of the 191 makers' products we know the error monitoring of, 183 chose Sentry (96%) and 0 GlitchTip (0%). Among the 34 launched in 2026, GlitchTip is in 0% and Sentry in 100%. At our calculator's default usage, GlitchTip comes to $15 a month and Sentry $29, at list prices. On GitHub, 0 public pull requests moved projects from GlitchTip to Sentry, and 4 the other way. Choose GlitchTip if your error data must stay on your own servers; choose Sentry if you want the widest SDK coverage and tracing next to errors.
When should I pick GlitchTip over Sentry?
Pick GlitchTip if: Your error data must stay on your own servers.
When should I pick Sentry over GlitchTip?
Pick Sentry if: You want the widest SDK coverage and tracing next to errors; Your product is a mobile app and crash-free rates per release matter; Your error data must stay on your own servers.
Which is cheaper, GlitchTip or Sentry?
At errors 50k events: GlitchTip $15/mo (Small), Sentry $29/mo (Team), at list prices.
How do GlitchTip and Sentry compare in cost as you grow?
Both cost $0 up to 1k events; from 5k events Sentry costs less ($0 vs $15); from about 10k events GlitchTip does ($15 vs $29); from about 1M events Sentry does ($228 vs $250). Cheapest usable plan at each scale, at list prices.
Are people switching from GlitchTip to Sentry?
Public GitHub pull requests since 2024-10-02: 4 from Sentry to GlitchTip.

