GlitchTip vs. Sentry vs. Bugsink

Bugsink vs. GlitchTip vs. Sentry
Three options for error tracking: Bugsink, GlitchTip, and Sentry.

If you run software in production somewhat seriously, you probably have an Error Tracker in place or are planning to add one. Bugsink, GlitchTip, and Sentry all fill that role and if you’re reading this you’re likely trying to choose between them.

All three do the same basic job: provide a place for your errors to be sent to, group them so you can triage, alert you if something’s wrong, and provide as much useful context to fix them as possible. All three use the same client-side SDKs (the Sentry-SDK), so switching between them is usually just a matter of changing the DSN.

There are also important differences, however. This page highlights the most relevant ones. You’re reading this comparison on the Bugsink website, and it’s written by Bugsink’s founder, so it comes with a bias. Still, I have actual experience with all three solutions, and some of the experience with the competition even informed my decision to start Bugsink in the first place, so I hope this comparison is useful to you.

Origins & Philosophy

Bugsink grew out of my frustration with self-hosting Sentry in 2023. I was working in a context where data absolutely had to remain on-site, needed to track production errors, and found existing self-hosted solutions too painful. At the same time, Sentry had grown from the focused error tracker I remembered into a much broader application-monitoring suite. I was frustrated by the complexity and was cocky enough to think I could make a better version for the core UI. Since then, I have added a managed offering for teams that want the same simplicity without running it themselves. It also provides a European option: the service is supplied by a Dutch company and its application data stays in the EU.

GlitchTip started in 2020 after Sentry replaced its open-source license with a non-open-source one. . Its answer was to preserve a Sentry-compatible tracker under permissive license (MIT). Open source remains central to what it is.

When Sentry was created in 2008 it blew many people’s minds: the ability to just see the full context of a production error, as well as get alerts about them, made it a must-have for many teams. It was also Open Source, and very developer-centric. Since that time, they’ve added support for dozens of languages, and have grown into a full-blown observability tool: tracing, session replay, and profiling are just three examples. They’re not strictly Open Source any more, and are leaning heavily into the agentic age with their own built-in agent called Seer.

The UI of an Error

The error page is where each product’s priorities become most visible. When production breaks, what do you see?

Bugsink: Stacktrace

Chained exception in Bugsink
The complete exception chain in Bugsink, with source context open.

Bugsink puts the stacktrace first. The exception chain is visible in one pass, source context is open, and local variables are available beside the relevant frame.

 

Bugsink: Details & Sparklines

That does not mean Bugsink throws the rest of the event away. It gives that information its own place. The details view contains the environment, release, request data, tags, user, runtime, and the other context sent by the SDK.

Event details in Bugsink
Event context has a separate details view; it does not push the stacktrace down the page.

The issue page also has a 28-day sparkline. It is a small thing, but a useful one: you can see whether an exception arrived with a deployment, occurs every morning, or has quietly gone away.

Issue occurrence sparkline in Bugsink
The sparkline is interactive; a point links to an event from that moment.

 

Bugsink: Tags

Tags are also given their own space. Their distributions can reveal that an issue only affects one browser, release, tenant, or server.

Tag value distributions in Bugsink
Tag values and their share of the issue in Bugsink.

GlitchTip

Here is the same generated exception in GlitchTip. The event data is there, but the page puts runtime metadata and exception mechanics above the trace. Source context and variables are folded into individual frames. There is even a current request for an “expand all” control, which gets at the practical difference rather well.

Chained exception in GlitchTip 4.2.10
The same exception in GlitchTip 4.2.10. This capture is from May 2025.

GlitchTip’s UI is substantially smaller than Sentry’s, and the essentials are all present. However, for the basic act of reading a traceback, it makes you unfold more things than Bugsink does.

Sentry

Sentry has by far the most context. It can connect an error to a trace, a replay, a release, a suspect commit, an owner, and the wider health of the application. If you use those systems together, this is Sentry at its best.

The price of that breadth is a busy issue page. Highlights, graphs, workflow controls, AI features, tabs, and metadata all compete with the exception.

The same exception in Sentry
The same exception in Sentry. There is a great deal here, including quite a lot that is not the stacktrace.

