New Relic Browser Pricing 2026: Tier-by-Tier Breakdown

The fast facts

The pricing model

Pay per GB of data ingested across all New Relic products plus a per-user seat charge. Browser RUM data counts toward the shared ingest pool.

The per-GB ingest model

New Relic prices observability as a unified ingest meter: every byte of telemetry from APM, logs, infrastructure, browser RUM, mobile RUM, synthetic, and serverless counts against the same GB-per-month budget. This makes the per-product cost of Browser RUM specifically hard to isolate — you cannot get a meaningful Browser RUM bill in isolation without knowing the rest of the New Relic spend.

A typical RUM workload sends roughly 40 MB of telemetry per 1,000 sessions (varies wildly with replay enabled vs disabled, sampling, and the number of custom attributes). At that rate, 1 million sessions per month generates ~40 GB of Browser RUM ingest, which costs $16/month on the Standard tier — an order of magnitude cheaper than per-session vendors at the same volume. But that number assumes Browser RUM is the only product ingesting; in practice, APM logs and infrastructure metrics dominate the meter.

The shared-meter trap

Teams adopting Browser RUM on New Relic should model total ingest, not RUM ingest alone. A team running New Relic APM at 50 hosts (~500 GB/month of ingest from traces and host metrics) will see Browser RUM as a small marginal addition. A team running only New Relic Browser will hit the meter ceiling much faster because the per-GB rate is the same regardless of source. The 100 GB/month free tier is enough for hobby use but disappears immediately under any commercial workload.

Session replay requires a full platform user

Session replay is not gated by ingest, it's gated by user-seat tier. To access session replay in the UI, a team member needs a “full platform user” seat ($99+/month per user). Basic and Core users cannot view replays. For a 5-person engineering team, that means $495/month in seats alone if everyone needs replay access, on top of the per-GB ingest bill.

The 85% ingest alert

New Relic sends a billing alert by default when monthly ingest reaches 85% of the free-tier allowance (or 85% of any committed monthly cap). This is genuinely useful operationally, teams typically tune sampling and reduce log verbosity in response. The alert is configurable; many teams set it lower (60-70%) to give more lead time.

How New Relic Browser compares

• Versus Datadog RUM, Datadog is per-session ($4.50/1K), New Relic is per-GB ($0.40/GB). For pure RUM workloads, New Relic is cheaper at moderate volume. For workloads that bundle RUM into a wider observability stack, Datadog's per-product meters are easier to budget than New Relic's shared meter.
• Versus AWS CloudWatch RUM, AWS is cheaper still (~$0.10/1K effective) but lacks New Relic's dashboard sophistication.
• Versus Elastic Browser RUM, Elastic also uses ingest-based pricing but tied to cluster compute. New Relic is simpler to budget month-to-month.
• Versus Sentry, Sentry's separate metering for errors, replays, and transactions is more granular than New Relic's unified ingest; harder to predict but easier to attribute cost to specific features.

When New Relic Browser is the right choice

• You already run New Relic for APM or infrastructure and want to add Browser RUM under the same contract.
• Your RUM workload is small relative to APM/log ingest and would be a marginal addition to an existing New Relic bill.
• You have organisation-wide commitment to a single observability vendor and want the unified pane.
• You can budget 1+ “full platform user” seats for replay access.

When New Relic Browser is the wrong choice

• You only need Browser RUM in isolation, the shared-meter model is hostile to single-product use.
• You need replay access for the whole engineering team but can't budget multiple Full Platform User seats.
• You are price-sensitive on RUM specifically, Sentry, Raygun, or AWS CloudWatch RUM is cheaper.

For New Relic on the APM and log management side, see our sister site's New Relic pricing breakdown. For the structural per-GB ingest model comparison, see per-GB ingest pricing models.

Try it in the calculator

The RUM cost calculator includes New Relic alongside 17 other vendors. Enter your monthly page views, session replay coverage, retention, and sampling rate to see how New Relic's pricing compares head-to-head against the alternatives.

Where to go next

• Multi-vendor calculator — estimate New Relic's cost against 17 alternatives at your specific workload.
• Per-session pricing models — how New Relic's pricing model compares structurally to Datadog, Dynatrace, and Raygun.
• Quote-only vendors — the five RUM vendors that don't publish prices and the operational consequences.
• Hidden RUM costs — sampling, retention storage, replay storage, and overage gotchas across the category.
• Methodology — how we verified the New Relic pricing data shown above (verified 2026-06-16).