Datadog APM & Error Tracking

Rest of world Report an error

Panel rating · 6 judges · How to read the stars

Category median

Sovereignty: 2 of 6 dimensions proven

0–5 in half steps. 5 means the rubric's top anchor is met on the evidence.

by Datadog, Inc. · www.datadoghq.com

Compare with Dynatrace → Report an error on this page Is this your product? →

Link to this page

Datadog APM & Error Tracking: AI-assisted analysis on whats-best.ai Datadog APM & Error Tracking: AI-assisted analysis on whats-best.ai (dark)

Add ?theme=dark to the image address for dark backgrounds. The badge shows the category and the month of the latest evaluation, and EU-Made where that is the product’s provenance. It never shows a score.

Datadog APM & Error Tracking at a glance

Vendor
Datadog, Inc.
Headquarters
Incorporated in the United States source, captured 6 Nov 2026
Data hosting
Not stated on the vendor’s pages as of 6 Nov 2026
Free plan
Yes, per the vendor’s own page source, captured 6 Nov 2026
Panel verdict
The AI panel rates Datadog APM & Error Tracking 3.5/5, the mean of 6 judges. Datadog APM & Error Tracking, from Datadog, Inc., a Delaware corporation, scored highest on performance tracing and lowest on pricing transparency. how scores are made
As of
Vendor pages captured 6 Nov 2026; evaluated by the panel 6 Nov 2026. all sources

Datadog APM & Error Tracking alternatives, European ones first →

Read this page as one judge. Each weighs the same scores by what they care about.

The panel's verdict

Datadog APM & Error Tracking, from Datadog, Inc., a Delaware corporation, scored highest on performance tracing and lowest on pricing transparency. Judges credited distributed tracing from browser and mobile to backend services and databases, automatic trace-to-profile linking, OpenTelemetry ingestion and retention published per data type in a public table; the same pages leave per-host prices at 'Contact sales for pricing' with no public price for APM hosts, error tracking or real user monitoring, so an annual cost is not computable from public pages alone. Error tracking loses ground where pages show no crash-free user or session rates and no native symbolication. Sovereignty split 5-7: lower scores weighed the US contracting entity and US-based AI, email, support and payment subprocessors; higher scores credited the EU site in Germany, a published data processing agreement incorporating SCCs and a public subprocessor list. Data controls split 6-8, between pages that show no IP anonymisation or spike protection and scrubbing documented down to the identifiers redacted before data leaves the host. Workflow and integrations held at 7; security and reliability at 6-7.

Report an error

Speaks for it

  • Distributed tracing from browser and mobile to backend services and databases, with automatic trace-to-profile linking and profiling across seven languages.
  • Error grouping documented down to stack-frame normalisation, with custom fingerprints taking precedence and issues carrying states, regression detection and suspect commits.
  • Sensitive identifiers such as password and accessToken redacted before data leaves the host, in modes that can be switched but not disabled, plus a regex-based Sensitive Data Scanner after upload.
  • Retention published per data type in a public table, with error samples at 30 days and issues one year after last activity.
  • Access control with three managed roles, clonable custom roles, SAML mappings, SCIM and an audit trail retained 90 days.

Report an error

Held against it

  • The Basic infrastructure plan reads 'Contact sales for pricing', and we found no public price for APM hosts, error tracking, real user monitoring, SSO or the EU region.
  • We found no public information on crash-free user or session rates, native symbolication for mobile crashes, or merging and splitting of grouped issues.
  • The contracting entity is the Delaware corporation, and the subprocessor list includes seven US AI services alongside US email, support and payment providers.
  • We found no public information on a public status page with incident history, a vulnerability disclosure programme, or how SDKs behave while Datadog itself is down.
  • We found no public information on IP anonymisation, spike protection with its billing behaviour, or deletion of individual events or users.

Report an error

Best for

  • You need distributed tracing from browser and mobile applications to backend services and databases, with traces automatically linked to profiles.
  • You ship across browser, mobile and more than ten backend languages and want error grouping you can override with custom fingerprints.
  • You hold customer data that must be scrubbed before it leaves your hosts, with redaction that cannot be disabled.
  • Your on-call workflow runs on Jira, GitHub or GitLab and webhooks with retries and per-service queues.

Report an error

Avoid if

  • You must compute a full annual cost from public prices before talking to sales.
  • Your store-rollout gate depends on crash-free user or session rates per release, or native symbolication.
  • You require a European contracting entity or a chain without US subprocessors; the contract is with the Delaware corporation and the AI, email, support and payment links are US providers.
  • Your procurement requires service credits for outages; the published availability remedy is termination with a pro-rated refund after two consecutive months below standard.

Report an error

The scores

Panel median The median of the judges’ scores per criterion. Each label opens its reasoning below.

Error capture, grouping & triage

Show reasoning
How this is scored

