Datadog cost estimator

How a Datadog bill is built

There is no single Datadog price, there are several meters that add up. Infrastructure Monitoring is charged per host per month. APM (tracing) is charged per host again, usually on a subset of your infrastructure hosts. Logs are billed twice over: once to ingest the data, per gigabyte, and again to index it so it stays searchable, priced per million log events at a given retention. The estimate above is just the sum of those four meters, which is why one noisy service or one chatty log stream can move the total more than adding servers does.

The line that usually surprises people

Hosts are predictable; logs are where the bill runs away. Ingestion and indexing are separate charges, so a service that logs verbosely costs you on the way in and again to keep it queryable. The cheapest control is usually to ingest broadly but index selectively, keeping only the log events you actually search at full retention. The breakdown above shows whether logs or hosts are your biggest line, so you know which lever to pull first.

Custom metrics, honestly

Each Infrastructure Pro host includes about 100 custom metrics, and overage is billed by usage. Datadog does not publish a fixed per-metric overage rate, so this tool deliberately does not invent one; it only shows your included allotment. If you run high-cardinality custom metrics, that line can be significant and is worth confirming directly against your account.

The line this calculator does not include: Bits AI credits

This estimate covers the meters that make up the bulk of a typical bill: hosts, APM, and logs. It does not price Datadog's newer AI line, Bits AI, which is metered in AI Credits, where one credit is a unit of work done by a Datadog AI product. Four products draw them down (Bits Chat, Bits Investigation, Bits Code, and Bits Agent Builder), and the line scales with how much AI-assisted work your team runs, not with your host count or log volume, so a host-based estimate has no row for it.

It is left out on purpose, not by oversight: the credit line depends on usage this tool cannot see, and it behaves unlike the rest of the bill. Committed credits, bought in 500-credit monthly bundles on a monthly or annual term, reset on the first of each month and do not roll over, so a bundle you under-use is money gone, while the host and log meters simply bill less when you consume less. If you are turning Bits AI on, treat it as a separate line and start On-Demand until you can measure a stable monthly floor, then commit only to that floor.

Honest limits

Every rate is an editable default pre-filled with Datadog published annual list pricing, verified in 2026 and shown next to the field. On-demand pricing without an annual commitment runs higher, and enterprise contracts are negotiated, so treat this as a planning baseline to frame the decision, then confirm against your own contract. It is an estimate, not a quote.

Who this is for

Engineering leads sizing an observability budget, teams hit by a Datadog renewal and trying to see where the cost sits, and anyone comparing the all-in price before they commit. For a full breakdown of where a Datadog bill actually grows, read why your Datadog bill keeps climbing.

Datadog cost questions, answered