New Relic APM & Errors Inbox

Rest of world Report an error

Panel rating · 6 judges · How to read the stars

Category median

Sovereignty: 2 of 6 dimensions proven

0–5 in half steps. 5 means the rubric's top anchor is met on the evidence.

by New Relic, Inc. · newrelic.com

Report an error on this page Is this your product? →

Link to this page

New Relic APM & Errors Inbox: AI-assisted analysis on whats-best.ai New Relic APM & Errors Inbox: AI-assisted analysis on whats-best.ai (dark)

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.

New Relic APM & Errors Inbox at a glance

Vendor
New Relic, Inc.
Headquarters
Not stated on the vendor’s pages as of 6 Nov 2026
Data hosting
Outside the EU by default source, captured 6 Nov 2026
Free plan
Yes, per the vendor’s own page source, captured 6 Nov 2026
Panel verdict
The AI panel rates New Relic APM & Errors Inbox 2.5/5, the mean of 6 judges. New Relic's APM and errors inbox scores highest on pricing transparency and performance tracing (7 with no spread). how scores are made
As of
Vendor pages captured 6 Nov 2026; evaluated by the panel 6 Nov 2026. all sources

New Relic APM & Errors Inbox alternatives, European ones first →

Read this page as one judge. Each weighs the same scores by what they care about.

The panel's verdict

New Relic's APM and errors inbox scores highest on pricing transparency and performance tracing (7 with no spread). The judges could largely compute the bill from public pages — 100 GB of free ingest per month that stops at the cap, $0.40/GB beyond or $0.60/GB with Data Plus, Standard full users at $10 for the first and $99 for each additional up to five, Pro at $349/user on annual commitment or $418.80/user monthly — and found transaction traces, distributed traces linked to each error group, full OpenTelemetry ingestion and machine-learning anomaly detection all documented. The weakest marks are security and reliability at a flat 4, with data controls, workflow and integrations, and sovereignty at 4–5: the judges found no public information on single sign-on, two-factor authentication, audit logs or an availability SLA, and the vendor's documentation itself states role restrictions are enforced only in errors-inbox comments. The only spread wider than a point is error tracking, where the mobile lead, citing no public information on symbolication for iOS, Android or Flutter, scored two points below the SaaS CTO.

Report an error

Speaks for it

  • Agents for Go, Java,.NET, Node.js, PHP, Python and Ruby plus full OpenTelemetry ingestion are documented
  • Each error occurrence carries its stack trace, distributed trace, logs in context and error attributes
  • Public prices cover most of the bill, including 100 GB free monthly ingest then $0.40/GB and the free tier's stated stop at the cap
  • The free tier requires no credit card and includes one free full platform user with unlimited free basic users
  • A public status page breaks out Data Ingest, Alert Notifications and UI components across the United States, Europe and Japan regions

Report an error

Held against it

  • We found no public information on single sign-on, two-factor authentication, audit logs, encryption statements or an availability SLA
  • The vendor's documentation states role restrictions are enforced only in errors-inbox comments, so read-only users can change error group states
  • The notifications category lists six destinations without naming any, and we found no public information on paging destinations or two-way issue-tracker sync
  • The data centre documentation states customer data may be temporarily processed outside the chosen region, that New Relic may access and process it in the United States, and that Systems Operations Data is stored in the US for all regions
  • We found no public information on configurable scrubbing rules, IP anonymisation, error and trace sampling, or a subprocessor list and data processing agreement

Report an error

Best for

  • You need to budget observability spend from public per-GB and per-user prices, with a free tier that stops at 100 GB rather than invoicing overage
  • You run web and backend services in Go, Java,.NET, Node.js, PHP, Python or Ruby and want one inbox linking each error to its traces and logs
  • You ingest via OpenTelemetry and want those traces alongside APM views, infrastructure metrics and Web Vitals benchmarking
  • Your team triages in Slack and assigns error groups to any email address, including people who are not users

Report an error