What happens to an exception or crash: SDKs for the languages, frameworks and platforms a team runs (PHP and Laravel, JavaScript in the browser and Node, Python, Ruby, Java, .NET, Go, iOS, Android, Flutter, React Native), stack traces with source maps and symbolication, context (request, user, breadcrumbs, environment, local variables), grouping and custom fingerprints, deduplication, issue states (resolved, ignored, regressed), releases and deploy tracking, suspect commits, crash-free sessions and users for mobile apps, and search and filters over issues.

0 — Catches no application errors or crashes; a log viewer or an external check only.

3 — Errors from one or two platforms arrive with a stack trace and are grouped; context, issue states, releases and source maps are basic or not described.

5 — SDKs for the common web and backend platforms, stack traces with source maps, request and user context and breadcrumbs, automatic grouping with issue states and regression detection, release and deploy tracking, and issue search and filters.

8 — SDKs across backend, frontend and mobile with symbolication documented, custom fingerprinting and merge or split of issues, suspect commits or code owners, crash-free users and sessions, local variables or source context per frame, and every SDK documented with its configuration options.

10 — Error tracking a large engineering organisation standardises on: every platform it runs covered with parity stated, grouping rules editable and explained, release health with adoption and regression per version, and the full issue lifecycle reachable by API.

Report an error

The Agency Tech Lead

Grouping is properly documented — service, error class, message and topmost stack frame, with custom fingerprints that override the default, token normalisation explained, and stack-frame noise like versions and IDs stripped before grouping. Issues get states, regression detection, suspect commits, team ownership, impacted-user counts, and Exception Replay captures local variable values at the exception for Python, Java,.NET and PHP, with source-code previews inside the trace. We found no public information on symbolication, merging or splitting issues, or crash-free session and user figures, so we stop below the top band. 3 6 14 15

Report an error

The SaaS CTO

Error Tracking covers browser, mobile and ten-plus backend languages, groups by service, error type, message and topmost stack frame, and lets me override grouping with a custom fingerprint; issue states, regression detection, suspect commits, team ownership and auto-assign are documented, and Exception Replay captures local variable values with source-code previews inside the stack trace. We found no public information on crash-free user or session rates, symbolication for mobile stacks, or merging and splitting of grouped issues, which is what keeps this short of the top of the range for a team of our size. 3 6 14 15

Report an error

The Mobile Team Lead

Error grouping is documented in real depth — default grouping on service, error class, message and the topmost stack frame, overridable with a custom fingerprint — and issue states, regression detection, suspect commits and Exception Replay's captured local variable values are all evidenced, with SDKs listed for iOS, Android and Flutter. What I could not find on the captured pages is the mobile release-health side I run on: crash-free users or sessions per release and native symbolication are not documented here, so I cannot confirm my store-rollout gate from this evidence. 3 6 14 15

Report an error

The Site Reliability Engineer

Grouping is properly documented — default grouping on service, error type, message and the topmost stack frame, with custom fingerprints that take precedence and can apply to a subset of errors — and the issue lifecycle carries states, regression detection, suspect commits and team ownership across browser, mobile and backend sources. Exception Replay captures local variable values for Python, Java,.NET and PHP, with code previews in stack traces via the source code integration. I found no public information on symbolication for mobile crashes, merging or splitting issues, or crash-free session and user rates, so I score it just below the top level. 3 6 14 15

Report an error

The Data Protection Officer

Errors arrive from browser, mobile and backend across ten-plus languages and frameworks, grouping is explained down to stack-frame normalisation with custom fingerprints taking precedence, and issues carry states, regression detection, suspect commits, team ownership and even captured local variables. That variable capture is generally available only for Python, Java,.NET and PHP and only for tracing-based errors, and we found no public information on symbolication, merge or split of issues, or crash-free user and session figures. 3 6 14 15

Report an error

The Skeptic

Grouping is documented down to the tokens it ignores and custom error fingerprints that take precedence over the default strategy, and Exception Replay captures local variable values for Python, Java,.NET and PHP with code previews inside stack traces, beside suspect commits, regression detection and issue team ownership. We found no public information on native crash symbolication, crash-free session or user rates, or merging and splitting of grouped issues, which keeps it short of the top tier. 3 6 14 15 21

Report an error

APM, tracing & profiling

Show reasoning
How this is scored

How the product shows where time goes: transaction and endpoint timings with percentiles, slow database queries and N+1 detection, background jobs and queues, external HTTP calls, distributed tracing across services, OpenTelemetry ingestion, code-level profiling, frontend performance and Core Web Vitals (real user monitoring), host or container metrics beside the traces, anomaly detection on throughput and latency, and the link from a slow trace to the error it caused.

0 — No performance data of any kind; errors only.

3 — Response times per endpoint or a simple performance view; tracing across services, query analysis and profiling are basic or not described.

5 — Transaction timings with percentiles per endpoint, slow query and N+1 detection, background job monitoring, distributed tracing across services, a link between traces and errors, and frontend performance or Web Vitals offered.

