New Relic vs Datadog cost comparison: pricing models, hidden traps, and workload fit

New Relic and Datadog are the two platforms most SRE teams shortlist before signing a major observability contract, and SRE teams usually frame the New Relic vs Datadog decision as a feature comparison. The billing structure is the part that decides whether your spend stays forecastable. Both cover APM, logs, infrastructure, and AIOps, and both bill in ways that scale with data volume rather than with the size of your fleet.

New Relic charges per GB of ingested data plus per user seat. Datadog charges per host, per SKU, across separately billed products. Neither model decouples cost from telemetry volume, so the question to evaluate is how each bill behaves when log volume spikes 10x during an incident, when autoscaling doubles your host count for an hour, or when a developer ships a custom metric with unbounded cardinality.

New Relic vs Datadog at a glance

Pricing models compared

At 500 nodes, Finance can forecast spend only if the model exposes the variables; feature depth rarely decides that. The two models charge for different things, so the same workload can cost 3x more on one platform than the other depending on its shape.

New Relic: ingestion plus per-user pricing

New Relic bills two primary meters: data ingest and user seats. Ingest costs $0.40/GB for Original Data or $0.60/GB for Data Plus beyond a free 100 GB/month, with a $0.05/GB surcharge for EU data center storage. Those rates have climbed 33% since April 2024, when the list price was $0.30/GB.

Seats stack on top. Core users cost $49/user/month; full platform users cost $99/additional user on Standard (capped at 5) and $349/user/month on Pro annual commitments, or $418.80 month-to-month.

A third meter arrived in February 2024: the Compute Add-On SKU bills CCUs on top of data and user fees, and New Relic AI features began consuming Advanced CCUs in June 2025. That adds a query and AI-usage variable to a model that already depends on ingest and user count.

Datadog: per-host, per-SKU model

Datadog’s base meter is the host: Infrastructure Pro runs $15/host/month annual ($18 on-demand), Enterprise $23 ($27). Each additional capability is a separate SKU with its own meter:

• APM bills $31–$40/host/month annual depending on tier, plus $0.10/GB for ingested spans and $1.70–$2.50 per million additional indexed spans.
• Log management bills $0.10/GB ingested plus $1.06–$3.75 per million indexed events depending on retention and billing mode.
• Database Monitoring costs $70/host/month annual, $84 on-demand.
• Custom metrics come with an allotment included per host, then cost $0.05 per metric on overage.
• Containers are included at 5 per Pro host and 10 per Enterprise host; extras bill at $0.002/container/hour on-demand or $1/container/month prepaid.

Which is more predictable at scale?

Neither model is predictable in absolute terms; the answer depends on workload shape. VendorBenchmark’s 500-host analysis found that at 10 engineers, 1 TB/day of ingest, and 500 hosts, New Relic runs $85K–$145K/year against Datadog’s $280K–$450K. Flip the shape to 100 engineers, 50 GB/day, and 200 hosts, and Datadog runs $200K–$350K while New Relic hits $700K–$980K because of per-seat costs. At small scale the gap is proportionally wider: CompareTiers model modeled a 32-host environment at $1,572/month on Datadog against $218/month on New Relic, though that model used New Relic’s older $0.30/GB rate.

Negotiated discounts at enterprise scale run 35–45% on Datadog per VendorBenchmark’s model, and one documented New Relic negotiation (Cloudbeds account) reached nearly 90% off list. No independent, audited head-to-head TCO study at 50–500+ nodes exists; every published figure is a model or a single-company account.

The structural verdict: Finance models New Relic against data volume and headcount. Finance must model Datadog across host count, container count, metric cardinality, indexed events, and every new SKU you enable, which makes it harder to forecast even when each dimension is documented.

Hidden costs and billing traps to audit

Datadog and New Relic document most of these mechanics in their own billing docs; engineers reported the rest first-hand. Audit your contract for each before signing.

Datadog’s host and container meters generate most of its documented surprises:

