Bugsink is an error tracker you run on your own server: it shows you when your code fails in production and why, with full stacktraces, local variables and request context. It is built to be dropped into a project in minutes, and it speaks the Sentry wire protocol, so any Sentry SDK can send events to it without changing your application code.
You create a team and a project, connect your application with the project DSN, and exceptions start arriving. Bugsink groups them into issues, counts every occurrence, and keeps the “last seen” timestamps so you can tell a brand-new bug from a long-standing one. Each issue opens on a stacktrace with the surrounding source lines, the request that triggered it, breadcrumbs before the failure, tags, and the full event list for that group.
The self-hosted install is one Docker container. Bring it up with a secret key and a superuser, then create your first project and copy its DSN:
docker run -d -e SECRET_KEY=<50+ random chars> -e CREATE_SUPERUSER=you@example.com:password -e PORT=8000 -p 8000:8000 bugsink/bugsink
Bugsink is a stand-alone error tracker rather than a suite: it deliberately covers exception monitoring only, so there are no performance traces, session replays or uptime checks bundled in.
Not open source. Bugsink is released under the PolyForm Shield License 1.0.0: the source code is public and you may self-host it, but the licence does not permit using it to compete with Bugsink. The ee/ directory and Sentry-derived parts carry their own licences. Bugsink B.V. also sells a hosted service at bugsink.com, so the licence is what funds the project rather than an OSI-approved grant.