Alerting

For alerts, Bugsink follows the issue lifecycle: a new issue, a regression, or an issue crossing its mute threshold. Email preferences can be set at global, team, and project level. Project alerts can also go straight to Slack, Mattermost, Discord, Microsoft Teams, Telegram, Google Chat, or a custom JSON webhook. These integrations are included on the free hosted plan; the alerting guide has the details.

GlitchTip has per-project frequency rules for errors and uptime changes. Recipients can be team email addresses or webhooks.

Sentry goes much further into ownership, escalation, metric alerts, anomaly detection, and third-party workflow integrations: useful for a larger incident-management setup, but more to configure. Also: the free plan does not include webhooks, so you have to pay to get alerts into Slack, Teams, or Discord.

Bugsink search handles free text and structured key:value terms across issues and events. That includes exception type, message, environment, release, arbitrary tags, and request URLs. The syntax is deliberately small and is documented with examples.

GlitchTip uses PostgreSQL full-text search and structured filters such as tag:value. Its search is capable enough for normal error-tracking work, although the syntax is spread between the interface, release notes, and issue tracker rather than one complete search reference.

Sentry has the deepest search and reporting model of the three. It is especially strong when queries cross errors, traces, releases, and other Sentry data. Naturally, that also gives it the largest query language to learn.

SDKs, source maps, and native crashes

All three use the Sentry SDK ecosystem, so Python, JavaScript, Java, PHP, Ruby, Go, .NET, mobile, and many other platforms can report errors without a Bugsink- or GlitchTip-specific SDK.

Bugsink supports debug-ID source-map uploads through sentry-cli. Its native support has also moved beyond merely accepting a JSON event: Bugsink can ingest minidumps, accept debug-information files, and symbolicate native frames. That path became production-ready in Bugsink 2.6.2, although self-hosted installations still have to enable it. The complete Linux and Crashpad path is tested; other platforms and framework SDKs should still be verified against the exact build pipeline.

GlitchTip 6 supports source maps, minidump ingestion, and native debug symbols too, including dSYM, PDB, and ELF uploads through its CLI. Sentry remains the most mature choice for a large or unusual native-crash pipeline.

APM and observability

GlitchTip has transaction and span views, uptime monitors, structured logs, release tracking, and an optional MCP server. GlitchTip 6.2 added spans to transaction details and OpenTelemetry log ingestion. It is becoming a small observability suite, not just an error tracker.

Sentry is the much larger version of that idea: tracing, replay, logs, profiling, application metrics, dashboards, uptime and cron monitoring, release health, and Seer. Its cross-linking between those features is a genuine advantage.

Bugsink is an error tracker. It does not collect traces, replays, performance transactions, or uptime checks. I would rather keep making the error-tracking path faster, clearer, and easier to operate than to add more and more APM features.

European data sovereignty

For European customers, when using the managed service, keeping the data under European sovereignty is often a requirement or a strong preference. All three services offer a way to do that to some extent, but the practical and legal differences may matter more than the label “European data region”.

Bugsink takes the European data-sovereignty requirement seriously. The EU-hosted service is supplied by a Dutch company, and the application and email providers are in Europe. Because Bugsink itself is a European company, the EU-hosted service is not just a data region: it is a European supplier.

GlitchTip’s EU instance stores data in Frankfurt but is supplied by Burke Software LLC in the US. Sentry offers an EU data region while remaining a US company.

Question Bugsink GlitchTip Sentry
EU-hosted service Yes Yes, Germany Yes, EU region
European supplier Yes, Netherlands No, United States No, United States
Self-host in the EU Yes Yes Yes

More details about how Bugsink shines here are in the article describing Bugsink as a serious Sentry EU Alternative.

Hosted pricing

At comparable paid error volumes, Sentry is the most expensive of the three at every level shown below. Whether that is worth it depends on how much of Sentry’s wider observability suite you actually use. Note, however, that the prices below are for error tracking only. In other words: if you want the broader Sentry features that justifies the higher price, you will pay more than the numbers below.

Published monthly US prices in September 2026:

