Dynatrace
Rest of world Report an errorPanel 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
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
Read this page as one judge. Each weighs the same scores by what they care about.
The panel's verdict
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. The tracing strength is concrete — distributed traces from OneAgent or a documented OpenTelemetry route with published ingest limits, code-level profiling, SQL statement analysis, real-user Core Web Vitals and retention priced per signal — though the judges found no public information on trace sampling. Pricing transparency also scores 7–8 on public unit rates ($58 / mo per 8 GiB host, $2.25 per 1,000 sessions, $0.10 per AI unit) inside an annual platform commitment. The genuine split is sovereignty at 4–6: the Data Protection Officer and the Skeptic scored 4, citing the US-headquartered group and unconfirmed SaaS data residency, while higher scores credited the public subprocessor list, a data processing agreement in nine languages, and the Managed edition that keeps all monitoring data on your own infrastructure, at the price of required outbound access for remote management.
Speaks for it
- Distributed tracing via OneAgent or a documented OpenTelemetry Collector route, with published ingest limits and code-level profiling in the full-stack plan
- Public per-unit rates for nearly every signal: '$58 / mo per 8 GiB host' for full-stack monitoring, '$2.25 per 1,000 sessions', traces at '$0.20 per GiB' ingested, and AI at '$0.10 per AI unit' with worked examples
- Masking documented at several layers — on source with OneAgent, on write during ingest, in the OpenTelemetry Collector and in Live Debugger — with an anonymization API and retention configurable from 1 day to 10 years
- Certifications including ISO 27001:2022, SOC 2 Type II, SOC 1 Type II and FedRAMP Moderate, audit logs with customizable retention, and penetration test reports available under NDA
- The Managed edition keeps all monitoring data on your own infrastructure, alongside a published subprocessor list with locations and a data processing agreement in nine languages
Held against it
- Error tracking scored 4 with no higher mark recorded, and we found no public information on issue grouping, issue states such as resolved and regressed, or per-language error SDKs
- The crash-remediation engine described as delivering ready-to-apply code fixes is marked as a preview that customers must join
- The Jira integration auto-generates tickets but does not automatically close resolved issues, supports REST API v2 only, and uses basic authentication with username and API token
- We found no public information on single sign-on, SCIM provisioning, two-factor authentication or SLA credits on the captured pages
- We found no public information confirming SaaS data residency, while the subprocessor page names Dynatrace LLC as headquartered in the United States and AI inference runs through Anthropic in the United States
Best for
- You run distributed services and want end-to-end tracing with a documented OpenTelemetry ingest route and public per-unit rates to model the bill
- You ship iOS and Android apps and need symbolicated, deobfuscated crash reports with error trends by device and app version
- You must keep monitoring data on your own infrastructure and can provide the outbound access the Managed edition requires for remote management
- You need per-user export and deletion of Grail logs through a reviewed workflow with reviewer approval and an audit trail
Avoid if
- You depend on issue grouping and resolved or regressed states as a core workflow — error tracking scored 4 and we found no public information on them
- You must guarantee an EU data region for the SaaS product — the captured pages do not confirm SaaS data residency and the headquarters entity named on the subprocessor page is US-based
- You need tickets to close themselves when problems resolve — the Jira integration requires manual closing
- You need a published monthly term rather than an annual platform-level commitment with volume discounts
The scores
| Criterion | Panel median |
|---|---|
| Error capture, grouping & triage | 2 of 5 |
| APM, tracing & profiling | 4 of 5 |
| Alerting, integrations & developer workflow | 3 of 5 |
| Data scrubbing, retention & volume control | 4 of 5 |
| Access control, security & the vendor's reliability | 3.5 of 5 |
| European sovereignty | 3 of 5 |
| Pricing transparency | 4 of 5 |
Error capture, grouping & triage
Show reasoningHide 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.
The Agency Tech Lead
Mobile crash reports come with a documented symbolication and deobfuscation service for iOS and Android, the frontend side has source maps with error trends by device, browser, geolocation and app version, and exceptions are correlated with traces and logs in context. But we found no public information on how issues are grouped, issue states like resolved or regressed, or per-language SDK configuration, and the crash-remediation engine promising ready-to-apply code fixes is explicitly marked Preview. 2 3 15 16 17
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
The Mobile Team Lead
Mobile crashes are covered where I care most — the symbolication service interprets iOS and Android crash reports through a symbol-file API, error trends split by device and app version, and session and click-path tracking gives the screens before a crash. But we found no public information on crash-free users per release, issue grouping and issue states, or SDKs for Flutter, React Native and the backend languages, and the AI crash-remediation engine that promises ready-to-apply code fixes is marked preview. 3 15 16
The Site Reliability Engineer
Mobile crash handling is the best documented piece — the symbolication service deobfuscates Android and symbolicates iOS/tvOS stack traces with symbol files managed by API, and frontend error trends come with source maps and root cause context. The backend error lifecycle is thinner on these pages: grouping, issue states, release tracking and per-language error SDKs are not described, and the AI crash-remediation engine that would fill that gap is flagged as a preview requiring sign-up. 2 3 15 16
The Data Protection Officer
The pages show a real crash pipeline for mobile — a symbolication service interpreting Android and iOS stack traces, version-specific error analysis and AI-generated troubleshooting documents — plus frontend error intelligence across devices, browsers, geolocations and app versions with source maps and root cause context. I found no public information on grouping, custom fingerprints or issue states such as resolved and regressed, so I cannot tell how a flood of traces carrying member numbers would be triaged and deduplicated. 2 3 15 16
The Skeptic
Web error intelligence with source maps and root cause context, an API-managed symbolication and deobfuscation service for iOS and Android crash reports, and exceptions correlated with traces, metrics and logs in context are all documented, with version-specific mobile error analysis on top. What we found no public information on is the error-tool half of the ledger: grouping or custom fingerprints, issue states like resolved or regressed, breadcrumbs, or per-language error SDKs; the engine that promises ready-to-apply crash fixes is a Preview a customer must join. 2 3 15 16
APM, tracing & profiling
Show reasoningHide 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.
The Agency Tech Lead
This is the strongest area for my shop: distributed traces across services via OneAgent or OpenTelemetry, SQL statement analysis to find slow queries, code-level profiling in the Full-Stack plan, real user monitoring with Core Web Vitals and waterfall views, host and Kubernetes metrics beside the traces, and intelligent baselines on latency and error rates, with retention per signal published right on the pricing page. We found no public information on trace sampling configuration or background job and queue monitoring. 2 3 5 17 18
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
The Mobile Team Lead
This is the product's core strength: distributed traces end to end with OneAgent or OpenTelemetry ingest documented down to request-size limits, code-level profiling in Full-Stack Monitoring, slow-SQL analysis, real user monitoring with Core Web Vitals, and intelligent baselines on latency and error rates — retention per signal is even priced. We found no public information on configurable trace sampling and its effect. 2 3 5 17 18
The Site Reliability Engineer
This is what I want at 3 a.m.: distributed traces from OneAgent or OpenTelemetry (with OTLP request-size and span limits documented), code-level profiling, intelligent baselines on latency and error rates, slow SQL analysis with bind variables, host and Kubernetes metrics beside the traces, and real user monitoring with Core Web Vitals, plus per-signal retention such as 10 days of traces extendable to 10 years. I found no public information on how trace sampling is configured and what its effect is, which is the one gap keeping this off the top. 2 3 4 5 17 18
The Data Protection Officer
OpenTelemetry ingest is documented down to request-size limits with attribute types preserved and queryable, full-stack monitoring includes code-level profiling, real user monitoring covers Core Web Vitals, and slow SQL analysis and intelligent baselines for latency are described; retention per signal is published alongside the prices. I found no public information on trace sampling and its cost effect, which is what I would ask about before ingesting request bodies at insurer scale. 2 3 5 17 18
The Skeptic
Distributed tracing end to end across services and serverless, OpenTelemetry ingest documented down to request-size and span-attribute limits, code-level profiling in the full-stack plan, real user monitoring with Core Web Vitals, host and Kubernetes metrics beside the traces, intelligent baselines on latency and error rates, and SQL slow-query analysis, with retention stated per signal. The one thing I look for and found no public information on is sampling: how to configure it and what it costs. 2 3 5 17 18
Alerting, integrations & developer workflow
Show reasoningHide 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.
The Agency Tech Lead
PagerDuty pushes problem notifications out of the box with a custom webhook option, Jira tickets are generated automatically with automatic severity updates, and a documented REST API plus a Workflows engine with connectors covers targeted notification and remediation. The Jira link is one-way with no auto-close, basic auth only and REST API v2 only; the AI agentic features are priced per unit with Anthropic named as the AI inference subprocessor, and we found no public information on Slack, Teams or email alert channels or GitHub and GitLab issue sync. 4 5 14 15 19 20
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
The Mobile Team Lead
An error reaches the on-call side well: PagerDuty pushes problem notifications out of the box, Jira tickets are auto-generated with severity auto-updates and a test button, and the Workflows app handles targeted notification and remediation, while the agentic AI is priced per unit and Anthropic is named as the AI subprocessor on the trust pages. The Jira link is one-way though — resolved problems never close tickets and staff close them manually — and we found no public information on Slack or email notification channels, alert rules for new or regressed errors, or scheduled digest reports. 4 5 14 19 20
The Site Reliability Engineer
PagerDuty is out of the box and pushes the problem card link to responders with a custom webhook option, Jira auto-generates tickets with automatic severity updates, anomaly alerts on business events and KPIs are documented, and the AI features are priced per unit with Anthropic named as the AI inference subprocessor. The Jira link is one-way on the captured pages (issues close manually, REST API v2, basic authentication only); I found no public information on chat channels like Slack or Teams, GitHub or GitLab integrations, CI deploy hooks, or scheduled reports. 4 5 14 19 20
The Data Protection Officer
Problem notifications push to PagerDuty out of the box with a custom webhook option, Jira tickets are auto-generated with automatic severity updates, a documented API exists, and the Mobile Crash Agent offers AI diagnosis with ready-to-apply fixes — with Anthropic in the United States named as the AI-inference subprocessor on the trust pages. The captured pages state that resolved issues must be closed manually in Jira, and I found no public information on chat channels, digests or scheduled reports. 4 14 15 19 20
The Skeptic
Problem notifications, anomaly-detection alerts on business events and KPIs, an out-of-the-box PagerDuty push with a custom-webhook variant, Jira tickets auto-generated with automatic severity updates and placeholders, a Workflows app for targeted notification and remediation, and a documented API section add up to a working pipeline. The Jira link is one-way — resolved problems never close the ticket, only Jira REST API v2 with username-and-token authentication — and we found no public information on Slack or email notification channels, source-code links or scheduled digests; the AI fix engine is in Preview and the model provider surfaces only indirectly on the subprocessor list. 4 14 15 19 20
Data scrubbing, retention & volume control
Show reasoningHide 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.
The Agency Tech Lead
Masking is documented at several layers — on source with OneAgent, on write during ingest, in the OTel Collector and in Live Debugger, plus session replay privacy settings, confidential request attributes and an anonymization API — and the Sensitive Data Center handles per-user export and GDPR deletion with reviewer approval and an audit trail, though it currently supports Grail logs only and the scanner for credit card numbers and IBANs is a preview. Retention per signal is public, consumption alerts and automated forecasting are built in, and the on-premise edition keeps monitoring data on our own servers. 5 8 9 21 22 23
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
The Mobile Team Lead
Scrubbing is documented at several layers — masking on the agent at source, on ingest, in the OTel collector and on capture in the live debugger — alongside request attributes marked confidential and scheduled scans for credit-card and IBAN patterns. Per-user export and deletion run through a reviewed, audited workflow, retention runs from one day to ten years per data type, consumption alerts and forecasting are built in, and the Managed edition keeps all monitoring data on our own servers. The sensitive-data scanner is a preview and the privacy app currently supports Grail logs only, which I would verify before relying on it. 5 9 21 22 23
The Site Reliability Engineer
Masking is documented at several layers — on source with OneAgent, on ingest with log processing, in the OTel Collector and on capture in Live Debugger — plus an anonymization API, confidential request attributes and a Sensitive Data Scanner for card numbers and IBANs in preview. Retention is priced and controllable per data type and per bucket with IAM policies, personal data can be exported or hard-deleted per user through a reviewed, audit-trailed workflow, and the self-hosted edition keeps monitoring data on your own infrastructure; I found no public information on spike protection, quota caps or how overage is billed, and deletion currently covers Grail logs only. 5 9 21 22 23
The Data Protection Officer
Masking is documented in layers — on source with the agent, on write during ingest, on capture with the live debugger — and a Sensitive Data Scanner in preview hunts mistakenly ingested credit card numbers and IBANs, exactly the fields a member portal emits; per-user export and deletion run through a reviewed workflow with an audit trail, though the pages state it currently covers Grail logs only. Retention is stated and extendable per signal, and an on-premise edition keeps all monitoring data on our own infrastructure. 5 8 9 21 22 23
The Skeptic
Masking is documented at several layers — on the source with the agent, on write during ingest, in the OTel Collector, on capture in the live debugger — plus an anonymization API, an audit-trailed deletion workflow per end user with reviewer approval, hard deletion of individual records, and retention stated per data type from 1 day to 10 years; the self-hosted edition keeps all monitoring data on the customer's own infrastructure. Caveats from my chair: the scheduled scanner for mistakenly ingested card numbers and IBANs is a preview, deletion may take time to process, and the documented volume control is alerts and forecasting — billing stays usage-based per unit. 5 8 9 21 22 23
Access control, security & the vendor's reliability
Show reasoningHide 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.
The Agency Tech Lead
Certifications are listed in breadth (ISO 27001:2022, SOC 2 Type II, ISO 27017, FedRAMP Moderate among them) with a Trust Center, penetration test reports available under NDA, a CVE disclosure page, audit logs with customizable retention, IAM groups and policies, and a public status page with availability history. Availability is only reported in aggregate across geographies and product categories, and we found no public information on single sign-on, SCIM, two-factor authentication or availability credits on the pages read. 6 7 10 21 23 24
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
The Mobile Team Lead
For the audit trail I need: ISO 27001, SOC 1 and SOC 2 Type II plus FedRAMP Moderate on the trust page, audit logs on Grail, a public status page with availability history, a CVE disclosure route, and penetration-test reports on request under NDA. We found no public information on SAML single sign-on, SCIM provisioning, two-factor authentication or SLA credits, so the enterprise identity layer stays unconfirmed to me. 6 7 10 21 23
The Site Reliability Engineer
The audit story holds up: ISO 27001:2022, SOC 1 and SOC 2 Type II in a long certification list, audit logs with customizable retention and their own bucket, IAM groups and multi-party access control, cryptographically signed SBOMs, a CVE disclosure page, penetration test reports under NDA, and a public status page with historical availability and status history. The self-hosted cluster's behaviour on the vendor's own bad day is documented (UI down up to one hour during upgrades, metrics collection typically uninterrupted); I found no public information on single sign-on, SCIM, two-factor authentication or SLA credits. 6 7 9 10 21 23 24
The Data Protection Officer
ISO 27001:2022, ISO 27017 and SOC 2 Type II are named on the trust center, audit logs with customizable retention exist in Grail, penetration test reports are available under NDA, and a public status page publishes availability history. I found no public information on single sign-on, SCIM provisioning or two-factor authentication, and the on-premise service-level page captured describes upgrade downtime of up to one hour rather than availability credits. 6 7 10 21 23 24
The Skeptic
A public status page with historical availability between 98 and 100 percent and a status-history link, ISO 27001:2022 and SOC 2 Type II among a long certification list, audit logs with customisable retention behind IAM policies, a CVE disclosure page, and cryptographically signed SBOMs for agent and cluster artifacts. We found no public information on SAML single sign-on with SCIM provisioning, two-factor authentication, or how the agent behaves when ingestion is down; and availability is reported only at an aggregate level across all geographies, hyperscalers and product categories, with individual customer environments acknowledged to vary. 6 7 9 10 21 24
European sovereignty
panel opinion
Show reasoningHide 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.
The Agency Tech Lead
The contracting picture is American — the subprocessor page names Dynatrace LLC as headquartered in the United States — and AI inference runs through Anthropic in the US with support on Salesforce and Atlassian, while SaaS hosting location and an EU data region are not confirmed on the vendor pages read. In its favour, the subprocessor list is public with locations, some cloud hosting options include Germany and Ireland, a multi-language data processing agreement is published, and the on-premise edition keeps all monitoring data on our own hardware — though that edition requires outbound access to fixed Dynatrace addresses for remote management and the Mission Control team can retrieve cluster logs and crash dumps. 13 14 23
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
The Mobile Team Lead
The chain is largely American: the headquarters entity is in the US, AI inference (Anthropic), support (Salesforce, Atlassian) and communications (Slack, Zoom) run through US subprocessors, and Ireland or Germany appear only as 'if selected' hosting options for AWS, Google and Microsoft. A data processing agreement is published in nine languages and the subprocessor list with locations is public, and the self-hosted Managed edition keeps all monitoring data on our own infrastructure — but it requires outbound access to Dynatrace for remote management and consumption tracking, so it is not a sealed chain. 13 14 23
The Site Reliability Engineer
Subprocessors are listed with their locations — AWS, Microsoft and Google each show EU options 'if selected hosting provider', while Anthropic for AI inference and Salesforce and Atlassian for support sit in the US — and a data processing agreement is published in nine languages, incorporated by reference. The self-hosted edition states all monitoring data remains on your infrastructure, but the named group headquarters is US-based with global personnel access, SaaS data residency is not confirmed on the captured pages, and the self-hosted cluster must reach the internet for remote management, with Mission Control able to retrieve logs and crash dumps. 13 14 23
The Data Protection Officer
A data processing agreement is published in nine languages and a dated subprocessor list names locations, with Germany, Ireland and the Netherlands among hosting options selectable on AWS, Google and Microsoft; against that, the group is headquartered in the United States with personnel access from any country of operation, and AI inference, support and communications run through Anthropic, Salesforce, Atlassian, Slack and Zoom in the United States. The on-premise edition keeps all monitoring data on the customer's infrastructure but requires outbound connectivity for remote management and sends self-monitoring metrics to the vendor, and I found no public information naming an EU contracting entity or a guaranteed EU data region for the platform. 13 14 23
The Skeptic
A subprocessor list is published with locations and a data processing agreement exists in ten languages, but the group's headquarters sit in the United States, data can be accessed by authorised personnel from any country where a Dynatrace Group entity operates including the United States, and the AI inference (Anthropic), the support desk (Atlassian, Salesforce) and the communication tools all run in the US. Hosting is described only as secure data centers on AWS, Azure or GCP if selected as hosting provider; we found no public information confirming an EU data region a customer can choose for the SaaS product. 8 13 14
Pricing transparency
Show reasoningHide 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.
The Agency Tech Lead
Unit pricing is unusually public: $58 per month per 8 GiB host for Full-Stack (billed at $0.01 per memory-GiB-hour), $2.25 per 1,000 real user sessions, traces at $0.20 per GiB ingested plus $0.0007 per GiB-day retention and $0.0035 per GiB-scanned query, AI units at $0.10 with worked examples, and retention from 10 days to 10 years depending on the signal. What stays opaque for budgeting is the annual platform commitment whose volume discounts are not scheduled, the on-premise licence price, and VAT and cancellation terms, on which we found no public information. 5
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
The Mobile Team Lead
As a buyer I can almost compute the year: hosts run from $7 / mo per host to $58 / mo per 8 GiB host with hourly rates beside them, real user sessions cost $2.25 per 1,000 sessions, traces $0.20 per GiB ingested plus $0.0007 per GiB-day retained, and AI work $0.10 per AI unit with worked examples per task. What is not computable: the platform is sold as an annual commitment with volume discounts rather than a fixed quota, and we found no public information on VAT or the licence price of the self-hosted Managed edition. 5
The Site Reliability Engineer
Unit pricing is unusually granular and public: hosts from $7 / mo per host up to $58 / mo per 8 GiB host with per-hour equivalents, traces at $0.20 per GiB ingest plus $0.0007 per GiB-day retention and $0.0035 per GiB-scanned for queries, sessions and synthetic actions priced per thousand, and even AI units at $0.10 with worked examples, plus consumption alerts and forecasting built in. Two gaps keep this off the top band: VAT treatment and the price of the self-hosted edition are not stated on the captured pages, and the commercial model is an annual platform-level commitment with volume discounts rather than a published monthly term. 3 5
The Data Protection Officer
Per-unit prices are published for every signal — full-stack monitoring at $58 per month per 8 GiB host, real user monitoring at $2.25 per 1,000 sessions, ingest at $0.20 per GiB with retention at $0.0007 per GiB-day, and AI at $0.10 per unit with worked examples — alongside retention ranges and built-in consumption alerts. I found no public information on VAT, on the licence price of the on-premise edition, or on what happens when a committed volume is exceeded. 5
The Skeptic
A rare case of public unit economics: hosts at $0.01 per memory-GiB-hour, sessions at $0.00225 each, traces and logs at $0.20 per GiB ingested plus $0.0007 per GiB-day retained and $0.0035 per GiB-scanned, retention defaults and extensions per signal, add-ons priced per host or container, and AI actions at $0.10 per AI unit with worked examples. But the discounts sit behind an annual platform commitment described only as the more you commit the more you save, and we found no public information on a price calculator, VAT treatment, cancellation terms, or what the self-hosted edition costs — the second year is only computable if your volumes and your commitment hold still. 3 5 23
European sovereignty — proven facts
3 of 6 dimensions provenBuilt only from facts shown on the vendor's own pages. A dimension we could not prove is left open, not scored as zero.
| Legal entity |
Incorporated in US
unverified
Why unverified?Stated on the subprocessor page rather than an imprint, and it names the headquarters of Dynatrace LLC (one of many Dynatrace Group entities) rather than a register or place of incorporation of the contracting entity. |
0/2 pts | 14 Report an error |
|---|---|---|---|
| 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
- Evidence ages. The oldest capture behind this page is from 6 Nov 2026. Vendors change pricing and policies without notice; every fact reflects its source as of the capture date shown in the registry.
- Weak sourcing — Data processing agreement. 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.
- Weak sourcing — Legal entity. Stated on the subprocessor page rather than an imprint, and it names the headquarters of Dynatrace LLC (one of many Dynatrace Group entities) rather than a register or place of incorporation of the contracting entity.
- Weak sourcing — Hosting options. 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.
- AI can misread a source. Extraction and judgement are automated; a citation guarantees traceability, not infallibility. If something here is wrong, say so — no account needed, every report is decided within 5 business days, and accepted corrections are published.
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.
- 39 product facts could not be confirmed on the vendor’s page as captured and were left out of this page and of the panel’s material. Know more? Tell us
- 5 integrations facts could not be confirmed on the vendor’s page as captured and were left out of this page and of the panel’s material. Know more? Tell us
- 5 pricing facts could not be confirmed on the vendor’s page as captured and were left out of this page and of the panel’s material. Know more? Tell us
- 4 compliance facts could not be confirmed on the vendor’s page as captured and were left out of this page and of the panel’s material. Know more? Tell us
- 4 support facts could not be confirmed on the vendor’s page as captured and were left out of this page and of the panel’s material. Know more? Tell us
- 1 hosting fact could not be confirmed on the vendor’s page as captured and was left out of this page and of the panel’s material. Know more? Tell us
- 1 subprocessors fact could not be confirmed on the vendor’s page as captured and was left out of this page and of the panel’s material. Know more? Tell us
- 6 of the readings below were written against an earlier fact sheet — a fact has been corrected, added or pulled since. Until the panel next runs on this product you are reading the older judgement. Know more? Tell us
Sources (24)
The pages every claim on this page was read from — each one checked, dated, and kept verifiable.
- 1 Vendor homepage www.dynatrace.com Checked 6 Nov 2026 Details →
- 2 Features page (APM) www.dynatrace.com Checked 6 Nov 2026 Details →
- 3 Features page (real user monitoring) www.dynatrace.com Checked 6 Nov 2026 Details →
- 4 Documentation docs.dynatrace.com Checked 6 Nov 2026 Details →
- 5 Pricing page www.dynatrace.com Checked 6 Nov 2026 Details →
- 6 Trust center www.dynatrace.com Checked 6 Nov 2026 Details →
- 7 Security / trust page www.dynatrace.com Checked 6 Nov 2026 Details →
- 8 Privacy policy www.dynatrace.com Checked 6 Nov 2026 Details →
- 9 Documentation (data privacy and security) docs.dynatrace.com Checked 6 Nov 2026 Details →
- 10 Public status page dynatrace.status.io Checked 6 Nov 2026 Details →
- 11 About page www.dynatrace.com Checked 6 Nov 2026 Details →
- 12 Terms of service www.dynatrace.com Checked 6 Nov 2026 Details →
- 13 Data processing agreement (dpa) www.dynatrace.com Checked 6 Nov 2026 Details →
- 14 Subprocessor list www.dynatrace.com Checked 6 Nov 2026 Details →
- 15 Error capture, grouping & triage — found from sitemap www.dynatrace.com Checked 6 Nov 2026 Details →
- 16 Error capture, grouping & triage — found from sitemap docs.dynatrace.com Checked 6 Nov 2026 Details →
- 17 APM, tracing & profiling — found from sitemap docs.dynatrace.com Checked 6 Nov 2026 Details →
- 18 APM, tracing & profiling — found from sitemap docs.dynatrace.com Checked 6 Nov 2026 Details →
- 19 Alerting, integrations & developer workflow — found from sitemap docs.dynatrace.com Checked 6 Nov 2026 Details →
- 20 Alerting, integrations & developer workflow — found from sitemap docs.dynatrace.com Checked 6 Nov 2026 Details →
- 21 Data scrubbing, retention & volume control — found from sitemap docs.dynatrace.com Checked 6 Nov 2026 Details →
- 22 Data scrubbing, retention & volume control — found from sitemap docs.dynatrace.com Checked 6 Nov 2026 Details →
- 23 Access control, security & the vendor's reliability — found from sitemap www.dynatrace.com Checked 6 Nov 2026 Details →
- 24 Access control, security & the vendor's reliability — found from sitemap www.dynatrace.com Checked 6 Nov 2026 Details →