Avoid if

  • You need role enforcement throughout the errors inbox, since the documentation applies standard restrictions only to comments
  • You must guarantee data never leaves your chosen region, since the documentation reserves temporary out-of-region processing and US access and processing for support
  • Your operations cannot tolerate a stop at the ingest quota, since the free tier ceases ingest and platform access at 100 GB
  • Your data rules require scrubbing beyond credit-card and Social-Security patterns, which is the documented scope of default logs obfuscation

Report an error

The scores

Panel median The median of the judges’ scores per criterion. Each label opens its reasoning below.

Error capture, grouping & triage

Show 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.

Report an error

The Agency Tech Lead

The PHP agent plus the errors inbox documentation covers the triage my Laravel and Shopware teams need: fingerprint grouping with managed normalization of UUIDs, hex values and emails, custom grouping by attribute, resolve, ignore and regression states with version tracking, bulk status changes up to 2,000 groups, assignment to any email address, and per-occurrence stack traces with logs in context and linked traces. The captured pages do not show merge or split of groups, suspect commits or code owners, mobile symbolication or crash-free user counts, or local variables per frame, so it sits above the solid middle but well short of the top band. 3 4 6 7

Report an error

The SaaS CTO

Agents are documented for Go, Java,.NET, Node.js, PHP, Python and Ruby, and the errors inbox gathers APM, browser, mobile and AWS Lambda errors with stack traces, source maps, fingerprint grouping under managed normalisation rules, custom grouping by attribute, resolve/ignore/regression states, bulk status changes and occurrences broken down by deployment version — my triage basics, with assignment to teams and discussions kept in context. We found no public information on symbolication for mobile, merging or splitting groups, suspect commits or crash-free users, so it sits below the highest level. 3 4 6 7

Report an error

The Mobile Team Lead

Errors from APM, browser, mobile and Lambda monitoring land in one inbox, grouped by fingerprint with managed normalisation, custom groups via a named attribute, resolve/ignore/unresolve in bulk and regression tags — and occurrences counted per deployment version with resolution targeting a specific version is exactly what I need to halt a bad store rollout. The documented agents cover Go, Java,.NET, Node.js, PHP, Python and Ruby with browser source maps, but I found no public information on symbolication for iOS, Android or Flutter, on crash-free users or sessions, or on breadcrumbs and the last screens before a crash. 3 4 6 7

Report an error

The Site Reliability Engineer

Errors from APM, browser, mobile and AWS Lambda all land in one inbox, grouped by fingerprint with managed normalisation of UUIDs, hex values and email addresses, and custom grouping via a named error attribute is documented across the browser, Go, Java, Node.js,.NET, Python, Ruby and PHP agents. Resolve, ignore and regression states, bulk updates of up to 2,000 groups, assignment to any email address, occurrences per deployment version, and stack traces, source maps and distributed traces per occurrence are all documented. We found no public information on symbolication, crash-free users and sessions, local variables per frame or suspect commits, which keeps this off the top level. 3 4 6 7

Report an error

The Data Protection Officer

One inbox fed by the Go, Java,.NET, Node.js, PHP, Python, Ruby and browser agents, fingerprint grouping that normalises identifiers, custom grouping via a named attribute, resolve/ignore/regression states, occurrences per deployment version and bulk status updates reaches the middle level solidly. The captured pages carry no documentation of mobile SDKs with symbolication, merge or split of error groups, suspect commits, or per-frame local variables — the depth a member-portal team would want before standardising on it. 7 3 6 4

Report an error

The Skeptic

Agents cover the common web and backend languages plus browser and mobile sources, with fingerprint grouping that normalises UUIDs, hex values and email addresses, custom grouping, resolve/ignore/regression states, bulk triage up to 2,000 groups and occurrence counts per deployment version. I found no public information on mobile symbolication, crash-free users and sessions, or suspect commits, so this sits above the common-platform level but well short of what a large engineering organisation standardises on. 3 4 6 7

Report an error

APM, tracing & profiling

Show 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.

Report an error

The Agency Tech Lead

Transaction traces, response time and throughput views, database query analysis, external service monitoring, distributed trace waterfalls linked to the errors they caused, web vitals benchmarking, machine-learning anomaly detection with learned baselines and full OpenTelemetry ingestion are all documented, with infrastructure metrics and log patterns in the same APM views. We found no public information on code-level profiling, per-endpoint percentiles, background job or queue monitoring, or how trace sampling is configured and what it costs in fidelity, which is what keeps it off the top band. 2 4 6 7

