Name: New Relic
Brand: New Relic

Published Oct 23, 2026

01Common complaints

1) If the organization needs to provide full troubleshooting access to a very large population of engineers at minimal per-seat cost - New Relic’s full platform user pricing can become a significant expense; some competitors provide more permissive user-access models. 2) If the organization has low maturity for cost governance - Usage-based ingest plus optional compute and feature toggles require financial and technical discipline. Organizations without that discipline may encounter unexpectedly high bills. 3) If the organization needs a simple, narrow toolset - Teams that only require uptime or basic infrastructure monitoring may find lighter-weight, lower-cost monitoring suites easier to operate. 4) If the organization requires a fully self-hosted deployment model for observability data - New Relic is primarily a SaaS offering; organizations with strict self-hosting requirements should consider alternatives that support on-premise deployments. 5) If the organization prefers specialized, single-purpose tools rather than an integrated platform - New Relic provides capabilities across telemetry domains; however, some teams prefer best-of-breed tooling focused on a single pillar (e.g., dedicated error tracking or dedicated log analytics).

Deal disqualifiers (poor fit)

The organization requires broad, low-cost troubleshooting access for a very large population of engineers under strict per-seat budget constraints
The organization cannot implement cost governance for usage-based ingest and add-on compute
The organization requires a primarily self-hosted, open-source-first observability stack with minimal vendor-managed data

Publicly visible limitations / risks

- **Pricing volatility risk:** frequently reported by users; the pricing model includes multiple cost levers (ingest, users, add-ons) - **Seat-limited Standard edition for full platform users:** Standard caps at 5 full platform users (per the pricing page) - **Deployment/documentation gaps reported by some users:** issues with outdated guides and agent setup have been reported - **Status incidents do occur:** the public status page documents recent alerting and ingestion/query irregularities in January 2026

Roadmap visibility

Roadmap visibility was not fully assessed in this research pass. Buyers should obtain roadmap and deprecation policy details from vendor sales, with specific attention to agent strategy (proprietary agents versus OpenTelemetry).

02Why they buy

Unique selling points supported by evidence in sources

- **Free tier with substantive included ingest** and a limited number of full platform users (as described on the official pricing page) - **Published ingest pricing** ($/GB) and documented user tiers on the pricing page - **NRQL** is frequently cited in reviews as a flexible query language used for custom analysis and dashboarding - **Native OTLP ingest** and an alignment with OpenTelemetry tooling in documentation and distributions

Areas where competitors may have an advantage

- **Dynatrace:** markets automated discovery, dependency mapping, and AI-assisted RCA and may position itself as having fewer per-user access limitations - **Datadog:** perceived market strength in integrations and SaaS polish, though pricing can escalate - **Grafana ecosystem / OSS-first:** provides more open and modular architectures and potentially lower licensing costs for organizations capable of self-hosting and operating the stack

03Field reports

Note on methodology: Review sites often contain a mix of incentivized and non-incentivized reviews, and many are sourced via seller invites. Individual quotes are directional signals rather than statistical proof.

G2 (examples)

**Positive themes (ease of use, integrated visibility, NRQL):** - Some reviewers note comprehensive observability capabilities and an intuitive user interface, and report use for real-time monitoring and alerting. - NRQL, the product's query language, is frequently cited as a flexible mechanism that can reduce troubleshooting time. **Negative themes (pricing, complexity, learning curve, performance):** - Reviewers commonly report that costs can increase unexpectedly with usage growth. - Users report a relatively steep learning curve and occasional complaints about interface complexity and dashboard performance with large datasets.

Capterra (examples)

**Positive:** - Some reviewers indicate synthetic checks and alerting functionality meet their needs. **Negative / critical:** - For large enterprise environments the licensing model has been reported as problematic, especially when access is user-based. - Reports include challenges during deployment (agent installation problems, outdated documentation in some cases), limited self-service account closure, and restricted support access for lower tiers. Capterra aggregates reviewer themes indicating that pricing can be a limiting factor for smaller organizations.

Community / Reddit (examples)

Community discussion includes comments from organizations that found the functionality useful but faced challenges with pricing changes and higher per-user costs for full platform access.

What customers say they chose it for (recurring)

Integrated telemetry across APM, infrastructure, logs, and tracing
NRQL for flexible querying and dashboarding
Alerting, synthetics, and workflows to support troubleshooting

Why some customers leave / hesitate (recurring)

Cost unpredictability (data ingest variability + user licensing)
Complexity and onboarding (feature breadth can overwhelm some teams)
Implementation friction in certain environments (agent install, discovery gaps, documentation issues reported by some)

Availability of quantified case studies

This research pass did not exhaustively inventory the vendor’s case study library; vendor pages reference well-known commercial customers across retail, travel, and consumer services. These references are vendor-published and are not the same as independently audited case studies.

Methodology caveat

Vendor-published outcomes (MTTR reduction, uptime improvements, cost savings) are common in product literature but often lack methodological disclosure (baseline, sample size, confounders). Procurement teams should request:
- definitions for pre/post metrics
- time windows used for measurement
- any control group or baseline comparisons
- assumptions about instrumentation completeness

Example of evidence-adjacent performance claims

Press materials may cite high customer ratings on third-party sites and vendor or analyst "Leader" positions. Such signals reflect market perception; they are not standalone proof of ROI.

04Best fit

Company size (practical guidance)

Best fit: Mid-sized through large organizations with multiple services and a need to standardize observability across teams.
Also viable: Startups and SMBs that can remain within the free tier or tightly control ingest and limit full platform seats.

Industries

Adoption is common in software-driven industries: SaaS, fintech, ecommerce, media, logistics, and travel—sectors where uptime and digital experience have direct business impact.

Roles/personas

Decision makers: VP Engineering, Head of SRE/Platform, CTO, IT Ops leadership
End users: SREs, platform engineers, backend engineers, DevOps, incident commanders, QA leads (synthetics)

Pain points addressed

Reducing MTTR through correlated telemetry
Increasing service reliability and refining alert quality
Monitoring customer experience via browser/mobile monitoring and synthetics
Consolidating multiple telemetry tools into a single vendor platform

Qualification criteria (practical fit)

Organizations should be able to invest in telemetry governance (sampling, log filtering, retention discipline)
Staff should be able to learn NRQL and develop shared dashboards/alerts
The organization should prioritize an integrated platform over stitching multiple best-of-breed tools

05The pitch

What the product does (objective value proposition)

New Relic is a full-stack observability platform used to collect, store, query, and correlate telemetry data (metrics, logs, traces, events) to monitor application performance, infrastructure health, digital experience, and operational reliability. It provides a broad set of capabilities including APM, infrastructure monitoring, browser/mobile monitoring, synthetics, alerting, dashboards, AIOps features, and increasing emphasis on AI-assisted workflows.

Target market and positioning

- **Primary buyers/users:** SRE/Platform Engineering, DevOps, application engineering, IT operations, security teams (including combined security and observability use cases) - **Common deployment context:** Mid-market through enterprise organizations with multiple services/environments; also accessible to small teams via a free tier - **Positioning themes (as evidenced by pricing and marketing pages):** - Integrated platform across telemetry types and workflows - Usage-based pricing for data ingest plus per-user licensing for core/full platform users and optional compute add-ons - Broad integration ecosystem and quickstarts

Get a comprehensive analysis of New Relic including market position, competitive landscape, adoption trends, and peer benchmarks.

Download full report →