REVIEWS / GENERAL / OWNER INSIGHTS
🦉 WE READ 648 OWNER COMMENTS
Grab 9: what owners actually say
Owners consistently praise the product's open-source model and fair pricing, but recurring concerns center on exception sampling and the long-term implications of venture funding.
What owners complain about
- Exception sampling SOME
Owners report that exceptions are sampled, meaning they cannot reliably view every instance of an error. Some need every single event saved for manual fixes and feel they cannot fully trust the tool for this reason.
- Self-hosting maintenance burden COMMON
Multiple commenters note that while self-hosting is possible and well-documented, maintaining an unfamiliar server and application becomes difficult as usage scales, pushing most users toward the SaaS version.
- Aggregate vs individual event tradeoff SOME
Owners point out the tool prioritises aggregate views over individual events, which suits large tech companies with high error volumes but frustrates smaller teams who need per-instance detail.
- Funding-driven open-source anxiety SOME
Several commenters express concern that after raising capital, the company could prioritise profit over open-source stewardship and eventually turn the product into crippleware, a pattern they've seen elsewhere.
- Overlap with logging tools FEW
At least one user questions whether Sentry is necessary if they already use a general logging tool that could capture both errors and logs, suggesting redundancy concerns.
What owners love
- Open source with low barrier
Owners love that the full codebase is open source and fully self-hostable, making it easy to try and evaluate without commitment or sales friction.
- Fair and competitive pricing
Multiple commenters say pricing is fair to the point where hosted SaaS is actually cheaper than self-hosting, eliminating the usual cost penalty of managed services.
- Responsive support
Owners specifically highlight very responsive support as a standout quality.
- Clean UI and good documentation
The user interface is praised as nice, and self-hosting documentation is described as extremely thorough and well-supported.
- Rich crash reports
Owners value the extremely detailed crash reports and day-to-day developer workflow tools compared to higher-level passive analytics competitors.
Surprising patterns
- Owners treat open source primarily as a marketing strategy: the low barrier to self-hosting drives adoption, but almost everyone migrates to the paid SaaS version once usage becomes serious, making self-hosting effectively an on-ramp rather than a long-term plan.
- The product is used in unexpected environments — one commenter was impressed to learn CCP Games used it for a PS3 multiplayer game (Dust 514), signalling cross-platform credibility beyond typical web development.
- The founder actively engages in public threads defending the open-source model and explicitly commits to not creating crippleware, which owners cite as a trust signal that is unusual for venture-backed companies.
WHO SHOULD SKIP IT
Teams that require every single exception instance to be captured without sampling — such as those doing manual, per-event debugging — may find the sampling behaviour unreliable for their workflow.
Synthesised from 648 real owner comments across 4 platforms. Every point is grounded in the comments — no marketing, no AI guessing. How we do it →