• High-water mark billing: Datadog bills the 99th percentile of hourly host counts. Spot instances and hourly-billed ephemeral workloads push the p99 up; one Hacker News engineer reported “our DD bill was more than the services being monitored” on short-term spot fleets. Datadog’s Hybrid Monthly/Hourly Plan is the documented remedy for autoscaling and spot fleets.
• Same-hour host replacement: if an autoscaled instance terminates and its replacement spins up within the same hour, same-hour host replacement can count both as billable host-hours. Duplicate hosts also occur on EKS when the Agent cannot reach the EC2 metadata service.
• Per-container billing: installing the Agent inside each container instead of once per host means each container bills as a full host. Crash-restart loops count against the container allotment.
• Custom metrics cardinality: one metric tagged with unique URLs multiplies into a timeseries per URL; one Reddit sysadmin thread documented a $30,000 overage with no warning.
• Per-SKU overages: log consumption above commitment bills at a 50% premium, and enabling a new SKU generates its own on-demand charges. One engineer got the notice after the fact: “Hey just a heads up you have $6,500 in on-demand costs for CloudSIEM, I hope that was expected.”
• SKU repricing: r/devops engineers reported a Fargate APM change taking per-task cost from $1 to $4.

New Relic’s surprises come from ingest volume and contract terms:

• Ingest spikes: a January 2024 r/devops post documented a bill rising from $900 to over $8,000 in two months after a Kubernetes namespace generated nearly 2 GB of logs per day.
• CCU unpredictability: teams cannot pre-calculate Advanced Compute charges per dashboard or query.
• Data Plus and retention premiums: the $0.60/GB Data Plus rate is 50% above Original Data, and extended retention adds $0.05/GB/month across all data types simultaneously, since New Relic requires teams to raise retention across all data types at once.
• Renewal defaults: a February 2026 TrustRadius reviewer reported: “Their pricing is lazy and they default to higher priced terms at renewal.” Contract customers remain responsible for commitment fees regardless of actual usage, and one community report says account closure was blocked.

Verdict: Datadog produces more frequent and larger documented bill-shock incidents (an $83K/year renewal cancellation, a reported $800K–$1M annual contract for a five-person team). New Relic’s traps are fewer but sharper, because a single misconfigured log source hits the one meter that everything flows through.

APM and distributed tracing

Datadog’s APM is the more polished product; New Relic’s retains more data by default at the tail. Datadog’s sampling and retention mechanics:

• The Agent samples head-based against a default target of 10 traces per second across services.
• The always-on Intelligent Retention Filter keeps a diversity sample of service entry spans for 30 days at no charge.
• Custom retention filters retain matching spans for 15 days and bill against the 1M indexed spans included per APM host.

Datadog’s tracing UI includes flamegraphs in the APM interface, and Continuous Profiler is a separate SKU at $19–$23/profiled host/month. It requires the Datadog SDK; OTel-instrumented services cannot use it.

New Relic’s standard agents use adaptive head-based sampling, but Infinite Tracing adds native tail-based sampling: 100% of trace data reaches the trace observer, which keeps duration outliers and error traces at a 100% target. Datadog has no native tail-based sampling; Datadog documents tail sampling as an OTel collector-level mechanism. Default trace retention is where New Relic looks weaker: 8 days on Original Data versus Datadog’s 15–30, though Data Plus extends it to 98 days.

New Relic also shipped eBPF APM to GA in December 2025, which auto-discovers services on hosts and Kubernetes nodes without code changes, language-agnostic. Datadog restricts eBPF to Universal Service Monitoring, network monitoring, and security; its core APM telemetry remains SDK-based.

Verdict: choose Datadog APM for UI depth and cross-signal navigation, New Relic for tail-based sampling and longer retention on Data Plus. Neither gives you profiling or full APM depth without proprietary instrumentation.

Log management

