New Relic's marketing says "100GB free forever." That sounds incredible. Then you enable APM on your Next.js app, turn on log forwarding, and add infrastructure monitoring. By day 3, you've ingested 95GB. By day 7, you're over the free tier and staring at a bill you didn't expect.
New Relic's pricing isn't expensive — it's confusing. The free tier is real, but the path from free to paid is full of gotchas that only become clear when the invoice arrives.
This guide breaks down exactly how New Relic's pricing works in 2026, what real teams actually pay, and when it makes sense vs. cheaper alternatives.
How New Relic's Pricing Model Works
New Relic charges on two dimensions: users and data ingestion. This is fundamentally different from Datadog (per-host) or Grafana Cloud (usage-based tiers).
Dimension 1: Users
New Relic has three user types:
| User type | Price | What they can do |
|---|---|---|
| Basic user | Free (unlimited) | View dashboards, run basic queries, see alerts. Cannot create custom dashboards, set up alerts, or access APM details. |
| Core user | $49/month | Everything Basic can do + create dashboards, configure alerts, access errors inbox. No APM traces or distributed tracing. |
| Full platform user | $49/month (Standard), $349/month (Pro), $549/month (Enterprise) | Everything. APM, distributed tracing, logs in context, vulnerability management. |
The free tier includes 1 full platform user. This means exactly one person on your team gets full access. Everyone else is limited to Basic (read-only dashboards) unless you pay.
For a team of 5 developers who all need to debug production issues, that's 4 additional full users at $49-349/month each.
Dimension 2: Data Ingestion
Every metric, trace, log line, and event that enters New Relic counts toward your monthly data ingestion:
| Tier | Included data | Overage cost |
|---|---|---|
| Free | 100 GB/month | Cannot exceed (data stopped) |
| Standard | 100 GB/month | $0.30/GB |
| Pro | 100 GB/month | $0.30/GB (first 100GB over), then volume discounts |
| Enterprise | Custom | Negotiated rates |
How fast does 100GB fill up? Here are typical ingestion rates:
- APM traces: 5-15 GB/month for a medium-traffic app (1,000 RPM)
- Infrastructure metrics: 1-3 GB/month per host
- Logs: 20-100+ GB/month depending on verbosity. This is where most teams blow their budget.
- Browser/RUM: 2-10 GB/month depending on traffic
A typical Next.js app with APM + logs + infrastructure monitoring ingests 30-80 GB/month for a small deployment. That's within the free tier — barely. Add a second environment (staging) or increase log verbosity, and you're over.
Real Cost Examples
Solo developer, 1 side project
Users: 1 full platform (free)
Data: ~25 GB/month (APM + basic logs)
─────────────────────────────────
Monthly cost: $0
Works on free tier? Yes ✅Team of 5, production SaaS
Users: 5 full platform × $49 = $245/month
Free: 1 user included = -$49
Data: ~150 GB/month (APM + logs + infra)
Over: 50 GB × $0.30 = $15/month
─────────────────────────────────
Monthly cost: $211/monthTeam of 10, high-traffic app
Users: 10 full platform × $49 = $490/month
Free: 1 user included = -$49
Data: ~500 GB/month (APM + verbose logs + infra + browser)
Over: 400 GB × $0.30 = $120/month
─────────────────────────────────
Monthly cost: $561/monthThe Hidden Costs
1. Log ingestion is the budget killer
Logs are the most data-intensive signal. A single Next.js app with console.log statements and request logging can generate 50+ GB/month of logs. Most teams don't realize this until the first bill because the default New Relic agent forwards all logs.
Fix: configure log filtering to only send errors and warnings, not info/debug. Or use log sampling (send 10% of logs). This alone can cut data ingestion by 60-80%.
2. The "full platform" user trap
Basic users can see dashboards but can't create alerts, investigate traces, or use the errors inbox. In practice, every developer who needs to debug production issues needs full platform access. You can't have one developer on the team who can see traces and four who can't.
3. Data retention costs extra
Default retention is 8 days for most data types. Extended retention (30, 60, 90 days) costs additional per GB stored. If your compliance requirements need 90-day retention on logs, this adds significantly to the bill.
4. Synthetic monitoring is separate
Synthetic checks (ping endpoints from multiple regions) are billed per check. 10,000 checks/month are included in paid plans, but if you monitor 10 endpoints every minute from 3 locations, that's 1.3M checks/month — well beyond the included amount.
New Relic vs Datadog: Price Comparison
| Scenario | New Relic | Datadog |
|---|---|---|
| Solo dev, 1 project | $0 (free tier) | ~$46/month (1 host, APM) |
| 5 devs, 3 hosts, moderate logs | ~$211/month | ~$300-500/month |
| 10 devs, 10 hosts, heavy logs | ~$561/month | ~$800-1,500/month |
| Pricing model | Per user + per GB | Per host + per module |
| Free tier | 100GB + 1 user | 14-day trial only |
| Serverless support | Partial (agent overhead) | Partial (agent overhead) |
New Relic is generally cheaper for small teams (1-5 devs) with moderate data volumes. Datadog becomes more competitive at larger scale where per-host pricing is predictable.
When New Relic Makes Sense
- You need full-stack observability (APM + logs + infrastructure + browser) and your team is 5-15 developers
- You want a free tier for evaluation — New Relic's 100GB/month is the best free offering in APM
- Data ingestion is moderate (under 200GB/month) — the per-user model is cheaper than Datadog here
- You need NRQL — New Relic's query language is more approachable than Datadog's DQL or Grafana's PromQL
When New Relic Doesn't Make Sense
- You only need API monitoring — New Relic is a full observability platform. If all you need is "alert me when my API routes are slow or broken," you're paying for 90% of features you don't use.
- High log volumes — At 500GB+/month of logs, New Relic's per-GB pricing gets expensive fast. Consider Grafana Loki (self-hosted, free) for logs.
- Serverless on Vercel — The New Relic Node.js agent adds 200-400ms to cold starts. On Vercel serverless functions, this directly impacts user experience.
The Lightweight Alternative for Next.js Teams
If your stack is Next.js and your monitoring need is "know when API routes break," Nurbak Watch is purpose-built for that use case:
// instrumentation.ts
import { initWatch } from '@nurbak/watch'
export function register() {
initWatch({
apiKey: process.env.NURBAK_WATCH_KEY,
})
}| New Relic | Nurbak Watch | |
|---|---|---|
| Monthly cost (5 devs) | $211+ | $29 flat |
| Setup time | 1-2 hours | 5 minutes |
| Cold start impact | +200-400ms | +5-15ms |
| Works on Vercel | Partially | Fully |
| Alerts | Email, Slack, PagerDuty | Email, Slack, WhatsApp |
| Best for | Full-stack observability | Next.js API monitoring |
Free during beta. No per-user pricing, no per-GB pricing, no surprises.

