BugSnag
Rest of world Report an errorPanel rating · 6 judges · How to read the stars
Category median
Sovereignty: 1 of 6 dimensions proven
0–5 in half steps. 5 means the rubric's top anchor is met on the evidence.
by SmartBear Software Inc. · www.bugsnag.com
Compare with Raygun → Report an error on this page Is this your product? →
Link to this page
Add ?theme=dark to the image address for dark backgrounds.
The badge shows the category and the month of the latest evaluation, and EU-Made where
that is the product’s provenance. It never shows a score.
BugSnag at a glance
- Vendor
- SmartBear Software Inc.
- Headquarters
- Not stated on the vendor’s pages as of 6 Nov 2026
- Data hosting
- Not stated on the vendor’s pages as of 6 Nov 2026
- Free plan
- Yes, per the vendor’s own page source, captured 6 Nov 2026
- Panel verdict
- The AI panel rates BugSnag 3/5, the mean of 6 judges. BugSnag is SmartBear's error tracking and performance monitoring product, and the bench rates its capabilities closely: error tracking, performance tracing, workflow and integrations, data controls and security and reliability each score between 6 and 7. how scores are made
- As of
- Vendor pages captured 6 Nov 2026; evaluated by the panel 6 Nov 2026. all sources
Read this page as one judge. Each weighs the same scores by what they care about.
The panel's verdict
BugSnag is SmartBear's error tracking and performance monitoring product, and the bench rates its capabilities closely: error tracking, performance tracing, workflow and integrations, data controls and security and reliability each score between 6 and 7. The judges praise versioned SDKs across mobile and backend platforms, OpenTelemetry-based tracing whose sampling and quota behaviour is documented in unusual detail, a two-way Jira sync, retroactive server-side redaction, and an overage policy that saves events beyond quota at no additional cost. Sovereignty is the clear weakness at 3 to 4: the contracting entity is SmartBear Software Inc. of Somerville, Massachusetts, the privacy policy states personal information is processed in the US and overseas under standard contractual clauses, and we found no public information on an EU data region or a subprocessor list. Pricing transparency spans 4 to 6: Free at $0/month with 7.5K events, 1M spans and 7-day retention is public, as are Select starting at $20/month and Preferred starting at $33/month, but the volumes those prices cover and paid-plan retention are not stated, and the captured pages give different cancellation terms.
Speaks for it
- Versioned error and performance SDKs are documented for Android, iOS, Flutter, React Native, Expo, Unity and Web plus Node, Java,.NET, Python, Go and Ruby, with symbol and mapping uploads for full stack traces.
- Tracing is built on OpenTelemetry with head- and tail-based sampling, selectable percentiles from P50 to P99, web vitals, and one-click navigation from an error to its trace.
- Events beyond the daily quota are saved at no additional cost, with an automatic upgrade only after more than three daily overages in a 30-day rolling period or rate limiting instead.
- Retroactive server-side redaction works via dot-notation rules over user, request, device, breadcrumb and metadata roots, creatable from a live event, though it is gated to the Enterprise plan and capped at 10 rules per project.
- A two-way Jira sync marks errors fixed when the linked issue closes, and notifications reach Slack, Microsoft Teams and email digests with alerts routable to code owners.
Held against it
- Sovereignty scores sit at 3 to 4, with a US contracting entity and no public information on an EU data region or a subprocessor list.
- Select and Preferred publish only starting-at prices ($20 and $33 per month) without the event or span volumes they cover, so a real annual cost cannot be computed.
- Retention is stated only for the Free tier at 7 days, and we found no public information on paid-plan retention.
- The captured pages give different cancellation terms — cancel anytime on the pricing page versus auto-renewal at then-current prices unless 60 days' notice in the terms.
- We found no public information on PagerDuty or Opsgenie routing, audit logs, a published SLA with credits, or the model behind the AI fix suggestions.
Best for
- You ship mobile or web apps across many platforms and want one monitored pipeline with versioned SDKs and per-release stability scores.
- Your services already emit OpenTelemetry and you want error-to-trace correlation with clearly documented sampling and quota behaviour.
- You want predictable spend, with over-quota events saved at no additional cost and spans beyond the vendor's prediction not charged.
- You can commit to the Enterprise plan and need retroactive redaction of sensitive fields in error payloads.
Avoid if
- Your buyers require data-residency commitments for error data — the pages state personal information is processed in the US and overseas under standard contractual clauses, and we found no public information on an EU data region or a subprocessor list.
- Your on-call rota pages through PagerDuty or Opsgenie — the documented notification services are Slack, Microsoft Teams, email, Campfire, Datadog, Pushed and Twilio.
- You must budget an exact annual figure before signing — the paid plans publish starting-at prices only and Enterprise is contact sales.
- You need server-side redaction without the Enterprise plan — Sensitive Data Management is available on Enterprise and capped at 10 rules per project.
The scores
| Criterion | Panel median |
|---|---|
| Error capture, grouping & triage | 3.5 of 5 |
| APM, tracing & profiling | 3.5 of 5 |
| Alerting, integrations & developer workflow | 3 of 5 |
| Data scrubbing, retention & volume control | 3.5 of 5 |
| Access control, security & the vendor's reliability | 3.5 of 5 |
| European sovereignty | 2 of 5 |
| Pricing transparency | 3 of 5 |
Error capture, grouping & triage
Show reasoningHide reasoning
How this is scored
What happens to an exception or crash: SDKs for the languages, frameworks and platforms a team runs (PHP and Laravel, JavaScript in the browser and Node, Python, Ruby, Java, .NET, Go, iOS, Android, Flutter, React Native), stack traces with source maps and symbolication, context (request, user, breadcrumbs, environment, local variables), grouping and custom fingerprints, deduplication, issue states (resolved, ignored, regressed), releases and deploy tracking, suspect commits, crash-free sessions and users for mobile apps, and search and filters over issues.
0 — Catches no application errors or crashes; a log viewer or an external check only.
3 — Errors from one or two platforms arrive with a stack trace and are grouped; context, issue states, releases and source maps are basic or not described.
5 — SDKs for the common web and backend platforms, stack traces with source maps, request and user context and breadcrumbs, automatic grouping with issue states and regression detection, release and deploy tracking, and issue search and filters.
8 — SDKs across backend, frontend and mobile with symbolication documented, custom fingerprinting and merge or split of issues, suspect commits or code owners, crash-free users and sessions, local variables or source context per frame, and every SDK documented with its configuration options.
10 — Error tracking a large engineering organisation standardises on: every platform it runs covered with parity stated, grouping rules editable and explained, release health with adoption and regression per version, and the full issue lifecycle reachable by API.
The Agency Tech Lead
The captured docs cover our whole stack and more: handled exceptions in PHP/Laravel, the JavaScript notifier, Node, Java,.NET, Python, Go and Ruby, plus Android, iOS, Flutter, React Native, Expo and Unity with named SDK versions; symbol and mapping uploads produce full stacktraces, breadcrumbs and custom metadata come standard, errors are marked fixed or snoozed and automatically reopened, and builds and deploys arrive via the Build API with stability scores per release. We found no public information on custom fingerprinting, merge or split of issues, suspect commits, or local variables per stack frame. 1 2 5 6 13 14 16 17
The SaaS CTO
The SDKs are documented with versions for almost exactly my stack — Go, Python, Node, Java,.NET and Ruby on the backend, Web, iOS, Android, Flutter and React Native on the client — with a symbol and mapping upload API for full stack traces, breadcrumbs and custom metadata, issue states that automatically reopen on regression, release tracking via a Build API, and an inbox that ranks by severity and user impact. What keeps it off the top tier for me: I found no public information on custom fingerprints or merging issues, suspect commits tied to releases, or per-frame local variables. 1 2 6 13 14 16 17
The Mobile Team Lead
Native SDKs for Android, iOS, Flutter and React Native are documented down to version numbers, symbol and mapping files are reported through the build API to show full stacktraces, and the pre-configured dashboards show breadcrumbs, stack traces, affected devices and impacted users — most of what I want before stopping a bad store rollout. Stability scores from session tracking and the Stability center compare the quality of one release to the next, and a fixed error reopens automatically when it recurs. We found no public information on custom fingerprints, merging or splitting issues, or local variables per frame. 1 2 5 6 16 17
The Site Reliability Engineer
Error SDKs are versioned and documented across Android, iOS, Flutter, React Native, Expo, Unity and web, with notifier guides for JavaScript and PHP/Laravel handled errors, symbol and mapping file uploads for full stack traces, and breadcrumbs, user and request context evidenced through the redaction field roots. Triage runs on fixed, snoozed and automatically reopened states with release and stability scoring and saved filters. We found no public information on custom fingerprinting or merge and split of issues, suspect commits, or crash-free sessions and users as a stated metric. 2 5 6 13 16 17 19
The Data Protection Officer
Stack traces with source maps and symbol uploads, breadcrumbs, custom metadata, request and user fields, and an inbox prioritised by severity and user impact are documented, with named SDKs for Android, iOS, Flutter, React Native, Expo, Unity and JavaScript plus PHP/Laravel guides and snippets for Node, Java,.NET, Python, Go and Ruby. Issue states with automatic reopening, release and deploy reporting, and filtered views with bookmarks are also documented. I found no public information on custom fingerprinting, merge or split of issues, suspect commits, per-frame local variables or crash-free session and user counts. 1 2 5 6 13 14 16 17
The Skeptic
Versioned SDKs are documented across mobile, desktop, web and backend (Android, iOS, Flutter, React Native, Unity, Expo, Web, plus Node, Java,.NET, Python, Go, Ruby, PHP), with symbol and mapping uploads for full stacktraces, breadcrumbs, and request, user and device context visible in the redaction paths. Issue states exist with automatic reopening when a fixed error recurs, releases are tracked via the Build API, and sessions feed release stability scores. We found no public information on custom fingerprinting, merging or splitting issues, suspect commits, or local-variable context per stack frame. 1 5 6 16 17 19
APM, tracing & profiling
Show reasoningHide reasoning
How this is scored
How the product shows where time goes: transaction and endpoint timings with percentiles, slow database queries and N+1 detection, background jobs and queues, external HTTP calls, distributed tracing across services, OpenTelemetry ingestion, code-level profiling, frontend performance and Core Web Vitals (real user monitoring), host or container metrics beside the traces, anomaly detection on throughput and latency, and the link from a slow trace to the error it caused.
0 — No performance data of any kind; errors only.
3 — Response times per endpoint or a simple performance view; tracing across services, query analysis and profiling are basic or not described.
5 — Transaction timings with percentiles per endpoint, slow query and N+1 detection, background job monitoring, distributed tracing across services, a link between traces and errors, and frontend performance or Web Vitals offered.
8 — OpenTelemetry ingestion documented, code-level or continuous profiling, real user monitoring with Web Vitals, host and container metrics beside the traces, anomaly detection on latency and throughput, and sampling of traces configurable with its effect explained.
10 — Full application performance management evidenced: traces, profiles, frontend and backend joined end to end, service maps, SLOs on endpoints, and every signal documented with its retention and sampling per plan.
The Agency Tech Lead
Tracing is built on OpenTelemetry with OTLP ingestion over gRPC or HTTP, sampling documented in real depth (head-based in the SDK, tail-based via a collector, parent-based recommended for complete traces), selectable percentiles from P50 to P99, web vitals on real users at P75 by default, CPU and memory system metrics, and a one-click jump from an error to its trace. We found no public information on slow query or N+1 detection, background job and queue monitoring, profiling, or anomaly detection on latency. 3 7 15 16 20
The SaaS CTO
Distributed tracing is built on OpenTelemetry with documented OTLP endpoints, collector support, and head-, tail- and parent-based sampling whose quota effects are explained in unusual detail — exactly the vendor-neutral instrumentation I want — plus selectable percentiles from P50 to P99, Web Vitals at P75, CPU and memory metrics, and one-click navigation from an error to its trace. But the captured pages give no information on slow-query or N+1 detection, background job monitoring, code-level profiling or anomaly detection, which is the difference between a tracing product and full APM for my twelve services. 3 4 15 16 20
The Mobile Team Lead
Tracing is OpenTelemetry-native with OTLP endpoints over gRPC or HTTP and a collector path for higher volumes, an error navigates to its trace in one click, and percentiles from P50 to P99 plus web vitals and CPU/memory system metrics are selectable. The sampling documentation is the most detailed I have read — managed and unmanaged span quotas, daily resets at midnight UTC, parent-based sampling advice, and warnings when data carries a large error margin. We found no public information on code-level profiling, anomaly detection, slow query analysis or background job monitoring. 3 4 15 16 20
The Site Reliability Engineer
OpenTelemetry ingestion is documented down to the endpoint, gRPC and HTTP export and collector setup, with distributed tracing, automatic error-to-trace linking, selectable P50 through P99 percentiles, web vitals and CPU/memory system metrics beside the traces. Sampling is explained better than most vendors I have evaluated — managed and unmanaged span quotas, head and tail-based options and exactly what quota exhaustion does to coverage. We found no public information on code-level profiling, slow query or N+1 detection, or background job monitoring. 3 15 16 20
The Data Protection Officer
Distributed tracing built on OpenTelemetry with gRPC and HTTP ingestion, collector support, head-based sampling in the SDK and tail-based rules via a collector, selectable P50 to P99 percentiles and trimmed means, CPU and memory system metrics, web vitals, and one-click navigation from an error to its trace are all documented. Sampling behaviour is unusually well explained, with the trace as the sampling unit, dynamic quota distribution and warnings when the error margin grows. I found no public information on code-level profiling, slow query or N+1 detection, background job monitoring, or host and container metrics beside the traces. 3 4 15 16 20
The Skeptic
OpenTelemetry ingestion is documented with head- and tail-based sampling explained in rare detail — including what happens when the unmanaged span quota is exhausted at midnight UTC, exactly the fine print I look for. Selectable percentiles up to P99, web vitals, system metrics, trace context propagation across services and one-click navigation from error to trace are all shown; we found no public information on code-level profiling, slow-query or N+1 detection, service maps or SLOs. 3 15 16 20
Alerting, integrations & developer workflow
Show reasoningHide reasoning
How this is scored
How an error reaches the person who fixes it: alert rules on new issues, regressions, frequency and performance thresholds, notifications to email, Slack, Microsoft Teams, PagerDuty or Opsgenie, issue tracker integrations (Jira, GitHub, GitLab, Linear) that create and sync issues, source code links to the repository, deploy and release hooks from CI, a documented REST API and webhooks, a CLI, AI features that explain an error or suggest a fix (and which model runs them), and digest or weekly reports.
0 — No notifications and no integrations; errors are only visible by logging in.
3 — Email or chat notifications for new errors and one or two integrations; alert rules, the issue tracker link and the API are basic or not described.
5 — Configurable alert rules for new, regressed and frequent errors, Slack and email and an on-call tool, issue tracker integrations with GitHub, GitLab or Jira, deploy tracking from CI, a documented REST API and webhooks.
8 — Two-way sync with issue trackers, source code and commit links, alerts on performance thresholds and anomalies with routing per team or project, a CLI for releases and source maps, AI explanations or fix suggestions with the model provider named, and scheduled reports.
10 — A workflow a large team runs on: ownership rules routing issues to teams, every setting reachable by API or infrastructure as code, alert noise controls documented, and every AI feature documented with its data handling and an opt-out.
The Agency Tech Lead
Alert rules go deep — new errors, frequent errors with customisable event and user counts per interval and one notification per interval, reopenings, new releases, rate-limit proximity — delivered to Slack, Microsoft Teams, email with daily and weekly digests, and a genuinely two-way Jira sync that maps Closed and Resolved back to fixed; there is a documented data access API, deploy reporting, and an MCP server with AI fix suggestions, though the model behind them is not named. We found no public information on PagerDuty or Opsgenie routing, GitHub or GitLab issue creation, webhooks, or a CLI. 1 5 6 17 18
The SaaS CTO
Notification rules are genuinely configurable — new, frequent and reopened errors with my own event and user thresholds, saved filter sets, performance monitors, daily and weekly digests — delivered to Slack, Microsoft Teams and email, and the Jira integration is documented with two-way sync, automatic issue creation modes and comment syncing, beside a documented REST API and an MCP server that surfaces errors in the IDE with AI fix suggestions and alert routing to code owners. I found no public information on PagerDuty or Opsgenie, a CLI, or which model powers the AI suggestions, and Jira is the only issue tracker documented in what I read. 1 5 6 7 17 18
The Mobile Team Lead
Slack, Microsoft Teams and email with daily and weekly digests receive alerts on new errors, frequent errors and automatically reopened ones; Jira syncs two ways and can create an issue per new error or at an event threshold; and the Data Access and Build APIs plus an MCP server surfacing errors in the IDE with AI fix suggestions round out the loop, with alerts routable to code owners. Advanced notification filtering on saved filtersets is limited to Preferred and Enterprise plans. We found no public information on PagerDuty or Opsgenie, a CLI, source code links, or the model behind the AI suggestions. 1 5 6 17 18
The Site Reliability Engineer
Alert rules cover new, frequent, event-count and automatically reopened errors with customizable counts and intervals, saved filtersets, daily and weekly digests, Slack and Microsoft Teams delivery, a Jira integration with two-way sync and comment mirroring, plus build and deploy reporting from CI and documented APIs. The documented team notification services are Campfire, Datadog, Microsoft Teams, Pushed, Slack and Twilio, and we found no public information on a direct PagerDuty or Opsgenie route — the one thing my rota needs at 3am. AI fix suggestions via the MCP server are described without naming the model, and we found no public information on a CLI. 1 5 6 17 18
The Data Protection Officer
Notification rules for new, frequent, reopened and collaborator-actioned errors with basic and saved filtersets, daily and weekly digests, Slack, Microsoft Teams, Twilio and Datadog, and a Jira integration with two-way sync and automatic issue creation once a set number of events arrive in a time window are documented, alongside public APIs for data access, builds, error reporting and traces, and routing of alerts to code owners. An MCP server surfaces errors in the IDE with AI-powered fix suggestions, though the pages do not name which model runs them or where it runs — the first question I would ask. I found no public information on PagerDuty or Opsgenie routing, GitHub or GitLab issue tracker integrations, or a CLI. 1 5 6 17 18
The Skeptic
Notification rules cover new, frequent, reopened and comment-triggered errors with basic and saved-filter filtering, daily and weekly email digests, Slack and Teams, and a genuine two-way Jira sync that marks errors fixed when the linked issue closes, plus a documented Data Access API and AI fix suggestions via an MCP server with alert routing to code owners. What a responder will miss: we found no public information on PagerDuty or Opsgenie, GitHub, GitLab or Linear issue trackers, a CLI, or which model provider runs the AI features. 1 6 17 18
Data scrubbing, retention & volume control
Show reasoningHide reasoning
How this is scored
What the product does with the personal and secret data an error carries and how volume is kept in check: scrubbing of passwords, tokens, card numbers and personal data in the SDK and on the server with configurable rules, IP address anonymisation, opting out of request bodies and user data, data retention per plan and deletion on request, sampling of errors and traces, rate limits, spike protection and quota caps per project, filters that drop events before they count, data export, and a self-hosted edition that keeps every event on the customer's own servers.
0 — No control over what is captured, no retention period stated, no limit on volume.
3 — Some default filtering of passwords and a retention period stated for one plan; server-side scrubbing, sampling and spike protection are basic or not described.
5 — Configurable data scrubbing in the SDK and default server-side scrubbing of common secrets, IP anonymisation, retention stated per plan, sampling and rate limits per project, a quota cap or spike protection, and event filters before ingestion.
8 — Custom server-side scrubbing rules with examples, per-project retention settings and deletion of individual events or users, spike protection documented with how overage is billed, data export by API, and a self-hosted edition or a documented option to keep data in the customer's chosen region.
10 — Data minimisation by design and evidenced: personal data off by default in every SDK, scrubbing rules auditable, retention and deletion controllable per data type, volume controls that never surprise the invoice, and a supported self-hosted edition with feature parity stated.
The Agency Tech Lead
Server-side redaction is documented in unusual detail — dot-notation paths over user, request, breadcrumbs and metadata, rules created on the fly from an event and applied retroactively — but it sits on the Enterprise plan with a cap of 10 rules per project. The volume story is exactly what a maintenance shop needs: events over the daily quota are saved at no additional cost, auto-upgrade only after more than 3 daily overages in a 30-day rolling period, or rate limiting instead, and an on-premises edition exists. Retention is only stated for the Free tier at 7 days, and we found no public information on IP anonymisation or default scrubbing inside the SDKs. 5 7 19 20 21
The SaaS CTO
Custom server-side redaction rules with documented dot-notation paths over user, request, device, breadcrumbs and metadata, retroactive redaction, and an on-the-fly rule from an individual event are exactly what I need for enterprise customers — and the volume side is unusually honest: burst protection, events beyond quota saved at no additional cost with automatic plan upgrade after more than three exceedances in a 30-day period or rate-limiting instead, and a configurable unmanaged span quota that resets daily. Retention is stated only for the Free tier at 7 days, redaction rules require the Enterprise plan, and I found no public information on IP anonymisation or default password scrubbing in the SDKs. 1 5 7 18 19 20
The Mobile Team Lead
Sensitive Data Management redacts user, device, request, breadcrumb and custom metadata fields via dot-notation rules that can be created from a live event and applied retroactively, but it is capped at ten rules per project and gated to Enterprise-plan admins. Volume behaviour is unusually clear: events beyond the daily quota are kept at no additional cost with an automatic plan upgrade after three overages in a 30-day rolling period or rate limiting instead, and span quotas are split managed and unmanaged with a daily reset. We found no public information on default scrubbing of common secrets, IP anonymisation, or retention beyond the Free tier's 7 days, and an on-premise edition is confirmed but without licence pricing. 5 7 19 20
The Site Reliability Engineer
Server-side redaction is documented in unusual depth — dot-notation rules over user, app, device, request, breadcrumb and metadata fields, creatable on the fly from a live event and applied retroactively — though it sits on the Enterprise plan capped at ten rules per project. Volume behaves the way I want during an incident: over-quota events are saved at no additional cost, automatic plan upgrade only after more than three overages in a 30-day rolling period, rate limiting as the alternative, and dynamic span sampling with daily quota resets. We found no public information on SDK-side scrubbing, IP anonymisation, or retention periods beyond the free tier's 7 days. 1 7 19 20
The Data Protection Officer
Server-side redaction rules over the user, request, device, breadcrumb and metadata roots, creatable from project settings or on the fly from a live event and applied retroactively, are the scrubbing I need before any member data touches an error payload; quota behaviour is equally clear, with events beyond quota saved at no additional cost, an automatic upgrade after three overages in thirty days, a rate-limiting option, spans never overage-charged, and a documented on-premises edition. Sensitive data management is gated to the Enterprise plan and capped at ten rules per project, and retention is stated only as seven days on the free tier. I found no public information on IP anonymisation or an SDK-side opt-out of request bodies and user data. 1 5 7 19 20
The Skeptic
The volume controls are the best I have seen in public: events beyond the daily quota are saved at no additional cost with a stated auto-upgrade trigger and a rate-limiting alternative, span overages are uncharged when the vendor's sampling prediction misses, and an exhausted quota is highlighted in the dashboard; the SDK also lets you cancel events before sending. Against that, retroactive redaction rules exist but sit on the Enterprise plan with a limit of 10 rules per project, retention is stated only for the free tier at 7 days, and although an on-premise edition is offered, the pages do not document its feature parity or whether it calls home. 5 7 13 19 20
Access control, security & the vendor's reliability
Show reasoningHide reasoning
How this is scored
Whether the service holds up in an audit and on the vendor's own bad day: organisations, teams and projects with roles, single sign-on (SAML or OIDC) and SCIM, two-factor authentication, audit logs, encryption in transit and at rest, security certifications and reports (ISO 27001, SOC 2), a security page and a vulnerability disclosure policy, the vendor's own public status page and incident history, a stated availability or SLA, and how ingestion behaves when the vendor is down (SDK buffering, no impact on the app).
0 — Nothing on access control, security or the vendor's own availability.
3 — User accounts with two-factor authentication and a security page; roles, SSO, certifications and a status page are basic or not described.
5 — Organisations and projects with roles, two-factor authentication, single sign-on offered on some plan, encryption in transit and at rest stated, a public status page, and a security page naming certifications or audits.
8 — SAML SSO and SCIM provisioning, audit logs, ISO 27001 or SOC 2 with its scope stated, an SLA with credits published, the incident history public, a vulnerability disclosure or bug bounty programme, and SDK behaviour during vendor outages documented.
10 — Enterprise-grade operation evidenced: granular roles per project and team, audit logs exportable to a SIEM, independent audit reports available on request, published uptime history over years, and ingestion designed and documented never to slow the customer's application.
The Agency Tech Lead
SAML single sign-on arrives on Preferred and SSO user provisioning on Enterprise, organisation admin and project owner roles are visible in the permission requirements, encryption in transit and at rest is stated, the certification list is long (ISO 27001, ISO 27017, ISO 27018, SOC 1, SOC 2, SOC 3, PCI DSS, CSA STAR) with independent assessments and a Trust Center, and the public status page shows per-component 90-day uptime alongside a responsible disclosure policy with a 72-hour confirmation commitment. We found no public information on audit logs, an SLA with credits, the scope of the certifications, or how the SDKs behave while the vendor is down. 7 8 9 18 21 22
The SaaS CTO
SOC 2 and ISO 27001 are stated alongside SOC 1 and 3, ISO 27017, ISO 27018 and CSA STAR, with encryption in transit and at rest, MFA for administrative access, a responsible-disclosure policy carrying a 72-hour confirmation commitment and a 90-day confidentiality window, SAML SSO on Preferred and automatic user provisioning on Enterprise, and a public status page showing 100% uptime for every component over the past 90 days. I found no public information on audit logs, an SLA with credits, or how the SDKs behave while ingestion is down. 7 8 9 21 22
The Mobile Team Lead
SAML single sign-on ships on Preferred with automatic user provisioning via SSO on Enterprise, SOC 2 and ISO 27001 appear in a broad certification list beside encryption in transit and at rest, and the responsible disclosure programme commits to confirming a report within 72 hours. The public status page shows every BugSnag component at 100% uptime over the past 90 days with historical uptime available. We found no public information on audit logs, an SLA with credits, the scope of the certifications, or how the SDKs behave when the vendor's ingest is down. 7 8 9 21 22
The Site Reliability Engineer
SAML single sign-on ships on Preferred with automatic user provisioning via SSO on Enterprise, organizations carry named Organization Admin and Project Owner roles, encryption in transit and at rest is stated, ISO 27001 and SOC attestations are listed with a Trust Center and a serious responsible-disclosure policy (72-hour confirmation, 90-day confidentiality). The public status page reports 90-day uptime per component including every ingestion endpoint, which is what I check first when checkout latency climbs. We found no public information on audit logs, an availability SLA with credits, or SDK behaviour during vendor outages. 7 8 9 22
The Data Protection Officer
SAML single sign-on ships on the Preferred plan and SSO user provisioning with sensitive data management on Enterprise, roles such as Organization Admin and Project Owner are named, encryption in transit and at rest, SOC 2 Type II, ISO 27001/27017/27018, CSA STAR, regular independent assessments and a responsible disclosure policy with a 72-hour confirmation and 90-day confidentiality are published, and the status page shows 90 days of 100% uptime per component. I found no public information on audit logs, a published SLA or service credits, or how the SDKs behave when the ingest endpoints are unavailable. The terms exclude downtime costs from recoverable damages and cap liability at twelve months of fees. 7 8 9 11 18 21 22
The Skeptic
SAML single sign-on ships on Preferred and SSO user provisioning on Enterprise, the security page lists ISO 27001, 27017, 27018, SOC 1/2/3 and CSA STAR with attestation access, the status page shows 100% uptime over 90 days for every component, and a responsible disclosure policy commits to 72-hour confirmation with a defined scope. We found no public information on audit logs, a published SLA with credits, customer-side two-factor authentication, or how the SDKs behave while the vendor's ingestion is down. 7 8 9 21 22
European sovereignty
panel opinion
Show reasoningHide reasoning
How this is scored
Who the contracting entity and the parent company are, where error events, stack traces, request data, traces, profiles, session data and account data are stored and processed, and who the subprocessors are (hosting, email and chat delivery, AI models that explain errors, support and payment tools). Independently sourced by the sovereignty pipeline. An EU data region the customer can choose counts for the product; a US default without a stated EU option does not. A self-hosted edition the customer runs on its own European servers counts as the customer's chain, whatever the vendor's seat.
0 — Non-EU vendor and contracting entity, hosting unstated, subprocessors unnamed, and no data processing agreement offered.
3 — A privacy policy and a data processing agreement exist, but hosting location is unstated or non-EU and the subprocessors are not listed.
5 — An EU data region available and an EU contracting entity or EU representative, but parts of the chain (AI features, email, support, payment) run through non-EU providers without a stated safeguard.
8 — EU hosting on named infrastructure, EU contracting entity, subprocessors listed with their locations, a data processing agreement published, and security certifications (ISO 27001, SOC 2) stated — or a self-hosted edition documented that keeps every event on the customer's own servers.
10 — Sovereign end to end and evidenced: European ownership, entity, hosting and every subprocessor including the AI models, or a self-hosted edition with no call home, data export and deletion documented, and certifications published with their scope rather than implied.
The Agency Tech Lead
The contracting entity is SmartBear Software Inc. of Somerville, Massachusetts — the terms route non-US customers under Irish law — with a European headquarters in Galway, a data processing agreement and standard contractual clauses for transfers out of the EEA, while the privacy policy states personal information is processed in the US and overseas, hosting location for the SaaS is not stated on the captured pages, and no subprocessor list is published. An on-premises edition you install, maintain and manage yourself is documented, which would put the chain in the customer's hands, but we found no public information on its data flows or feature parity. 5 10 11 12 21
The SaaS CTO
The contracting entity is SmartBear Software Inc. of Somerville, Massachusetts, the privacy policy states personal information is processed in the US and overseas with standard contractual clauses as the safeguard, a data processing addendum is referenced, customers outside the US and Canada get Irish governing law, and an on-premises BugSnag Enterprise edition is documented for teams that need their own chain. I found no public information on an EU data region for the hosted service, the hosting infrastructure, or a subprocessor list, so I cannot yet answer my enterprise customers when they ask where their error data sits. 5 10 11 12 21
The Mobile Team Lead
SmartBear Software Inc. of Somerville, Massachusetts is the contracting entity, the privacy policy describes personal information processed in the US and overseas under standard contractual clauses, and customers outside the US and Canada get Irish governing law with a European headquarters in Galway; a data processing addendum is referenced from the privacy policy. We found no public information on an EU data region or a subprocessor list. The on-premise edition is documented, which would keep events on our own servers, but without pricing or much deployment detail beyond a Replicated KOTS admin console. 5 10 11 12 21
The Site Reliability Engineer
The contracting entity is SmartBear Software Inc. of Somerville, Massachusetts; the privacy policy describes personal information processed in the US and overseas under standard contractual clauses, and we found no public information on an EU data region for the hosted product. A data processing addendum is available and an on-premises edition exists, but we found no public information on whether that edition keeps every event on the customer's own servers, nor any listing of subprocessors with their locations. 5 11 12 18
The Data Protection Officer
The contracting entity is SmartBear Software Inc. of Somerville, Massachusetts, with an EU representative and European headquarters in Galway and Irish law for customers outside the US and Canada; the privacy policy references a Data Processing Addendum and states personal information is processed in the US and overseas under standard contractual clauses. I found no public information on where error events and traces are stored, on an EU data region, on a subprocessor list, or on where the AI features run. An on-premises edition is documented, but the captured pages do not state that every event stays on the customer's own servers. 5 7 10 11 12
The Skeptic
The contracting entity is SmartBear Software Inc. of Somerville, Massachusetts, the privacy policy states personal information is processed in the US and overseas under standard contractual clauses, and we found no public information on an EU data region a customer could choose. There is a Galway headquarters, Irish law governs non-US customers and a data processing addendum is referenced, but no subprocessor list is published; an on-premise edition exists, delivered through Replicated, yet the captured pages do not document that it keeps every event on the customer's own servers. 5 10 11 12
Pricing transparency
Show reasoningHide reasoning
How this is scored
Whether a buyer can compute the real annual cost from public pages alone: price per plan, what is included (errors or events, spans or transactions, replays, profiles, logs, seats, projects, retention), what overage costs per unit and whether it is capped, which features (SSO, audit logs, longer retention, EU region, AI) need a higher plan, host or seat based pricing for suites, the price of the self-hosted edition, annual versus monthly terms, and VAT.
0 — No public prices at all; every customer is a sales call.
3 — A starting price exists, but what volume it covers and what overage, retention and add-ons cost is unclear.
5 — Plans are public with their price and main volume limits, but at least one commonly needed piece (overage per event or span, longer retention, SSO, the EU region or AI features) is unpriced or "contact sales".
8 — Every plan priced publicly with its volume limits and overage rates, a price calculator or table per unit, add-ons and retention priced, the behaviour at the quota (cap or overage) stated, and VAT and billing terms stated.
10 — Complete price computability: annual cost derivable for a given volume of errors, traces, seats and projects, with every add-on, retention step, support level and the self-hosted licence priced and the cancellation terms published.
The Agency Tech Lead
The published tiers are Free at "$0 /month" with "7.5K events and 1M spans per month" and 7 days of retention, Select "STARTING AT $20 /month", Preferred "STARTING AT $33 /month" and Enterprise on contact — and the quota behaviour is unusually honest: overage events are saved at no additional cost, an automatic upgrade comes only after more than 3 daily overages in a 30-day rolling period, and minidump events each count as 5 events for billing. What each paid price actually buys in events and spans, retention beyond the Free tier, and the on-premises licence price are absent from the captured pages, so I cannot compute a real annual cost for a given volume. 7 11
The SaaS CTO
The Free plan is fully specified at $0 with 1 user, 7.5K events and 1M spans per month and 7 days of retention, and the overage behaviour is unusually transparent — events beyond quota are saved at no additional cost, minidump events count as five for billing, and spans beyond prediction are not charged — with annual versus monthly terms and the tax basis stated. But Select starts at $20/month and Preferred at $33/month with no published volume limits, retention beyond the free tier is unstated, and the Enterprise plan is contact sales, so I cannot compute our real annual cost from the public pages. 7 11
The Mobile Team Lead
The Free plan at $0 with 7.5K events, 1M spans and 7-day retention, Select starting at $20 per month and Preferred starting at $33 per month are public, and the quota behaviour is explicit — events beyond the daily quota are saved at no additional cost with an automatic upgrade after three overages in a 30-day rolling period, or rate limiting — while minidump crashes count as five events, an annual discount exists and cancellation terms are stated. Still, Select and Preferred are starting prices with no per-event calculator or unit table, so I cannot compute our real annual cost for our crash volume. We found no public information on paid-plan retention, the on-premise licence, or the Enterprise price beyond contact us. 1 7 11
The Site Reliability Engineer
Prices are public — Free at $0/month, Select starting at $20/month, Preferred starting at $33/month, Enterprise by contacting sales — with the free tier's 7.5K events and 1M spans per month, a 14-day Preferred trial, an annual discount, cancel-anytime, and terms from net-30 payment to a 60-day non-renewal notice. Quota behaviour is stated unusually clearly for a buyer: over-quota events are saved at no additional cost, automatic upgrade only after more than three overages in a rolling 30-day period, rate limiting otherwise, and minidump events each count as 5 events. What blocks computing a real annual cost is that the paid plans' event and span volumes are not stated, retention beyond the free tier's 7 days is not priced, and the on-premises edition is contact-only. 7 11 20
The Data Protection Officer
The pricing page publishes a free tier at $0 per month with 7.5K events, 1M spans and 7 days of retention, Select starting at $20 and Preferred starting at $33 per month, annual billing at a discount, a 14-day Preferred trial without a card, and a custom-priced Enterprise plan behind contact. Quota behaviour is unusually well documented: events beyond quota are saved at no additional cost, an automatic upgrade follows three overages in thirty days, minidump events count as five, and spans are never overage-charged. The volume the $20 and $33 starting prices cover is not stated, retention for paid plans is not stated, and beyond US sales tax the pages leave taxes to the terms, which exclude them from the fees. 7 11 20
The Skeptic
Three tiers carry public prices — Free at $0, Select starting at $20 per month, Preferred starting at $33 per month — with the free tier's volumes (7.5K events and 1M spans per month, 7-day retention), an unusually honest overage policy and the odd detail that a minidump counts as 5 events. What stops me computing a real annual bill: the paid prices say only "starting at" with no stated volumes, Enterprise is contact-sales, retention beyond the free tier and VAT are unstated, and the captured pages give different cancellation terms — the pricing page allows cancelling anytime while the terms specify auto-renewal at then-current prices unless given 60 days' notice, non-refundable fees, and 1.5% monthly interest on late payment. 7 11
European sovereignty — proven facts
1 of 6 dimensions provenBuilt only from facts shown on the vendor's own pages. A dimension we could not prove is left open, not scored as zero.
| Legal entity | Not determined | — | uncited Report an error |
|---|---|---|---|
| Hosting location | Not determined | — | uncited Report an error |
| Hosting options |
Not determined
unverified
Why unverified?Not confirmed on the vendor’s own pages as captured. |
— | uncited Report an error |
| Open source | Not determined | — | uncited Report an error |
| Data processing agreement |
Published, self-serve
unverified
Why unverified?The excerpt only shows the Data Processing Addendum as a tab in the legal document menu, not its text or an online acceptance flow. |
1/1 pts | 11 Report an error |
| Transfer impact assessment | Not determined | — | uncited Report an error |
Questions about BugSnag
Is BugSnag European?
No. whats-best.ai classifies BugSnag as Rest of world.
Where does BugSnag store data?
Not stated on the vendor’s pages as of 6 Nov 2026.
Does BugSnag have a free plan?
Yes. BugSnag has a free plan, per the vendor’s page captured 6 Nov 2026.
What are the best alternatives to BugSnag?
As of 18 Nov 2026, the panel rates Sentry (3.5/5), Datadog APM & Error Tracking (3.5/5) and Dynatrace (3/5) highest among the other 19 Error Tracking & APM products evaluated. Ratings that look equal are rounded to half stars; the order uses the unrounded rating, then the name. The highest-rated European alternative is Tideways (EU-Made). Ratings are the AI panel’s opinion, formed from public evidence: how scores are made. The full list, with European products first: BugSnag alternatives.
Where this could be wrong
- Evidence ages. The oldest capture behind this page is from 6 Nov 2026. Vendors change pricing and policies without notice; every fact reflects its source as of the capture date shown in the registry.
- Weak sourcing — Data processing agreement. The excerpt only shows the Data Processing Addendum as a tab in the legal document menu, not its text or an online acceptance flow.
- Weak sourcing — Hosting options. Not confirmed on the vendor’s own pages as captured.
- AI can misread a source. Extraction and judgement are automated; a citation guarantees traceability, not infallibility. If something here is wrong, say so — no account needed, every report is decided within 5 business days, and accepted corrections are published.
What we left out
A claim that does not survive our checks costs us the claim, not the page. This is what was taken off this one.
- 14 product facts could not be confirmed on the vendor’s page as captured and were left out of this page and of the panel’s material. Know more? Tell us
- 11 compliance facts could not be confirmed on the vendor’s page as captured and were left out of this page and of the panel’s material. Know more? Tell us
- 6 integrations facts could not be confirmed on the vendor’s page as captured and were left out of this page and of the panel’s material. Know more? Tell us
- 3 support facts could not be confirmed on the vendor’s page as captured and were left out of this page and of the panel’s material. Know more? Tell us
- 2 data facts could not be confirmed on the vendor’s page as captured and were left out of this page and of the panel’s material. Know more? Tell us
- 1 hosting fact could not be confirmed on the vendor’s page as captured and was left out of this page and of the panel’s material. Know more? Tell us
- 1 legal fact could not be confirmed on the vendor’s page as captured and was left out of this page and of the panel’s material. Know more? Tell us
- 1 sovereignty dimension could not be confirmed on the vendor’s own pages and is shown as unknown. Know more? Tell us
- 6 of the readings below were written against an earlier fact sheet — a fact has been corrected, added or pulled since. Until the panel next runs on this product you are reading the older judgement. Know more? Tell us
Sources (22)
The pages every claim on this page was read from — each one checked, dated, and kept verifiable.
- 1 Vendor homepage www.bugsnag.com Checked 6 Nov 2026 Details →
- 2 Features page (error monitoring) www.bugsnag.com Checked 6 Nov 2026 Details →
- 3 Features page (performance monitoring) www.bugsnag.com Checked 6 Nov 2026 Details →
- 4 Features page (distributed tracing) www.bugsnag.com Checked 6 Nov 2026 Details →
- 5 Documentation docs.bugsnag.com Checked 6 Nov 2026 Details →
- 6 API documentation developer.smartbear.com Checked 6 Nov 2026 Details →
- 7 Pricing page www.bugsnag.com Checked 6 Nov 2026 Details →
- 8 Security / trust page smartbear.com Checked 6 Nov 2026 Details →
- 9 Public status page bugsnag.status.smartbear.com Checked 6 Nov 2026 Details →
- 10 About page (parent company) smartbear.com Checked 6 Nov 2026 Details →
- 11 Terms of service (names the operating company) smartbear.com Checked 6 Nov 2026 Details →
- 12 Privacy policy smartbear.com Checked 6 Nov 2026 Details →
- 13 Error capture, grouping & triage — found from sitemap docs.bugsnag.com Checked 6 Nov 2026 Details →
- 14 Error capture, grouping & triage — found from sitemap docs.bugsnag.com Checked 6 Nov 2026 Details →
- 15 APM, tracing & profiling — found from sitemap docs.bugsnag.com Checked 6 Nov 2026 Details →
- 16 APM, tracing & profiling — found from sitemap docs.bugsnag.com Checked 6 Nov 2026 Details →
- 17 Alerting, integrations & developer workflow — found from sitemap docs.bugsnag.com Checked 6 Nov 2026 Details →
- 18 Alerting, integrations & developer workflow — found from sitemap docs.bugsnag.com Checked 6 Nov 2026 Details →
- 19 Data scrubbing, retention & volume control — found from sitemap docs.bugsnag.com Checked 6 Nov 2026 Details →
- 20 Data scrubbing, retention & volume control — found from sitemap docs.bugsnag.com Checked 6 Nov 2026 Details →
- 21 Access control, security & the vendor's reliability — found from sitemap www.bugsnag.com Checked 6 Nov 2026 Details →
- 22 Access control, security & the vendor's reliability — found from sitemap docs.bugsnag.com Checked 6 Nov 2026 Details →