GlitchTip Hosting

How GlitchTip works

Applications send errors and performance transactions through Sentry-compatible SDKs. GlitchTip groups related failures into issues, records event context, and lets teams review releases, environments, tags, and stack traces. Performance data shows transaction timing, while uptime monitors make scheduled requests or receive heartbeat-style checks to confirm that a service is responding.

Projects sit inside organisations, allowing users and monitoring data to be separated by product or team. Background workers process incoming events and monitoring tasks, while PostgreSQL and Valkey support stored state and queues. Event volume is a central capacity factor because errors, transactions, releases, and uptime checks all create records.

Key GlitchTip features

Error tracking captures exceptions through familiar SDKs and groups repeated occurrences. Performance monitoring follows transactions and spans for supported integrations. Uptime monitoring checks endpoints or expected job signals, while issue comments and project views help teams coordinate investigation.

The platform can also expose log-related features in current releases, but customers should verify the installed image and SDK configuration before relying on a specific data type. Email notification, invitation, and recovery flows are disabled in this catalogue deployment, so the dashboard is the dependable review channel.

GlitchTip vs Sentry

GlitchTip is a self-hosted monitoring application combining errors, performance transactions, uptime checks, and selected project-management functions. Sentry is a broader commercial observability platform that includes errors, traces, logs, profiling, session replay, and provider-operated infrastructure across many language SDKs.

Sentry may suit larger teams that want a wider product portfolio and managed operational support. GlitchTip is more appropriate when Sentry SDK compatibility and self-hosted control matter, and the organisation can operate the event pipeline and accept a narrower feature set.

Who uses GlitchTip

Software teams monitor web applications, APIs, background jobs, and public endpoints. Agencies can separate customer projects, while internal platform teams use uptime checks and error events to understand whether a release introduced a failure.

Monitoring data can contain user identifiers, request details, URLs, or application context. SDK sampling, data scrubbing, retention, access roles, and project ownership should be configured before sending production events.

Self-hosting GlitchTip: requirements and cost

Resource use grows with errors, transaction spans, uptime checks, releases, event payloads, retention, background processing, and concurrent reviewers. PostgreSQL stores organisations, projects, issues, events, users, and configuration, while Valkey supports queued work. PostgreSQL is included but unmanaged, and its memory sits outside the exported application minimum.

AvaHost maps GlitchTip to Plan 4 at €20 after the database adjustment. One-click deployment, a custom monitoring domain, automated HTTPS, automatic application updates, and scheduled backups are included. Application email is disabled, so email alerts, invitations, and password-recovery messages are unavailable; teams should review the dashboard and validate other notification paths independently.