GlitchTip

devopsdeveloper tools

Self-hosted error tracking compatible with the Sentry SDK. Collect and group application errors with stack traces, release tracking, and uptime monitoring without Sentry's pricing

#error-tracking#monitoring#devops#sentry#self-hosted
Alternative to SentryRollbarBugsnag

Quick Start

docker run -d -p 8000:8000 -e SECRET_KEY=yoursecretkey -e DATABASE_URL=postgresql://postgres:postgres@db/postgres glitchtip/glitchtip:latest

Overview

GlitchTip is a self-hosted error tracking tool that is compatible with the Sentry SDK. If your application already sends errors to Sentry, you can point it at a GlitchTip instance instead by changing the DSN endpoint URL — nothing else in your code needs to change. Errors arrive, get grouped by type and stack trace, and appear in the GlitchTip dashboard the same way they would in Sentry.

The value proposition is straightforward. Sentry’s cloud pricing scales with event volume, which becomes meaningful for busy production applications. GlitchTip runs on your own server, stores as many events as your disk allows, and has no per-event cost. For applications generating hundreds of thousands of errors per month, the difference in cost is significant.

Error grouping and stack traces work as expected. GlitchTip clusters related errors together, shows the stack trace, logs the affected release version, and tracks how many times each error has occurred. Source maps for minified JavaScript are supported. The uptime monitoring feature adds basic HTTP endpoint checks alongside error collection, which consolidates two operational concerns in one tool.

The feature scope is more limited than Sentry. Performance monitoring, distributed tracing, session replay, and profiling are not available. GlitchTip is focused on error collection and grouping — the core use case — rather than the broader observability platform Sentry has grown into. For teams who use Sentry primarily for errors and not for performance data, that scope is sufficient.

Development is hosted on GitLab rather than GitHub, which means the star count does not reflect the project’s actual usage. It is a production-quality tool used by teams who need a Sentry alternative with no pricing ceiling.

GlitchTip: Pros & Cons

Pros (The Wins)Cons (The Friction)
Sentry SDK compatible:
Swap the DSN URL; no
application code changes needed.
Limited feature set:
No performance monitoring,
profiling, or session replay.
No event pricing:
Store errors up to your
disk capacity, no per-event cost.
Smaller community:
GitLab-hosted; slower development
pace than Sentry.
Uptime monitoring:
HTTP endpoint checks included
alongside error tracking.
Multi-container install:
Postgres and Redis required
alongside the web server.
MIT licence:
Simple, focused on errors;
no growing feature complexity.
SDK feature gaps:
Some Sentry SDK transaction
features not fully implemented.

Use Cases

Specific ways to use GlitchTip for your workflow.

01
Collect and group application errors from production without paying Sentry's per-event pricing
02
Track JavaScript, Python, Go, and other language errors with full stack traces in a self-hosted dashboard
03
Monitor application error rates across releases to catch regressions after deployments
04
Use existing Sentry SDK integrations without changing application code — swap the DSN endpoint only

Deployment Strategy

Recommended ways to host GlitchTip in your own environment.

docker
self-hosted