Report an error

The SaaS CTO

Full OpenTelemetry support is documented alongside the agents, distributed tracing connects browser incidents to backend code and the errors inbox links a group to its traces, with slow-query analysis, machine-learning anomaly detection, infrastructure and Kubernetes views beside the APM data, SLO tracking and Web Vitals benchmarking in browser monitoring. That is the browser-click-to-slow-database-call story I need, but we found no public information on code-level profiling or configurable trace sampling with its effect explained. 2 4 6 7

Report an error

The Mobile Team Lead

Distributed traces with waterfall views are linked straight to their error groups, and transaction traces, database query analysis, external service call monitoring, Apdex, OpenTelemetry ingestion, baseline-learning anomaly detection and web vitals benchmarking are all documented, with infrastructure metrics beside it. I found no public information on code-level profiling or on configurable trace sampling and its effect. 2 4 5 6 7

Report an error

The Site Reliability Engineer

The trace-to-error link works in the direction I need at 3am: the error group view attaches the distributed-trace waterfall, logs in context and error attributes to a single occurrence, and distributed tracing is documented as connecting browser incidents to backend code. Transaction traces, database query analysis, external call monitoring, machine-learning anomaly detection on learned baselines, OpenTelemetry ingestion, entity dependency maps, infrastructure metrics inside APM, SLO tracking and Web Vitals benchmarking are all documented. We found no public information on per-endpoint percentiles, N+1 detection, background job monitoring, code-level profiling or configurable trace sampling, which holds this just below the upper level. 2 4 6 7

Report an error

The Data Protection Officer

Response time and throughput trends, transaction traces, database query analysis, external calls, Apdex, full OpenTelemetry support, distributed traces linked to the error that caused them, web vitals benchmarking, infrastructure metrics beside APM views, machine-learning anomaly detection and SLO tracking are all documented. I found no public information on code-level profiling or on configurable trace sampling and its effect, which is what I would check before letting member-portal traces leave our estate. 6 2 4 7

Report an error

The Skeptic

Transaction traces, database query analysis, distributed tracing linked to each error group, full OpenTelemetry support, anomaly detection with learned baselines, infrastructure metrics inside APM, SLO tracking and Web Vitals benchmarking are all documented, with agent overhead stated at under 3%. Code-level profiling, per-endpoint percentiles, background job monitoring and how trace sampling is configured are not described, which caps it below the top band. 2 4 6 7

Report an error

Alerting, integrations & developer workflow

Show 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.

Report an error

The Agency Tech Lead

Slack notifications with error detail, intelligent alerting with learned baselines and KPI alerts, deployment markers with error-spike rollback signals, an Atlassian Open DevOps integration, assignment and in-context discussions, and documented REST and GraphQL API endpoints per region give a workable day-to-day workflow. The captured pages do not show two-way issue tracker sync, per-project alert routing or an on-call destination by name, a CLI, or an AI assistant with its model provider and data handling named, so the developer workflow is mid-band. 3 4 5 7 8

Report an error

The SaaS CTO

Slack notifications with detailed error information, intelligent alerting that learns application behaviour, error groups assignable to a team or any email address, an Atlassian Open DevOps integration, telemetry in the IDE via CodeStream, REST and GraphQL endpoints published per region and eight hundred-plus quickstarts make a workable triage loop. We found no public information on on-call tool destinations, two-way issue tracker sync, webhooks, a CLI for releases and source maps, or which model powers the AI features. 2 3 5 6 7 8

Report an error

The Mobile Team Lead

Slack notifications carry detailed error information, error groups can be assigned to any email address even non-users, deployment markers and error-rate spikes after a change are documented, the REST and GraphQL APIs are published with EU endpoints, and the catalogue tops 800 integrations. I found no public information on alert rules for new, regressed or frequent errors, on two-way issue tracker sync beyond an Atlassian Open DevOps announcement, on webhooks, a CLI or weekly digests, and the AI features are named without a model provider. 2 3 4 5 7 8

