GlitchTip is an open source error-tracking platform that speaks Sentry’s API: point any Sentry client SDK at it and exceptions, log messages and Content Security Policy violations stream into an issue list you can triage, assign and resolve. It is a partial fork and mostly a re-implementation of Sentry’s open source codebase from before that project changed licence, written to stay small enough to read and to run on a modest server.
Practically that means a Django application with PostgreSQL behind it, keyword search over issues, release and deploy tracking, and a web UI for projects, teams, alerts and uptime checks. The project quotes 512 MB of RAM for a small installation; Valkey is optional and only bought in when the ingest rate justifies a cache.
is:unresolved, tags, environment and release filters narrow the list without leaving the page.GlitchTip runs either way from the same code: the hosted service at app.glitchtip.com is sold in tiers (a free hobby tier of 1,000 events a month, then paid plans from around $15 a month for 100,000 events), while a self-hosted install is unlimited and free. A self-hosted instance never reports anything back to the project – no telemetry, no phone-home – which is the reason many teams pick it over the commercial error trackers.
Docker images and a compose file cover the whole stack: web, worker, PostgreSQL and an optional Valkey cache, with migration and a one-off superuser step on first start. Behind a reverse proxy the only care is that the ingest endpoint keeps its full request size limits so large event payloads are not rejected.
Open source, MIT licensed – you can run it internally, modify it and even resell it. The hosted subscription buys the managed service and support, not the software.