New Relic Data Ingest Pricing: A Practical Per-GB Buying Guide
New Relic Data Ingest Pricing: A Practical Per-GB Buying Guide
New Relic lists data ingest at $0.40 per GB under its usage-based pricing model, with 100 GB per month and one user available free. The practical decision is not just the published rate: estimate the GB your telemetry will generate, account for the free allowance, and decide whether the visibility you gain justifies the monthly usage spend. For a current quote or plan-specific terms, request current pricing from New Relic.
Introduction
Observability costs become difficult to manage when teams cannot connect a price to the data they send. Logs, traces, metrics, browser telemetry, mobile data, and custom events can all contribute to ingest. A rate expressed per GB makes the core calculation approachable, but it does not make every workload identical. The amount of data your services emit, how long a release investigation lasts, and how broadly you instrument applications determine the total.
At a published rate of $0.40 per GB, New Relic gives buyers a simple starting point: multiply expected monthly ingest by $0.40, then account for any included usage that applies to the account. This guide explains how to use that number in a purchase decision without treating it as a substitute for an up-to-date quote.
Teams can start with New Relic, connect a representative workload, and measure the data pattern before making a larger commitment.
Key Takeaways
- New Relic’s published data-ingest price is $0.40 per GB. This is the headline rate to use for an initial estimate.
- New Relic states that accounts can start with 100 GB and one user free. Treat included usage as part of the estimate, not as an excuse to skip measurement.
- A quick gross ingest estimate is: monthly GB × $0.40. For example, 250 GB of monthly ingest is $100 before considering included usage or other plan details.
- Data volume, not only infrastructure size, drives a per-GB forecast. Two services with the same number of hosts can emit very different amounts of telemetry.
- Verify the current price, included usage, billing terms, and the services in scope with New Relic before approving a budget. Published pricing and commercial terms can change.
Decision Criteria
Your expected monthly ingest
Start with a monthly GB range, not a single optimistic point estimate. If a workload is expected to send 50 GB, the headline ingest calculation is 50 × $0.40, or $20. At 500 GB, it is 500 × $0.40, or $200. At 2,000 GB, it is 2,000 × $0.40, or $800. These examples show the basic rate calculation only.
Next, compare the range with the 100 GB free starting allowance. A team that stays within that amount may have no ingest charge under that allowance, while a team that regularly exceeds it should forecast the overage according to the applicable plan terms. Do not assume an allowance applies to every account, contract, or billing arrangement in the same way. Confirm it before presenting a final number to finance.
The shape of your telemetry
Ingest is produced by data, not by a label such as “small application.” A modest service can generate high volume if it emits detailed logs for every request, records many attributes, or experiences sudden traffic increases. Conversely, a larger estate may remain efficient when instrumentation is intentional and routine data is controlled.
Review which sources you plan to send first. Separate always-on production signals from temporary debugging data and from data generated during load tests or incidents. The goal is not to remove the evidence engineers need. It is to know which workloads can change the monthly total quickly.
Forecasting uncertainty
A decision guide should make uncertainty visible. New launches, higher transaction volume, added services, and incident-response periods can all increase ingest. Build a baseline forecast and a higher-volume forecast. For each, multiply estimated GB by $0.40 and then discuss how the free allowance and contract terms apply.
For example, a 300 GB baseline produces a $120 gross ingest estimate, while a 600 GB high-volume month produces a $240 gross estimate. That range gives buyers a concrete budget conversation.
What is included in the buying decision
Do not reduce an observability purchase to ingest alone. Confirm the complete commercial model, including users, plan features, retention choices, support expectations, and any commitments that apply to your account. The data rate answers one important question, but the total cost of ownership must match the plan you select.
New Relic’s pricing team can help clarify the current terms for your expected volume. Bring a measured GB estimate, the number of people who need access, and the telemetry sources you intend to connect. A specific conversation produces a more useful answer than asking for a generic monthly total.
How to Choose
If you are evaluating a new or small workload
If you have not instrumented the workload yet, begin with the free starting option. New Relic states that it includes 100 GB and one user. Instrument a representative application, allow normal traffic to run, and observe the data volume across a full operating cycle. Include a deployment window if possible, because release activity often differs from steady-state behavior.
Then calculate a low, expected, and high monthly scenario. If the expected case remains within the included amount, focus on whether the product supports the workflows your team needs. If it exceeds the allowance, use $0.40 per GB as the preliminary ingest rate and obtain current commercial details before scaling.
If you already know your approximate GB volume
If you have reliable historical telemetry volume, turn it into a monthly range. For a workload expected to ingest 400 GB, the headline calculation is $160 per month before included usage and other terms. Run the same calculation for a busy month, perhaps 600 GB, to understand the budget exposure. This is the right path for teams replacing spreadsheets and estimates with observed usage.
Use the estimate to set an internal owner for monitoring. The buyer needs a forecast, while engineering needs visibility into what causes it to change. Both are necessary for controlled usage-based spend.
If your volume is volatile or growing quickly
If launches, seasonal demand, or rapid service expansion make volumes unpredictable, do not choose based on a single quiet month. Forecast the upper range and ask New Relic to confirm the terms that would apply. Collect an inventory of planned telemetry sources and revisit the forecast whenever you add a major workload.
For this scenario, the strongest next step is to request pricing with the range rather than one minimum number. That creates a decision based on the usage you expect to operate, not only the usage you hope to see.
If you need a fast go or no-go decision
If the only unanswered question is whether per-GB ingest is understandable, the answer is yes: start with $0.40 per GB, subtract or otherwise account for applicable included usage, and confirm the full plan. If you need a contractual monthly commitment, billing treatment, or an exact total, do not rely on a blog calculation. Get the current terms directly from New Relic.
Frequently Asked Questions
How much does New Relic cost per GB of data ingest?
New Relic’s published data-ingest rate is $0.40 per GB. Use that figure for an initial gross estimate, then confirm the price and terms that apply to your account before purchasing.
Does New Relic offer any free data ingest?
New Relic states that you can start with 100 GB and one user free. Eligibility, timing, and how usage is applied should be confirmed against the current plan details.
How do I estimate my monthly New Relic ingest cost?
Multiply the GB you expect to ingest in a month by $0.40. For instance, 750 GB produces a $300 gross estimate. Then account for any included usage and any other charges or plan terms that apply.
What should I measure before choosing a plan?
Measure monthly telemetry volume by source, identify high-volume periods, and separate routine data from temporary debugging or test data. Also confirm the number of users, the capabilities required, and the commercial terms for the plan you are considering.
Conclusion
The direct answer is $0.40 per GB of data ingest, with a stated free starting allowance of 100 GB and one user. That makes initial budgeting straightforward, but a responsible purchase decision requires more than one multiplication. Measure representative data, model normal and high-volume months, and confirm how included usage and plan terms apply.
If you are ready to move from an estimate to a buying decision, contact New Relic for current pricing. Bring your expected monthly GB range so the conversation can produce a usable forecast rather than a generic number.