Report an error

The Site Reliability Engineer

Slack notifications with detailed error information, intelligent alerting, assignment to any email address, the Atlassian Open DevOps link, an 800-plus integration catalog and documented REST and GraphQL endpoints per region give a workable daytime workflow. For the on-call path I found no public information naming PagerDuty, Opsgenie, Microsoft Teams or email as notification destinations, and none on issue-tracker creation and syncing, webhooks, a CLI, scheduled digests or AI error explanations with a model provider named. The six notification destinations in the catalog are not enumerated, so I cannot confirm paging from these pages. 3 5 6 7 8

Report an error

The Data Protection Officer

Slack notifications with error detail, an Atlassian Open DevOps integration, assignment of error groups to any user or email address, deploy tracking, and documented REST and GraphQL APIs with EU endpoints put this at the middle level. I found no public information naming a Jira, GitHub or GitLab sync, a CLI, scheduled digests, or the model behind the AI features, and the on-call destinations appear only as an unnamed category count. 7 3 5 9

Report an error

The Skeptic

Slack notifications with detailed error information, an 800+ integration catalogue with a dedicated notifications category, Atlassian Open DevOps for error tracking, documented REST and GraphQL API endpoints per region, assignment of error groups to any email address, in-context discussions and deployment tracking make a workable triage loop. Two-way issue tracker sync with GitHub, GitLab or Jira, a CLI, webhooks, scheduled reports and the model behind the AI features are not described on the captured pages. 3 5 7 8

Report an error

Data scrubbing, retention & volume control

Show 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.

Report an error

The Agency Tech Lead

Documented controls are default log obfuscation masking credit-card and Social-Security patterns, default retention of at least 8 days with 90 extra days via Data Plus, historical export under Data Plus, GDPR and CCPA data request handling, and a free tier that stops ingest at 100 GB after an alert at 85 percent. For shops that hold customer addresses that is thin: we found no public information on configurable scrubbing of request bodies or user data in the SDK or on the server, IP anonymisation, or error and trace sampling rules. 8 9

Report an error

The SaaS CTO

Retention is stated (at least 8 days by default, up to 90 days extra with Data Plus), the free tier caps at 100 GB with ingest and access ceasing plus an alert at 85 percent, logs are obfuscated by default for card and social security patterns, and Data Plus adds export to external destinations. We found no public information on configurable scrubbing rules, IP anonymisation, per-project retention, deletion of individual events, or a self-hosted edition. 9

Report an error

The Mobile Team Lead

Default logs obfuscation automatically masks credit-card and social-security patterns, retention is stated at at least 8 days with 90 more via Data Plus, and the free tier simply stops ingesting at 100 GB after a warning at 85% — a quota behaviour that never surprises an invoice. I found no public information on configurable scrubbing rules, IP anonymisation or sampling, and historical export sits behind the Data Plus bundle. 7 9

Report an error

The Site Reliability Engineer

Default logs obfuscation masks credit-card and Social-Security-number patterns, retention is stated as at least 8 days by default with up to 90 extra days on Data Plus, and quota behaviour is explicit: an email and onscreen alert at 85% of the 100 GB free monthly ingest, ingest and access ceasing at 100 GB, plus Feature Control Manager to switch capabilities off and control spend. Expected-error filtering and Data Plus export are documented. We found no public information on SDK-side or custom server-side scrubbing rules, IP anonymisation, error or trace sampling, filters that drop events before they count, or a self-hosted edition. 7 9

Report an error

The Data Protection Officer

Default obfuscation automatically masks credit-card and Social-Security patterns in logs, retention is stated (at least 8 days by default, up to 90 extra days with Data Plus), and the free tier alerts at 85% of the 100 GB and then stops ingesting rather than invoicing us. I found no public information on configurable server-side scrubbing rules, IP anonymisation, SDK-side scrubbing, or sampling of errors and traces — the controls I require before a member number or IBAN can travel in a stack trace or request body. 9 8

Report an error

The Skeptic