Datadog splits log billing into two meters, and the second one is where log-heavy teams get hurt. Ingest costs $0.10/GB; making logs searchable costs another $1.06–$3.75 per million indexed events depending on retention tier and billing mode, with overages at a 50% premium above the annual rate. Flex Logs offers lower-cost long-term storage at $0.05/M events but does not support monitors or Watchdog Insights, and forwarding logs anywhere other than S3, GCP Storage, or Azure Storage costs $0.25/GB per destination.

New Relic bills logs at the same per-GB rate as everything else: $0.40/GB Original or $0.60/GB Data Plus. Default log retention is 30 days on Original Data and 120 days on Data Plus, against Datadog’s 15-day default for on-demand customers. Search runs through NRQL, the same language used for metrics and traces; Datadog logs use Lucene-based syntax, separate from its metrics and APM query interfaces.

Verdict: New Relic’s single-meter model is easier to forecast for log-heavy SRE teams and retains logs twice as long as Datadog’s 15-day on-demand default. Datadog’s split model rewards teams disciplined enough to index a small fraction of what they ingest, and punishes everyone else at overage rates.

Infrastructure monitoring

Datadog covers the broader surface: Linux, Windows, macOS, and AIX hosts, serverless, host maps, container maps, and the Orchestrator Explorer for Kubernetes, backed by 1,000+ integrations. Container allotments of 5 per Pro host or 10 per Enterprise host, per-pod Agent misconfiguration billing containers as hosts, and cardinality explosions from dynamic labels make Kubernetes the leading source of Datadog surprise bills.

New Relic charges nothing per host; cost flows entirely through ingest. Kubernetes deploys with a single command, and Pixie (a CNCF Sandbox eBPF project New Relic acquired in December 2020) provides protocol-level spans for HTTP, DNS, MySQL, PostgreSQL, Cassandra, Redis, and Kafka, with Pixie’s on-cluster data incurring no ingest charges for up to 24 hours.

Datadog sells each eBPF capability as a per-host add-on stacked on the base infrastructure fee:

• Cloud Network Monitoring adds $5/host.
• Universal Service Monitoring adds $9/host.
• Workload Protection adds $15/host.

New Relic’s eBPF features carry no per-host charge; you pay for whatever data they generate.

Verdict: Datadog for heterogeneous fleets spanning Windows, macOS, and AIX. New Relic for Kubernetes-heavy environments where Datadog’s container and cardinality meters bite hardest.

OpenTelemetry support and vendor lock-in

Both platforms now ingest all three OTLP signals natively, and both still gate their most differentiated features behind proprietary agents.

New Relic ingests all three OTLP signals: traces, metrics, and logs. Documented gaps remain: exemplars are not supported and summary metrics break on ingest. Code-level metrics, browser distributed tracing, and IAST require the New Relic agent, though a June 2026 hybrid mode lets the agent act as the OTel SDK at runtime.

Datadog offers four OTel paths, and direct OTLP intake went GA in July 2026. Direct OTLP ingest does not populate the Infrastructure Host List, the Agent’s OTLP receiver ships with logs disabled by default, and Continuous Profiler and App and API Protection require the Datadog SDK outright. A DEV Community account of the developer experience: “fully half of the tutorials on their blog and docs site are outdated and nonfunctional.”

Verdict on lock-in: Datadog is the stickier platform. Deep agent integration, three separate query syntaxes, multi-dimensional billing, and a 90-day renewal notice compound switching costs, and Hacker News threads consistently describe it that way. New Relic’s lock-in runs through NRQL queries, dashboards, and alert configurations rather than the instrumentation layer, which makes an OTel-first exit path more practical.

AI and AIOps

Datadog’s Bits AI is further along and priced as its own meter. Bits Investigation went GA in December 2025 for monitor-triggered investigations, correlates logs, metrics, infrastructure state, and source code, and completes investigations in roughly 3–4 minutes. Pricing is $500 per 500 credits/month billed annually, at about 6.5 credits per autonomous investigation, and unused credits do not roll over.

