Datadog Renewal Negotiation Guide

Pricing structures and available terms vary by plan and contract. Confirm the current terms with the vendor before negotiating.

Why Datadog renewals surprise people

Datadog contracts can include committed volumes across products such as infrastructure hosts, logs and APM. Usage beyond a commitment follows the contract’s overage terms, which can differ by product. Compare your contracted baseline with actual usage well before the renewal conversation.

This is a direct example of the true-up mechanic that shows up across usage-based SaaS generally, but it's sharper with Datadog because the products that drive overage — log volume especially — can spike suddenly with a single misconfigured service or a traffic event, not just gradual growth. See our note on consumption spikes for how this plays out operationally.

What to check before renewing

• Actual usage against committed baseline, by product, not blended. Host count, log ingestion volume, and custom metrics may be billed differently — a contract can look on-budget in aggregate while one specific product exceeds its commitment. Check your actual agreement.
• Where log ingestion and retention are driving cost. Log volume is a potential source of Datadog overage, and retention settings (how long logs are kept at full fidelity vs. archived) are often set once at implementation and never revisited as volume grows.
• Whether custom metrics counts have grown beyond what's actually monitored. Custom metrics are easy to create and rarely cleaned up — dashboards built for a project that's since ended often keep generating metric volume nobody is using.
• The committed-vs-on-demand rate gap. Ask directly what the per-unit difference is between committed and on-demand pricing for each product you're using meaningfully above baseline — this is the number that tells you whether raising the commitment or cutting usage is the better lever.

Where the real leverage is

• Right-size the commitment to actual trailing usage, not a growth projection. An account team may propose a higher commitment tier sized to projected growth. Counter with trailing 90-day actual usage data — it's a harder number to argue against than a forecast, and it avoids locking in a commitment level you may not reach.
• Separate "waste" from "growth" before negotiating. Unused custom metrics, forgotten dashboards, and log retention set longer than needed are waste — cut these first, for free, before discussing commitment levels. What's left after that cut is your real growth trajectory, and that's what should drive the renewal commitment.
• Negotiate the on-demand rate, not just the committed rate. Even with a well-sized commitment, usage may exceed it. Ask how the overage rate is calculated, since it's the rate you'll actually pay on anything above baseline.
• Multi-product bundling leverage. If you're using several Datadog products (APM, logs, RUM), negotiating the renewal as a single bundled commitment across products — rather than each product's baseline negotiated separately — may be worth asking about; compare the quoted terms with separate line-item prices before committing.

A worked example

Illustrative scenario: a team commits to 500 GB of daily log ingestion and later averages 640 GB. Before accepting a proposed 750 GB commitment, it finds and fixes verbose logging in one service. The team can now discuss a commitment against corrected usage. Actual overage charges and reconciliation depend on the contract.