Retention is stated (at least 8 days by default, up to 90 days extra with Data Plus while error groups are stored long term), the free tier hard-stops at 100 GB with an alert at 85%, and logs are obfuscated by default for credit-card and Social Security number patterns. What I look for first is missing: configurable scrubbing rules, IP anonymisation, per-project sampling and deletion of individual events are not described, and data export requires the Data Plus option. 7 9

Report an error

Access control, security & the vendor's reliability

Show 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.

Report an error

The Agency Tech Lead

A public status page with regional components and status history, a Trust Center, FedRAMP Moderate and HIPAA eligibility under Data Plus, and published support response times per edition are good signs of a vendor that survives an audit conversation. But two-factor authentication, single sign-on, encryption in transit and at rest, audit logs and an availability SLA are not described on the captured pages, and the errors inbox documentation states role restrictions are enforced only for comments, meaning read-only users can change error group states — a real concern when each client is a separate project. 7 9 10 11

Report an error

The SaaS CTO

A public Trust Center, a status page with per-region components, status history and subscription, edition-based support response commitments (a one-hour critical initial response for Enterprise), and roles such as read-only and standard are on the record — though the errors inbox documentation states those role restrictions are enforced only in the comments feature. We found no public information on two-factor authentication, single sign-on and SCIM, audit logs, encryption statements, or certifications with their scope. 7 9 10 11

Report an error

The Mobile Team Lead

A public trust centre, a public status page with per-region components, status history and update subscription, FedRAMP Moderate and HIPAA eligibility with Data Plus, GDPR/CCPA request handling and per-tier support response SLAs are documented. But the errors inbox documentation itself states that role restrictions are only enforced in the comments feature — with rotating on-call across our six-person team I want granular enforcement everywhere — and I found no public information on single sign-on, two-factor authentication, audit logs, encryption or an availability SLA. 1 7 9 10 11

Report an error

The Site Reliability Engineer

The status page is genuinely operational — public, broken out by Data Ingest, Alert Notifications and UI components across United States, Europe and Japan regions, with status history and subscriptions — and support response times are published per edition (1-hour critical for Enterprise, 2-hour for Pro, 2 business days for Standard), with a Trust Center and FedRAMP Moderate and HIPAA eligibility stated with Data Plus. We found no public information on single sign-on, SCIM, two-factor authentication, audit logs, encryption statements or an availability SLA with credits. The documentation itself notes that role restrictions are enforced only in errors inbox comments, so read-only users can assign and update error group states — a finding an auditor would flag. 7 9 10 11

Report an error

The Data Protection Officer

There is a public status page with per-component status and history for the United States, Europe and Japan, a trust centre, and FedRAMP Moderate and HIPAA eligibility with Data Plus. I found no public information on single sign-on, two-factor authentication, audit logs, encryption in transit and at rest, or ISO 27001/SOC 2, and the errors inbox documentation itself states role restrictions are enforced only in comments, so read-only users can assign errors and change group states — a finding I would raise in any audit. 11 10 9 7

Report an error

The Skeptic

There is a public status page with per-region components, a viewable status history and subscription to updates, a New Relic Trust Center exists, FedRAMP Moderate and HIPAA eligibility are stated with Data Plus, and support response SLAs are published per edition. Single sign-on, two-factor authentication, audit logs, encryption statements and an availability SLA are not described on the captured pages, and the documentation itself states role restrictions are only enforced in the comments feature of the errors inbox. 7 9 10 11

Report an error

European sovereignty panel opinion

Show 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.

Report an error

The Agency Tech Lead

An EU data centre is selectable at sign-up for an additional $0.05/GB per month with full feature availability, but the US is the default region, New Relic may access and process Customer Data in the United States, customer data may be temporarily processed outside the chosen region, and Systems Operations Data is stored in the US for all regions. The contracting entity is the US corporation with New Relic International Limited as EU representative; the subprocessor list, a published data processing agreement and the named hosting infrastructure are unknown on the captured pages, so the chain is only partly European. 8 9

Report an error

The SaaS CTO

An EU region is selectable at sign-up with EU user interface, API and source-map endpoints and full feature availability, at a stated surcharge of $0.05/GB per month, which is what my enterprise customers ask about. The captured pages, though, state New Relic may access and process customer data in the United States, that systems operations data is stored in the US region for all available regions, and that data may be temporarily processed outside the chosen region; the vendor is a Delaware corporation, and we found no public information listing subprocessors or a data processing agreement. 8 9

