HackerReposA FIELD GUIDE TO OPEN SOURCE
ProSponsor the shelf♧ 0
← Back to top all-time
getsentry
sentry
Python2012–2026
getsentry / sentry

sentry

Developer-first error tracking and performance monitoring

60Distinct people
88Mentions
0Explicit recommenders
45.8KGitHub stars
REPOSITORY AT A GLANCE

What to know before exploring

What it is

Developer-first error tracking and performance monitoring

GitHub

Where it is used

  • GitLab — GitLab uses Sentry to monitor frontend errors and performance on GitLab.com. Their production site is configured to send data to a GitLab-managed Sentry instance. Source

What people are saying

No recommendation phrase was found in the indexed comments.

No classified warning is attached to this page. Read the discussions before treating silence as approval.

Also in these discussions

Mentioned in the same Hacker News threads. That is not proof they are substitutes.

This week on Hacker News

Nov 8–Nov 15 UTC · Direct repository links and separately labeled related project stories. Indexed through 11/15/2026, 5:05:26 PM UTC.

No direct repository links were found in the indexed HN discussions over the past seven days. Older discussions are available below.

Mentions over time

HN mentions by year88 dated mentions

Observed mentions: 2012-10-01 16:28:41 UTC to 2026-02-07 15:56:46 UTC.

0510152012-01-01 00:00:00 UTC to 2013-01-01 00:00:00 UTC (exclusive): 3 mentions; 0 submissions, 3 comments20122013-01-01 00:00:00 UTC to 2014-01-01 00:00:00 UTC (exclusive): 7 mentions; 0 submissions, 7 comments2014-01-01 00:00:00 UTC to 2015-01-01 00:00:00 UTC (exclusive): 4 mentions; 1 submissions, 3 comments2015-01-01 00:00:00 UTC to 2016-01-01 00:00:00 UTC (exclusive): 7 mentions; 0 submissions, 7 comments2016-01-01 00:00:00 UTC to 2017-01-01 00:00:00 UTC (exclusive): 13 mentions; 0 submissions, 13 comments2017-01-01 00:00:00 UTC to 2018-01-01 00:00:00 UTC (exclusive): 6 mentions; 1 submissions, 5 comments2018-01-01 00:00:00 UTC to 2019-01-01 00:00:00 UTC (exclusive): 8 mentions; 0 submissions, 8 comments2019-01-01 00:00:00 UTC to 2020-01-01 00:00:00 UTC (exclusive): 7 mentions; 1 submissions, 6 comments20192020-01-01 00:00:00 UTC to 2021-01-01 00:00:00 UTC (exclusive): 3 mentions; 0 submissions, 3 comments2021-01-01 00:00:00 UTC to 2022-01-01 00:00:00 UTC (exclusive): 6 mentions; 0 submissions, 6 comments2022-01-01 00:00:00 UTC to 2023-01-01 00:00:00 UTC (exclusive): 5 mentions; 0 submissions, 5 comments2023-01-01 00:00:00 UTC to 2024-01-01 00:00:00 UTC (exclusive): 8 mentions; 0 submissions, 8 comments2024-01-01 00:00:00 UTC to 2025-01-01 00:00:00 UTC (exclusive): 6 mentions; 1 submissions, 5 comments2025-01-01 00:00:00 UTC to 2026-01-01 00:00:00 UTC (exclusive): 4 mentions; 0 submissions, 4 comments2026-01-01 00:00:00 UTC to 2027-01-01 00:00:00 UTC (exclusive): 1 mentions; 0 submissions, 1 comments. Incomplete calendar period.2026*

* An incomplete calendar period is marked with an outlined bar. Its count is not directly comparable with a full period.

Counts come from the repository’s dated source evidence. Index cutoff: 2026-11-02 08:16:59 UTC.

