
Application Performance Monitoring
Fast & Cost-Effective APM with AI-based sampling. Runs On-Prem with no traces data sent out of your cloud.

Application Performance Monitoring
Fast & Cost-Effective APM with AI-based sampling. Runs On-Prem with no traces data sent out of your cloud.
Enter your data volume, team size, and usage. See an instant New Relic monthly billing estimate and how it compares to CubeAPM.
| Component | New RelicNR | CubeAPMCube |
|---|---|---|
| Data Ingest | $0 | $0.15/GB |
| Users | $0 | $0 · Unlimited |
| Synthetics | $0 | Included |
| Add-Ons | $0 | $0 |
| Infra (in-VPC) | $0 · NR managed | $0.02/GB |
| Cloud Data-Out | $0 | $0 · in-VPC |
| Total / Month | $0 | $0 |
Runs entirely inside your own AWS / GCP / Azure account — your data never leaves your infrastructure. No per-user fees, no egress costs, no add-on paywalls.
No per-user fees. No data-out charges. Flat per-GB rate with everything included — running inside your own cloud.
Estimates based on publicly available New Relic list pricing, verified February 2026. Actual bills vary by contract terms and volume discounts. Always verify at https://newrelic.com/pricing. This calculator is not affiliated with or endorsed by New Relic, Inc.
To give feedback or report any discrepancy, reach out to [email protected]
This calculator allows you to model New Relic pricing based on expected telemetry volume, usage patterns, number of users and scale. By adjusting inputs to reflect real production behavior, teams can estimate how costs evolve as infrastructure, traffic, and observability coverage grow.
The calculator is especially useful for pre-scale planning, budgeting discussions with FinOps teams, and evaluating cost impact before enabling additional monitoring features.
New Relic pricing is multi-dimensional, which includes separate pricing based on ingestion volume, user access levels, and compute consumption, instead of a single flat subscription fee.
As organizations expand observability coverage across services, infrastructure, browser monitoring, and distributed tracing, multiple cost dimensions begin to scale simultaneously.
Understanding these underlying cost drivers is essential before evaluating the Free, Standard, Pro, and Enterprise tiers in detail.
New Relic’s core billing for telemetry (metrics, traces, logs, events) is usage-based. You pay based on how much data you ingest and store.
For its ingestion pricing, there are two clearly defined options: Original data ingest and Data Plus data ingest. Each edition, Free, Standard, Pro, and Enterprise, follows the structure shown below.
Free | Standard | Pro | Enterprise | |
Option 1: Original data ingest | 100 GB free | $0.40/GB beyond the free 100 GB limit | $0.40/GB beyond the free 100 GB limit | Contact Sales |
Option 2: Data Plus data ingest | Not available | $0.60/GB beyond the free 100 GB limit | $0.60/GB beyond the free 100 GB limit | Contact Sales (includes FedRAMP Moderate and HIPAA eligibility) |
Free: This tier is designed for early experimentation or low-volume workloads.
Standard: Standard ingestion is suitable for production workloads with predictable data growth.
Under this model,
Here, cost scales linearly with telemetry growth. If a team ingests:
This becomes material in log-heavy or microservices environments.
Pro: The cost is the same as Standard.
Pro retains the same per-GB ingestion rate as Standard for original data ingest, but unlocks additional platform capabilities (covered in other pricing sections).
Pro customers ingest more telemetry due to:
In high-scale environments, ingestion becomes the dominant cost driver.
Enterprise: Enterprise ingestion pricing is not publicly listed. Organizations must request a custom quote. Pricing is contract-based and may include negotiated ingestion commitments, volume discounts, and bundled features.
Data Plus is positioned as a higher-tier ingestion model that supports extended data retention, enhanced governance, and regulatory capabilities, and higher performance for complex and historical queries.
Ingestion under Data Plus is billed at $0.60 per GB. This tier becomes relevant when teams:
Free: Data Plus is not offered under the Free edition.
Standard: This option increases the ingestion rate in exchange for expanded retention and data capabilities.
At scale, the difference between $0.40/GB and $0.60/GB significantly affects total spend. For example:
That pricing compounds quickly as environments grow.
Pro: The pricing is the same as Standard.
Pro customers can choose Data Plus for environments requiring longer retention and deeper historical investigations.
Enterprise: Enterprise Data Plus pricing is contract-based. It includes compliance-oriented capabilities such as FedRAMP Moderate and HIPAA eligibility, making it suitable for regulated industries.
Free | Standard | Pro | Enterprise | |
Basic users | $0 | $0 | $0 | $0 |
Core users | – | $49/user | $49/user | $49/user |
Full platform users | 1 free user | $10 first user, $99/additional user (max 5) | $349/user (annual) or $418.80/user (monthly pay as you go) | Contact Sales |
New Relic separates users into three categories:
Each edition, Free, Standard, Pro, and Enterprise, applies different pricing rules.
Basic Users: Basic users are free across all editions. These users typically have limited permissions, such as:
Core Users: Core users are not available in the Free edition.
Under Standard, Pro, and Enterprise, it costs $49 per user per month. Core users typically require:
Cost calculations at scale:
10 Core users
25 Core users
100 Core users
As observability expands across engineering teams, Core user costs scale linearly.
Full Platform Users: The Free edition includes:
This user has full access to platform capabilities.
Standard: Under Standard,
Cost calculations:
5 Full platform users:
Pro: Under Pro,
There’s no 5-user limit.
Cost calculations at scale:
If monthly pay-as-you-go:
The difference between annual and monthly pricing becomes significant at scale.
Enterprise: Enterprise Full platform user pricing is not publicly listed.
Enterprise agreements may bundle:
Free | Standard | Pro | Enterprise | |
Core Compute (CCU-based billing) | – | – | Contact Sales | Contact Sales |
New Relic offers an alternative to per-user pricing through Core Compute billing, measured in Compute Capacity Units (CCUs). Instead of paying per seat, organizations pay for the compute resources consumed by platform activity.
CCUs measure the compute used when teams:
Unsuccessful actions typically do not consume CCUs. Data ingestion is still billed separately per GB.
Under CCU billing:
This model shifts the cost driver from number of users to platform activity.
Because CCU pricing is contract-based, rates are not publicly published. But usage typically increases when:
In high-activity environments, compute consumption can grow faster than ingestion volume.
As teams grow from small to mid-size and large environments, New Relic costs increase across multiple usage dimensions. Pricing is shaped by the combined impact of infrastructure scale, telemetry volume, user access, and data movement, rather than a single metric.
As more services and nodes are added, APM and infrastructure host counts rise, increasing baseline platform usage.
Adoption of full-fidelity tracing drives rapid growth in indexed spans, especially in microservices and high-throughput systems.
Ingested logs (live and rehydrated) grow with service count and verbosity, while indexed log events add additional cost as teams rely more on search and investigations.
Increased use of custom metrics and dynamic attributes amplifies telemetry volume beyond initial estimates.
As observability data is shared across SREs, platform teams, and stakeholders, per-user licensing costs increase alongside usage.
Querying, exporting, and rehydrating telemetry introduces network transfer costs charged by the cloud provider, which become significant at scale.
This calculator brings these factors together hosts, ingestion volume, spans, logs, users, events, and data egress to help teams understand how New Relic pricing evolves as observability adoption deepens.
Consider three growth scenarios*:
*All pricing comparisons are calculated using standardized Small/Medium/Large team profiles defined in our internal benchmarking sheet, based on fixed log, metrics, trace, and retention assumptions. Actual pricing may vary by usage, region, and plan structure. Please confirm current pricing with each vendor.
User licensing can become a substantial recurring cost, especially as observability access expands beyond SREs to product, QA, leadership, and operations teams.
New Relic costs typically increase across three primary dimensions: data ingestion, user licenses, and compute consumption (CCUs). To manage spending effectively, teams need visibility into each driver before scaling observability coverage.
Ingestion is billed at $0.40 per GB under Original data ingest and $0.60 per GB under Data Plus. As log volume and distributed tracing expand, ingestion often becomes the largest cost driver.
To reduce ingestion costs:
Reducing ingestion by just 1 TB per month saves:
1,000 GB × $0.40 = $400/month
or
1,000 GB × $0.60 = $600/month
At scale, telemetry optimization delivers meaningful savings.
User-based pricing increases as observability access expands across teams.
Review whether:
Reducing 10 Full platform users under Pro saves:
10 × $349 = $3,490/month
License discipline directly impacts recurring cost.
CCU billing replaces per-user licensing with compute-based pricing. While it allows unlimited users, costs scale with platform activity.
Compute usage increases with:
Use New Relic’s Compute Optimizer to identify high-usage dashboards or inefficient queries and reduce unnecessary compute consumption.
Choosing Data Plus increases ingestion from $0.40 to $0.60 per GB. Extended retention and advanced governance features may justify this tier, but not all workloads require it.
Consider:
Retention strategy directly influences long-term observability cost.
Enabling distributed tracing, RUM with session replay, synthetics, or advanced alerts introduces additional usage dimensions. Before rollout, estimate:
Using a pricing calculator before enabling new capabilities helps prevent unexpected cost growth.
Not every workload requires full-fidelity observability. Consider:
Aligning observability depth with business impact ensures monitoring scales intelligently rather than automatically.
CubeAPM is designed for teams that need predictable observability costs at scale.
CubeAPM uses transparent, data-volume-based pricing of $0.15/GB with full control over ingestion, retention, and deployment. It doesn’t charge based on the number of users or features, or for longer retention periods.
CubeAPM supports context-based, Smart Sampling strategy. Rather than applying fixed or probabilistic sampling that drops data uniformly, CubeAPM prioritizes high-value telemetry such as error traces, high-latency requests, and anomalous behavior while aggressively sampling low-signal, repetitive traffic. This ensures critical insights are preserved without ingesting unnecessary volume.
Combined with self-hosted and controlled deployment models, this approach lets teams reduce ingestion costs without losing diagnostic depth. This also avoids vendor-imposed throttling, and forecasting observability spends becomes more easier as systems scale.
The key difference between New Relic and CubeAPM is mostly about architecture.
New Relic operates as a fully managed SaaS platform, where pricing scales with telemetry usage, traces, number of users, retention, and so on. CubeAPM runs inside customer-controlled infrastructure (BYOC or on-prem), giving teams direct control over data flow, retention, and cost boundaries.
| *Approx. cost for teams (size) | New Relic | CubeAPM |
|---|---|---|
| Small (~40) | $7,896 | $2,080 |
| Mid-Sized (~125) | $25,990 | $7,200 |
| Large (~250) | $57,970 | $15,200 |
For a detailed breakdown of features and pricing, see CubeAPM vs New Relic.
*All pricing comparisons are calculated using standardized Small/Medium/Large team profiles defined in our internal benchmarking sheet, based on fixed log, metrics, trace, and retention assumptions. Actual pricing may vary by usage, region, and plan structure. Please confirm current pricing with each vendor.
