New Relic Pricing Explained: Ingest, Users and Data Plus

New Relic's bill is built from data ingest, priced per gigabyte beyond a free 100 GB a month, and from full platform and core users, priced per seat. On Pro and Enterprise, optional full consumption (compute) pricing replaces the user fees. On the list prices on newrelic.com/pricing, as of 4 Nov 2026, ingest is $0.40 per GB, or $0.60 per GB with Data Plus. Basic users are free, core users are $49 and full platform users run from $10 to $418.80 a month depending on the edition.

If you are weighing a switch rather than a smaller invoice, start with our comparison of New Relic alternatives and competitors. If you want to keep the platform and cut what you send to it, that is the work behind New Relic consulting from AceMQ. These are list prices, and Pro and Enterprise customers can hold commitments and discounts, so treat every figure as the ceiling a negotiation starts from.

New Relic's pricing model, as its pricing page describes it, rests on two core metrics: users and data ingest, or compute and data ingest. It also says it does not charge per host, so hosts, containers and agents do not appear as a line item. Everything else is an add-on: extra retention, the EU data center at $0.05 per GB, and synthetic checks beyond those included, at $0.005 each. The result is a bill with one metered quantity that engineers control (what they send) and one that managers control (who gets a seat). New Relic sells pay-as-you-go billing at the end of each calendar month on Standard and Pro, and commitment contracts with volume and savings plans on Pro and Enterprise. The free tier needs no credit card.

Each account gets 100 GB of ingest a month free. Beyond that, the original data option is $0.40 per GB and Data Plus is $0.60 per GB. The page says ingest is calculated on the data saved in the platform after processing, including transformation and trimming rules, so what you drop before it is stored is not billed. On the Free edition, ingest stops when you exceed 100 GB until you upgrade or the month rolls over; New Relic emails you at 85 percent.

Data Plus is the price of governance features: up to 90 days of extra data retention for most data types, advanced log obfuscation and enhanced export, plus FedRAMP Moderate and HIPAA eligibility for Enterprise customers. It is worth its extra $0.20 per GB only if you use those features.

There are three user types. Basic users are free and unlimited: they can run queries, build custom dashboards and set up alerts, but cannot use curated experiences such as the APM UI. Core users are $49 and add the errors inbox, the full logs interface and an IDE extension (which needs Advanced Compute), but not the curated APM, infrastructure or browser experiences. Full-platform users can use the whole platform, and their price depends on the edition:

• Free: one full platform user.
• Standard: $10 for the first, $99 for each additional, with a maximum of five. Standard also lists a two-business-day support response.
• Pro: $349 per user a month with an annual commitment, or $418.80 on pay as you go, with unlimited full platform users and a two-hour critical initial response.
• Enterprise: quoted by sales, with a one-hour critical initial response.

The Pro and Enterprise pages also offer full consumption pricing with no user licenses, where the platform is paid for through compute capacity units (CCUs) instead of seats. The pricing page does not publish CCU rates, so that option is quoted.

This is arithmetic on list prices, not a quote. Take 1,000 GB of ingest a month: 900 GB is billable, which is $360 on the original data option or $540 on Data Plus. Add ten full platform users on Pro with annual commitment, at $349 each, and the user line is $3,490 a month, larger than the ingest line. On Standard, five users would be $10 plus four at $99, or $406. The point of the example is the ratio: for many teams the seat count, not the gigabytes, sets the bill, and for others it is the other way around. Compute both before you decide what to attack.

• Drop rules and sampling. Because ingest is counted after processing, rules that remove debug logs, high-cardinality attributes or events nobody queries cut the bill directly.
• Log levels at the source. Debug output left on after an incident is an easy volume to miss.
• Metric intervals. Infrastructure metrics collected far more often than any dashboard displays are volume without value.
• User types. Moving engineers who only need queries and custom dashboards from full platform to basic removes seats; basic users cannot open the curated APM, infrastructure or browser experiences.
• Retention. Extra retention and Data Plus are choices; set them per data type you actually need to keep.

One typical engagement is described in New Relic telemetry volume and cost governance: attribute ingest by team and source, check what is actually queried, and put controls at the collection layer so the reduction holds.

Look at alternatives when the bill is high after the controls above are applied, or when the reason is not price at all: keeping telemetry in your own account, standardizing on OpenTelemetry and open storage, or consolidating onto an engine you already operate. New Relic says it aims to have first-class OpenTelemetry support and to ingest all OTLP data, so OpenTelemetry instrumentation keeps both paths open. Our New Relic alternatives page sets out the options on the same criteria and says when staying is right. For 24/7 help with agents and pipelines whichever you choose, see New Relic support.

• New Relic pricing page, newrelic.com/pricing, prices as of 4 Nov 2026. All prices are list prices on that date and change.
• New Relic OpenTelemetry introduction, docs.newrelic.com/docs/opentelemetry/opentelemetry-introduction/, read 4 November 2026.