Enterprises that want a single pane of glass across infra, apps, and security and can budget for the bill.
Cost-sensitive startups — observability bills balloon quickly; Grafana Cloud or self-hosted Prometheus + Loki often fit better.
What is Datadog?
Datadog is the dominant enterprise observability platform. What began as infrastructure monitoring now spans 20+ products: APM, logs, RUM, synthetics, network performance, Cloud SIEM, ASM, CSPM, and LLM Observability. Its biggest pain point is cost — most customers eventually hit per-host, per-GB log, or custom-metric bills that force careful tuning.
Key features
Integrations
What people actually pay
No price data yet — be the first to share
No price data yet for Datadog. Help the community — share what you pay (anonymized).
The default observability platform — and the cost of default
Datadog owns enterprise observability. APM, logs, metrics, RUM, security all work. The pricing is genuinely brutal at scale, and the alternatives (Grafana Cloud, Honeycomb, Coroot) have gotten serious enough to evaluate.
Datadog's product breadth is unmatched in observability — APM, infrastructure monitoring, log management, RUM, synthetic checks, network monitoring, security monitoring (Cloud SIEM), and now AI/LLM observability. The unification advantage is real: a single dashboard that correlates application traces with infrastructure metrics with log lines with security events is something Grafana Cloud and the unbundled Honeycomb/Sentry stack don't fully match.
The pricing is the persistent and severe complaint. Datadog's consumption-based model — host-counts, indexed log volume, custom metrics, RUM sessions, APM hosts — produces uncomfortable bills at scale. $1M-$10M annual Datadog contracts are routine in mid-market and enterprise; many companies report Datadog as their second-largest infrastructure expense after cloud spend itself. The "Datadog tax" is so well-known that "we're replacing Datadog" is now a common engineering project.
The alternatives have gotten credible. Grafana Cloud + Loki + Tempo + Mimir delivers most of Datadog's functionality at meaningfully lower cost for engineering-mature teams. Honeycomb wins on tracing depth for high-cardinality use cases. Coroot, OpenTelemetry-native open-source, and the Sentry product line cover specific niches better.
Buy Datadog if you're a 1,000+ employee organization where observability unification matters more than cost optimization, or where your team doesn't want to operate observability infrastructure. Negotiate hard. Replace with Grafana Cloud if cost is now first-order and you have engineering capacity. Replace specific surfaces (Honeycomb for tracing, Sentry for errors) before doing a wholesale migration.
1,000+ employee organizations where observability unification matters more than cost; teams that don't want to operate observability.
Cost-sensitive scale-ups; engineering-mature teams who can run Grafana Cloud or self-hosted observability cheaper.
Written by StackMatch Editorial. StackMatch editorial reviews are independent analyst commentary, not user reviews. We have no affiliate relationship with this tool. See user reviews below for community perspective.
Before you buy Datadog
Vendors don't tell you about their competitors. We do — with verdicts attached when we have them.
What Datadog actually costs
Sticker price isn't the real cost. We add implementation, training, and a probability-weighted lock-in penalty.
When to negotiate Datadog
Vendor sales pressure is non-uniform — quarter-close, year-end, and post-funding-round are your high-leverage windows.
Strong negotiation window. Reps will push for end-of-quarter signature. Don't move first — let them initiate the discount. Target 15-30% off list plus negotiated terms.
Take this to your sales call
11 questions vendor sales teams steer around — generated from Datadog's pricing tier, lock-in profile, and editorial verdict.
- 1PRICINGDatadog is professional-tier on the public site. What's the discount path for small-sized teams committing annually vs. monthly?
- 2PRICINGWhat overages or seat-overflow charges should we plan for? Show me the worst-case bill if our usage grows 2x in year 1.
- 3CONTRACTAuto-renewal: how many days notice is required to terminate, and what happens if we miss the window? Will you commit to a renewal-reminder email at 90 and 60 days?
- 4MIGRATIONData export: what's the complete spec — format, frequency, and what data does the export NOT include? After contract end, how long do we have read-only access?
- 5MIGRATIONImplementation runs 2–6 weeks for initial coverage. Who from your team is included by default, and who do we add at additional cost? Is a CSM assigned?
- 6FITIndependent analysis (StackMatch Editorial) flags this verdict: "The default observability platform — and the cost of default." How do you address this concern specifically for our use case?
- 7FITDatadog is best for: 1,000+ employee organizations where observability unification matters more than cost; teams that don't want to operate observability.. We're [describe your situation]. Walk me through the failure modes if our profile doesn't match.
- 8FITConnect us with 2-3 reference customers at our company size in your industry — not the case-study list, customers who've been live for 18+ months and have churned at least one tool from your stack.
- 9INTEGRATIONDatadog lists 4 integrations including AWS, Kubernetes, GitHub. Which of OUR existing tools — bring our list — have you confirmed shipping integration with versus "on roadmap"? Show me the actual status.
- 10VENDORTrack record over the last 18 months: any pricing model changes, executive departures, layoffs, M&A activity, or material customer churn we should know about?
- 11VENDORIf you're acquired or shut down, what's the contractual continuity — source-code escrow, data portability, transition period? Show me the actual clause.
What to actually test in the demo
Vendor sales teams script demos to maximize close rate. Here's what they'd rather you not test — derived from Datadog's lock-in profile and editorial verdict.
- 1PERFORMANCEBring YOUR data, not their demo data. Insist on running the demo workflow against a sample of your real records, files, or queries. If they refuse — that's a signal.
- 2PERFORMANCEEditorial flags: "The default observability platform — and the cost of default." Construct a demo scenario that directly tests this concern. Ask the rep to walk you through it in real time, not promise a follow-up.
- 3PERFORMANCEDatadog demo will be built around the happy path. Ask: "Show me what happens when [the most common failure mode in our context]" — make them improvise.
- 4EDGE CASESPush the limits live: largest dataset, longest workflow, most users concurrent. Vendors prep demos for medium loads — your real-world usage might 10x what they show.
- 5EDGE CASESMobile and offline behavior: how does Datadog degrade on slow connections, on iPad, in airplane mode? Test in the demo if your team uses these surfaces.
- 6PRICINGModel your worst-case bill: 2x the seats, 3x the usage. Show the exact dollar figure on screen during the demo. Refuse "we'll get back to you" — get the math live.
- 7INTEGRATIONVendors love their integration logo wall. Test the actual depth: pick the 2-3 (AWS, Kubernetes-style) integrations you depend on most, and ask the rep to demo a real two-way data sync, not a marketing screenshot.
- 8INTEGRATIONAPI and webhook reality check: rate limits, payload size limits, retry behavior, auth refresh handling. Ask for actual API docs in the demo, not "we'll send those."
- 9MIGRATIONDemo the full data export workflow. Even with low lock-in, you want to see how clean the exit looks before signing.
- 10SUPPORTSubmit a real support ticket DURING the demo. Use the actual support channel customers use, not the rep's email. Time the response. This is your most honest data point about post-sale reality.
- 11SUPPORTAsk to be connected with a customer in the demo who you can email TODAY (not "we'll arrange a reference call next week"). The vendor's confidence in their references is a tell.
User Reviews
Be the first to review this tool