8 — OpenTelemetry ingestion documented, code-level or continuous profiling, real user monitoring with Web Vitals, host and container metrics beside the traces, anomaly detection on latency and throughput, and sampling of traces configurable with its effect explained.

10 — Full application performance management evidenced: traces, profiles, frontend and backend joined end to end, service maps, SLOs on endpoints, and every signal documented with its retention and sampling per plan.

Report an error

The Agency Tech Lead

Distributed tracing from browser and mobile down to the database, continuous profiling across seven languages including PHP, endpoint-scoped flame graphs, OpenTelemetry ingestion, RUM with vitals events, ML-based anomaly alerts and Watchdog root-cause analysis — and a retention page spells out what every signal keeps per plan, which is what my maintenance contracts actually need to answer. Trace-to-profile linking is automatic when both run, sampling is adjustable at host, service and endpoint level, and RUM sessions associate with backend traces. We found no public information on service maps or explicit per-endpoint percentile views, so not the top score. 2 5 16 21

Report an error

The SaaS CTO

This is the part I care most about and it holds up: distributed tracing from browser and mobile down to the database, OpenTelemetry ingestion documented, continuous profiling with automatic trace-to-profile linking and endpoint profiling across Java, Python, Go, Ruby, Node,.NET and PHP, and real user monitoring with vitals events joined to backend traces. Retention is published per data type — indexed spans fifteen or thirty days depending on plan, errors fifteen days — with sampling adjustable at host, service and endpoint level; service maps and sampling per plan are the pieces the captured pages do not confirm. 2 5 16 21

Report an error

The Mobile Team Lead

This is where the evidence is strongest: code-level distributed tracing from browser and mobile applications to backend services and databases, automatic trace-to-profile linking with endpoint profiling across seven languages, OpenTelemetry support, real user monitoring with vitals events, ML-based anomaly alerts, and sampling controls at host, service and endpoint level. Retention is even published per data type, which is more than I need to trust the numbers. 2 4 5 16 21

Report an error

The Site Reliability Engineer

Distributed tracing from browser and mobile to backend services and databases is documented, with OpenTelemetry ingestion, continuous profiling automatically linked to traces (endpoint profiling across seven languages), real user monitoring whose vitals events sit alongside error events, infrastructure and container monitoring beside the traces, Watchdog and machine-learning anomaly alerts, and sampling and retention filters configurable from host down to endpoint. A retention table states errors, indexed spans, statistics and flame graphs by plan. I found no public information on service maps, so I stop just short of full marks. 2 5 16 17 21

Report an error

The Data Protection Officer

Distributed tracing reaches from browser and mobile into backend services and databases, OpenTelemetry ingestion and a continuous profiler across seven languages are documented, traces and profiles are automatically linked, and real user monitoring events include vitals with retention stated per signal in a public table. Anomaly detection comes via machine-learning based alerts and Watchdog; we found no public information on service maps or on sampling rates stated per plan. 2 4 16 21

Report an error

The Skeptic

Distributed tracing from browser and mobile down to the database, automatic trace-to-profile linking, continuous profiling across seven languages, real user monitoring with vitals events, machine-learning anomaly alerts and sampling controls at host, service and endpoint level are all documented with retention stated per data type. We found no public information on per-endpoint percentile timings, N+1 or slow-query detection, or what a chosen sampling rate actually does to the data you keep and pay for. 2 4 5 16 21

Report an error

Alerting, integrations & developer workflow

Show reasoning
How this is scored

How an error reaches the person who fixes it: alert rules on new issues, regressions, frequency and performance thresholds, notifications to email, Slack, Microsoft Teams, PagerDuty or Opsgenie, issue tracker integrations (Jira, GitHub, GitLab, Linear) that create and sync issues, source code links to the repository, deploy and release hooks from CI, a documented REST API and webhooks, a CLI, AI features that explain an error or suggest a fix (and which model runs them), and digest or weekly reports.

0 — No notifications and no integrations; errors are only visible by logging in.

3 — Email or chat notifications for new errors and one or two integrations; alert rules, the issue tracker link and the API are basic or not described.

5 — Configurable alert rules for new, regressed and frequent errors, Slack and email and an on-call tool, issue tracker integrations with GitHub, GitLab or Jira, deploy tracking from CI, a documented REST API and webhooks.

8 — Two-way sync with issue trackers, source code and commit links, alerts on performance thresholds and anomalies with routing per team or project, a CLI for releases and source maps, AI explanations or fix suggestions with the model provider named, and scheduled reports.

10 — A workflow a large team runs on: ownership rules routing issues to teams, every setting reachable by API or infrastructure as code, alert noise controls documented, and every AI feature documented with its data handling and an opt-out.

Report an error

The Agency Tech Lead

