Open Source Rollbar Alternatives
A curated collection of the 2 best open source alternatives to Rollbar.
The best open source alternative to Rollbar is Sentry. If that doesn't suit you, we've compiled a ranked list of other open source Rollbar alternatives to help you find a suitable replacement. Other interesting open source alternative to Rollbar is Bugsink.
Rollbar alternatives are mainly Monitoring & Observability. Browse these if you want a narrower list of alternatives or looking for a specific functionality of Rollbar.
Debugging platform that helps developers detect, trace and fix issues in shipped code, with official SDKs for most languages and runtimes.
Users and logs provide clues, Sentry provides answers. The platform helps every developer detect, trace and fix issues in code that is already running, turning a vague report that something broke into the specific request and line that caused it.
Instrumentation happens through official SDKs, and the breadth of that list is the part that matters most when picking an error tracker. The project maintains more than twenty of them, each in its own repository with its own release cycle, so a polyglot estate reports into a single place.
The official SDKs span most environments where application code runs.
- Web and JavaScript: JavaScript, Electron and React Native reach browser, desktop and cross-platform mobile apps.
- Backend languages: Python, Ruby, PHP with a Laravel package, Go, Rust, Java and Kotlin, Elixir and Clojure.
- Apple and Microsoft stacks: Objective-C and Swift, C sharp and F sharp, plus PowerShell for scripting environments.
- Systems and cross-platform: a native C and C++ SDK alongside Dart and Flutter, and a Perl client.
- Game engines: Unity, Unreal Engine and Godot Engine each get a dedicated SDK.
Documentation, a bug tracker and GitHub discussions handle bugs, feature requests and general questions, while a Discord server hosts the wider community. The interface is translated through a public Transifex project anyone can join, and contributing guidelines for the platform itself live in the docs.
Self-hosted error tracking for teams already using Sentry SDKs, keeping stack traces, local variables, and user data on your own hardware.
Error reports carry the same sensitive material as the application that produced them: user identifiers, email addresses, session tokens, whatever was in scope when the exception fired. Scrubbing all of that before shipping it to a third party is never finished work, and a missed field stays undetectable until it leaks. Bugsink keeps error tracking on hardware you control instead.
Your application reports through an SDK and Bugsink is the server that receives, groups, and displays what arrives. It is compatible with Sentry's open source SDKs, so connecting an existing project means changing a DSN rather than rewriting instrumentation. Evaluating it takes one docker run, after which the interface answers on port 8000.
The interface is arranged around the moment you actually need it, when something has broken in production.
- Stacktrace first: the full call stack sits at the top of the page rather than behind an expander.
- Local variables: the values held at the time of the error are shown alongside the code.
- Frame separation: in-app frames are distinguished from library frames so attention lands in the right place.
- Alerts: notifications fire on new issues, regressions, and issues whose mute period has expired.
- Smart retention: events are sampled by issue volume and age, so disks fill slowly instead of hitting a quota.
Published figures put throughput at 18 events per second on a two-core virtual machine with 4GB of memory, and the stress test scripts ship with the code so you can check that yourself. MySQL and PostgreSQL are both supported.
