As of 6 Nov 2026, the panel rates BugSnag 3/5 and Raygun 2.5/5 in Error Tracking & APM. Weighted by what each judge cares about, 6 of the 6 judges pick BugSnag and 0 pick Raygun. BugSnag scores higher on 7 of 7 criteria (European sovereignty, Data scrubbing, retention & volume control, APM, tracing & profiling, plus 4 more). Provenance — BugSnag: Rest of world; Raygun: Rest of world, New Zealand. Ratings are the AI panel’s opinion, formed from public evidence: how scores are made.
The short answer
BugSnag leads the means on performance tracing (6.5 to 5.2; 6 lean BugSnag, 0 Raygun, 0 tie), data controls (6.8 to 4.8) and sovereignty (3.5 to 1.3), both leaning 6 to 0 with 0 ties, pricing transparency (5.2 to 4.2; 4 lean BugSnag, 2 tie), security and reliability (6.5 to 5.8; 3 lean BugSnag, 3 tie) and workflow and integrations (6.3 to 6.0; 2 lean BugSnag, 4 tie). Error tracking is the genuine split: 6.5 to 6.3, 2 judges lean BugSnag, 1 Raygun, 3 tie — the table's only Raygun lean — on resolve-in-version workflows and an audit log of grouping changes. All six sovereignty attributes — legal entity jurisdiction, data residency, hosting options, open source, data processing agreement, transfer impact assessment — read unknown for both products. Weighted totals span 6 to 4.5 for the skeptic judge, closest 6.1 to 5.4 for the SRE judge; the lean differs by judge and criterion.
Choose BugSnag if
You need OpenTelemetry-based tracing with documented sampling and quota behaviour across your stack — performance tracing leans BugSnag 6 judges to 0 (means 6.5 to 5.2).
Your compliance process requires retroactive server-side redaction of event data — data controls leans BugSnag 6 judges to 0 (means 6.8 to 4.8).
You need published prices before talking to sales — Free at $0/month with 7.5K events, 1M spans and 7-day retention, Select starting at $20/month and Preferred starting at $33/month are public, and events beyond quota are saved at no additional cost; pricing transparency leans BugSnag 4 judges to 0, with 2 ties.
Your team works in Jira and ships across mobile and backend platforms — a two-way Jira sync and versioned SDKs are documented, and workflow and integrations leans BugSnag 2 judges to 0, with 4 ties.
Your procurement rubric weights sovereignty — that criterion leans BugSnag 6 judges to 0, with means 3.5 to 1.3.
Choose Raygun if
You close errors at release time — Raygun's resolve-in-version workflows tied to deployment tracking drew the panel's only Raygun lean, in error tracking (1 judge leans Raygun, 2 lean BugSnag, 3 tie).
You need custom grouping you can audit — stack-trace-based grouping with custom grouping keys and an audit log of grouping changes were credited under error tracking (mean 6.3).
Your alerts must fire per error group — Raygun documents alerts settable per error group, part of its workflow and integrations score of 6.0, where 4 judges tied.
Your servers run.NET, Ruby or Node.js — Raygun's server-side APM covers those runtimes, with millisecond flame charts and N+1 detection rules documented.
You must contract outside the United States — the verdicts name SmartBear Software Inc. of Somerville, Massachusetts for BugSnag and Raygun Limited under New Zealand law for Raygun.
Read this comparison as one judge. Each weighs the same scores by what they care about.
The SaaS CTO
CTO of a B2B SaaS company in Berlin with thirty-five engineers, twelve services in Go, Python and TypeScript on Kubernetes and a React frontend. Wants one trace from the click in the browser to the slow database call three services down, OpenTelemetry so the instrumentation is not locked to one vendor, errors routed to the team that owns the service, releases linked to the commits that broke them, and an EU region because the enterprise customers ask where their data goes.
BugSnag
This judge's pick
Raygun
Criterion by criterion
Error capture, grouping & triage
BugSnag
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.
Raygun
Crash reporting documents full stack traces with environment, browser, version, class name and host, automatic grouping on exception type, class and method with custom grouping keys plus message-based and provider-based grouping, and a full status workflow of active, resolved, ignored and permanently ignored with reactivation and resolve-in-version tied to registered deployments. Source map decoding comes via GitHub, Bitbucket and GitLab integrations with private source map support. What keeps it below the top: we found no public information on suspect commits or code owners, crash-free users and sessions, or per-SDK configuration documentation.
APM, tracing & profiling
BugSnag
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.
Raygun
Traces are segmented by the millisecond across methods, requests, queries and external calls, with a flame chart, hot path, async and multithreaded views, named dependency providers from SqlClient to Redis and Elasticsearch, custom detection rules for N+1 and chatty APIs, and real user monitoring with Core Web Vitals and a DNS-to-transfer waterfall; trace sampling is configurable per trace and per URL and even covers background entry points. However, we found no public information on distributed tracing across services or OpenTelemetry ingestion, so the browser-click-to-slow-query trace across my twelve services is not something these pages show, and percentiles per endpoint, host metrics and anomaly detection are also not described.
Alerting, integrations & developer workflow
BugSnag
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.
Raygun
Twenty-five integrations are listed including Slack, PagerDuty, VictorOps, Jira OAuth, GitHub, GitLab and webhooks, alert conditions can be set per error group, new issues trigger email, and there is a daily digest email plus a daily Slack performance summary; source code is viewable natively from GitHub, Bitbucket and Azure Repos. The AI root-cause suggestions name OpenAI and are opt-in only, which is the disclosure I want. The documented CLI manages the APM agent rather than releases and source maps, and we found no public information on a documented REST API, two-way issue tracker sync, or alert routing per team.
Data scrubbing, retention & volume control
BugSnag
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.
Raygun
Scrubbing is documented at code level in every provider with before-send filtering for data like card details, IP collection can be switched off, sampling is configurable per trace and per URL with overrides that reach agents within ten minutes, and discarded occurrences of permanently ignored or resolve-in-next-version errors do not count toward the quota; PII and identified users can be deleted, content is deleted on cancellation, and raw trace data exports as JSON. We found no public information on server-side scrubbing rules, retention periods per plan, spike protection, or a self-hosted edition.
Access control, security & the vendor's reliability
BugSnag
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.
Raygun
Teams with granular permissions on the Team plan and up, SAML2 single sign-on with documented configurations for Okta, Jumpcloud, ADFS, Azure AD and G-Suite plus auto-provisioning and TOTP two-factor, TLS in transit and encrypted storage on AWS, third-party pentests every six months, and a public status page with component monitors give me the middle ground. The certifications named are HIPAA, GDPR, CCPA and PCI and we found no public information on ISO 27001 or SOC 2; deprovisioning goes through support rather than SCIM, the audit log we saw covers grouping changes and merges, and we found no public information on a vulnerability disclosure policy or on how SDKs behave when Raygun itself is down.
European sovereignty
BugSnag
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.
Raygun
The contracting entity is Raygun Limited, a New Zealand company under New Zealand law, with US customers possibly paying Raygun Incorporated; hosting is on Amazon Web Services and we found no stated region. The terms acknowledge third-party vendors and hosting partners without listing them, and while the privacy policy commits to GDPR with PII deletion and a breach policy, we found no published data processing agreement and no EU data region. When my enterprise customers ask where their data goes, these pages do not answer.
Pricing transparency
BugSnag
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.
Raygun
The unit economics are public: on-demand charged at $0.001 per error, "Save 60% per month purchasing reserved events versus using on-demand", annual plans saving 33%, SAML SSO free on Business and Enterprise or a $50/month add-on, unlimited apps and team members, and a 14-day trial without a credit card. But we found no public information on per-plan prices and their volume limits, retention per plan, or VAT treatment, and the quota behaviour is only described as excessive usage being charged or an upgrade requested; Enterprise is "Talk to us".
Sovereignty, side by side
Dimension
BugSnag
Raygun
Legal entity
Not determined
Incorporated in NZ
Hosting location
Not determined
Not determined
Hosting options
Not determined
Not determined
Open source
Not determined
Not determined
Data processing agreement
Published, self-serve
Not determined
Transfer impact assessment
Not determined
Not determined
Facts, side by side
Only facts both products carry under the same definition — anything else would not be a fair row.
Fact
BugSnag
Raygun
Compliance · Certifications
PCI DSS · ISO 27001 · ISO 27017 · ISO 27018 · SSAE 16 / ISAE 3402 Type II (SOC 1, SOC 2, SOC 3) · CSA STAR · EU GDPR · CCPA1
As of 6 Nov 2026, the panel rates BugSnag higher: 3/5 against 2.5/5. Weighted by what each judge cares about, 6 of the 6 judges pick BugSnag and 0 pick Raygun. Which one fits depends on the criteria that matter to you; the table on this page shows both side by side, and each judge’s reading has its own page. Both were scored by the same AI bench under the same rubric, from public evidence only, as the methodology describes.
Is BugSnag or Raygun European?
BugSnag is not European by provenance (Rest of world). Raygun is not European by provenance (Rest of world, New Zealand). Provenance is read from each company’s own legal pages: who builds it and who owns it.
Do BugSnag and Raygun have a free plan?
As of 6 Nov 2026, BugSnag’s own pages state a free plan; Raygun’s pages as captured do not. Each product page links the pricing page it was read from.