Monitors sit directly on error-tracking events such as new issues and high error volume, alerts are unlimited on all plans, and webhooks go deep — custom payloads, hidden variables, OAuth with token refresh, per-service retry queues, Terraform support — with Slack and PagerDuty named alongside them. Jira issues are created and kept synced from alerts with templates and template variables, GitHub and GitLab source integrations exist, and there is a documented API with bearer-token auth plus Bits AI features. We found no public information on a CLI for releases and source maps, scheduled error digests, or which model provider runs each AI feature. 2 6 18 19 23

Report an error

The SaaS CTO

Monitors fire on new issues and high error volume with machine-learning-based anomaly alerts, the Jira integration syncs two ways with issue templates and template variables, GitHub and GitLab source integrations link commits and ownership, and webhooks support OAuth with token refresh, retries and Terraform. Bits AI can investigate errors, but we found no public information naming which model runs those features, and no CLI for releases and source maps or scheduled digest reports on the pages we read. 2 6 18 19

Report an error

The Mobile Team Lead

Monitors on new issues and high error volume, a Jira integration with bidirectional case sync, GitHub and GitLab source links, webhooks with OAuth, retries and per-service queues, Terraform and a documented API, plus team ownership and auto-assign — that covers my on-call rota. The captured pages give no CLI for releases and source maps, no scheduled digest reports, and the AI features are named without a model tied to them, so I stop short of the top level. 1 2 6 18 19

Report an error

The Site Reliability Engineer

Monitors sit on error tracking events such as new issues and high error volume, with machine-learning anomaly alerts, and webhooks retry on 5XX with per-service queues — the PagerDuty and Slack isolation example reads exactly like on-call tooling. Jira syncs both ways with issue templates and attribute sync, GitHub and GitLab source integrations exist, roles and settings reach an API plus Terraform, and the Bits AI features are listed while the AI model providers appear by name on the subprocessor page. I found no public information on a CLI for releases and source maps or on scheduled error digest reports. 6 8 13 18 19 23

Report an error

The Data Protection Officer

Monitors on error events, unlimited alerts on all plans, a deeply documented webhook system with OAuth token handling and retries, and a Jira integration with bidirectional case sync cover the core workflow, with GitHub and GitLab source integrations and issue team ownership routing errors to owners. We found no public information on a CLI for releases or source maps or on scheduled reports, and the Bits AI features are named without a model attribution per feature. 6 8 18 19

Report an error

The Skeptic

Monitors on new issues and error volume, a Jira integration with bidirectional sync and issue templates, GitHub commit and ownership data in Error Tracking, webhooks with five retries and OAuth token handling, and a documented permissions API cover most of what a team runs on. We found no public information naming which model provider runs each Bits AI feature, a CLI for releases and source maps, or scheduled error digests. 1 6 13 18 19 23

Report an error

Data scrubbing, retention & volume control

Show reasoning
How this is scored

What the product does with the personal and secret data an error carries and how volume is kept in check: scrubbing of passwords, tokens, card numbers and personal data in the SDK and on the server with configurable rules, IP address anonymisation, opting out of request bodies and user data, data retention per plan and deletion on request, sampling of errors and traces, rate limits, spike protection and quota caps per project, filters that drop events before they count, data export, and a self-hosted edition that keeps every event on the customer's own servers.

0 — No control over what is captured, no retention period stated, no limit on volume.

3 — Some default filtering of passwords and a retention period stated for one plan; server-side scrubbing, sampling and spike protection are basic or not described.

5 — Configurable data scrubbing in the SDK and default server-side scrubbing of common secrets, IP anonymisation, retention stated per plan, sampling and rate limits per project, a quota cap or spike protection, and event filters before ingestion.

8 — Custom server-side scrubbing rules with examples, per-project retention settings and deletion of individual events or users, spike protection documented with how overage is billed, data export by API, and a self-hosted edition or a documented option to keep data in the customer's chosen region.

10 — Data minimisation by design and evidenced: personal data off by default in every SDK, scrubbing rules auditable, retention and deletion controllable per data type, volume controls that never surprise the invoice, and a supported self-hosted edition with feature parity stated.

Report an error

The Agency Tech Lead

Scrubbing is the strong point: two redaction modes that cannot be disabled, only switched, with sensitive identifiers like password and accessToken scrubbed before data leaves the host, custom identifier and type lists set by environment variable, a high-entropy secrets scanner, and a regex-based Sensitive Data Scanner server-side on top — exactly the posture I need when shops hold customer addresses. Retention is documented per data type and product, trace sampling is configurable through ingestion controls and retention filters, snapshots are rate-limited, and telemetry quotas with blocking enforcement exist. We found no public information on IP anonymisation, spike protection, or deletion of individual events, and overage behaviour at quota is only priced out for containers and custom events. 15 20 21 22

Report an error

The SaaS CTO

Scrubbing is unusually well documented: identifiers like password and accessToken are redacted before data leaves the host, strict and targeted redaction modes cannot be switched off, custom identifier and type rules are configurable by environment variable, and the Sensitive Data Scanner applies regex rules server-side after upload. Retention is published for every data type — error samples thirty days, issues a year after last activity, spans fifteen or thirty days by plan — and overage is priced per unit for containers and custom events; we found no public information on spike protection as such, IP anonymisation, or deletion of individual events or users. 8 15 20 21