View mention counts and date ranges
UTC ranges include their start and exclude their end. Select a period to filter the source evidence.
PeriodStart (UTC)End (exclusive, UTC)MentionsSubmissionsComments
20122012-01-01 00:00:00 UTC2013-01-01 00:00:00 UTC303
20132013-01-01 00:00:00 UTC2014-01-01 00:00:00 UTC707
20142014-01-01 00:00:00 UTC2015-01-01 00:00:00 UTC413
20152015-01-01 00:00:00 UTC2016-01-01 00:00:00 UTC707
20162016-01-01 00:00:00 UTC2017-01-01 00:00:00 UTC13013
20172017-01-01 00:00:00 UTC2018-01-01 00:00:00 UTC615
20182018-01-01 00:00:00 UTC2019-01-01 00:00:00 UTC808
20192019-01-01 00:00:00 UTC2020-01-01 00:00:00 UTC716
20202020-01-01 00:00:00 UTC2021-01-01 00:00:00 UTC303
20212021-01-01 00:00:00 UTC2022-01-01 00:00:00 UTC606
20222022-01-01 00:00:00 UTC2023-01-01 00:00:00 UTC505
20232023-01-01 00:00:00 UTC2024-01-01 00:00:00 UTC808
20242024-01-01 00:00:00 UTC2025-01-01 00:00:00 UTC615
20252025-01-01 00:00:00 UTC2026-01-01 00:00:00 UTC404
2026 (partial)2026-01-01 00:00:00 UTC2027-01-01 00:00:00 UTC101

From the project README

An excerpt from the repository, fetched Nov 13, 2026.

Read the project’s introduction
Users and logs provide clues. Sentry provides answers. What's Sentry? Sentry is the debugging platform that helps every developer detect, trace, and fix issues. Code breaks, fix it faster. Official Sentry SDKs Resources Documentation Discussions (Bugs, feature requests, general questions) Discord Contributing Bug Tracker Code Transifex (Translate Sentry!)
Read the full README on GitHub

What Hacker News says

6 sources
This is a great initiative, but one wonders to which degree this is mostly a marketing stunt, white-washing their own "fair source" efforts. Sentry is a multi-billion company, and Open Source pays exactly none of their bills (though it may serve other purposes). This leads to pages such as [1] where they actively steer users away from self-hosting their "open source" (in name only) solution. Much has been said about Sentry's switch to "Fair Source"[2], but for me personally, the ship of "open source in name only" sailed long before that with the ever-increasing complexity of managing your own setup.[3] It’s clear that the priority here has shifted to pushing users toward their hosted, paid plans. Business models beat licenses every time if you want to understand actual intentions. Disclaimer: I am the solo-everything at a competitor, whic
Read the rest
h is in fact _not_ Open Source.[4] [1] https://sentry.io/resources/self-hosted-vs-cloud/ (click on pdf for scary pictures) [2] https://news.ycombinator.com/item?id=41171665 [3] https://github.com/getsentry/sentry/ commit/78bc759d1be4fa6b8ae3e2764e7156e05eb22ab9 [4] https://www.bugsink.com/
In Sentry just gave $750k to open source projects
1) Do you have two separate codebases for free and paid? No. Sentry has one codebase between free and paid. We have a Django monolith plus some services where all our features are implemented: https://github.com/getsentry/sentry https://github.com/getsentry/relay https://github.com/getsentry/snuba https://github.com/getsentry/vroom etc. We have a Docker Compose wrapper in a separate repo: https://github.com/getsentry/self-hosted We have a private repo called getsentry/getsentry that is another Django app that imports the public one and uses Django signals (iirc) to meter usage for billing. That is what we deploy to SaaS. All product features are implemented in the public repos. 3) How about employee access? Employee access is managed through UI, I honestly don't know whether it lives in getsentry/sentry (public) or getsentry/getsentry (pr
Read the rest
ivate). Probably the latter? 2) How do you handle updates to your product? Employees work in public on GitHub. We ship more or less continuously to SaaS. It's possible to deploy approximately continuously on self-hosted as well, though we also bless monthly snapshots for a more relaxed cadence. Does that answer this question?
In Ask HN: Founders who offer free/OS and paid SaaS, how do you manage your code?
Sentry is built on-top of Django. It's a good example of a real-world non-trivial code base that has had to adapt as it grew up and scaled up. I haven't looked at the code in a few years, but I used to run it on-premise and found it fairly approachable and well-written, but with just the sorts of hacks you'd expect to see in a software code base that had evolved over time. https://github.com/getsentry/sentry Here's all the database models: https://github.com/getsentry/sentry/tree/master/src/sentry/m... Here's an example of hacks in the form of massive caching to improve performance: https://github.com/getsentry/sentry/blob/master/src/sentry/d...
In Your database skills are not 'good to have' (2023)

MAKE YOURSELF AT HOME

A few shortcuts

/
Search the collection
?
Open this guide
Esc
Close dialogs and navigation

Your saved repositories and interests stay in this browser.