New Relic pricing: does cost per host explain the bill?

New Relic brings together application and infrastructure telemetry. Cost per host divides spending by monitored machines, but it does not determine the current bill: the metric fails when an operation does not measure what it ingests or requires a fixed price per machine. Engineering and procurement teams need to measure consumption, check retention, and compare proposals with the same scope.

The cover image is a generated illustration; it does not depict a verified New Relic installation or imply its endorsement.

Decision matrix / Key facts: Use case: investigating applications and infrastructure. Main unit: GB ingested and users, or GB ingested and compute. Free allowance: 100 GB per month; exceeding it stops ingestion and access until an upgrade or the next month. Additional cost: access, compute, and retention depend on the edition and contract. Buying in Brazil: New Relic on Nexforce Marketplace states that customers can contract in Brazilian reais with a tax invoice.

New Relic cost per host: what determines the bill?

New Relic's current offering lists unlimited hosts. There is no additional charge per host. Spending depends on ingestion and users or compute, as well as retention and add-ons. Original APM contracts follow different rules, so buyers need to identify their contracted billing model.

New Relic receives logs, metrics, events, and traces from applications and infrastructure to help investigate problems. Services on shared hosts produce different volumes of telemetry. Hosts serve the inventory, not a standalone forecast of the current bill, which responds to measured consumption and the billing units in the proposal. The bill reflects what was measured, not the machine count. Under the original per-host APM model, one equivalent host corresponds to 750 connected hours in a month, with fractions of a connected hour counted as one hour. This legacy rule does not establish the contracted rate and should not automatically be transferred to the current offering or interpreted as a universal additional per-host charge. To compare models, confirm the edition, billing model, region, and period in writing, along with any migration at renewal.

How much does New Relic cost for data, users, and retention?

New Relic's pricing table separates data and users. Free is suited to limited evaluations; Standard and Pro show prices for data and access, while Enterprise data and Full Platform prices require a quote. Ingestion and retention are separate pricing dimensions that need confirmation in the proposal.

In the New Relic monthly pricing table, Free offers 100 GB of ingestion per month, unlimited Basic users, and one free Full Platform user, but stops ingestion and access when the limit is exceeded, until an upgrade or the next month. For Standard and Pro, the table publishes US$ 0.40 per GB for Original Data and US$ 0.60 per GB for Data Plus beyond the 100 GB allowance, subject to account conditions. The Pro description mentions Data Plus, although the table shows the option for Standard; confirm availability in the commercial proposal. Pro has pricing with an annual commitment or monthly pay-as-you-go; Enterprise data and Full Platform remain subject to a vendor quote. Basic costs US$ 0 in paid editions, but the Free allowance does not establish an automatic deduction. Confirm categories and prices in the proposal.

The table lists SAML single sign-on for Standard; the SAML and SCIM documentation requires a paid edition. Overage conditions outside Free and renewal conditions are not established and depend on the proposal.

Billable volume differs from raw data, and the retention period varies by option and data type.

The billing rules say ingested data is the data stored after cuts and transformations, with exceptions by type. Under the contractual definition, 1 GB equals one billion bytes. Ingestion is rounded to a whole number. Original Data provides at least eight days of retention; Data Plus adds up to 90 days for most eligible types, depending on configuration. The retention documentation publishes US$ 0.05 per GB per month for an additional 30 days, applied to the types in the interface. According to the documentation, reducing retention for specific sources after enabling the longer period does not change the charge; changes during the contracted period require confirmation.

Image: Retention configuration, official New Relic documentation. The values illustrate one configuration, not universal periods.

What data should buyers gather before contracting?

Before requesting a proposal, gather a service inventory, GB ingested by telemetry type, active users, desired retention, region, and the contracted model. The seven-step master checklist makes the comparison verifiable and avoids repeating the 100 GB allowance for each service.