New Relic’s equivalent is Autopilot, launched as SRE Agent in February 2026, renamed in June, and GA since July 2026. It triages alerts, traverses traces and logs to isolate likely cause, and recommends remediation, but every action requires human review and approval. It carries no standalone price; it consumes Advanced Compute CCUs, adding AI usage to the least predictable meter New Relic has.

New Relic’s FedRAMP and HIPAA customers are ineligible for its AI features because processing happens in New Relic’s SaaS, and neither vendor runs AI analysis inside customer infrastructure by default.

Verdict: Datadog leads on autonomy and GA maturity. New Relic leads on human-in-the-loop guardrails. Both turn AI into a new billing dimension.

Query languages, dashboarding, and usability

NRQL is New Relic’s strongest usability argument. One SQL-like language queries metrics, events, logs, and traces in the unified NRDB. Community sentiment on r/sre: “I find NRQL quite easy to use… I love it.” The platform UI draws less affection; Hacker News users have called it “super confusing.”

Datadog splits the query surface across logs, metrics, and APM: Lucene-based syntax for logs, a proprietary metrics language, and a separate APM interface. R/sre users call the dashboard syntax “powerful but weirdly rigid,” and say it “tends to enforce better best practices.” Where Datadog wins is cross-signal navigation: click from a slow request into its APM trace, into the slow service, onto the host it ran on.

For day-to-day SRE work, New Relic offers a lower cognitive load for querying and Datadog a faster investigative click-path.

Platform architecture: unified telemetry vs modular SKUs

The way each vendor packages telemetry explains how each platform charges. New Relic stores every telemetry type in a single database, NRDB, which is why one per-GB rate covers everything and one language queries it. The platform is SaaS-only in US and EU regions: every signal exits your infrastructure to New Relic’s cloud, with no BYOC (Bring Your Own Cloud) or on-premises option.

Datadog packages observability as separately metered products. Granular adoption also drives the business model: net revenue retention in the low 120% range indicates existing customers collectively spend about 20% more year over year as they adopt additional SKUs.

Adding security, profiling, or database monitoring to Datadog adds billing dimensions; adding data types to New Relic adds gigabytes to one meter. Neither structure removes the underlying volume sensitivity.

Where groundcover fits

Both platforms tie cost to how much you observe, which forces teams to sample traces, drop logs, skip non-production environments, and ration seats. groundcover removes the volume meter entirely.

• Flat per-node pricing: Pricing is based on the monthly average of actively monitored Kubernetes nodes: $30/host/month on Pro, $35 on Pro+/Enterprise, and $50 for Enterprise On-Premises, with all integrations included and no per-GB, per-seat, per-metric, or per-session charges. A 10x log spike during an incident does not change the bill, and 100% signal capture with no sampling carries no financial penalty.
• eBPF deployment model: The groundcover eBPF sensor deploys as a single DaemonSet, one pod per node. It captures metrics, traces, logs, and Kubernetes events directly from the Linux kernel with zero application instrumentation.
• BYOC data plane: BYOC (Bring Your Own Cloud) is the default architecture at every tier. The data plane runs inside your VPC, while groundcover manages the control plane for UI and orchestration.
• Storage backends: ClickHouse stores logs, traces, and Kubernetes events. VictoriaMetrics stores metrics.
• Hosting cost: BYOC hosting is a real added cost you pay your cloud provider. Better Stack estimates roughly $23,000/year for a 450-node deployment.
• Scope limits: groundcover is purpose-built for Kubernetes and Linux, not for Windows, macOS, AIX, bare metal, or serverless and managed PaaS platforms that block kernel access.

On cost outcomes, groundcover’s Datadog pricing guide reports an unnamed customer running about 700 Kubernetes nodes who moved from $2.54M/year on Datadog to $297K/year, an 87% reduction with full APM and no trace sampling. That figure is vendor-reported and not independently audited. Better Stack’s independent modeling estimates 40–60% savings for Kubernetes-heavy environments, varying by workload.