Report an error

The Mobile Team Lead

An EU region is selectable at sign-up for an additional $0.05/GB per month, with EU endpoints for the UI and APIs, and New Relic International Limited is named as EU representative of a Delaware corporation headquartered in San Francisco. The same documentation states New Relic may access and process Customer Data in the United States and other affiliate jurisdictions, Systems Operations Data is stored in the US for all regions, and AI features vary by region — and I found no public information on the subprocessor list or a published data processing agreement. 8 9

Report an error

The Site Reliability Engineer

An EU region is selectable at sign-up for an extra $0.05/GB per month with full feature availability, New Relic International Limited is the EU representative, and the US is the default region; the captured pages also state that Customer Data is stored in the selected region but may be temporarily processed outside it, that New Relic may access and process Customer Data in the United States, and that Systems Operations Data is stored in the US for all regions. GDPR and CCPA personal data request handling is described. We found no public information on the subprocessor list, the data processing agreement, or where the AI features run beyond a note that AI capability varies by hosting region. 8 9

Report an error

The Data Protection Officer

An EU region is selectable at sign-up regardless of where we sit, for an additional $0.05/GB per month, and the documentation states customer data is stored in the chosen region. The same documentation reserves access and processing of customer data in the United States for support and other purposes, says data may be temporarily processed outside the chosen region, and stores systems operations data in the US for all regions, and I found no public information on the subprocessor list, the named hosting infrastructure, or a published data processing agreement. 8 9

Report an error

The Skeptic

An EU region is selectable at sign-up for an extra $0.05/GB per month, with its own UI and API endpoints, but the vendor is a US company and the same documentation states New Relic may access and process Customer Data in the United States, that systems operations data is stored in the US for all regions, and that data may be temporarily processed outside the chosen region. The captured pages list no subprocessors and show no data processing agreement, so the chain is only partly visible. 8 9

Report an error

Pricing transparency

Show 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.

Report an error

The Agency Tech Lead

The public pricing page gives real numbers: 100 GB of free data ingest per month that ceases at the cap after an alert at 85 percent, $0.40/GB beyond, $0.60/GB with Data Plus, $10 for the first full platform user and $99 for additional users on Standard capped at five users, $349/user on annual commitment or $418.80/user monthly on Pro, core users at $49, 500 synthetic checks with extras at $0.005 per check, no host or egress charges, and the EU data centre at $0.05/GB per month. We found no public information on the Enterprise edition price or VAT, and Japan-region pricing is contact sales, so the exact annual cost is not fully computable from the public pages. 8 9

Report an error

The SaaS CTO

Prices are unusually public: user-based tiers ($10/first user and $99/additional user on Standard, $349/user for annual commitments or $418.80/user monthly pay-as-you-go on Pro), 100 GB of free data ingest per month with $0.40/GB ingested beyond and $0.60/GB for Data Plus, a $0.05/GB per month EU surcharge, extra synthetic checks at $0.005 per check, and the behaviour at the quota spelled out for the free tier. Japan-region pricing is contact sales, and we found no public information on VAT treatment or a volume calculator, so the final annual figure still needs a question or two. 8 9

Report an error

The Mobile Team Lead

User prices are public per edition (standard $10/first user and $99/additional user, pro $349/user for annual commitments or $418.80/user monthly pay as you go), ingest beyond the 100 GB free is $0.40/GB (Data Plus $0.60/GB), the EU data centre costs $0.05/GB per month and extra synthetic checks $0.005 per check, with the free tier's stop-at-100-GB behaviour stated — enough to budget our six-person team. VAT is not stated, Japan pricing is contact-sales only, and Enterprise terms are commit contracts. 8 9

Report an error

The Site Reliability Engineer