Gathering data before requesting a proposal reduces rework and makes it possible to compare offers with the same scope. The inventory turns isolated estimates into a comparable, auditable basis that the vendor can address with figures for the same period. It must cover what will be monitored and what will be billed, without confusing raw volume with ingested volume. Ask the platform team for the list of services and environments, and the finance team for the contracted model and current terms. If the organization does not yet measure ingestion, use a representative week and identify the estimate during negotiation. A service without a measurement belongs in the unallocated portion, never at zero. Document the date of each figure because published prices and rules change, and keep the previous proposal to identify price adjustments and edition changes. Without that basis, any comparison mixes different scopes and hides the true cost per service. The sequence below organizes the collection. Start with the inventory.

1. List services, environments, and telemetry types.
2. Measure or estimate GB ingested per service and environment in the month.
3. Record users by type and pending invitations.
4. Define retention by data type and the extensions needed.
5. Confirm the edition, region, exchange rate, and taxes in the proposal in Brazilian reais.
6. Request the organization total and the breakdown needed to allocate costs by service.
7. Record the verification date for each price.

How is observability cost per service calculated?

Cost per service is a management allocation of the organization's total, not a separate New Relic invoice. The allocation follows a documented policy, and the amount assigned to services plus the unallocated portion must reconcile with the vendor's total.

