BugSnag vs Raygun

BugSnag

Rest of world

Sovereignty: 1 of 6 dimensions proven

Full evaluation →

Raygun

Rest of world

Sovereignty: 1 of 6 dimensions proven

Full evaluation →

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 Agency Tech Lead

Technical lead at a web agency in Cologne with fourteen developers and forty client sites on Laravel, Shopware and WordPress, most on maintenance contracts. Wants every client in its own project with its own alert channel, PHP stack traces that show the query and the queued job, slow pages found before the client calls, request data scrubbed because the shops hold customer addresses, and a monthly bill that does not jump when one client's cron job throws the same exception a million times.

BugSnag

This judge's pick

Raygun

Criterion by criterion

Error capture, grouping & triage

BugSnag

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.

Raygun

Crash reporting is documented down to the grouping engine: full stack traces with method and class data, automatic grouping on the stack trace, custom grouping keys, message-based and provider-based grouping, and a complete triage workflow with active, resolved, ignored and permanently-ignored states, version-bound resolution, bulk status changes and regression reactivation. Source map decoding, private source maps and deployment tracking are documented, and discarded instances of ignored errors stay off the quota. We found no public information on PHP or Laravel SDKs specifically, breadcrumbs, local variables per frame, symbolication or crash-free user and session rates, so it sits just above the solid mid-tier rather than at the top.

APM, tracing & profiling

BugSnag

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.

Raygun

APM shows millisecond trace views with call tree, flame chart and hot path, dependency details down to the SQL query, Redis and outbound HTTP with durations, custom N+1 and chatty-API issue rules, and configurable trace sampling per URL or per trace — plus real user monitoring with Core Web Vitals, waterfall breakdowns and error correlation. We found no public information on distributed tracing across services, percentile timings per endpoint, OpenTelemetry ingestion or host metrics beside the traces, and server-side APM is documented for.NET, Ruby and Node.js only, so nothing covers our PHP stacks.

Alerting, integrations & developer workflow

BugSnag

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.

Raygun

Twenty-five documented integrations cover Slack, PagerDuty, VictorOps, Jira, GitHub, GitLab, Azure DevOps and webhooks; alerts can be bound to specific error groups with conditions, new issues trigger a notification email, and there is an APM daily digest and a Slack daily performance summary. AI root-cause and fix suggestions run on OpenAI and are opt-in only. We found no public information on a documented REST API, two-way issue tracker sync or Microsoft Teams, and the CLI we saw configures the.NET APM agent rather than releases and source maps.

Data scrubbing, retention & volume control

BugSnag

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.

Raygun

Scrubbing is code-level and happens before anything leaves the app — developers filter credit card details and other sensitive values in every provider — IP collection can be switched off per plan, PII and identified users can be permanently deleted, and data is purged from online storage and backups when retention expires. Volume is kept in check because permanently ignored errors can be set to discard without touching the error quota and APM sampling is configurable per URL and per trace, with on-demand usage charged at "$0.001 per error". We found no public information on server-side scrubbing rules, stated retention lengths per plan, error sampling or a self-hosted edition.

Access control, security & the vendor's reliability

BugSnag

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.

Raygun

Teams per plan get manually configurable granular permissions (Team plan and up), SAML2 SSO with auto-provisioning for Okta, Entra, ADFS, G-Suite and Jumpcloud — free on Business and Enterprise, otherwise a $50/month add-on — plus TOTP two-factor, TLS in transit, encrypted storage on AWS, third-party pentests every six months, an audit log covering grouping changes and merges, and a public status page with component monitors and incident history. We found no public information on ISO 27001 or SOC 2, on deprovisioning beyond contacting support, on a published SLA with credits, or on how the SDKs behave during a Raygun outage — the certifications named are HIPAA, GDPR, CCPA and PCI.

European sovereignty

BugSnag

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.

Raygun

Raygun Limited is a New Zealand company under New Zealand law, is built on Amazon Web Services with no region stated, and where third-party AI is used it runs on OpenAI behind an opt-in — the chain the evidence shows runs outside Europe end to end. GDPR commitments, permanent PII deletion and custom privacy arrangements are documented. We found no public information on an EU data region, an EU contracting entity, a published data processing agreement, or a self-hosted edition.

Pricing transparency

BugSnag

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.

Raygun

The pricing page publishes the on-demand rate of "$0.001 per error", 60% savings on reserved versus on-demand, 33% annual savings, unlimited apps and team members, and a 14-day free trial with no credit card; SSO is priced as a $50/month add-on below Business and Enterprise, and Enterprise is "Talk to us". The terms spell out USD billing, annual-monthly commitments with no refund on early cancellation, overage charged on usage or an upgrade request, and 1.5% monthly late-payment interest with a 14-day grace period. We found no public information on per-plan prices with included error volumes, retention tiers or VAT, so a real annual figure for a known volume is not computable from the captured pages alone.

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

captured 6 Nov 2026 · Report an error

HIPAA · GDPR · CCPA · PCI2

captured 6 Nov 2026 · Report an error

Compliance · Encryption yes3

captured 6 Nov 2026 · Report an error

yes4

captured 6 Nov 2026 · Report an error

Data · Retention retained per stated uses and legal/financial/compliance obligations5

captured 6 Nov 2026 · Report an error

until retention period expires or manual deletion6

captured 6 Nov 2026 · Report an error

Legal · Entity SmartBear Software Inc. and affiliates5

captured 6 Nov 2026 · Report an error

Raygun Limited · 18996736

captured 6 Nov 2026 · Report an error

Legal · Entity name SmartBear Software Inc. · 450 Artisan Way, Somerville, MA 02145, USA7

captured 6 Nov 2026 · Report an error

Raygun Limited · 18996738

captured 6 Nov 2026 · Report an error

Legal · Governing law Ireland · Massachusetts7

captured 6 Nov 2026 · Report an error

New Zealand8

captured 6 Nov 2026 · Report an error

Legal · Terms last updated 2026-11-047

captured 6 Nov 2026 · Report an error

January 20248

captured 6 Nov 2026 · Report an error

Pricing · Annual discount yes9

captured 6 Nov 2026 · Report an error

3310

captured 6 Nov 2026 · Report an error

Pricing · Late payment interest 0.0157

captured 6 Nov 2026 · Report an error

1.5 · 148

captured 6 Nov 2026 · Report an error

Pricing · Trial all Preferred features · 14 · no9

captured 6 Nov 2026 · Report an error

14 · no11

captured 6 Nov 2026 · Report an error

Questions about BugSnag and Raygun

Which is better, BugSnag or Raygun?

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.