Report an error

The Mobile Team Lead

Scrubbing is unusually well documented: Strict and Targeted modes redact passwords, access tokens, card numbers and high-entropy secrets before data leaves the host and cannot be switched off, a regex-based Sensitive Data Scanner runs after upload, retention is published per data type, and snapshot rate limits and sampling controls exist. I found no public information on spike protection with its overage billing, on deleting individual events or users, or on data export by API. 5 10 15 20 21

Report an error

The Site Reliability Engineer

Scrubbing is taken seriously: Strict and Targeted redaction modes that cannot be switched off, identifier and type rules redacting before captured data leaves the host, and a regex-based Sensitive Data Scanner working after upload. Retention is published per data type and plan, ingestion controls set sampling by service and resource, Exception Replay snapshots are rate-limited to one per exception type per instance per hour, and containers and custom events have published on-demand rates. I found no public information on IP anonymisation or on spike protection for error and span volume, which is the piece I would want before an incident also becomes a billing surprise. 5 8 15 20 21

Report an error

The Data Protection Officer

Sensitive identifiers such as password and accessToken are redacted before captured data leaves the host, in strict and targeted modes that can be switched but not disabled, and a regex-based Sensitive Data Scanner scrubs server-side after upload — the order of operations I look for. A public table states retention per data type, with error samples at 30 days and issues one year, and trace sampling is configurable; we found no public information on IP anonymisation, per-project retention settings, deletion of individual events, or spike protection with its billing behaviour. 15 20 21

Report an error

The Skeptic

Sensitive values tied to identifiers like password and accessToken are scrubbed before they leave the host, the redaction modes cannot be disabled only switched, a high-entropy secrets scanner runs, and a full retention table per data type is published. We found no public information on IP anonymisation, deletion of individual events or users, spike protection and how overage is billed, or export by API — exactly the controls that keep an invoice honest. 5 10 15 20 21

Report an error

Access control, security & the vendor's reliability

Show reasoning
How this is scored

Whether the service holds up in an audit and on the vendor's own bad day: organisations, teams and projects with roles, single sign-on (SAML or OIDC) and SCIM, two-factor authentication, audit logs, encryption in transit and at rest, security certifications and reports (ISO 27001, SOC 2), a security page and a vulnerability disclosure policy, the vendor's own public status page and incident history, a stated availability or SLA, and how ingestion behaves when the vendor is down (SDK buffering, no impact on the app).

0 — Nothing on access control, security or the vendor's own availability.

3 — User accounts with two-factor authentication and a security page; roles, SSO, certifications and a status page are basic or not described.

5 — Organisations and projects with roles, two-factor authentication, single sign-on offered on some plan, encryption in transit and at rest stated, a public status page, and a security page naming certifications or audits.

8 — SAML SSO and SCIM provisioning, audit logs, ISO 27001 or SOC 2 with its scope stated, an SLA with credits published, the incident history public, a vulnerability disclosure or bug bounty programme, and SDK behaviour during vendor outages documented.

10 — Enterprise-grade operation evidenced: granular roles per project and team, audit logs exportable to a SIEM, independent audit reports available on request, published uptime history over years, and ingestion designed and documented never to slow the customer's application.

Report an error

The Agency Tech Lead

Three managed roles plus clonable custom roles with per-permission defaults, SAML with multiple providers and SCIM, an audit trail with 90-day retention, encryption in transit and at rest, an annual SOC 2 commitment with annual penetration tests and background checks, and a Trust Center that hands over documentation on request — that holds up in a client audit. The service terms publish an availability remedy of termination with a pro-rated refund after two consecutive months below standard. We found no public information on a public status page with incident history, a vulnerability disclosure programme, or how the SDKs behave when Datadog itself is down. 8 9 12 21 22

Report an error

The SaaS CTO

Access control is granular enough for my thirty-five engineers — three managed roles, clonable custom roles, sensitive permissions flagged, SCIM, multiple SAML providers and IP allowlists on higher plans, plus an audit trail with ninety-day retention. The data processing agreement commits to annual SOC 2 renewal and annual penetration testing, a FedRAMP High site exists, and the subscription agreement offers termination with a pro-rated refund after two months below standard; we found no public information on a status page, incident history, a vulnerability disclosure programme, or how SDKs behave when Datadog itself is down. 7 8 10 12 22

Report an error

The Mobile Team Lead

Granular role-based permissions with a permissions API, multiple SAML providers and SCIM, a 90-day audit trail, encryption in transit and at rest, annual penetration tests and SOC 2 maintained annually with ISO 27001 guidelines — that would pass our audit. What the captured pages do not show is a public status page or incident history or a vulnerability disclosure programme, the availability remedy is termination with a pro-rated refund rather than credits, and nothing documents how SDKs behave while Datadog itself is down. 8 10 12 21 22