To calculate New Relic cost per service, start with GB measurements by service, environment, and telemetry type, preserving unidentified data. When the public Standard or Pro conditions apply, the data component is maximum(0, organization's rounded billable GB minus applicable allowance) × confirmed rate, without repeating the 100 GB for each service. Allocate that component proportionally to measured GB when the basis can be reconciled, keeping unassigned data in the denominator so its share is not passed on to known services. Calculate users or Core Compute according to the contracted model, add Advanced Compute when contracted, and record retention and add-ons without counting an item twice. The CCU rate was not verified. Include implementation costs only when supported by evidence; the allocation method for shared items must be reproducible.

Conceptual diagram of internal allocation, not a New Relic invoice. Source for the components: New Relic pricing and billing rules.

How should teams assess operations and compare proposals?

New Relic serves teams that investigate applications and infrastructure and manage ingestion, access, and retention. A small evaluation requires attention to the Free limit. Shared services require telemetry identification. With multiple teams, check permissions, shared costs, and responsible owners.

Two reviews from customers identified as verified, dated March 2021 and published on the New Relic Marketplace page, report benefits in production monitoring, application metrics, and dashboards that bring together infrastructure layers. The reviews cite difficulties with navigation, licensing cost, dashboard and alert automation, user management, and filtering before ingestion; these are old experiences, not current measurements or results observed on day 90. The page lets readers consult the reviews and their sources, while the team tests whether the points still apply in its own environment. Before contracting, compare direct and local proposals for the same period, edition, volume, users or compute, retention, and add-ons, including commitment, renewal, cancellation, support, and price adjustment. Before deciding, check the technical scope of each offer and record the differences.

Screenshot from public New Relic documentation, used as a quotation: synthetic monitor options, not contract terms.

The audit of unused licenses reviews access; direct purchase or marketplace compares purchasing methods.

How can teams verify the budget and correct common errors?

Verify the budget by reconciling the contracted total, invoices, and measurements by service for the same period, keeping the unallocated portion visible. Three checks cover the most common discrepancies: an allowance repeated for each service, raw volume treated as billable data, and retention counted twice in the proposal.

Reconcile during the first cycle and repeat the check when the edition, region, or volume changes. Compare the invoice total with the sum allocated to services plus the unallocated portion; a difference can come from the allocation method, approximate measurements, or billing, and the cause must be investigated before making any assignment. Check that the allowance was applied once for the organization and that the data counted is ingested, not raw. Check that additional retention was charged once, without repeating days already included. Record who approved the allocation method and when, so the comparison survives a change in ownership. This check corrects the basis before renewal. Record the date of each check. On day 90, review access, alerts, and configurations without assuming operational results before measurement.

• Repeated allowance: apply the 100 GB to the organization's total, not to each service.
• Raw volume in place of billable volume: use data ingested after cuts.
• Duplicate retention: confirm what the edition already includes before adding the extension.

Frequently asked questions about New Relic pricing

Free limits monthly ingestion, and the current offering adds no per-host rate. Retention varies by data type and contracted option. To obtain a proposal in Brazilian reais, the team presents its inventory and confirms prices, add-ons, and commercial terms with the vendor.

New Relic's Free plan lists a monthly allowance of 100 GB and stops ingestion and access when it is exceeded, until an upgrade or the next month, without guaranteeing automatic continuation upon payment for an overage. In the current model, the table lists unlimited hosts with no additional per-host charge. A legacy APM account may follow the original model and requires confirmation of the contractual rate. Data Plus offers up to 90 additional days on top of standard retention for most eligible types, depending on configuration, and does not establish a uniform period for all telemetry. To obtain a local quote, the buyer should provide the period, data, access or compute, and retention, requesting terms in writing for comparison with a proposal of the same scope. The Marketplace page states that customers can contract in Brazilian reais with a tax invoice, but the dollar pricing table is not a Brazilian quote.

Does the New Relic Free plan have a limit?

Yes. The public offering lists 100 GB per month, unlimited Basic users, and one free Full Platform user. When the limit is exceeded, ingestion and access stop until an upgrade or the next month, without an automatic overage charge. The allowance belongs to the organization and does not apply to each service.

Does New Relic charge per host?

There is no additional per-host charge under the current model in the public table. An original APM contract may use equivalent hosts based on connected hours, and that model's rate depends on the contract. The number of hosts does not determine ingestion, paid users, or retention.

How can buyers request a New Relic proposal in Brazilian reais?

The New Relic page on Nexforce Marketplace, consulted on November 12, 2026, states that customers can contract in Brazilian reais with a Brazilian tax invoice. Send an inventory of data, access or compute, retention, and period. Request pricing, price adjustments, and add-ons in writing and compare them with a direct proposal of the same scope.

References and Further Reading

Official sources allow buyers to check New Relic billing units, public prices, and retention rules, but they do not replace the organization's proposal. The values consulted on November 12, 2026 are dollar references, not contracted prices in Brazil. Revalidate the terms before buying.

The pricing table presents editions and public data and user prices, while the billing rules describe ingestion, rounding, users, and compute. For billable access, the documentation counts the highest user type assigned during the UTC calendar month, including a pending invitation, without guaranteeing a lower bill when the type is downgraded mid-month. The Usage UI presents approximate values and does not guarantee complete attribution by service, requiring attention to the period and scope of each reading. More attribute combinations can increase observed series or data, but cardinality alone does not establish a per-series rate; usage and pricing for Unlimited Cardinality, classified as Advanced Compute, require confirmation. For SSO, SCIM, permissions, APIs, and webhooks, request a demonstration and the terms of the proposed edition, including limits and any plan change.

Ask for a proposal with the inventory in hand

With the inventory, measurements, and retention defined, the next step is to request a proposal for the same scope and period, comparing the total, allocation by service, and renewal terms. Record the quote date, the contracted model, and who approved the internal allocation method before deciding.

The proposal should specify the edition, model, region, allowance, rates, retention, and periods, as well as charges included in the amount in Brazilian reais. Request separate breakdowns for data, users or compute, retention, and add-ons, so the allocation uses the same structure as the bill. The New Relic Marketplace page states that customers can contract in Brazilian reais with a Brazilian tax invoice, but price and terms depend on a proposal for the inventory submitted. Confirm the overage rule, price adjustment policy, and cancellation terms in writing. Ask for them in writing. If the operation monitors few services and consumption fits within the free allowance, reassess the purchase before making an annual commitment. Record the verification date and source for each public price cited in this guide. Keep the accepted proposal alongside the internal allocation and the date of the reconciliation.