A buyer can compute most of the bill: 100 GB free ingest then $0.40/GB, or $0.60/GB with Data Plus for the longer retention; Standard full users $10 first and $99 additional up to five users; Pro $349/user for annual commitments or $418.80/user monthly pay as you go; core users $49; unlimited free basic users; 500 synthetic checks then $0.005 per check; EU hosting at an extra $0.05/GB per month; no egress fees; and the free-tier behaviour at the quota is stated outright. Enterprise commitment pricing, Japan-region pricing (contact sales) and VAT are not stated, ingest cost varies by region, and we found no public information on whether paid-tier overage is capped. Close to fully computable, held back by those gaps. 8 9

Report an error

The Data Protection Officer

The pricing page publishes the free tier with its 100 GB and the stated behaviour at the cap, per-GB overage rates ($0.40/GB original data, $0.60/GB Data Plus), per-user prices for Standard, Pro and pay-as-you-go ($349/user annual commitment, $418.80/user monthly), the EU region surcharge, and synthetic checks at $0.005 per check. Japan-region pricing is contact sales, ingest costs vary by region, and I found no public information on VAT or on the Enterprise edition's price, which keeps the annual figure from being fully computable. 9 8

Report an error

The Skeptic

This is unusually computable: 100 GB free per month with a documented hard stop (ingest and access cease until upgrade or next month), $0.40/GB beyond on original data, $0.60/GB for the Data Plus option, full platform users at $349/user for annual commitments or $418.80/user monthly pay as you go, synthetics at $0.005 per check beyond 500, and the EU data center priced at $0.05/GB per month. Gaps remain: ingest costs "may vary depending on your data center region" without a table, Japan pricing is contact sales, and VAT, Enterprise pricing and cancellation terms are not stated. 8 9

Report an error

European sovereignty — proven facts

2 of 6 dimensions proven

Built only from facts shown on the vendor's own pages. A dimension we could not prove is left open, not scored as zero.

Hosting location Outside the EU unverified
Why unverified?

An EU region is selectable at sign-up (for an extra $0.05/GB per month per S5), and S4 states New Relic may access and process Customer Data in the United States and other jurisdictions where it has affiliates.

0/4 pts 8 Report an error
Hosting options EU region selectable unverified
Why unverified?

The region choice applies within New Relic's hosted service; no self-hosted or on-premises option appears in the excerpts, and EU hosting costs extra.

1/1 pts 8 Report an error
Open source Not determined — uncited Report an error
Data processing agreement Not determined — uncited Report an error
Transfer impact assessment Not determined — uncited Report an error

Questions about New Relic APM & Errors Inbox

Is New Relic APM & Errors Inbox European?

No. whats-best.ai classifies New Relic APM & Errors Inbox as Rest of world.

Where does New Relic APM & Errors Inbox store data?

New Relic APM & Errors Inbox stores customer data outside the EU by default, per the vendor’s page captured 6 Nov 2026.

Does New Relic APM & Errors Inbox have a free plan?

Yes. New Relic APM & Errors Inbox has a free plan, per the vendor’s page captured 6 Nov 2026.

What are the best alternatives to New Relic APM & Errors Inbox?

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: New Relic APM & Errors Inbox alternatives.

Where this could be wrong

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.

Sources (11)

The pages every claim on this page was read from — each one checked, dated, and kept verifiable.

  1. 1 Vendor homepage newrelic.com Checked 6 Nov 2026 Details →
  2. 2 Features page (APM) newrelic.com Checked 6 Nov 2026 Details →
  3. 3 Features page (error tracking) newrelic.com Checked 6 Nov 2026 Details →
  4. 4 Features page (browser monitoring) newrelic.com Checked 6 Nov 2026 Details →
  5. 5 Integrations page newrelic.com Checked 6 Nov 2026 Details →
  6. 6 Documentation (APM) docs.newrelic.com Checked 6 Nov 2026 Details →
  7. 7 Documentation (errors inbox) docs.newrelic.com Checked 6 Nov 2026 Details →
  8. 8 Documentation (data centre regions) docs.newrelic.com Checked 6 Nov 2026 Details →
  9. 9 Pricing page newrelic.com Checked 6 Nov 2026 Details →
  10. 10 Security / trust page trust.newrelic.com Checked 6 Nov 2026 Details →
  11. 11 Public status page status.newrelic.com Checked 6 Nov 2026 Details →