Skip to content

Best Self-Hosted Error tracking Tools

Error trackers collect the exceptions your apps throw, group repeats into one issue and tell you when something new breaks. The four picks differ in protocol and weight. Bugsink and GlitchTip accept the Sentry SDKs, so only the DSN changes: Bugsink is one container on SQLite by default under the PolyForm Shield licence, and GlitchTip is an MIT Django app that adds uptime checks and basic performance monitoring. Sentry is the full product, with tracing, session replay and profiling, but its self-hosted stack is about 50 containers under the Functional Source License and the catalog gives it a 16 GB RAM floor. Errbit is the old-school option: an MIT Rails app on MongoDB that speaks the Airbrake API and does only error collection. Pick Bugsink for the smallest footprint, GlitchTip for a Sentry-compatible server with more features, Errbit if your apps already use Airbrake notifiers, and Sentry only when you need its depth and have the hardware. Error reports contain stack traces, request data and sometimes user details, so keep the server behind TLS and a login, scrub sensitive fields in the SDK, and back up the database.

We earn commissions when you shop through the links below. Full disclosure →

Error tracking apps

Error tracking

Bugsink

A deliberately small, self-hosted error tracker that speaks the Sentry SDK protocol — one container, SQLite by default, built to run your team's exception stream on a tiny box instead of an event-priced SaaS bill.
PythonDjango
easyRead guide →
Error tracking

Errbit

A self-hosted error catcher that accepts reports from Airbrake-compatible notifiers, groups repeats of the same exception into one problem and tracks them per app and environment. It keeps backtraces, request params and a comment thread per problem, and can open GitHub issues (other trackers such as Jira through plugin gems) and notify Slack, webhooks and email. It is a Rails app on MongoDB, deliberately simpler than Sentry: no performance tracing, replay or profiling.
Ruby on RailsMongoDB
easyRead guide →
Error tracking

GlitchTip

An open-source, Sentry-compatible error tracking server — your apps keep using the official Sentry SDKs, but the exceptions, stack traces, and alerts land on your own lightweight Django instance.
PythonDjangoAngular
moderateRead guide →
Error tracking

Sentry

The full self-hosted edition of Sentry's error tracking and performance monitoring: exceptions, stack traces, releases, alerts, tracing, session replay and profiling, using the same SDKs as the hosted product. The upstream self-hosted repository is a Docker Compose blueprint of about 50 containers (Kafka, ClickHouse, Postgres, Snuba, Relay and more) licensed under the Functional Source License (FSL-1.1-Apache-2.0) — source-available, converting to Apache 2.0 after two years — and it needs 4 CPU cores and 16 GB of RAM at minimum.
PythonDjangoRustClickHousePostgreSQLKafka
hardRead guide →

Head-to-heads in this category

Where to host itaffiliate disclosure
Kamaterafree trial
From $4/mo · 1 vCPU / 1 GB / 20 GB · US + EU + Asia
Start free on Kamatera → (opens in new tab)
DigitalOceanalso works on
From $6/mo · 1 vCPU / 1 GB / 25 GB · US + EU + Asia
Deploy on DigitalOcean → (opens in new tab)

Paid link — we earn a commission if you shop through it.

Replace a paid tool

Common questions

How much RAM do self-hosted apps in Error tracking need?

Across the 4 apps in Error tracking, minimums run from 256 MB (Bugsink) to 16384 MB (Sentry).

Which app in Error tracking uses the least RAM?

Of the 4 apps in Error tracking we measured, Bugsink used the least: 204 MB at idle (first boot, measured Sep 2026).

Do self-hosted apps in Error tracking support Docker?

All 4 apps in Error tracking list Docker support.

Analytics cookies only (Google Analytics, PostHog). No ad networks, no cross-site tracking. See our privacy policy.