Monthly errors Bugsink GlitchTip Sentry Team
Free 15K accepted
5K retained, 1 user
1K
unlimited users
5K
1 user
Around 100K 75K for $16 100K for $15 100K for about $44
Around 500K 600K for $50 500K for $50 500K for about $132
3 million $158 $250 about $600

The Sentry estimates use its $26 annual-billing Team base, including 50K errors, followed by its published pay-as-you-go error rates. Monthly billing costs more. Bugsink and GlitchTip prices are their normal monthly prices.

These allowances are not identical products in three boxes. GlitchTip’s quota is shared by error occurrences, uptime checks, performance transactions, and release-file megabytes. It gradually throttles above the allowance and blocks at twice the quota. Bugsink’s allowance is only for errors, and its retention model can accept more occurrences than it stores in full. Sentry meters its different products separately.

Self-hosting: ease of operation

With Self-hosting being the original reason for Bugsink’s existence, it’s no surprise that Bugsink is the clear winner: one application, that can run as one container with SQLite, or use PostgreSQL/MySQL when that better fits your setup. There is no Redis service or separate queue to operate. The installation page gets you running and the upgrade guide covers the equally short update path.

GlitchTip requires PostgreSQL 14+ and one application service. The web and worker roles can be split when scaling; Valkey/Redis is now optional rather than mandatory. Its own installation guide recommends 512MB of RAM and enables a smaller all-in-one setup. That is a sensible, compact deployment—just not quite as self-contained as Bugsink.

GlitchTip also has more storage machinery because it stores more kinds of data. PostgreSQL is the hot store, while optional DuckDB/Parquet cold storage can move older data to a filesystem or S3-compatible storage. That is useful if you want searchable historical logs and transactions. It is also another system to understand.

Full self-hosted Sentry remains a distributed stack involving PostgreSQL, Kafka, Redis, ClickHouse, Snuba, Symbolicator, Relay, and more. Sentry’s own repository describes it as intended for “low-volume deployments and proofs-of-concept”. I tried running it anyway; the longer version of why I stopped is here.

Self-hosting: Scale

Bugsink has a deliberately boring scale story. A benchmark on a 2-vCPU, 4GB, €5/month VPS sustained 1.5 million events per day. There is no external ingestion queue in that setup. Smart retention keeps complete events while volume is normal, then keeps representative samples while preserving issue counts and grouping when traffic spikes. A noisy exception should not be allowed to fill the disk while everyone is asleep.

GlitchTip gives a rough planning figure of 30GB of disk for one million events per month, exposes retention controls, and documents cold storage. Valkey and split workers are available for larger installations. What it does not publish is an equivalent small-machine throughput benchmark, so a prospective operator still has to establish the limits for their own mix of errors, traces, and logs.

Sentry SaaS operates at an entirely different scale. Self-hosted Sentry can also process serious volume, but then the Kafka/ClickHouse-style operational model is part of the deal. That can be appropriate for an observability team; it is not what I want to maintain in order to collect exceptions.

Self-hosting: License

Bugsink uses the Polyform Shield License. You can run it, inspect it, modify it, and contribute to it; the license restricts using it to provide a competing product or service.

GlitchTip is MIT licensed. If an OSI-approved permissive license is a hard requirement, this is the uncomplicated choice.

Sentry uses the Functional Source License for its self-hosted source. Basically: don’t use it to run a competing service, but the licence converts to Apache 2.0 after 2 years. Sentry’s hosted service and its agentic tools are proprietary.

Which one would I choose?

I built Bugsink, so I’m obviously biased. I have also run GlitchTip in production, filed issues against it, and contributed code. That is to say: it’s not like I didn’t try the alternatives.

Choose Bugsink for the best Error Tracking experience. The error is easier to read, the hosted plans remain economical as volume grows, and the self-hosted version is a small application rather than an infrastructure project. It keeps the parts I valued in the older Sentry experience and resists turning them into one tab in a much larger product.

There are two clear exceptions. If you need an OSI-approved permissive license, choose GlitchTip. If what you actually want is the full APM package (traces, replays, profiling, dashboards, and the connections between them) hosted Sentry is the most complete choice.

Stop reading and Sign up for free; you’ll know more in one minute and a DSN-change than all the reading in the world