Datadog Infrastructure Monitoring lists at $15 per host per month on the Pro tier and $23 per host on Enterprise. APM lists at $31 per host. Logs ingestion runs $0.10 per GB plus retention at $1.27 to $2.13 per million log events depending on retention period. A 1,000-host enterprise deployment with full Infrastructure plus APM plus Logs plus RUM commonly lists at $1.6 to $2.4 million per year before negotiated discount. Realised enterprise discounts at $500,000 commit land at 12 to 22 percent. At $2 million the band moves to 22 to 32 percent. At $5 million it reaches 30 to 42 percent. This guide covers Datadog's pricing across the 18 products, the bill-shock pattern that catches most buyers, and the negotiation framework that recovers 25 to 40 percent of typical Datadog spend.
Datadog product line list pricing
Datadog now sells 18-plus modular products. Each has its own pricing unit. Most enterprises start with three or four and find themselves at 10 or 12 within 18 months.
| Product | Pricing unit | Pro tier list | Enterprise tier list |
|---|---|---|---|
| Infrastructure Monitoring | Per host per month | $15 | $23 |
| Container Monitoring | Per container per month (cardinality) | $1 per container | Included with Infrastructure Enterprise (limit applies) |
| APM (Application Performance Monitoring) | Per host per month | $31 | $36 |
| APM + Continuous Profiler | Per host per month | n/a | $40 |
| Logs Ingestion | Per GB ingested | $0.10 | $0.10 |
| Logs Retention (15 days) | Per million log events | $1.27 | $1.27 |
| Logs Retention (30 days) | Per million log events | $1.70 | $1.70 |
| RUM (Real User Monitoring) | Per 1,000 sessions | $1.50 | $1.80 |
| Synthetic Monitoring (API) | Per 10,000 test runs | $5.00 | $5.00 |
| Synthetic Monitoring (Browser) | Per 1,000 test runs | $12.00 | $12.00 |
| Database Monitoring | Per database host | $70 | $70 |
| Network Performance Monitoring | Per host | $5 | $5 |
| Cloud Cost Management | Percent of cloud spend monitored | 2 percent | 2 percent |
| Cloud SIEM | Per GB log analysed | $0.20 | $0.20 |
| Application Security Monitoring | Per APM host | $17 | $17 |
| CI Visibility | Per committer per month | $30 | $30 |
| Workflow Automation | Per action executed | $0.001 | $0.001 |
Pricing is per-product-per-host. A host in Infrastructure costs $15. The same host in Infrastructure plus APM costs $46. With Continuous Profiler plus Logs plus Network Performance Monitoring plus Database Monitoring, the same host lists at $116 per month. The modular pricing rewards adoption at every layer but compounds quickly.
The Datadog bill-shock pattern
Three patterns drive most Datadog bill shock. Each is technically defensible but commercially asymmetric.
One: container cardinality. Datadog charges per host. For Kubernetes estates where pods scale up and down hourly, the daily peak container count drives billing. A workload that averages 200 containers but peaks at 2,000 during deploys bills at the peak. Negotiation lever: switch to high-cardinality container metering with negotiated peak limits.
Two: log retention multiplier. The retention rate per million events looks small. The multiplier on actual production log volumes is not small. A platform ingesting 3 TB of logs per day generates approximately 600 million events per day. At 30-day retention that is 18 billion events, listing at $30,600 per month for retention alone, on top of $9,000 per month for ingestion. Total monthly Logs bill: $39,600 from a single 3-TB-per-day platform.
Three: APM unit drift. APM is per host. Modern container platforms scale pods 5 to 50x per host. Datadog's APM still counts the underlying host correctly in most cases, but customers running ephemeral compute (Lambda, Fargate, Cloud Run) accumulate APM unit counts that surprise their finance teams. Watch for "APM serverless" pricing, which bills per million invocations instead of per host.
The single biggest Datadog lever: Move Logs from full-fidelity hot retention to a tiered model. Send raw logs to S3 or Azure Blob, send only essential fields to Datadog. The Datadog Sensitive Data Scanner and Logs Pipelines features can drop low-value fields at ingest time. Customers who implement aggressive log filtering typically reduce Logs bill by 50 to 75 percent.
Datadog discount bands
| Annual commit (TCV) | Infrastructure discount | APM discount | Logs discount |
|---|---|---|---|
| $100K to $500K | 5 to 12 percent | 5 to 12 percent | 0 to 8 percent |
| $500K to $2M | 12 to 22 percent | 12 to 22 percent | 8 to 18 percent |
| $2M to $5M | 22 to 32 percent | 22 to 32 percent | 18 to 28 percent |
| $5M+ | 30 to 42 percent | 30 to 42 percent | 25 to 38 percent |
Datadog commits run 1, 2, or 3 years. Two-year commits typically add 3 to 5 percentage points over one-year. Three-year commits add a further 2 to 4 points. Multi-year commits should be weighed against the rapid product expansion: Datadog has launched 10-plus new SKUs in the past three years, and the buyer who commits to today's product set may find tomorrow's flagship feature priced outside the commit.
Seven negotiation levers
One: cross-product commit pool. By default, Datadog commits are per-product. Negotiate a pooled commit that can be drawn against any Datadog product, with periodic re-allocation. Two: ingest band lock. Lock the Logs ingest rate for the contract term with no annual escalation. Three: retention tier flex. Right to move log retention from 30-day to 15-day or 7-day for any data stream without contract amendment. Four: container peak smoothing. Bill against 7-day rolling average container count rather than daily peak. Five: APM serverless inclusion at no incremental price. Six: free non-production environments up to a defined host cap. Seven: true-down right of up to 20 percent at annual anniversary.
Datadog alternatives in the negotiation
Effective Datadog negotiation requires a credible BATNA. Three alternatives carry real negotiating power. First, the Splunk Observability Cloud and SignalFx combination has narrowed the feature gap, particularly on metrics and APM. Second, New Relic has restructured its commercial model to per-user plus consumption, which can land 30 to 50 percent below Datadog for organisations with few-but-deep users. Third, the open-source plus managed-services stack (Prometheus, Grafana, OpenTelemetry, Loki) handles 80 percent of typical observability needs at materially lower licensing cost, traded for higher operational cost.
For the three-way observability comparison and the decision framework that picks among them, see our Datadog vs Splunk vs New Relic comparison. For broader observability spend context, see our observability licensing guide. For the underlying cloud commit interaction (Datadog spend can be drawn against AWS Marketplace, Azure Marketplace, and GCP Marketplace commits), see our AWS Marketplace procurement strategy and AWS EDP negotiation. For broader cost controls, see our cloud cost optimization and cloud contracts guide. For Elastic and OpenSearch as a partial observability alternative, see our Elastic pricing and negotiation. To engage on Datadog negotiation, see our cloud contract negotiation service and SaaS license optimisation service.
Marketplace, partner, and reseller channel
Datadog is available via the AWS Marketplace, Azure Marketplace, and Google Cloud Marketplace. Marketplace purchases count toward the customer's cloud commitment (AWS EDP, Azure MACC, Google CUD). For organisations holding large cloud commits, routing Datadog through Marketplace is a structural saving that does not require Datadog discount negotiation: the same Datadog list price draws against the cloud commit, effectively recovering the cloud discount on the Datadog spend.
The Marketplace structural saving is typically 8 to 22 percent for buyers holding multi-million cloud commits. The trade-off is that Marketplace-purchased Datadog is subject to the Marketplace billing process and not all Datadog products are available via every Marketplace. Confirm the SKU coverage before routing. For the AWS Marketplace mechanics, see our AWS Marketplace procurement strategy.
Renewal-cycle bill-shock and how to defuse it
Datadog's renewal pattern is well-documented in advisor-led negotiations. The default renewal motion proposes a 12 to 25 percent annual increase, justified by SKU expansion, new product adoption, and inflation. Customers who accept the renewal motion without rebuilding the consumption baseline find themselves locked into a higher run-rate.
The defusal pattern is four-step. First, baseline current consumption by SKU 60 days before renewal, with peak versus average measurements per SKU. Second, identify the 20 percent of SKUs and the 20 percent of hosts driving 80 percent of the bill. Third, model three commercial scenarios: status quo, log filtering plus container peak smoothing, and partial migration to an alternative. Fourth, walk into the renewal with all three scenarios on paper. The default proposal becomes a negotiating position rather than a fait accompli.