Report an error

The Site Reliability Engineer

Roles go deep — three managed roles, cloneable custom roles with a long permission list and a permissions API — and SAML with multiple providers, SCIM, IP allowlists and an audit trail kept 90 days are documented. The data processing addendum commits to annually renewed SOC 2 with encryption in transit and at rest and annual penetration testing, the terms publish an availability remedy of termination with a pro-rata refund after two consecutive months below standard, and a FedRAMP High site exists. I found no public information on a public status page with incident history, a vulnerability disclosure programme, or how the SDKs behave when Datadog itself is down — the questions I ask when the monitoring is the thing that is broken. 7 8 9 10 12 21 22

Report an error

The Data Protection Officer

Role-based access is genuinely granular — three managed roles, clonable custom roles, flagged sensitive permissions, SAML mappings and SCIM among the advanced admin features, plus an audit trail retained 90 days — and the agreement commits to annual SOC 2 renewal with an availability remedy of termination and pro-rata refund. We found no public information on two-factor authentication, a public status page with incident history, or a vulnerability disclosure programme, and the SOC 2 scope itself is not stated. 8 10 12 21 22

Report an error

The Skeptic

Granular permissions with SCIM and multiple SAML providers, an audit trail, annual penetration testing, an SOC 2 commitment renewed annually, and an availability section whose remedy is termination after two consecutive bad months rather than credits. We found no public information on a public status page or incident history, a vulnerability disclosure programme, service credits, or how the SDK behaves while Datadog itself is down. 8 9 10 12 21 22

Report an error

European sovereignty panel opinion

Show reasoning
How this is scored

Who the contracting entity and the parent company are, where error events, stack traces, request data, traces, profiles, session data and account data are stored and processed, and who the subprocessors are (hosting, email and chat delivery, AI models that explain errors, support and payment tools). Independently sourced by the sovereignty pipeline. An EU data region the customer can choose counts for the product; a US default without a stated EU option does not. A self-hosted edition the customer runs on its own European servers counts as the customer's chain, whatever the vendor's seat.

0 — Non-EU vendor and contracting entity, hosting unstated, subprocessors unnamed, and no data processing agreement offered.

3 — A privacy policy and a data processing agreement exist, but hosting location is unstated or non-EU and the subprocessors are not listed.

5 — An EU data region available and an EU contracting entity or EU representative, but parts of the chain (AI features, email, support, payment) run through non-EU providers without a stated safeguard.

8 — EU hosting on named infrastructure, EU contracting entity, subprocessors listed with their locations, a data processing agreement published, and security certifications (ISO 27001, SOC 2) stated — or a self-hosted edition documented that keeps every event on the customer's own servers.

10 — Sovereign end to end and evidenced: European ownership, entity, hosting and every subprocessor including the AI models, or a self-hosted edition with no call home, data export and deletion documented, and certifications published with their scope rather than implied.

Report an error

The Agency Tech Lead

The contracting entity is the Delaware corporation, but there is a selectable EU site in Germany that is completely independent of the other sites, a published data processing agreement with SCCs and Irish governing law for EEA transfers, DPF certification, and a subprocessor list naming every provider with its country — including the US AI vendors behind the Bits features. For my clients that means an EU region plus contractual safeguards rather than a European chain, and none of it is a European entity end to end. We found no public information on a self-hosted edition. 7 10 11 12 13

Report an error

The SaaS CTO

There is a German EU site I can point enterprise customers at, sites are fully independent with no data sharing across them, Datadog Ireland Limited serves as the GDPR Article 27 representative, a data processing agreement with SCC modules two and three is published, and the subprocessor list is public with locations. But the contracting entity is Datadog, Inc., a Delaware corporation, and every AI provider, support platform and payment processor on that list — OpenAI, Anthropic, Salesforce, Zendesk, PayPal's Braintree — is US-based, so the chain beyond hosting is not European. 7 10 11 12 13

Report an error

The Mobile Team Lead

There is a real EU option: the EU1 site runs in Germany with sites fully independent of each other, Datadog Ireland Limited serves as the GDPR Article 27 representative, a data processing agreement with Standard Contractual Clauses is published, and the subprocessor list names every provider with its country. But the contracting entity is the Delaware corporation in New York, and the AI, email, support and payment subprocessors are all United States providers, so a Hamburg buyer can keep events in Germany while the contract and the AI chain stay American. 7 10 11 12 13

Report an error

The Site Reliability Engineer

There is a German EU site that is completely independent with no data sharing across sites, an Article 27 EU representative (Datadog Ireland Limited), a published data processing addendum with standard contractual clauses, and a subprocessor list with locations. But the contracting entity is the Delaware corporation, and the AI, email, support and payment links in the chain run through US providers, so this is an EU region on a US-parented chain rather than a European one. I found no public information on a self-hosted edition; the closest documented option covers logs only. 7 10 11 12 13

