Compare · updated 2026-08-24
APM pricing models: Datadog vs Dynatrace vs New Relic
Datadog prices per host with separate meters for logs, custom metrics, and products, Dynatrace prices on consumption units across capabilities, and New Relic prices on data ingested plus seats.
01The mechanics
What actually differs
The unit each option charges on, and who owns what afterwards, matter more than any single quoted figure.
APM pricing is where bills surprise hardest, because the meters multiply: a host fee here, a custom-metrics line there, log ingest charged once to collect and again to index. Each vendor's model makes a different behaviour expensive, so the same estate can cost wildly different amounts depending on which meter its habits land on.
This comparison is being assembled cell by cell against each vendor's own published pricing page, with a source and a checked date on every cell. A row does not ship until every cell in it is sourced, which is the same rule the rest of this site holds itself to. The qualitative read below stands on its own.
02The honest row
When each is the right answer
Every option in this comparison is the right answer for somebody, and saying when is the part most comparisons leave out.
Datadog
The right answer when developer experience drives adoption and the estate lives cloud-native. The APM and trace view earn their price on crown-jewel services, and the corners of the bill respond well to upstream governance.
Dynatrace
The right answer for complex, deeply distributed enterprise applications where automatic instrumentation and causal analysis genuinely shorten incidents, and where that depth is worth a premium on the services that need it.
New Relic
The right answer when a consolidated per-GB plus per-seat model fits the team shape, and when predictable all-in-one pricing beats a basket of separate product meters.
03Questions
Asked about this comparison
Why is APM spend so hard to predict?
Because the meters compound: hosts, custom metrics, log ingest and indexing, synthetics, and per-product add-ons each bill separately. Estates rarely watch all meters at once, so growth lands quietly on whichever one nobody owns. One metering view by source and destination is the fix that precedes any vendor change.
Is switching APM vendors worth it for price alone?
Rarely. Instrumentation is sticky and engineers' workflow attachment is real. The moves that pay reliably are governing what reaches the meters and taking ordinary infrastructure hosts off APM-grade pricing entirely, both of which work whichever vendor you keep.
Model it against your estate
The comparison that matters is the one run on your volumes and your contracts. The review reads them with you, and you leave with your version of the Logmetry Blueprint. No system access, no obligation.