Raygun
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 Raygun Limited · raygun.com
Compare with BugSnag → 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.
Raygun at a glance
- Vendor
- Raygun Limited
- Headquarters
- Incorporated in New Zealand source, captured 6 Nov 2026
- Data hosting
- Not stated on the vendor’s pages as of 6 Nov 2026
- Free plan
- Not stated on the vendor’s pages as of 6 Nov 2026
- Panel verdict
- The AI panel rates Raygun 2.5/5, the mean of 6 judges. Raygun is a New Zealand-based error tracking and APM platform whose strongest showing is error tracking, scored 6-7: judges credited stack-trace-based grouping with custom grouping keys, resolve-in-version workflows tied to deployment tracking, and an audit log of grouping changes. 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
Raygun is a New Zealand-based error tracking and APM platform whose strongest showing is error tracking, scored 6-7: judges credited stack-trace-based grouping with custom grouping keys, resolve-in-version workflows tied to deployment tracking, and an audit log of grouping changes. Workflow and integrations scored 6 throughout, on 25 named integrations and alerts settable per error group. Performance tracing sits at 5-6 — millisecond flame charts and N+1 detection rules are documented, but server-side APM covers.NET, Ruby and Node.js only, and we found no public information on distributed tracing or OpenTelemetry ingestion. The weakest area is sovereignty at 1-2: the contracting entity is Raygun Limited under New Zealand law, hosting runs on Amazon Web Services with no data region named, and we found no public information on an EU data region, a published data processing agreement or a self-hosted edition. Data controls and pricing transparency lose ground on retention durations without published figures and unpublished per-plan prices. Judges stayed within one point of each other everywhere; no substantive disagreement was recorded.
Speaks for it
- Error tracking scored 6-7, the highest marks in the scoring, for grouping documented down to custom grouping keys, hasher versions and an audit log of merges, with resolve-in-version and resolve-in-next-version tied to deployment tracking
- Server-side profiling for.NET, Ruby and Node.js shows millisecond flame charts, hot paths, dependency timings for SQL clients, Redis and outbound HTTP, and custom N+1 and chatty-API rules, with sampling per trace or per URL
- Developers control the payload: code-level scrubbing before send, IP collection that can be disabled, PII and identified-user deletion that reaches backups, and discarded ignored errors that skip the quota
- SAML2 single sign-on with named identity providers, org-wide enforcement and auto-provisioning, TOTP two-factor, granular per-team permissions (Team plan and up), third-party pentests every six months, and a public status page with monitored components
- Published unit economics: on-demand usage at $0.001 per error, 'Save 60% per month purchasing reserved events versus using on-demand', a 33% annual saving, unlimited apps and team members, and a 14-day free trial with no credit card required
Held against it
- Sovereignty scored 1-2: Raygun Limited contracts under New Zealand law, US customers may be directed to pay Raygun Incorporated, hosting runs on Amazon Web Services with no region named, and we found no public information on an EU data region, a data processing agreement or a subprocessor list
- Server-side APM is documented for.NET, Ruby and Node.js only, and we found no public information on distributed tracing across services, OpenTelemetry ingestion or percentile timings per endpoint
- We found no public information on per-plan prices, included volumes, retention durations or VAT treatment; Enterprise is 'Talk to us Custom' and annual plans paid monthly bind you for 12 months
- We found no public information on SOC 2 or ISO 27001 reports, SCIM provisioning or a published SLA with credits, and deprovisioning goes through support
- Scrubbing is documented as code-level and before-send only, we found no public information on server-side scrubbing rules, and the terms state excessive usage is charged based on usage
Best for
- You run.NET, Ruby or Node.js services and want release-tied error triage, where grouping, resolve-in-version and deployment tracking are the product's strongest documented ground
- You buy on per-error economics — on-demand at $0.001 per error, 60% savings on reserved events versus on-demand, a 33% annual saving, and unlimited apps and team members
- You must name third-party AI providers in governance reviews — OpenAI is named and the feature is opt-in, not on by default
- You need SAML2 single sign-on across named identity providers with per-team granular permissions on the Team plan and up
Avoid if
- You need EU data residency or a published data processing agreement in place before production use — sovereignty scored 1-2 with hosting on Amazon Web Services and no region named
- Your services are mobile-native (iOS, Android, Flutter) or PHP — server-side APM is documented for.NET, Ruby and Node.js only, and we found no public information on mobile crash symbolication, crash-free sessions or PHP SDKs
- You must produce a full annual price before signing — we found no public information on plan prices or included volumes, and Enterprise is 'Talk to us Custom'
- You require SOC 2 or ISO 27001 reports or SCIM provisioning as procurement gates — we found no public information on these, and deprovisioning goes through support
The scores
| Criterion | Panel median |
|---|---|
| Error capture, grouping & triage | 3 of 5 |
| APM, tracing & profiling | 2.5 of 5 |
| Alerting, integrations & developer workflow | 3 of 5 |
| Data scrubbing, retention & volume control | 2.5 of 5 |
| Access control, security & the vendor's reliability | 3 of 5 |
| European sovereignty | 0.5 of 5 |
| Pricing transparency | 2 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
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. 2 5 7 13 14
The SaaS CTO
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. 2 5 7 13 14
The Mobile Team Lead
Grouping and the release workflow are documented in depth: errors are grouped automatically from the stack trace with a custom grouping key and merge supported, statuses reactivate when an instance recurs, and 'resolved in version' plus deployment tracking tell me when a bug was introduced after a release — the loop I need on a two-week cadence. For a mobile team, though, the pages only show iOS and Android through real user monitoring SDKs; we found no public information on native crash symbolication, crash-free sessions or users per release, or breadcrumbs and device logs from a customer's phone. 2 4 7 10 13 14
The Site Reliability Engineer
Automatic grouping is documented down to the stack-trace logic, with custom grouping keys, message-based grouping, hasher versions and an audit trail when grouping settings change or groups are merged; error statuses with resolve-in-version reactivation, deployment tracking, affected-user counts and source map decoding including private source maps are all on the record. We found no public information on breadcrumbs, symbolication for mobile crashes, suspect commits or crash-free session metrics, so it sits below the top band but comfortably past the middle one. 13 14 2 5 7 10
The Data Protection Officer
Automatic stack-trace grouping with a custom grouping key, message-based and provider-based variants, and an audit trail of grouping changes and merges is documented, together with a complete status workflow — active, resolved, ignored, permanently ignored — reactivation on new instances, resolve-in-version, deployment tracking, filtering by version, host, OS and browser, and affected-user tracking. I found no public information on breadcrumbs, mobile symbolication, crash-free sessions or suspect commits, and the SDK list is a general claim rather than a per-platform catalogue. 2 5 7 13 14
The Skeptic
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. 13 14 2 7 5
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
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. 3 4 15 16 20
The SaaS CTO
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. 3 15 4 16 20
The Mobile Team Lead
Traces capture methods, requests, queries and external calls with a millisecond flame chart, hot path and link to source, custom rules catch N+1 queries and chatty APIs, sampling is configurable per trace or per URL, and real user monitoring adds Core Web Vitals with a full waterfall breakdown. Server-side APM is documented for.NET, Ruby and Node.js only, which leaves my iOS, Android and Flutter apps outside the profiler; we found no public information on distributed tracing across services, OpenTelemetry ingestion, or percentiles per endpoint. 3 4 15 16 20
The Site Reliability Engineer
Traces capture methods, requests, queries and external calls with millisecond timeline views, flame charts and hot paths, dependency detection across the main.NET data stacks plus outbound HTTP, and custom rules for N+1 and chatty-API detection; real user monitoring adds Core Web Vitals and waterfall breakdowns, and errors correlate with performance issues. APM is documented for.NET, Ruby and Node.js, and we found no public information on latency percentiles per endpoint, distributed tracing across services, OpenTelemetry ingestion, host and container metrics or anomaly detection. 15 3 4 20
The Data Protection Officer
Server-side traces are documented per millisecond with a call tree, flame chart and hot path, database and dependency calls captured with durations and credentials excluded, custom performance rules such as N+1 queries, sampling configurable per trace or per URL, and real user monitoring with Core Web Vitals. I found no public information on percentile timings per endpoint, distributed tracing across services, OpenTelemetry ingestion, or host and container metrics beside the traces. 3 4 15 16 20
The Skeptic
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. 3 15 4 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
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. 4 11 13 16 17
The SaaS CTO
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. 17 16 4 3 11 18
The Mobile Team Lead
Alerts can be set on specific error groups with conditions, new issues trigger notification emails, and Slack, PagerDuty, VictorOps, GitHub, GitLab and Jira are among twenty-five listed integrations, with a daily digest email and a Slack daily performance summary. The AI fix suggestions name OpenAI as the provider and are opt-in rather than on by default, which I respect; we found no public information on a documented REST API or two-way tracker sync, and the command line tool targets the APM agent rather than releases and source maps. 2 4 11 13 16 17 18
The Site Reliability Engineer
PagerDuty, Slack and VictorOps appear on a 25-item integration list alongside GitHub, GitLab and Jira, with webhooks, alert conditions per error group, notification frequency settings and daily digest emails; AI fix suggestions are stated to run through OpenAI on an opt-in basis, and a CLI exists, though it configures the APM agent rather than releases and source maps. We found no public information on a documented REST API, alerts on performance thresholds, or two-way issue tracker sync. 17 13 16 4 2 11 18
The Data Protection Officer
Twenty-five integrations are listed including Slack, PagerDuty, VictorOps, Jira OAuth, GitHub and GitLab plus webhooks, alerts can be configured per error group, new issues trigger email, and there is an APM daily digest and a Slack daily performance summary. AI fix suggestions are documented and the provider is named — OpenAI, available only on explicit opt-in — which is exactly the disclosure I look for. I found no public information on a documented REST API or two-way tracker sync, and the command line documented is for configuring the APM agent, not for releases and source maps. 2 4 11 13 15 16 17
The Skeptic
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. 17 2 18 16 11 15
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
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. 6 12 14 19 20
The SaaS CTO
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. 19 12 20 14 11 15 7
The Mobile Team Lead
Credit card details and other sensitive data can be filtered out at code level before anything is sent, IP address collection can be disabled, trace sampling is set per trace or per URL, discarded instances of ignored errors do not count toward the quota, and PII plus identified users can be permanently deleted on request with everything deleted on cancellation. We found no public information on server-side scrubbing rules, retention durations per plan, or spike protection; the terms say only that excessive usage is charged based on usage and an upgrade may be requested. 7 11 12 14 15 19 20
The Site Reliability Engineer
Sensitive data can be filtered out before sending — a credit-card example is given — with code-level PII scrubbing across all providers, IP collection that can be disabled, deletion of PII and known users, and APM sampling per trace or per URL; discarded occurrences of ignored errors are stated not to count toward the error quota. A retention period is stated to exist without figures per plan, and we found no public information on server-side scrubbing rules or spike protection; excessive usage is charged rather than capped. 19 12 7 20 14 11
The Data Protection Officer
Developers control what is sent, sensitive fields can be filtered out before sending in all providers, IP collection can be disabled per plan, data is removed from online storage and backups when retention expires or on manual deletion, identified users and their PII can be permanently deleted, and trace sampling is fully controllable per trace or per URL with discarded occurrences exempt from the quota. All documented scrubbing happens before events are sent; I found no public information on server-side scrubbing rules, retention durations per plan, or a self-hosted edition. 7 12 14 19 20
The Skeptic
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. 19 12 7 20 14 11
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
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. 1 7 9 13 21 22
The SaaS CTO
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. 22 21 7 1 9 13
The Mobile Team Lead
SAML2 single sign-on with enforcement for all members and auto-provisioning is documented per identity provider, TOTP two-factor authentication and granular team permissions exist, an audit log records grouping changes and merged groups, independent penetration tests run every six months, and the public status page shows ingestion, search and the database as monitored components. The certifications named are HIPAA, GDPR, CCPA and PCI; we found no public information on SOC 2 or ISO 27001, SCIM provisioning, or a published SLA with credits beyond custom SLAs on Enterprise. 1 6 7 9 13 21 22
The Site Reliability Engineer
SAML2 single sign-on with named identity providers, enforcement for all members and TOTP two-factor are documented, alongside granular team permissions, TLS, encrypted storage, third-party pentests every six months, a public status page with monitored components, and HIPAA compliance with a BAA offered. The audit log shown covers grouping changes only, we found no public information on SCIM provisioning, ISO 27001 or SOC 2, a published SLA with credits, or SDK behaviour during vendor outages, and the status history captured shows a single week of days. 21 22 7 1 9 13 6
The Data Protection Officer
SAML2 single sign-on is documented with named identity providers, organisation-wide enforcement and auto-provisioning, TOTP two-factor authentication, granular team permissions, TLS in transit and encrypted storage, third-party pentests every six months, and a public status page with monitored components. I found no public information on ISO 27001 or SOC 2 with stated scope, SCIM provisioning, a published SLA with credits, a vulnerability disclosure programme, or documented SDK behaviour when the vendor itself is down. 1 7 9 13 21 22
The Skeptic
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. 7 21 22 9 6
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
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. 7 11 12
The SaaS CTO
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. 11 12 7
The Mobile Team Lead
Raygun Limited is a New Zealand company and the terms are governed by New Zealand law, with US customers possibly paying Raygun Incorporated; hosting is on Amazon Web Services with no region stated. We found no public information on an EU data region, a published data processing agreement, or named subprocessors beyond unnamed third-party vendors and hosting partners — for our Hamburg compliance review that is the deciding gap, even with the GDPR commitments and custom privacy arrangements on request. 7 8 11 12
The Site Reliability Engineer
Raygun Limited is a New Zealand company, the terms are governed by New Zealand law and US customers may be directed to pay Raygun Incorporated; hosting is on Amazon Web Services with no region stated and the third-party vendors are not named. The privacy policy states GDPR commitments, PII deletion and custom arrangements on request, but we found no public information on an EU data region, a published data processing agreement, or a subprocessor list with locations. 11 12 7
The Data Protection Officer
The contracting entity is Raygun Limited, a New Zealand company under New Zealand law, with US customers possibly paying Raygun Incorporated, hosting on Amazon Web Services with no region stated, and OpenAI named as the third-party AI provider. I found no public information on an EU data region, a data processing agreement, or a subprocessor list — without a DPA and a named chain, nothing of ours would go into production. 7 11 12
The Skeptic
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. 11 12 7
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 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. 3 6 11 21
The SaaS CTO
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". 6 21 3 11 4
The Mobile Team Lead
An on-demand rate of $0.001 per error, a 33% annual saving, 60% saved by reserved events versus on-demand, and a $50 per month single sign-on add-on are public, alongside a 14-day trial without a credit card, unlimited apps and team members, and annual monthly-payment locking you in for twelve months. We found no public information on plan prices with their included volumes, VAT terms, or retention pricing; Enterprise is contact sales, and the terms state only that excessive usage is charged based on usage. 3 6 11 21 22
The Site Reliability Engineer
The pricing page publishes an on-demand rate of "$0.001 per error", a 33% annual saving, 60% savings on reserved events versus on-demand, and SAML SSO as a "$50/month" add-on that is free on Business and Enterprise; the terms state USD billing, the 12-month commitment when paying monthly on an annual plan, late-payment interest and price changes on 7 days' notice. We found no public information on the dollar price and volume limits of each plan tier, retention pricing or VAT, and the Enterprise tier is "Talk to us". 6 11 21
The Data Protection Officer
Public figures exist: on-demand errors at $0.001 per error, 60% savings on reserved events versus on-demand, a 33% annual discount, a 14-day free trial with no credit card required, and SAML SSO free on Business and Enterprise or $50/month as an add-on, billed in US dollars. I found no public information on the individual plan prices or retention pricing, and Enterprise is "Talk to us Custom", so a full annual cost cannot be computed from the captured pages. 3 6 11 21
The Skeptic
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. 6 11 21
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 |
Incorporated in NZ
unverified
Why unverified?The Terms direct US-based customers to pay Raygun Incorporated, so a related US billing entity exists, but the contracting entity throughout the documents is the New Zealand company. |
0/2 pts | 12 Report an error |
|---|---|---|---|
| Hosting location |
Not determined
unverified
Why unverified?Not confirmed on the vendor’s own pages as captured. |
— | uncited Report an error |
| Hosting options | Not determined | — | uncited Report an error |
| Open source | Not determined | — | uncited Report an error |
| Data processing agreement |
Not determined
unverified
Why unverified?Not confirmed on the vendor’s own pages as captured. |
— | uncited Report an error |
| Transfer impact assessment | Not determined | — | uncited Report an error |
Questions about Raygun
Is Raygun European?
No. whats-best.ai classifies Raygun as Rest of world. Its vendor, Raygun Limited, is incorporated in New Zealand, per the vendor’s page captured 6 Nov 2026.
Where does Raygun store data?
Not stated on the vendor’s pages as of 6 Nov 2026.
Does Raygun have a free plan?
Not stated on the vendor’s pages as of 6 Nov 2026.
What are the best alternatives to Raygun?
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: Raygun 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 — Legal entity. The Terms direct US-based customers to pay Raygun Incorporated, so a related US billing entity exists, but the contracting entity throughout the documents is the New Zealand company.
- Weak sourcing — Hosting location, Data processing agreement. 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.
- 20 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
- 13 pricing 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
- 9 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
- 8 legal 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
- 5 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
- 4 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
- 2 hosting 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 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 sovereignty dimensions could not be confirmed on the vendor’s own pages and are 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 raygun.com Checked 6 Nov 2026 Details →
- 2 Features page (crash reporting) raygun.com Checked 6 Nov 2026 Details →
- 3 Features page (APM) raygun.com Checked 6 Nov 2026 Details →
- 4 Features page (real user monitoring) raygun.com Checked 6 Nov 2026 Details →
- 5 Documentation raygun.com Checked 6 Nov 2026 Details →
- 6 Pricing page raygun.com Checked 6 Nov 2026 Details →
- 7 Security / trust page raygun.com Checked 6 Nov 2026 Details →
- 8 GDPR page raygun.com Checked 6 Nov 2026 Details →
- 9 Public status page status.raygun.com Checked 6 Nov 2026 Details →
- 10 About page raygun.com Checked 6 Nov 2026 Details →
- 11 Terms of service (names the operating company) raygun.com Checked 6 Nov 2026 Details →
- 12 Privacy policy raygun.com Checked 6 Nov 2026 Details →
- 13 Error capture, grouping & triage — found from sitemap raygun.com Checked 6 Nov 2026 Details →
- 14 Error capture, grouping & triage — found from sitemap raygun.com Checked 6 Nov 2026 Details →
- 15 APM, tracing & profiling — found from sitemap raygun.com Checked 6 Nov 2026 Details →
- 16 APM, tracing & profiling — found from sitemap raygun.com Checked 6 Nov 2026 Details →
- 17 Alerting, integrations & developer workflow — found from sitemap raygun.com Checked 6 Nov 2026 Details →
- 18 Alerting, integrations & developer workflow — found from sitemap raygun.com Checked 6 Nov 2026 Details →
- 19 Data scrubbing, retention & volume control — found from sitemap raygun.com Checked 6 Nov 2026 Details →
- 20 Data scrubbing, retention & volume control — found from sitemap raygun.com Checked 6 Nov 2026 Details →
- 21 Access control, security & the vendor's reliability — found from sitemap raygun.com Checked 6 Nov 2026 Details →
- 22 Access control, security & the vendor's reliability — found from sitemap raygun.com Checked 6 Nov 2026 Details →