BugFuse

Lightweight, open source, self-hosted error tracking. Works with the Sentry SDKs you already use and runs on a single Postgres database. No Kafka, no ClickHouse, no fleet of containers to babysit.

Website · Docs · Installation

Important

BugFuse is in active development and hasn't reached 1.0 yet. It works, but expect rough edges and breaking changes between updates. Back up your Postgres data before upgrading.

Quick start

git clone https://github.com/hemantapkh/Bugfuse
cd Bugfuse
docker compose up -d
# → open http://localhost:3000

Postgres is the only required dependency. Redis (cache), SMTP (email), and S3 (artifact storage) are optional. See the installation docs and configuration reference.

Features

• Sentry SDK compatible: envelope and store protocols; point any Sentry SDK at a BugFuse DSN
• Issue grouping: events fingerprinted into issues, with regression detection and affected-user counts
• Search: Sentry-style query language (is:unresolved level:error payment) with 25+ filter keys, operators, and negation
• Alerting automations: occurrence, threshold, frequency, and spike conditions; delivery via Slack, Discord, Telegram, email, webhooks, or any of the 100+ services Apprise supports
• Source maps: sentry-cli chunk upload, JavaScript symbolication, local or S3 storage
• Teams: organizations with owner/admin/member roles, email invites, saved views, issue assignment and comments, API tokens

Roadmap / TODO

• Durable background task queue (ingestion currently runs in-process)
• Data retention policies (events are currently kept indefinitely)
• Release management UI (releases are tracked; management screens are missing)
• More automation actions beyond notifications
• Per-project ingestion quotas
• Event volume / issue stats dashboards
• Alert digests and scheduled reports

Not planned right now: performance tracing, session replay, and profiling. BugFuse stays focused on lightweight error tracking.

License

Copyright (C) 2026 Hemanta Pokharel

BugFuse is open source, licensed under the GNU AGPL-3.0. Contributions are accepted under the terms described in CONTRIBUTING.md.