Datadog Pricing Explained: Hidden Costs, Billing Traps & a ...

But one thing comes up again and again in engineering communities, Slack channels, and Reddit threads: the bill. Teams report receiving invoices that were 3x, 5x, even 10x what they budgeted, not because they misunderstood the product, but because Datadog's pricing model has layers of complexity that only reveal themselves at scale or during unexpected traffic spikes. … ## The Core Problem: Multi-Dimensional Pricing Most SaaS tools charge you for one thing - seats, API calls, or storage. Datadog charges for many things simultaneously, each with its own pricing metric, allotment structure, and overage calculation. You're not buying one product; you're buying a bundle of sub-products that each generate their own line items. This creates a situation where forecasting your monthly bill requires understanding a dozen interrelated variables. A configuration change, a new service deployment, or a temporary traffic spike can silently trigger significant cost increases that only appear on next month's invoice. If you’re trying to estimate or reduce these costs, try our pricing calculator to see how much you could save by switching to OpenObserve. ... ### 1. Per-Host Billing in a World of Dynamic Infrastructure Datadog prices its core Infrastructure Monitoring and APM products on a per-host basis. In a world of containerized microservices and auto-scaling Kubernetes clusters, this model creates a structural mismatch between how you run software and how you get billed for monitoring it. Infrastructure monitoring starts at **$15 per host/month**. APM with continuous profiler starts at **$31 per host/month**. The definition of a "host" is deliberately broad: a VM, a Kubernetes node, an Azure App Service Plan, or an AWS Fargate task can all count. … #### The Container Trap This issue is amplified in containerized environments. The intended setup is one Datadog Agent per Kubernetes node. But if the agent is mistakenly deployed inside every pod, each pod is billed as a separate host. A misconfiguration on a 50-node cluster running hundreds of pods can multiply your bill by 10x or more overnight. ### 2. Why Custom Metrics Become Expensive at Scale This is frequently cited as the most unpredictable part of a Datadog bill. Datadog charges a premium for "custom metrics" any metric that doesn't come from a native Datadog integration. That includes virtually every application-level metric you create yourself, and critically, **all metrics sent via OpenTelemetry are billed as custom metrics**. … #### Metrics Without Limits™: A Complex Workaround Datadog's answer to cardinality costs is a feature called **Metrics Without Limits™**, which lets you control which tag combinations are indexed. But it adds another billing layer: - **Indexed metrics:** billed at the standard overage rate - **Ingested metrics:** a separate fee of **$0.10 per 100 metrics** for *all* data sent before filtering … To cut costs, you might index only 20% of your logs. But that means 80% of your data is invisible during an incident precisely when you need full visibility most. This pricing structure creates a perverse incentive: the teams that most need comprehensive logging are punished most heavily for it. Budget constraints lead to strategic under-logging, which leads to longer incident resolution times. … **The Configuration Trap** The "opt-out" is not a simple toggle in the Datadog UI. Because the billing is triggered by the *presence* of specific metadata in your OTel spans: 1. **Default Ingestion:** By default, the Datadog Agent and OTLP intake will process any recognized GenAI attributes. 2. **Manual Suppression:** To avoid these charges, engineers must manually configure their **OpenTelemetry Collector** or **Datadog Agent** to drop or mask GenAI-specific attributes (e.g., using a transform processor) before the data reaches Datadog's servers. … ## The Bottom Line Datadog is a powerful platform with deep integrations and strong brand recognition. ... But for teams running modern cloud-native architectures with auto-scaling, OpenTelemetry instrumentation, LLM-powered features, and cost sensitivity Datadog's pricing model creates friction at every layer. The per-host model discourages architectural flexibility. The custom metric tax penalizes comprehensive instrumentation. The log indexing structure forces a trade-off between cost and visibility.