A productized migration tool transfers dashboards, monitors, and integrations from Datadog. The free tier includes the full BYOC architecture with no credit card (12-hour retention), so you can deploy Flora on a single cluster and check the zero application instrumentation claim against your own workloads.

Which should you choose?

Choose New Relic if:

• Your workload is high-ingest and low-user: VendorBenchmark’s model shows New Relic at $85K–$145K/year where Datadog runs $280K–$450K for 10 engineers at 1 TB/day.
• You want one query language (NRQL) across all signals and a single billing meter to forecast.
• You need the most generous free tier for evaluation: 100 GB/month across all signals, unlimited hosts.
• You need SAP, mobile, or network performance monitoring alongside standard signals.

Choose Datadog if:

• Your fleet spans Windows, macOS, AIX, serverless, and bare metal alongside Kubernetes.
• You need a security suite (Cloud SIEM, CSPM, ASM) or software delivery tooling New Relic does not offer.
• Your workload is high-user and low-ingest, where per-seat pricing would dominate a New Relic bill.
• Your team values Datadog’s trace UI and its click-path from log to trace to host enough to manage the SKU sprawl.

Consider groundcover if:

• You run Kubernetes and Linux and want cost that scales with node count only, so Finance can forecast 50 to 500 nodes as a linear line item.
• You want 100% signal capture without sampling trade-offs or indexing decisions driven by billing.
• Data sovereignty matters, with regional or contractual requirements that telemetry never leave your VPC.
• You want every engineer to have access, since there are no per-seat charges to ration.

FAQ

These are the questions SRE and platform teams usually ask after comparing the pricing mechanics. Workload shape, not feature count, drives the platform fit.

Which platform is more cost-predictable at scale?

Neither is predictable in the way flat pricing is. New Relic’s bill tracks data volume and seats; Datadog’s tracks hosts, containers, metric cardinality, and indexed events across separate SKUs. VendorBenchmark’s analysis shows which platform costs less flips depending on your ratio of data volume to user count.

What are the biggest billing traps to audit before signing?

For Datadog: 99th percentile high-water mark host billing, same-hour host replacement double-counting, custom metric cardinality, and 50% log overage premiums. For New Relic: unexpected log ingest (documented $900 to $8,000+ in two months), CCU charges, and renewal terms that default higher.

Who has the deeper APM?

Datadog has the stronger tracing UI and flamegraphs, with Continuous Profiler as a $19–$23/host add-on requiring its SDK. New Relic offers native tail-based sampling through Infinite Tracing and 98-day trace retention on Data Plus, versus Datadog’s 15–30 days.

How do log costs compare for log-heavy teams?

Datadog charges twice, $0.10/GB to ingest and $1.06–$3.75 per million events to index, so cost depends on what fraction you index. New Relic charges once per GB at $0.40–$0.60 with 30-day default retention against Datadog’s 15.

Does OpenTelemetry eliminate lock-in on either platform?

Misconception: “OTLP support makes both platforms portable.” Not accurate. Both ingest all three OTLP signals, but profiling, security, and code-level features require proprietary agents at both vendors. Datadog is the stickier of the two given its agent depth and multi-syntax query surface.

Which platform’s AI actually helps during an incident?

Datadog’s Bits Investigation is GA and runs autonomous investigations in roughly 3–4 minutes at about 6.5 credits each against a $500/500-credit monthly pool. New Relic’s Autopilot requires human review and approval for every action and bills through Advanced Compute CCUs.

Is NRQL or Datadog’s query syntax easier to learn?

NRQL is one SQL-like language across metrics, events, logs, and traces in NRDB. Datadog splits Lucene-based log search, a proprietary metrics language, and a separate APM interface, so engineers learn three surfaces instead of one.

Which fits Kubernetes best?

Datadog’s container allotments and per-pod billing make Kubernetes its most trap-prone environment. New Relic avoids per-host charges but ships all telemetry to its SaaS. groundcover is built specifically for Kubernetes: the Flora eBPF sensor collects all signals from one DaemonSet, data stays in your VPC, and the bill tracks node count alone.