// the find
getsentry/sentry
Developer-first error tracking and performance monitoring
Sentry is the self-hostable version of the commercial error tracking and APM platform most developers already pay for. It's a Django monolith backed by Postgres, Redis, Kafka, Clickhouse, and Snuba — a substantial piece of infrastructure. You'd run this if you want Sentry's feature set without the per-event pricing.
The SDK coverage is genuinely impressive — every mainstream language and framework has a first-party SDK maintained by the same team, so you're not stitching together community ports. The trace and span model is well-thought-out: distributed tracing, session replays, and profiling all feed into a unified issue timeline rather than being bolted-on tabs. The codebase has a mature internal agent/skill system (`.agents/skills/`) for codegen and bug-fixing workflows, which signals serious investment in developer tooling. Fair Source licensing means you can read and audit the production code you're actually running.
Self-hosting this is a real commitment: the dev stack requires Kafka, Clickhouse, Snuba, Relay, Redis, and Postgres all running together — the `devservices/config.yml` alone orchestrates multiple containers just for local work. Clickhouse in particular is operationally heavy and most teams underestimate it until something goes wrong at 2am. The Python Django backend is a large surface area to keep patched and upgraded, and Sentry's own migration cadence is aggressive — falling behind means painful catch-up migrations. There's also a soft ceiling: the self-hosted version lags the cloud product on features (Seer AI, some newer insights views), so you get the infrastructure burden without always getting the latest product work.