{"slug": "datadog-pricing-breakdown-plans-costs-hidden-fees-2026", "title": "Datadog Pricing Breakdown: Plans, Costs & Hidden Fees (2026)", "summary": "Datadog's modular pricing model, with over 40 separately metered products, often results in invoices two to three times higher than initial estimates, according to a 2026 pricing breakdown. The platform charges per host, gigabyte, event, session, committer, or AI credit across tiers like Infrastructure, APM, and Log Management, with annual, month-to-month, and on-demand billing options. The analysis warns that unexpected scaling can trigger costly on-demand rates, making cost forecasting difficult for teams.", "body_md": "# Datadog Pricing Breakdown: Plans, Costs & Hidden Fees (2026)\n\nIf you've used or looked into Datadog, you already know Datadog is not one product with one price. It is a platform with more than 40 separately metered products stacked onto a single bill, each charged by its own unit, whether that is hosts, gigabytes, events, sessions, committers, or AI credits. That structure is why teams routinely see invoices two to three times higher than their first estimate.\n\nThis blog breaks down how Datadog actually charges you, from the plans and per-unit prices for the products that drive most bills to the billing mechanics that catch people off guard and the levers that keep costs under control. Every price here comes from Datadog's official pricing pages, captured in July 2026.\n\nBy the end of this article, you will be able to read a Datadog quote and estimate your bill before signing, with a clear sense of where costs grow fastest. We have also added a more affordable [Datadog alternative](https://signoz.io/datadog-alternative/) at the end for you to consider.\n\nHow Datadog pricing works (the billing model in plain English)\n\nDatadog is, at its core, a modular platform. There is **no single Datadog subscription**. You assemble a bill from individual products you choose, and the total depends entirely on which ones you turn on and how much data each one sees.\n\nThe following three ideas explain almost every line on a Datadog invoice.\n\n1. Price is Modular\n\nDatadog fragments its pricing across different products like Infrastructure Monitoring, [Application Performance Monitoring (APM)](https://signoz.io/application-performance-monitoring/), [Log Management](https://signoz.io/log-management/), Real User Monitoring (RUM), and the security suite, all billed separately. While this is often marketed as flexibility, the reality is that each new service brings its own unique pricing meter. As your observability needs grow, bolting on new features means juggling multiple billing dimensions, making it increasingly difficult to forecast your overall spend and avoid surprise overages.\n\n2. The Usage-Based Billing Matrix\n\nDatadog bills every product using a different yardstick: hosts for infrastructure, dual-metrics (GBs and events) for logs, sessions for RUM, and active committers for CI tools. This matrix of usage metrics means there is no single lever to control your costs. If you don't monitor every single one of these disparate units, you are practically guaranteed a billing surprise at the end of the month.\n\n3. Three Billing Options\n\nDatadog offers three billing tiers.\n\n`Annual`\n\nis the lowest rate and requires a committed volume.`Month-to-month`\n\nis a higher monthly rate with no annual commitment.`On-demand`\n\nis the highest rate, billed by actual usage with no commitment.\n\nFor example, while Infrastructure Pro is advertised at $15 per host annually, falling short on your estimation forces you into the $18 on-demand rate, turning any unexpected scaling into a costly premium penalty.\n\nDatadog's Core Product Pricing Overview\n\nTo give you a clearer picture, here’s an overview of how Datadog prices its main offerings.\n\nBelow prices are based on publicly available information for billing as of July 2026 and may be subject to change. It's always best to consult Datadog's official pricing page for the latest figures.\n\nProduct | Annual Billing | Key Details & Inclusions |\n|---|---|---|\nInfrastructure (Pro) | $15 per host/month | • On-demand: $18/host • 5 containers/host • 100 custom metrics/host • 500 custom events/host • 15-month retention |\nInfrastructure (Enterprise) | $23 per host/month | • On-demand: $27/host • 10 containers/host • 200 custom metrics/host • 1,000 custom events/host • ML alerts + governance |\nAPM | $31 per host/month | • On-demand: $36/host • 150 GB ingested spans/host • 1M indexed spans/host • Distributed tracing included |\nAPM Pro | $35 per host/month | • On-demand: $42/host • Everything in APM + Data Streams Monitoring |\nAPM Enterprise | $40 per host/month | • On-demand: $48/host • Everything in APM Pro + Continuous Profiler |\nContinuous Profiler (standalone) | $19 per profiled host/month | • On-demand: $23/host • 4 containers/profiled host • Extra containers: $2 each |\nLog Management - Ingest | $0.10 per GB/month | • Per GB uncompressed ingested • Covers processing, live tail, archiving • Charged even if not indexed |\nLog Management - Index | $1.70 per 1M events/month (15-day) | • On-demand: $2.55/1M • Retention: $1.06 (3-day), $1.27 (7-day), $2.50 (30-day) • Makes logs searchable + alertable • Flex Logs $0.05/1M for long retention |\nCustom Metrics | $5 per 100 metrics/month (overage) | • 100/host (Pro), 200/host (Ent.) included • Priced on cardinality • OTel counts as custom |\nReal User Monitoring (RUM) | $0.15 per 1,000 sessions (Measure) | • On-demand: $0.22/1K • Investigate: $3/1K sessions • Session Replay: +$2.50/1K • Scales with traffic |\nDatabase Monitoring | $70 per DB host/month | • On-demand: $84/host • Query-level metrics • Separate from infra host count |\nSynthetic API Tests | $5 per 10,000 runs/month | • On-demand: $7.20/10K • Scales with frequency & test locations |\nSynthetic Browser Tests | $12 per 1,000 runs/month | • On-demand: $18/1K • Full browser journey • Mobile testing: $50/100 runs |\nCloud Security Management | $10/host (Pro) $25/host (Enterprise) | • On-demand: $12 / $30 • Workload Protection separate ($15) |\nAI Credits | $500 per 500-credit bundle/month | • On-demand: $1.30/credit • No rollover • 0.3–6.5 credits per action |\n\nUnderstanding the Datadog Billing Mechanics & Hidden Costs\n\nDatadog does not simply multiply your average host count by the rate. It uses complex billing mechanics that often lead to bills significantly higher than initial estimates. Here are the four most common hidden traps to watch out for:\n\nHigh-Water-Mark Host Billing Trap\n\nDatadog's pricing for Infrastructure and APM is often tied to the number of hosts you're monitoring. It measures your host count every hour, discards the top 1% of hours with the highest usage, and then bills the entire month based on the next-highest hour, roughly the 99th percentile. This protects you from very brief spikes, but it means any period of sustained high usage sets the price for the whole month.\n\nFor example: Suppose you normally run 50 hosts, and for a 5-day marketing event you scale to 200. At the end of the month, Datadog ignores about the top 1% of hours (roughly 7 hours of your peak usage), but it still sees 200 hosts for the rest of that stretch, your host count was consistently 200. Your APM bill for the month is calculated on 200 hosts, not your typical 50.\n\n**Your Expectation (based on average):** Closer to`$2,260`\n\n**Billed (based on 5-days peak usage):**`$6,200`\n\n(200 hosts x $31/month)\n\nYou end up paying for your busiest week across the entire month, which is where most \"why is my bill so high\" surprises originate.\n\nThe Container Overallocation Trap\n\nThe same host model gets dangerous in containerized environments. The recommended setup is one Datadog Agent per host, for example, one per Kubernetes node. If an agent is misconfigured to run in every pod, each pod can be counted as a separate host. On a 50-node cluster running hundreds of pods, that single mistake can multiply the bill many times over.\n\nDouble Tariff for Log Management\n\nDatadog's log pricing is a two-part tariff. You pay once to collect logs (`Ingest`\n\n) and again to make them searchable (`Index`\n\n).\n\nBilling Type | Price | What it covers |\n|---|---|---|\nIngest | $0.10 per GB | Collect, process, and archive all logs |\nIndex | $1.70 per 1M events (15-day) | Make logs searchable + alertable. Other retention tiers: $1.06 (3-day), $1.27 (7-day), $2.50 (30-day) |\n\nThe Problem is that this model forces you to pay twice for the same data to make it useful for debugging. You must pay to collect every gigabyte of logs, but to get real-time query and alerting capabilities, you must again pay the much higher per-event indexing fee. This creates a strong financial disincentive to log comprehensively.\n\nImagine your application generates a modest 200 GB of logs in a month, which equates to roughly 100 million log events.\n\n**Ingest Cost:** You are first charged**$20/month**(200 GB x $0.10) just to get the logs into Datadog's system.** Indexing Cost:**To make these logs searchable for your developers during an incident, you then pay an additional**$170/month**(100 million events x $1.70) for 15-days of retention.\n\nYour total bill is **$190/month**. To cut that, teams index only a fraction of their logs, which means most of their log data is not searchable during an incident, exactly when they need it.\n\nDatadog's newer Flex Logs tier softens this for long-retention use cases. Flex storage is `$0.05`\n\nper million events stored and keeps data queryable for up to `15 months`\n\n, but it does not support monitors or Watchdog Insights, so it fits audit and compliance data more than active debugging. For a fuller breakdown of ingestion, indexing, and retention tiers, see our dedicated [Datadog logs pricing](https://signoz.io/blog/datadog-logs-pricing/) guide.\n\nThe Custom Metrics Pricing Trap\n\nCustom metrics are the most unpredictable part of a Datadog bill. A custom metric can be defined as any metric that does not come from a standard Datadog integration, which includes almost every metric you create for your own application. Critically, metrics sent through OpenTelemetry, the open-source observability standard, are also billed as custom. Our [Datadog custom metrics pricing](https://signoz.io/blog/datadog-custom-metrics-pricing/) guide goes deeper, but here is the short version.\n\nCustom Metrics | Price |\n|---|---|\nPro | 100 custom metrics per host |\nEnterprise | 200 custom metrics per host |\nOverage | $5 per 100 metrics/mo |\nIngested metrics (Metrics without Limits) | $0.10 per 100 metrics/mo |\n\nThe cost is driven by cardinality, meaning the number of unique combinations of a metric name and its tags.\n\nCardinality grows faster than people expect. Say you track `api.request.latency`\n\nacross 10 endpoints, 3 status codes, and 3 customer tiers. That is `10 x 3 x 3 = 90 unique metrics`\n\nfrom a single metric name. Add one [high cardinality](https://signoz.io/blog/high-cardinality-data/) tag such as `customer_id`\n\nand the count jumps into the thousands, triggering significant overage fees.\n\nTo manage this, Datadog offers `Metrics without Limits`\n\n, which lets you control which tags are indexed (and thus searchable). While this can lower costs, it introduces its own complexity and a new charge:\n\n-\n**Indexed Metrics:** You are billed the standard overage rate for the metrics you choose to index with specific tags. -\n**Ingested Metrics:** You also pay a separate, smaller fee (**$0.10 per 100 metrics**) for** all**the original metric combinations you sent to Datadog before your tags were filtered.\n\nEssentially, you are either paying a high price for full visibility or juggling two different charges to reduce it, adding another layer of complexity to your bill. If you want to bring an existing Datadog bill down, our guide on [how to reduce Datadog costs](https://signoz.io/guides/how-to-reduce-datadog-costs/) walks through the practical levers.\n\nThe pricing discussed in above section is Datadog's cardinality-based model, which applies unless your contract opts into the alternative. That alternative, **Metric Name pricing** model, bills by the number of unique metric names you submit and the volume of datapoints they produce, rather than by tag combinations. The two are mutually exclusive, so confirm which one your contract uses before forecasting.\n\nSigNoz Cloud: The Cost-Effective Datadog Alternative\n\nLook back at your own Datadog bill for a moment. For most teams, the spend concentrates in a handful of places like infrastructure hosts, APM hosts, indexed logs, and custom metrics. Everything covered in the sections above points to the same question. How much of that bill is buying you insight, and how much is just the cost of how the tool meters usage?\n\nAnswer it with your own numbers, because what you find decides whether a different pricing model would actually help you. Here is how Datadog and SigNoz compare on each cost driver from the sections above:\n\nDimension | Datadog | SigNoz Cloud |\n|---|---|---|\nBilling model | Per host + per-product usage | Usage-based on data volume |\nHosts | `$15 to $40` per host/month | No per-host charge |\nCustom metrics | `$5 per 100` over allotment; OTel is billed as custom | Not charged separately; OTel is not penalized |\nLogs | `$0.10/GB` ingest + `$1.70/1M` indexed | `$0.30/GB` ingested; No extra cost for indexing |\nTraces | `$31 to $40` per host + span overages | `$0.30/GB` ingested |\nMetrics | Cardinality-based custom metric fees | `$0.10 per million` samples |\nForecasting | Multiple meters + high-water-mark host counting | Single volume-based meter |\nVendor lock-in | Proprietary agent and data formats. Leaving means re-instrumenting | OpenTelemetry-native. Instrumentation stays portable if you switch |\n\nRun your last invoice against the above table. If it is dominated by host counts and custom metrics, the gap is not a rounding difference, and you can see exactly where it comes from.\n\n[SigNoz](https://signoz.io/) is an all-in-one, OpenTelemetry-native observability platform that unifies metrics, traces, and logs in a single application. Because it is built around [OpenTelemetry](https://signoz.io/opentelemetry/), sending your data through OTel does not trigger a custom-metric surcharge, and there is no per-host fee to optimize around. The instrumentation belongs to you, not the vendor, so your telemetry stays portable and you are not locked into proprietary agents that make leaving expensive. The [SigNoz pricing](https://signoz.io/pricing/) is easy to understand: `$0.30 per GB of logs`\n\n, `$0.30 per GB of traces`\n\n, and `$0.10 per million metric samples`\n\n.\n\nWhether Datadog's model fits your architecture is a call only you can make, and it should be made with your own bill in front of you. If the pattern you keep seeing is rising host counts and overages you did not forecast, it is worth putting a predictable, volume-based model side by side with your next Datadog quote before you renew. For teams already on Datadog, our [Datadog migration guide](https://signoz.io/docs/migration/migrate-from-datadog-to-signoz/) walks through moving dashboards and instrumentation instead of rebuilding them by hand.\n\nGet started with SigNoz\n\nThe easiest way to try SigNoz is [SigNoz Cloud](https://signoz.io/teams/), which comes with a 30-day free trial with access to all features.\n\nTeams with data-privacy requirements that prevent sending data outside their infrastructure can use the [enterprise self-hosted or BYOC offering](https://signoz.io/contact-us/). Teams that prefer to manage everything themselves can start with the free, self-hosted [community edition](https://signoz.io/docs/install/self-host/).\n\nFAQs\n\nHow much does Datadog cost per month?\n\nThere is no single number. Infrastructure Monitoring starts at $15 per host per month on annual billing, and you add per-product charges for APM, logs, metrics, and anything else you enable. A small production stack typically lands in the low hundreds; large environments reach five and six figures.\n\nWhy is my Datadog bill so high?\n\nThe usual causes are high-water-mark host billing during traffic spikes, the double charge for log ingest and indexing, and custom metric overages from high-cardinality tags. These are billed on top of the base plan and often appear in the second month of usage.\n\nDoes Datadog have a free plan?\n\nYes. The Free tier covers up to 5 hosts with 1-day metric retention. It is fine for evaluation but not for production, given the retention limit and host cap.\n\nHow does Datadog count hosts?\n\nA host is any physical or virtual OS instance, including VMs and Kubernetes nodes. Datadog measures host count hourly, drops the top 1% of hours, and bills the month on the next-highest hour.\n\nWhy are custom metrics so expensive in Datadog?\n\nCustom metrics are billed by cardinality, the number of unique metric-and-tag combinations. Pro includes 100 per host, then $5 per 100 metrics. A single high-cardinality tag can push the count into the thousands. Metrics sent via OpenTelemetry are billed as custom.\n\nIs Datadog cheaper billed annually or on-demand?\n\nAnnual is cheaper but requires a committed volume. Infrastructure Pro is $15 per host annually versus $18 on-demand, and usage above your commitment is billed at the higher on-demand rate.", "url": "https://wpnews.pro/news/datadog-pricing-breakdown-plans-costs-hidden-fees-2026", "canonical_source": "https://signoz.io/blog/datadog-pricing", "published_at": "2026-07-14 00:00:00+00:00", "updated_at": "2026-07-14 10:24:05.165416+00:00", "lang": "en", "topics": ["developer-tools", "ai-infrastructure"], "entities": ["Datadog", "SigNoz"], "alternates": {"html": "https://wpnews.pro/news/datadog-pricing-breakdown-plans-costs-hidden-fees-2026", "markdown": "https://wpnews.pro/news/datadog-pricing-breakdown-plans-costs-hidden-fees-2026.md", "text": "https://wpnews.pro/news/datadog-pricing-breakdown-plans-costs-hidden-fees-2026.txt", "jsonld": "https://wpnews.pro/news/datadog-pricing-breakdown-plans-costs-hidden-fees-2026.jsonld"}}