New Relic is a capable platform and its pricing model is, unusually, an advantage at this size: unlimited hosts at no extra cost, 100 GB of free ingest a month, unlimited free basic users, and a published rate card you can actually plan against. If your estate is host-dense — Kubernetes, autoscaling groups, ephemeral workers — that shape can be materially cheaper than a per-host competitor.
But the meter that decides your invoice is user type, and it is brutally steep. New Relic publishes full platform users at $349 per user per month on Pro with annual upfront billing (rising to $390.88 on monthly billing and $418.80 pay-as-you-go), $549 on Enterprise, against $49 for a core user and $0 for a basic user. That is a 7.1× step from core to full platform and an infinite one from basic — per person, per month, for a whole year.
So the condition is specific and it is not a negotiating tactic: decide, in writing, which roles get which user type, before you sign. Fifty people provisioned as full platform users who should have been core is $180,000 a year at Pro list. No discount you negotiate on data will recover that, and no vendor will volunteer that you got it wrong.
The money, named
What you pay for people. New Relic's published Usage Plan lists a price for every user type and billing shape. Standard is capped at five full platform users, so at this size you are on Pro or Enterprise:
| User type / billing | List price per month | Per user per year | 25 users / yr | 100 users / yr |
|---|---|---|---|---|
| Basic user | $0 | $0 | $0 | $0 |
| Core user | $49 | $588 | $14,700 | $58,800 |
| Pro full platform, annual upfront | $349 | $4,188 | $104,700 | $418,800 |
| Pro full platform, monthly billing | $390.88 | $4,690.56 | $117,264 | $469,056 |
| Pro full platform, pay as you go | $418.80 | $5,025.60 | $125,640 | $502,560 |
| Enterprise full platform, annual | $549 | $6,588 | $164,700 | $658,800 |
Three things fall straight out of that table. A full platform user on Pro costs 7.1 times a core user. Paying as you go rather than committing annually costs 20% more — $83,760 a year at 100 full platform users. And the Enterprise step is $200 per user per month, or $240,000 a year at 100 full platform users, which had better be buying a compliance requirement you can name.
What you pay for data. New Relic publishes 100 GB of free data ingest per month and $0.40 per GB beyond it. That is the number everyone remembers, and at this size it is usually the smaller half of the bill:
| Ingest per month | Billable GB | Per month | Per year |
|---|---|---|---|
| 2,000 GB | 1,900 | $760 | $9,120 |
| 10,000 GB | 9,900 | $3,960 | $47,520 |
| 30,000 GB | 29,900 | $11,960 | $143,520 |
| 50,000 GB | 49,900 | $19,960 | $239,520 |
Put the two meters side by side and the priority becomes obvious. An org ingesting 10 TB a month pays $47,520 a year for data. The same org with 100 full platform users on Pro pays $418,800 for people. The data conversation is worth having — but it is the one everybody has, while the expensive one goes unexamined.
What it has to beat. Take a deliberately disciplined shape: 40 full platform users, 200 core users, everyone else basic, and 10 TB a month of ingest.
40 full platform users (Pro, annual) 40 x $349 x 12 = $167,520 / year
200 core users 200 x $49 x 12 = $117,600 / year
10,000 GB/month ingest (10,000 - 100) x $0.40 x 12 = $47,520 / year
total = $332,640 / year
$332,640 / $90 per hour ( = $180,000 / 2,000) = 3,696 engineer-hours / year
across a 500-engineer org = 7.4 hours per engineer per yearSeven and a half hours per engineer per year is a defensible bar for a platform that shortens incidents and finds the slow query before a customer does — most orgs clear it. Now run the undisciplined version of exactly the same org: 240 full platform users instead of 40-plus-200, and the licence line alone is $1,004,640 a year. Same tool, same data, same value, three times the invoice. That is the entire argument of this page.
The reason, at this size
1. The user-type policy is the contract.
New Relic publishes three user types, and the gap between them is the widest per-person price step of anything on your renewals list: $0, $588 a year and $4,188 a year. In practice that means every provisioning decision — made by a manager, in a ticket, on a Tuesday — is a four-figure annual commitment.
Write the policy down before you buy, in a form a manager can apply without asking: which roles get full platform (typically SREs, platform engineers, the on-call leads for tier-one services), which get core, and which get basic. Then review it quarterly against actual login and query activity, and downgrade. Fifty misassigned seats is $180,000 a year against core, or $209,400 against basic, and it is the most reversible mistake on this page — but only if somebody looks.
2. Unlimited hosts is a genuine structural advantage — if your estate is host-dense.
New Relic publishes unlimited hosts at no additional cost, with the bill driven by data and users instead. For a Kubernetes estate with hundreds of ephemeral nodes, that is a real and defensible difference from a per-host competitor — the same infrastructure that inflates a per-host bill costs nothing here except the telemetry it emits.
The corollary is that the two meters you do pay for are both things engineers control day to day: how much telemetry each service emits, and how many people hold a full platform licence. Which means cost discipline here is an engineering practice, not a procurement event — and it is why the controls below are about instrumentation and provisioning rather than about negotiation.
3. Committing annually is published as cheaper, by a lot.
New Relic publishes three prices for the same Pro full platform user: $349 annual upfront, $390.88 monthly billing, $418.80 pay as you go. That is a 12% and a 20% premium respectively, for the same product, published on the vendor's own page.
At 100 full platform users that is $50,256 and $83,760 a year in extra cost. Teams land on pay-as-you-go for understandable reasons — a proof of concept that became production, a reluctance to commit before the estate settles — and then stay there through inertia. If you have been on the platform a year, the commitment decision has effectively already been made; only the price hasn't.
4. Ingest volume is an instrumentation decision, not a fixed cost.
At $0.40 per GB above the free 100 GB, the difference between logging every debug line from every pod and logging what you actually query is tens of thousands of dollars a year at this size — 10 TB a month is $47,520, 30 TB is $143,520. Nobody decides to triple their ingest; it arrives one verbose service and one new integration at a time.
The control is the same as it is on every telemetry platform: decide what is worth ingesting per service, sample the high-volume low-value streams, and review the top ten emitters monthly. Do that before you negotiate the rate. A vendor discount on data you should not be sending is a worse outcome than sending less of it.
5. There is a published alternative billing shape — ask about it explicitly.
New Relic's own pricing page offers, on Pro and Enterprise, full consumption pricing with no user licences as an option. For an org whose bill is dominated by full platform seats — which, per the arithmetic above, is most orgs at this size — that is a materially different shape, and it exists precisely because the per-user model does not fit everyone.
We are not going to price it for you: we did not read a published per-unit rate for the compute-based model, and inventing one would be exactly the failure this library refuses to commit. What we will say is that you should ask for both quotes, side by side, on your real usage — the per-user shape and the consumption shape — and that a vendor who offers two pricing models will usually quote the one you asked for rather than the one that suits you.
What to do instead of just renewing it
Four controls. The first is worth six figures a year at this size and takes an afternoon.
1. Write the user-type policy, then audit against actual usage.
Which roles get full platform, which get core, which get basic — one page, applied at provisioning time. Then quarterly, list full platform users with no meaningful query activity in ninety days and downgrade them. At published Pro list, every fifty downgrades from full platform to core is $180,000 a year.
2. Move off pay-as-you-go if you have been live for a year.
New Relic publishes $418.80 pay-as-you-go and $390.88 monthly against $349 annual upfront for the same Pro full platform user. At 100 such users that is $83,760 and $50,256 a year respectively. You are not switching platforms mid-year; price it accordingly.
3. Review the top ten data emitters every month.
At $0.40 per GB above the free 100 GB, a single verbose service can add five figures a year. Decide per service what is worth ingesting, sample the rest, and make the review a fifteen-minute standing item rather than a post-invoice investigation.
4. Ask for the consumption-priced quote alongside the per-user one.
New Relic publishes full consumption pricing with no user licences as an option on Pro and Enterprise. If your bill is seat-dominated, get both quotes on the same usage, in the same document, with the year-two uplift stated. There is no published rate for the compute model, so the quote is the only way to know.
What would change our mind
- Fewer than five people need full platform access. Then Standard, capped at five full platform users with the first at $10 and the rest at $99, may cover you outright and none of the Pro arithmetic applies.
- Your estate is host-sparse but data-heavy. The unlimited-hosts advantage disappears and the comparison against a per-host competitor reopens on the data meter alone — which is a different page and different published rates.
- You have a named FedRAMP or HIPAA requirement. Those sit with Enterprise and Data Plus, and a documented compliance requirement outranks a $200-per-user-per-month cost comparison every time.
- New Relic publishes per-unit rates for Advanced Compute or the consumption model. Both are real budget lines we could not source a published price for, and both could change the shape of this verdict. When they are published, this page needs re-running.
- You can show us a signed rate materially below list. We price at published list because that is what is verifiable. The user-type argument survives any discount — a misassigned seat is misassigned at any price per seat.
What we checked
Every figure above came from a page we opened, so you can check our work before you forward this to finance.
- New Relic — Pricing — 100 GB of free data ingest per month and $0.40 per GB ingested beyond it; unlimited free basic users; unlimited hosts at no additional cost; Standard limited to 5 full platform users; core users $49 per user; Pro full platform users $349 per user for annual commitments; and full consumption pricing with no user licences offered as an option on Pro and Enterprise. Read 30 August 2026.
- New Relic Docs — Usage plan (list prices) — Published list prices per full platform user per month: Standard $99; Pro $349 annual upfront billing, $390.88 monthly billing, $418.80 pay as you go; Enterprise $549 annual upfront, $614.88 monthly, $658.80 pay as you go. Core users $49 per month. Read 30 August 2026.
Provenance. Every per-user and per-GB price on this page was read from a New Relic page on 30 August 2026 — the ingest rate, free allowance, unlimited-hosts statement and the consumption-pricing option from newrelic.com/pricing, and the per-user list prices for each user type and billing shape from New Relic's own Usage Plan documentation. The annual totals, the 7.1x core-to-full-platform multiple, the $180,000 and $209,400 misassignment figures, the $83,760 pay-as-you-go premium, the worked $332,640 estate and the 3,696-hour break-even (at a $180,000 fully-loaded cost per engineer and 2,000 hours a year) are our arithmetic on those published numbers, and are labelled as ours in each caption. Advanced Compute and Data Plus rates are deliberately absent because we did not read a published per-unit price for either, and no negotiated discount is assumed because New Relic publishes none. No data volume or user mix is assumed for your org: the volumes above are named examples to show the shape of the meters. No sponsorship, no affiliate link, no vendor review of this page. Last reviewed 30 August 2026. Corrections: [email protected].
Questions we get asked about this one
Is New Relic worth it for a 100–1,000 person engineering team?
Yes, on one condition: write the user-type policy before you sign. New Relic publishes unlimited hosts at no extra cost, 100 GB of free ingest a month and unlimited free basic users, which is a genuinely good shape for a host-dense Kubernetes estate. But it publishes full platform users on Pro at $349 per user per month against $49 for a core user and $0 for a basic one, so the provisioning decision is worth $4,188 a year per person. A disciplined shape — 40 full platform, 200 core, 10 TB a month of ingest — is about $332,640 a year, or 7.4 engineer-hours per engineer per year at a $180,000 fully-loaded cost. The undisciplined version of the same org is over a million.
What does New Relic cost for 500 engineers?
Headcount is not the meter — user type and data are. On New Relic's published list prices, 100 full platform users on Pro with annual billing is $418,800 a year, 200 core users is $117,600, and basic users are free however many you have. Data is $0.40 per GB above the free 100 GB a month, so 10 TB a month is $47,520 a year and 30 TB is $143,520. The answer for a 500-engineer org is therefore anywhere between roughly $200,000 and well over $1m a year depending entirely on how many people you provision as full platform users.
What is the difference between a full platform, core and basic user in New Relic?
It is the biggest per-person price step on your renewals list. New Relic publishes basic users as free and unlimited, core users at $49 per user per month, and full platform users at $349 per user per month on Pro with annual upfront billing — $0, $588 and $4,188 a year respectively. That means a full platform user costs 7.1 times a core user. Deciding which roles genuinely need full platform access, writing it down, and auditing it quarterly against real query activity is worth $180,000 a year for every fifty people who were assigned the wrong type.
Is New Relic cheaper than a per-host observability platform?
It can be, and the reason is structural: New Relic publishes unlimited hosts at no additional cost and bills for data and users instead. For a Kubernetes or autoscaling estate where host count is high and volatile, that removes the meter a per-host competitor charges on. But it replaces it with a steep per-user meter — $349 per full platform user per month on Pro at list — so the comparison depends entirely on your ratio of hosts to people who need deep access. Run both vendors' published rates against your own host count, user mix and ingest volume; do not take either vendor's example estate as yours.
How do we cut a New Relic bill without losing observability?
In this order. Audit user types and downgrade full platform users with no meaningful query activity — at published Pro list, every fifty downgrades to core is $180,000 a year, and it removes nobody's dashboards or alerts, since basic users are free. Move off pay-as-you-go if you have been live a year: $418.80 against $349 per full platform user per month is $83,760 a year at 100 users. Review the top ten data emitters monthly and sample high-volume, low-value telemetry at $0.40 per GB. Then ask for a consumption-priced quote alongside the per-user one, since New Relic publishes that as an option and it suits a seat-dominated bill.
Tomorrow morning, five tools you haven’t heard of yet.
This verdict is free and always will be. The newsletter is the part you pay for: five new AI tools every weekday morning, one line on what each does, one line on why it matters for a PM, and the link. Start with this morning’s issue, free.
$10/month or $96/year after 7 free days, cancel in one click · a real Adoption Brief, in full · every issue, published free · [email protected]
Other verdicts at this size
- Is Atlassian Jira worth it for a 100–1,000 person engineering team? — Yes, on Standard — the tool is not the decision at this size, the edition is. Jira Cloud Standard is $36,500 a year at 500 users and $68,500 at 1,000, and the Premium step is $26,000 and $42,000 a year for a checkbox that applies to everyone on the site.
- Is LaunchDarkly worth it for a 100–1,000 person engineering team? — Yes, once you have counted service connections and client-side MAU — neither of which is your headcount. $10 per connection per month and $8.33 per 1,000 MAU means one extra environment across 80 services costs $9,600 a year, and the governance tier is quote-only.
- Is Okta worth it for a 100–1,000 person engineering team? — Yes — identity is a control, not a convenience, at this size. The money is the suite: Okta publishes $6, $14 and $17 per user per month, so 500 identities is $36,000, $84,000 or $102,000 a year, and the upper suites only pay if somebody staffs the automation.
- Is PagerDuty worth it for a 100–1,000 person engineering team? — Yes, on Professional and billed annually. At 500 responders that is $126,000 a year against $246,000 on Business — and the money leaks through licences held by people who left the rota, at $252 each per year.
- Is Sentry worth it for a 100–1,000 person engineering team? — Yes, and paid plans include unlimited users so hiring does not raise the bill. The money is the rate card: Business re-prices every error at two to three times the Team rate, which is $5,268 a year at two million errors a month and $19,668 at ten million.
- Is Cursor worth it for a 100–1,000 person engineering team? — Yes, on Standard seats billed annually. At 500 engineers that is $192,000 a year against $576,000 for the all-Premium version of the same purchase — and the rework exposure is 4.7x to 38x the licence.
- Is Datadog worth it for a 100–1,000 person engineering team? — Yes, but only on a host count you measured yourself. Infrastructure Pro and APM on the same 500 hosts is $276,000 a year at list — and Datadog's own published retention rate says bills like yours grow about 20% a year.
- Is GitHub Copilot worth it for a 100–1,000 person engineering team? — Yes, on Business at $19 a seat. At 500 engineers that is $114,000 a year against a rework exposure of $900,000 to $7.4m — which is why the three controls matter more than the purchase order.
- Is Snowflake worth it for a 100–1,000 person engineering team? — Yes, on Standard at $2.00 a credit unless somebody can name the Enterprise feature. One X-Large warehouse left running is $280,320 a year — the settings decide this bill, not the contract.
- Should we buy an LLM observability platform? — The next telemetry purchase you will be pitched, and our call on it.
- Should we buy ThoughtSpot Spotter? — A verbatim generator run on a tool priced per seat against data you already hold.
- Is Claude Code worth it for a 25-person engineering team? — Where a vendor's own pages contradict each other on price, and what to ask.
Every published verdict is listed on the verdicts index.