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 Skeptic
Has seen a "free tier" that ran out on the first busy Monday, an overage bill larger than the plan after one deploy looped on an exception, "EU hosting" with the support desk and the AI assistant in the US, and an SDK that slowed the app it was meant to watch. Asks what happens at the quota, how long events are really kept, whether the instrumentation works with another vendor after leaving, what the self-hosted edition leaves out — and what the second year costs.
BugSnag
This judge's pick
Raygun
Criterion by criterion
Error capture, grouping & triage
BugSnag
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.
Raygun
Grouping is genuinely documented — stack-trace-based, with custom grouping keys, message-based and provider-based modes, hasher versions and merged groups visible in an audit log — and the lifecycle goes deep: ignore conditions with counts and timeframes, resolve-in-version, resolve-in-next-version, and discarded instances that skip the error quota. The claim of SDKs for all major languages is marketing breadth with no per-SDK list or configuration pages behind it, and we found no public information on breadcrumbs, local variables, symbolication or crash-free users and sessions.
APM, tracing & profiling
BugSnag
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.
Raygun
The code-level story is real: flame charts with hot paths, call trees, millisecond segment views, dependency timing for the common SQL and Redis clients and outbound HTTP, N+1-style custom rules, and sampling set per trace or per URL with ten-minute agent propagation. But server-side APM is documented for three languages only, and we found no public information on distributed tracing across services, percentile timings per endpoint, OpenTelemetry ingestion or host and container metrics. Front-end Web Vitals, waterfall breakdowns and per-session diagnostics are documented on the real user monitoring side.
Alerting, integrations & developer workflow
BugSnag
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.
Raygun
Twenty-five named integrations including PagerDuty, Slack, VictorOps, GitHub, GitLab and Jira, source code pulled from the repository straight into trace details, a daily digest, alerts settable per error group, and an AI fix suggestion whose provider (OpenAI) and opt-in-not-default handling are both on the record — that last part is rarer than it should be. The documented command line is the APM agent's, not a release tool, and we found no public information on a documented REST API, two-way tracker sync, or alert routing per team.
Data scrubbing, retention & volume control
BugSnag
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.
Raygun
Scrubbing is a client-side story: custom filters and code-level removal before anything is sent, IP collection switchable off, PII and identified-user deletion with removal from backups — all real, but we found no public information on configurable server-side scrubbing. Sampling is documented per trace and per URL, and permanently ignored instances can be discarded so they skip the error quota; still, no retention length is stated anywhere in the captured pages, and the terms say excessive usage gets charged based on usage — exactly the bill I ask about after one bad Monday.
Access control, security & the vendor's reliability
BugSnag
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.
Raygun
SAML2 single sign-on with named identity providers and org-wide enforcement, TOTP two-factor, granular per-team permissions, TLS and encrypted storage, third-party penetration tests every six months, and a live public status page make a credible mid-market showing. Deprovisioning is a support contact rather than SCIM, and we found no public information on SOC 2 or ISO 27001 reports, exportable audit logs, a vulnerability disclosure programme, or how the SDK behaves when ingestion is down; custom SLAs exist only at Enterprise.
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 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.
Raygun
The contracting entity is Raygun Limited of New Zealand under New Zealand law, US customers may be directed to pay Raygun Incorporated, and the platform runs on Amazon Web Services with no data region named anywhere in the captured pages. GDPR compliance is claimed with PII deletion functionality and the AI provider is named as OpenAI behind an opt-in, but we found no public information on an EU data region option, a published data processing agreement, or a self-hosted edition that keeps events on your own servers.
Pricing transparency
BugSnag
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.
Raygun
The unit economics are public — additional usage charged on-demand at $0.001 per error, reserved events saving 60% per month, annual payment saving 33%, SAML SSO a $50/month add-on free on Business and Enterprise — plus the terms a skeptic wants to see: excessive usage is charged, annual plans paid monthly bind you for 12 months, and prices move on 7 days' notice. What we found no public information on is plan price points with their volume tiers, retention add-ons or VAT treatment, and Enterprise is a sales conversation.
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.