Report an error

The Data Protection Officer

An EU site in Germany is documented with sites fully independent of one another, a published data processing agreement incorporates the SCCs as module two and three with Irish governing law for EEA disputes, and the subprocessor list names every provider with country and purpose — including seven US AI services — with a change-notification subscription. The contracting entity remains the Delaware corporation, and we found no public information on an EU contracting entity or a self-hosted edition, so the chain, above all the AI features, stays largely in the United States behind contractual safeguards. 7 10 11 12 13

Report an error

The Skeptic

An EU site in Germany is documented with each site fully independent, a data processing agreement with SCCs and Data Privacy Framework certification is published, and every subprocessor is listed with its country. But the contracting entity is a Delaware corporation, and the AI, email and support subprocessors are all US companies covered by SCCs rather than EU hosting. 7 10 11 12 13

Report an error

Pricing transparency

Show reasoning
How this is scored

Whether a buyer can compute the real annual cost from public pages alone: price per plan, what is included (errors or events, spans or transactions, replays, profiles, logs, seats, projects, retention), what overage costs per unit and whether it is capped, which features (SSO, audit logs, longer retention, EU region, AI) need a higher plan, host or seat based pricing for suites, the price of the self-hosted edition, annual versus monthly terms, and VAT.

0 — No public prices at all; every customer is a sales call.

3 — A starting price exists, but what volume it covers and what overage, retention and add-ons cost is unclear.

5 — Plans are public with their price and main volume limits, but at least one commonly needed piece (overage per event or span, longer retention, SSO, the EU region or AI features) is unpriced or "contact sales".

8 — Every plan priced publicly with its volume limits and overage rates, a price calculator or table per unit, add-ons and retention priced, the behaviour at the quota (cap or overage) stated, and VAT and billing terms stated.

10 — Complete price computability: annual cost derivable for a given volume of errors, traces, seats and projects, with every add-on, retention step, support level and the self-hosted licence priced and the cancellation terms published.

Report an error

The Agency Tech Lead

The pricing page does show structure — a free tier at no cost with five hosts and one-day retention, overage rates such as $0.002 per container per hour on demand and $2 for 100 000 custom events billed annually, per-plan allotments for containers and custom metrics, and multi-year discounts from 500 hosts — and the contract terms are public, with fees in U.S. dollars, 30-day payment, taxes excluded, auto-renewal and 15-day non-renewal notice. But the Basic infrastructure plan reads 'Contact sales for pricing', and we found no public price for the Pro and Enterprise plans or per-unit prices for APM and RUM, so I cannot compute a real annual bill for a client from the captured pages. 1 8 10

Report an error

The SaaS CTO

The pricing page shows the plan structure and volume limits — containers, custom metrics and events per host, retention per plan — and prices overage per unit, quoting "$0.002 per container per hour" and "$2 for 100 000 custom events (billed annually or $3 on-demand)", with fees exclusive of taxes and annual, monthly and hourly billing options. But we found no public information on the per-host price of the paid tiers — the Basic tier says "Contact sales for pricing" — nor on what APM spans, RUM sessions or error tracking cost, so I cannot compute a real annual bill from the captured pages. 1 8 10

Report an error

The Mobile Team Lead

The pricing page publishes genuine unit economics — a free tier of up to five Basic hosts with 1-day metric retention at no cost, custom events at $2 for 100 000 billed annually or $3 on-demand, additional containers at $0.002 per container per hour — plus per-plan volume allotments, and the agreement states usage-based monthly invoicing in US dollars with fees exclusive of taxes. But the captured pages give no per-host price for the paid plans, with Basic infrastructure listed as "Contact sales for pricing", and no per-event or per-span price for error tracking or real user monitoring, so I cannot compute my annual cost from public pages alone. 1 8 10

Report an error

The Site Reliability Engineer

A free tier of five hosts with one-day metric retention, on-demand container rates of $0.002 per container per hour, prepaid containers at $1 per container per month, and $2 for 100,000 custom events billed annually or $3 on-demand are public, along with per-plan allotments, 15-month retention, and USD invoicing monthly in arrears with fees exclusive of taxes. But the host plans themselves read "Contact sales for pricing", and I found no public information on APM or error unit pricing, real user monitoring pricing, or what the EU region or AI features cost. From these pages alone I could not compute the annual bill for my checkout services. 1 8 10

Report an error

The Data Protection Officer

The free tier is fully specified at five basic hosts with one-day metric retention, and unit prices exist for additional containers at $0.002 per container per hour and custom events at $2 for 100 000 billed annually or $3 on-demand. But the basic host price shows Contact sales for pricing, and we found no public price for APM hosts, error tracking, SSO or the EU region on the pages we read, so an annual cost is not computable from public pages alone. 1 8 10

Report an error

The Skeptic

