GlitchTip is an open source error tracking and performance monitoring platform you can self-host — a Sentry alternative that speaks the same SDK protocol, so you point an app at it by changing one DSN.

What is GlitchTip?

GlitchTip is an open source error tracking platform that collects exceptions, stack traces, and crash reports from your applications in real time so you can triage and fix them in one place. It’s compatible with Sentry’s open source SDKs, so existing Sentry clients send data to a GlitchTip instance unchanged — you just swap the DSN.

What is GlitchTip best for?

Teams that want Sentry-style error tracking without the per-event bill or Sentry’s heavy self-hosted stack. It’s a strong fit for small-to-midsize projects and self-hosters who need to catch errors, get alerted, and read stack traces on modest hardware. If your only need is uptime checks, a dedicated tool like Uptime Kuma is simpler — GlitchTip earns its place when application errors and performance matter too.

What can GlitchTip do?

Capture errors, exceptions, log messages, and Content Security Policy violations with full stack traces
Monitor performance — surface slow web requests, database calls, and other transactions
Run uptime monitoring that pings sites or receives heartbeat checks and alerts on downtime
Search and filter application logs alongside error and performance data
Accept data from any Sentry SDK by changing the DSN — no code changes
Alert your team by email and webhooks, with unlimited projects and members
Self-host with Docker Compose or a Helm chart, or use the managed cloud

Where does GlitchTip fall short?

It intentionally covers the core of Sentry, not all of it — no session replay, no full distributed tracing, and lighter release-management tooling. Independent reviewers put it at roughly 80% of Sentry’s feature set.
Fewer built-in integrations and a smaller community than Sentry, so expect fewer prebuilt connectors and third-party guides.
Its performance monitoring is basic next to Sentry’s deep tracing — good for spotting slow endpoints, not a replacement for full APM-style distributed traces.

Is GlitchTip free?

Yes — GlitchTip is free and MIT-licensed to self-host, so you only pay for the server it runs on. The managed cloud at app.glitchtip.com adds a free tier (1,000 events/month, unlimited projects and members) and paid plans from $15/month for 100k events up to $250/month for 3 million events.

What does GlitchTip replace?

GlitchTip is a self-hosted Sentry alternative. It does the same core job — catching errors, alerting you, and showing stack traces — while using a fraction of the infrastructure. Self-hosted Sentry pulls in Kafka, ClickHouse, Snuba, and a stack of workers; GlitchTip runs on Postgres plus an optional cache, and its SDK compatibility means migrating is often just a DSN change.

FAQ

Is GlitchTip open source? Yes — the code is on GitLab under the MIT license, one of the most permissive OSI-approved licenses. You’re free to self-host, modify, and run it without restriction.

Can I self-host GlitchTip for free? Yes. Self-hosting is free; you only pay for your own server. A small instance runs on about 512 MB of RAM with PostgreSQL, using far fewer resources than self-hosted Sentry.

Is GlitchTip a good Sentry alternative? For most teams, yes — it captures errors, alerts you, and shows stack traces while using far less infrastructure than self-hosted Sentry. If you need session replay or full distributed tracing, Sentry still leads.

What do I need to run GlitchTip? Docker, PostgreSQL 14+, and roughly 512 MB of RAM for a small instance. Valkey or Redis 7+ is recommended for performance, and you should plan disk around 30 GB per million events per month.