Bugsink

Bugsink is a lightweight, self-hosted error tracking service for applications.

  • Other
  • Productivity
  • Tools & Utilities
Bugsink is a lightweight, self-hosted error tracking service for applications. It captures runtime errors, groups related events, records stack traces and context, and sends alerts. It is for developers and small teams who want a privacy-friendly alternative to cloud error tracking products.

Platform availability

Available on 1 of 9 platforms

  • Unraid
  • TrueNAS (not listed)
  • Umbrel (not listed)
  • ZimaOS (not listed)
  • Proxmox (not listed)
  • Helm (not listed)
  • Mac (not listed)
  • Windows (not listed)
  • Linux (not listed)

Health score?A 0-100 score computed nightly from four factors: maintained (40%: recent commits and steady activity), popular (25%: GitHub stars, log scale), easy to install (20%: platforms, install notes, setup guides, Docker image) and light to run (15%: minimum RAM, ARM support). When the source code has been checked, a fifth factor, security check (20%: automated scan for committed secrets, unsafe desktop-app settings, known-vulnerable dependencies and project hygiene; any serious finding caps it at 20), is added. Factors without data are left out and the rest are rescaled.

75/100 Good

Maintained
100last commit 18 days ago
Popular
662,104 GitHub stars
Easy to install
351 install platform, install notes, Docker image
Light to run
No data

Based on 3 of 4 factors.

Availability: platform listings confirmed today, links checked 15 days ago

GitHub stars
2,104
Open issues
132
Last commit
2026-09-25
Latest release
2.6.1
Activity
declining

Checked 12 days ago - source: GitHub (bugsink/bugsink)

Resources & Compatibility

ARM (e.g. Raspberry Pi) is supported.

Checked 15 days ago - source: Docker Hub image tags and published docs

First-install notes

  • Start Bugsink in Docker with a real secret Run the Docker command, but replace SECRET_KEY with a long random string of at least 50 characters and replace CREATE_SUPERUSER with your own admin email and password. If you skip the secret, the admin account, or the -p 8000:8000 mapping, you may get a server you cannot log into or open in a browser on port 8000 (a network door). source
  • Give your app the Bugsink DSN Copy the DSN from your Bugsink project into your app's Sentry error-tracking SDK settings when it starts; the DSN is the address and key that tells your app where to send errors. If it is missing or wrong, your app can still run, but Bugsink will not see the error reports. source
  • Send one test error on purpose After wiring up the SDK, deliberately throw or capture a simple test error from real app code, not just the browser console. If that error appears in Bugsink, your setup works; if it does not, check the DSN, SDK, or port configuration. source

Fetched 15 days ago - each note links to its source

Alternatives (5)

  • Datadog - Datadog Agent is an on-host monitoring agent that collects metrics, logs, and traces from hosts, containers, and Kubernetes clusters and se…
  • GlitchTip - GlitchTip is an open-source error tracking and monitoring platform that collects and organizes application errors so you can find and fix b…
  • Honeybadger - Honeybadger is an application health monitoring tool built by developers for developers.
  • Rollbar - Rollbar collects errors that happen in your application, notifies you, and analyzes them so you can debug and fix them.
  • Sentry - Monitors applications for real-time errors, sending alerts via email, SMS, or chat, showing detailed diagnostic information and release imp…

Checked 12 days ago - source: AlternativeTo

Common questions

What Docker settings do I need to start Bugsink and access the admin login?

Set a SECRET_KEY that is a long random string of at least 50 characters and set CREATE_SUPERUSER with your admin email and password. Also map port 8000 from the container to the host, because skipping it can make the server unreachable in a browser.

Can I point an existing Sentry SDK at Bugsink?

Yes, copy the Bugsink project DSN into the Sentry error-tracking SDK settings so the SDK knows where to send errors. If the DSN is missing or wrong, the application can still run, but Bugsink will not receive the error reports.

How can I confirm that error reports are reaching Bugsink?

Send one deliberate test error from real application code rather than only the browser console. If that error appears in Bugsink, the setup works; if it does not, check the DSN, SDK, or port configuration.

What personal API token features are available in recent Bugsink updates?

Bugsink 2.6.0 added personal API tokens with selectable capabilities.

Answers sourced from forum.cloudron.io, github.com, github.com, github.com

Community

Collected 9 days ago - public community threads