Unit prices exist for some things — additional containers at $0.002 per container per hour and custom events at $2 for 100 000 billed annually, or $3 on-demand — with plan-level allotments, 15-month retention, billing terms, auto-renewal and fees exclusive of taxes in the agreement. But the Basic infrastructure plan says contact sales for pricing, and we found no per-host or per-span price for APM in the captured pages, so a real annual cost is not computable from public prices alone. 8 10

Report an error

European sovereignty — proven facts

2 of 6 dimensions proven

Built only from facts shown on the vendor's own pages. A dimension we could not prove is left open, not scored as zero.

Hosting location Not determined unverified
Why unverified?

Not confirmed on the vendor’s own pages as captured.

— uncited Report an error
Hosting options Not determined unverified
Why unverified?

Not confirmed on the vendor’s own pages as captured.

— uncited Report an error
Open source Not determined — uncited Report an error
Data processing agreement Published, self-serve 1/1 pts 12 Report an error
Transfer impact assessment Not determined — uncited Report an error

Questions about Datadog APM & Error Tracking

Is Datadog APM & Error Tracking European?

No. whats-best.ai classifies Datadog APM & Error Tracking as Rest of world. Its vendor, Datadog, Inc., is incorporated in the United States, per the vendor’s page captured 6 Nov 2026.

Where does Datadog APM & Error Tracking store data?

Not stated on the vendor’s pages as of 6 Nov 2026.

Does Datadog APM & Error Tracking have a free plan?

Yes. Datadog APM & Error Tracking has a free plan, per the vendor’s page captured 6 Nov 2026.

What are the best alternatives to Datadog APM & Error Tracking?

As of 18 Nov 2026, the panel rates Sentry (3.5/5), Dynatrace (3/5) and Tideways (3/5) highest among the other 19 Error Tracking & APM products evaluated. Ratings that look equal are rounded to half stars; the order uses the unrounded rating, then the name. The highest-rated European alternative is Tideways (EU-Made). Ratings are the AI panel’s opinion, formed from public evidence: how scores are made. The full list, with European products first: Datadog APM & Error Tracking alternatives.

Where this could be wrong

What we left out

A claim that does not survive our checks costs us the claim, not the page. This is what was taken off this one.

Sources (23)

The pages every claim on this page was read from — each one checked, dated, and kept verifiable.

  1. 1 Vendor homepage www.datadoghq.com Checked 6 Nov 2026 Details →
  2. 2 Features page (APM) www.datadoghq.com Checked 6 Nov 2026 Details →
  3. 3 Features page (error tracking) www.datadoghq.com Checked 6 Nov 2026 Details →
  4. 4 Features page (real user monitoring) www.datadoghq.com Checked 6 Nov 2026 Details →
  5. 5 Documentation (tracing) docs.datadoghq.com Checked 6 Nov 2026 Details →
  6. 6 Documentation (error tracking) docs.datadoghq.com Checked 6 Nov 2026 Details →
  7. 7 Documentation (data sites and regions) docs.datadoghq.com Checked 6 Nov 2026 Details →
  8. 8 Pricing page www.datadoghq.com Checked 6 Nov 2026 Details →
  9. 9 Security / trust page www.datadoghq.com Checked 6 Nov 2026 Details →
  10. 10 Terms of service (names the operating company) www.datadoghq.com Checked 6 Nov 2026 Details →
  11. 11 Privacy policy www.datadoghq.com Checked 6 Nov 2026 Details →
  12. 12 Data processing agreement (dpa) www.datadoghq.com Checked 6 Nov 2026 Details →
  13. 13 Subprocessor list www.datadoghq.com Checked 6 Nov 2026 Details →
  14. 14 Error capture, grouping & triage — found from sitemap docs.datadoghq.com Checked 6 Nov 2026 Details →
  15. 15 Error capture, grouping & triage — found from sitemap docs.datadoghq.com Checked 6 Nov 2026 Details →
  16. 16 APM, tracing & profiling — found from sitemap docs.datadoghq.com Checked 6 Nov 2026 Details →
  17. 17 APM, tracing & profiling — found from sitemap docs.datadoghq.com Checked 6 Nov 2026 Details →
  18. 18 Alerting, integrations & developer workflow — found from sitemap docs.datadoghq.com Checked 6 Nov 2026 Details →
  19. 19 Alerting, integrations & developer workflow — found from sitemap docs.datadoghq.com Checked 6 Nov 2026 Details →
  20. 20 Data scrubbing, retention & volume control — found from sitemap docs.datadoghq.com Checked 6 Nov 2026 Details →
  21. 21 Data scrubbing, retention & volume control — found from sitemap docs.datadoghq.com Checked 6 Nov 2026 Details →
  22. 22 Access control, security & the vendor's reliability — found from sitemap docs.datadoghq.com Checked 6 Nov 2026 Details →
  23. 23 Access control, security & the vendor's reliability — found from sitemap docs.datadoghq.com Checked 6 Nov 2026 Details →