Panel rating · 6 judges · How to read the stars

Category median

Sovereignty: 3 of 6 dimensions proven

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

by Dynatrace · www.dynatrace.com

Compare with Datadog APM & Error Tracking → Report an error on this page Is this your product? →

Link to this page

Dynatrace: AI-assisted analysis on whats-best.ai Dynatrace: 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.

Dynatrace at a glance

Vendor
Dynatrace
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
Not stated on the vendor’s pages as of 6 Nov 2026
Panel verdict
The AI panel rates Dynatrace 3/5, the mean of 6 judges. Dynatrace is judged here as an APM and tracing platform, and the scores carry that shape: persona-weighted totals ranged from 6.0 to 6.6, with performance tracing and data controls clustering at 7–8 and error tracking at 4 with no higher mark recorded. how scores are made
As of
Vendor pages captured 6 Nov 2026; evaluated by the panel 6 Nov 2026. all sources

Dynatrace alternatives, European ones first →

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

The SaaS CTO

Weighted verdict

CTO of a B2B SaaS company in Berlin with thirty-five engineers, twelve services in Go, Python and TypeScript on Kubernetes and a React frontend. Wants one trace from the click in the browser to the slow database call three services down, OpenTelemetry so the instrumentation is not locked to one vendor, errors routed to the team that owns the service, releases linked to the commits that broke them, and an EU region because the enterprise customers ask where their data goes.

Same scores as the panel view — this lens weights them the way this judge cares.

Scored by The SaaS CTO

Panel median The SaaS CTO This judge’s scores over the panel median. Each label opens its reasoning below.
Scores per criterion, in stars out of 5
Criterion Panel median The SaaS CTO
Error capture, grouping & triage 2 of 5 2 of 5
APM, tracing & profiling 4 of 5 4 of 5
Alerting, integrations & developer workflow 3 of 5 3 of 5
Data scrubbing, retention & volume control 4 of 5 4 of 5
Access control, security & the vendor's reliability 3.5 of 5 3.5 of 5
European sovereignty 3 of 5 3 of 5
Pricing transparency 4 of 5 4 of 5

Error capture, grouping & triage

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 SaaS CTO

Frontend error intelligence comes with source maps and trends across browsers, devices and app versions, mobile crashes are symbolicated for iOS and deobfuscated for Android through a documented API, and exceptions are correlated with traces in context. Beyond web and mobile the picture thins: we found no public information on per-language SDKs, automatic grouping, issue states or regression detection, and the crash-remediation engine that delivers ready-to-apply code fixes is marked as a preview. Good enough for my React frontend and the mobile app, unproven on the captured pages for my Go and Python services. 2 3 15 16

Report an error

APM, tracing & profiling

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 SaaS CTO

This is the criterion closest to my day job and the evidence is strong: distributed traces from OneAgent or a documented OpenTelemetry Collector route with ingest limits spelled out, SQL statement analysis for slow queries, code-level profiling in the full-stack plan, Core Web Vitals from real users, and host and Kubernetes metrics priced alongside the traces. Retention is public per signal — ten days of traces extendable to ten years, thirty-five days for sessions. We found no public information on trace sampling configuration or SLOs on endpoints, which is what holds it back from the top. 2 3 5 17 18

Report an error

Alerting, integrations & developer workflow

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 SaaS CTO

Jira tickets are generated automatically for new auto-detected problems with severity auto-updates (closing stays manual), PagerDuty works out of the box with a custom-webhook option, anomaly-detection alerts cover business KPIs, and an integration hub, a Workflows app and a documented API back it up. AI features exist — troubleshooting documents tied to problem IDs and a Mobile Crash Agent — but they are in preview, and while Anthropic is named as the AI-inference subprocessor the pages do not tie a model to a specific feature. We found no public information on chat or email notification channels, per-team routing, or scheduled reports. 4 15 19 20

Report an error

Data scrubbing, retention & volume control

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 SaaS CTO

Masking is documented at several layers — on source with OneAgent, on write during ingest, in the OpenTelemetry Collector and in Live Debugger — request attributes can be marked confidential, an anonymization API exists, and scheduled scans hunt mistakenly ingested card numbers and IBANs. The Sensitive Data Center runs a reviewed, audited export-and-deletion workflow for personal data, though its own documentation states that data types other than Grail logs are not supported today; retention is configurable per signal with per-GiB-day prices. Usage alerts and automated forecasting are built in and the Managed edition keeps all monitoring data on our own infrastructure, but we found no public information on error or trace sampling. 5 9 21 22 23

Report an error

Access control, security & the vendor's reliability

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 SaaS CTO

The certification list reads like an enterprise checklist — ISO 27001:2022, SOC 2 Type II, SOC 1 Type II, FedRAMP Moderate — audit logs are documented with customizable retention and a dedicated privacy-audit bucket, the public status page shows historical availability between 98 and 100 percent with a stated aggregate scope, and penetration test reports are available under NDA alongside signed SBOMs. For my audit conversations, though, we found no public information on single sign-on, SCIM, two-factor authentication or an SLA with credits in the captured pages. 6 7 10 21 24

Report an error

European sovereignty

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 SaaS CTO

The contracting chain reads American: the subprocessor page names Dynatrace LLC as headquartered in the United States with authorized staff access from any country of operation, and AI inference (Anthropic), support (Salesforce, Atlassian) and internal chat (Slack) all run through US providers. A data processing agreement is published in nine languages and subprocessors are listed with their locations — Ireland and Germany appear for AWS and Google when selected as hosting provider — but we found no public information confirming where SaaS error and trace data is actually stored. The escape hatch for my EU-sensitive customers is documented: the Managed edition keeps all monitoring data on our own infrastructure, at the price of required outbound access to Dynatrace for remote management and the vendor's ability to retrieve cluster logs and crash dumps. 13 14 23

Report an error

Pricing transparency

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 SaaS CTO

Nearly every capability carries a public per-unit rate on one page: '$58 / mo per 8 GiB host' for full-stack monitoring, '$2.25 per 1,000 sessions' for real user monitoring, '$0.20 per GiB' ingest for traces and logs, AI at '$0.10 per AI unit' with worked examples, and retention extensions priced per GiB-day. The model is an annual platform-level commitment with volume discounts, and usage alerts and automated forecasting are built in. We found no public information on VAT, on what happens when the commitment is exceeded, or on the licence price of the Managed edition. 3 5

Report an error

European sovereignty — proven facts

3 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 — uncited Report an error
Hosting options Self-hostable unverified
Why unverified?

Dynatrace Managed is a separate edition alongside the SaaS platform and requires customer-provided hardware, and the cluster still needs outbound internet access to Dynatrace for remote management and consumption tracking.

1/1 pts 23 Report an error
Open source Not determined — uncited Report an error
Data processing agreement Published, self-serve unverified
Why unverified?

The DPA text is published but only incorporated by reference into the subscription agreement; an executable, separately signed copy must be requested from the account executive or privacy@dynatrace.com.

1/1 pts 13 Report an error
Transfer impact assessment Not determined — uncited Report an error

Questions about Dynatrace

Is Dynatrace European?

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

Where does Dynatrace store data?

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

Does Dynatrace have a free plan?

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

What are the best alternatives to Dynatrace?

As of 18 Nov 2026, the panel rates Sentry (3.5/5), Datadog APM & Error Tracking (3.5/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: Dynatrace 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 (24)

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

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