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 Atatus · www.atatus.com
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.
Atatus at a glance
- Vendor
- Atatus
- Headquarters
- Not stated on the vendor’s pages as of 17 Nov 2026
- Data hosting
- Not stated on the vendor’s pages as of 17 Nov 2026
- Free plan
- Yes, per the vendor’s own page source, captured 17 Nov 2026
- Panel verdict
- The AI panel rates Atatus 3/5, the mean of 6 judges. Atatus is an error tracking and APM platform. how scores are made
- As of
- Vendor pages captured 17 Nov 2026; evaluated by the panel 18 Nov 2026. all sources
Read this page as one judge. Each weighs the same scores by what they care about.
The panel's verdict
Atatus is an error tracking and APM platform. Its strongest showing is performance tracing, where scores cluster at 7 on documented distributed tracing with service maps, slow-query capture across PostgreSQL, MySQL, MongoDB, Redis and Elasticsearch, continuous profiling with flame graphs, and OpenTelemetry ingestion. Error tracking scores cluster at 6 — mobile crash capture is documented in depth, with server-side dSYM and R8 symbolication and root-cause grouping — while we found no public information on issue states such as resolved or regressed, or crash-free rates. The weakest tendencies are workflow and integrations at 5-6 and data controls at 4-6, where we found no public information naming notification channels such as Slack or PagerDuty, documenting webhooks or a CLI, or covering sampling, rate limits, spike protection or quota caps. Sovereignty is the genuine split, 3 to 8: higher scores credit the on-premises edition that stores telemetry entirely within the customer's network perimeter with zero external data transfer, while the lowest weighs the unstated jurisdiction of contracting entity NamLabs Technologies Pvt Ltd, with no public information on SaaS hosting location or subprocessors.
Speaks for it
- Performance tracing is documented end to end — transaction traces, service maps, slow-query capture across PostgreSQL, MySQL, MongoDB, Redis and Elasticsearch, continuous profiling with flame graphs and anomaly insights, and OpenTelemetry ingestion
- Mobile crash capture is documented in depth, with server-side dSYM and R8 symbolication, root-cause grouping into issues, and per-build mapping files
- Alerting is configurable, with warning and critical levels set independently, evaluation windows of 5 to 60 minutes, and rules scoped per application
- The trust center publishes ISO 27001:2022 with a 15 September 2027 expiry, SOC 2 Type II reports on request under NDA, annual third-party penetration tests, and SAML, LDAP and Active Directory SSO
- An on-premises edition stores telemetry entirely within the customer's network perimeter, with zero external data transfer and unlimited retention
Held against it
- We found no public information on notification channels such as Slack, PagerDuty or email, webhooks or a CLI, leaving the alert-to-pager path unconfirmed
- We found no public information on trace sampling, rate limits, spike protection or quota caps
- We found no public information on issue states such as resolved or regressed, issue search and filters, or crash-free user and session rates
- We found no public information on a public status page, incident history or an availability SLA with credits
- The AI features run without a named model or provider on the captured pages
Best for
- You need APM-style performance diagnostics — distributed traces, service maps, slow database queries and continuous profiling — with OpenTelemetry ingestion
- You ship iOS and Android apps and want server-side symbolication and root-cause grouping with session attribution
- You can operate the on-premises edition and want telemetry stored entirely inside your own network perimeter with unlimited retention
- You face audits or client security reviews and need ISO 27001:2022, SOC 2 Type II, SAML SSO and audit logs to point to
Avoid if
- Your on-call workflow depends on documented notification channels, webhooks or a CLI; workflow and integrations scored 5-6, and we found no public information naming them
- You must cap data volume under load; data controls scored 4-6, and we found no public information on sampling, rate limits or spike protection
- You are procuring the SaaS edition only and need a stated hosting region and subprocessor list; sovereignty scores run from 3 to 8
- Your incident process needs your vendor's own reliability to be visible; security and reliability scored 6-7, and we found no public information on a status page or availability commitment
The scores
| Criterion | Panel median |
|---|---|
| Error capture, grouping & triage | 3 of 5 |
| APM, tracing & profiling | 3.5 of 5 |
| Alerting, integrations & developer workflow | 2.5 of 5 |
| Data scrubbing, retention & volume control | 3 of 5 |
| Access control, security & the vendor's reliability | 3 of 5 |
| European sovereignty | 3.5 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
Grouping by root cause with a custom fingerprint is documented, and the mobile SDK pages show real depth: dSYM symbolication and server-side R8 deobfuscation, a 200-frame stack cap that keeps the crash site, and crashes persisted to disk and uploaded on next launch. Laravel, Symfony and WordPress are on the framework list alongside a dedicated Laravel Octane agent, which is exactly my stack. I found no public information on issue states such as resolved or regressed, issue search and filters, or crash-free user and session numbers, so I hold this below the stronger descriptions. 3 4 5 6
The SaaS CTO
The mobile SDK documentation is the deepest evidence here — server-side symbolication via dSYMs and R8 mappings, root-cause grouping into issues, a custom fingerprint hook and an event filter that can drop events before they count — and GitHub shows agents for Node.js, Python, Java, PHP, Go, Ruby and the browser, with deploy correlation in the APM product. I found no public information on suspect commits or code owners, crash-free user rates, local variables per frame, or issue states like resolved and regressed that my on-call rotation would live in. 4 5 3 6 2
The Mobile Team Lead
The iOS and Android pages are the strongest part for us: dSYM and R8 mapping upload restore symbols server-side, issues group by root cause with the device, OS and app version distribution they occur across, and every error is attributed to the view and RUM session it happened in — the last screens before a crash — with custom fingerprint grouping on top. Backend and web agents exist too (Node, Go, Laravel Octane, browser and SPA). But we found no public information on crash-free users or sessions per release, issue lifecycle states like resolved or regressed, or Flutter and React Native SDKs, and the mapping upload path shown runs manually through the dashboard, which hurts at a two-week cadence. 4 5 3 6 2
The Site Reliability Engineer
Crash capture is documented in unusual depth for mobile — fatal signals, uncaught exceptions, app hangs and watchdog terminations, with dSYM and R8 symbolication done server-side, grouping by root cause, custom fingerprints, session and view attribution, and per-build mapping files — and backend coverage runs across Node.js, Go, PHP, Java, Python and Ruby with 47 framework guides. For my rotation, though, we found no public information on issue lifecycle states such as resolved or regressed, issue search and filters, crash-free users, or source maps for browser errors, so triage depth beyond mobile is unproven. 2 3 4 5 6
The Data Protection Officer
Server-side symbolication is documented for mobile crashes via dSYMs and R8 mappings, errors are grouped into issues by root cause with custom fingerprints, and backend agents cover Node, Python, Java, PHP, Go and Ruby alongside thoroughly documented iOS and Android SDKs with request, view and session context. Release correlation and deploy comparison are described. We found no public information on issue states such as resolved or regressed, merging or splitting issues, suspect commits, or crash-free user and session rates. 2 4 5 6
The Skeptic
The mobile side is genuinely documented — iOS and Android SDKs with server-side symbolication via dSYMs and R8 mappings, custom fingerprint grouping, an event filter that drops events before they land, and issues grouped by root cause with device and version distribution — but the depth stops there: web and backend error capture is a one-line description, and we found no public information on issue states like resolved or regressed, suspect commits, or crash-free users and sessions. 4 5 2 3 6
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
Transaction traces, slow database queries for PostgreSQL, MySQL, MongoDB and Redis, background job metrics, external call timings, service maps and percentile alert rules are all documented, and the profiling pages are genuinely good: continuous CPU and memory profiling, flame graphs, anomaly insights and a low-overhead production claim. OpenTelemetry integration gets one line, and I found no public information on trace sampling and its cost effect, so I stop short of the top descriptions. 3 6 7 9
The SaaS CTO
This is the part I would buy: distributed tracing with service maps, slow query capture across PostgreSQL, MySQL, MongoDB, Redis and Elasticsearch, background job and external call metrics, percentile-based alerting, continuous profiling with flame graphs and anomaly detection, Core Web Vitals from the browser, and infrastructure metrics beside the traces. OpenTelemetry support is confirmed in a single sentence, which keeps me off single-vendor instrumentation but tells me nothing about protocol detail, and I found no public information on how trace sampling is configured. 6 7 9 2 3
The Mobile Team Lead
Transaction traces with slow database queries and poor network calls, background job metrics, service maps with throughput, latency and errors per dependency, runtime metrics and a configurable Apdex are all documented, plus continuous profiling with flame graphs and anomaly detection, OpenTelemetry ingestion, infrastructure and container metrics beside the traces, and RUM with Core Web Vitals. What keeps it short of the top level: we found no public documentation of trace sampling configuration and its effect, and no retention or sampling per signal per plan. 6 7 9 2 3
The Site Reliability Engineer
This is what I want during a checkout-latency spike: end-to-end request tracing with service maps, slow database query capture across PostgreSQL, MySQL, MongoDB, Redis and Elasticsearch, background job metrics, runtime metrics, continuous profiling with flame graphs and anomaly insights, Core Web Vitals in the browser product, and OpenTelemetry ingestion. Alerting already covers response-time percentiles and baseline deviations with independent warning and critical levels; we found no public information on configurable trace sampling or its effect on cost and data. 2 3 6 7 9
The Data Protection Officer
Transaction traces, slow database queries, external call timings, a service map and runtime metrics are documented, with continuous profiling in flame graphs, anomaly detection on profiling data, and baseline plus percentile alert rules; OpenTelemetry ingestion and a real-user module with Core Web Vitals are stated. We found no public information on trace sampling and its effect, which is what determines whether our data volume and our invoice stay predictable. 2 3 6 7 9
The Skeptic
Transaction traces with percentile alert rules, slow query capture across five databases, background job and external service metrics, distributed tracing claims, OpenTelemetry ingestion, continuous profiling with anomaly insights, Core Web Vitals RUM, and host metrics beside it all — that is most of the way to the top tier, but trace sampling and its cost effect are undocumented, which is exactly the lever that decides my bill. 6 7 9 3 2
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
The alert engine is well documented — independent warning and critical levels, five evaluation windows, baseline deviation alerts, rules scoped per application, and coverage of web transactions, background jobs, database queries, external calls and exceptions — and the Jira guide is detailed down to custom fields and issue types. Beyond a claim of 200+ integrations, I found no public information naming notification channels such as Slack, email or PagerDuty, nor on webhooks, a CLI or source-code links. The AI agent answers from plain English but the model provider is not named on the captured pages. 3 8 9 6
The SaaS CTO
The alert rules are genuinely configurable — percentile and baseline rules, independent warning and critical levels, fixed evaluation windows and scoping per application — and Jira issue creation with custom fields is documented end to end, alongside an AI agent and an MCP server that hands rankings to Claude Code, Cursor or Codex. I found no public information on notification channels such as Slack, PagerDuty or Opsgenie by name, two-way tracker sync, source commit links, a CLI, or the model behind the AI features. 9 8 6 3
The Mobile Team Lead
Alert rules are documented in real depth — application metrics, key transactions, response time percentiles, baseline deviations with warning and critical levels, five-to-sixty minute evaluation windows — and Jira issues are created or linked from the error page with custom fields, alongside a plain-English AI agent and an MCP server for Claude Code, Cursor and Codex. But we found no public information naming notification channels like Slack, email, PagerDuty or Teams, no webhook documentation, no CLI for releases and mapping files, and the AI features run without a named model provider. 8 9 3 6
The Site Reliability Engineer
The alert engine is the strong part — rule types for application metrics, external services, key transactions and response-time percentiles, evaluated over 5 to 60 minute windows with all-or-any bucket logic and scoped per application — and Jira issue creation is documented down to custom fields and issue types, alongside a plain-English AI agent and an MCP server for Claude Code, Cursor and Codex. We found no public information on notification channels such as PagerDuty, Slack or email delivery, on webhooks, a CLI, or two-way tracker sync, and the AI model behind the agent is not named, so I cannot confirm the path from an alert to the person holding the pager. 3 6 8 9
The Data Protection Officer
Alert rules with independent warning and critical thresholds, evaluation windows and per-application scoping are documented, a Jira integration creates and links issues with custom fields, and an AI agent with an MCP server is offered. We found no public information on notification channels such as email, Slack or on-call paging, webhooks, a CLI, or two-way tracker sync. The AI features do not name the model or provider that runs them, which I require before any member data touches an explanation pipeline. 3 6 8 9
The Skeptic
The alert engine is real — threshold, percentile and baseline rules with warning and critical severities and per-application scoping — and the Jira integration creates and links issues with custom fields, but the captured pages never name the notification channels, document webhooks or a CLI, or say which model runs the AI features, so I cannot confirm an error actually reaches the person on call. 9 8 3 6
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, redaction and exclusion filters are documented for traces, logs and analytics, APM is stated to collect no personal data by default, retention follows the plan with automatic purge and unrestorable deletion, and an event filter can drop errors before grouping. The on-premises edition with Apache-licensed Helm charts stores telemetry entirely within our own perimeter with unlimited retention — the edition my shop clients would want. I found no public information on sampling, rate limits, quota caps or spike protection, which is exactly what protects the bill when a client's cron throws the same exception a million times. 2 3 5 10 11
The SaaS CTO
Defaults lean the right way — APM and browser monitoring capture no personal data by default, masking, redaction and exclusion filters are documented for traces, logs and analytics, and retention follows the plan with automatic purge and no restore of deleted data. The on-premises edition keeps every event inside my network perimeter with unlimited retention, but I found no public information on sampling, per-project rate limits, spike protection, API export, or deleting an individual user's data. 11 10 2 5
The Mobile Team Lead
The privacy pages document masking and redaction for traces, logs and analytics, exclusion filters, an SDK event filter that drops events before sending, PII off by default in APM and browser RUM, retention defined by the plan with automatic purge, and deletion that cannot be restored, plus an on-premises edition with unlimited retention. We found no public information on sampling, rate limits, spike protection or quota caps, IP anonymisation, or export and per-user deletion by API. 11 10 4 2
The Site Reliability Engineer
The scrubbing side is real — masking, redaction and exclusion filters across traces, logs and analytics, PII off by default in the APM, RUM and infrastructure modules, retention defined by plan with automatic purge and non-restorable deletion, a client-side event filter that drops events, and an on-premises edition that keeps everything inside our network with unlimited retention. We found no public information on sampling, rate limits, spike protection or quota caps, which are the controls that stop an incident night from also blowing the quota. 2 4 10 11
The Data Protection Officer
Masking, redaction and exclusion filters are documented across traces, logs and analytics, with personal data off by default in APM and browser monitoring and scrubbing cited among the HIPAA controls; retention follows the plan with automatic purge, deleted data is not restorable, and an SDK event filter can drop events before sending. An on-premises edition with unlimited retention keeps telemetry inside the customer's network. We found no public information on sampling, per-project rate limits, spike protection or quota caps, and the retention periods per plan carry no numbers. 2 5 10 11
The Skeptic
PII off by default in APM and browser RUM, masking and redaction for traces, logs and analytics, an SDK event filter that drops events before ingestion, retention defined by plan with automatic purge, and an on-premises edition claiming all telemetry stays inside your perimeter with unlimited retention — yet we found no public information on sampling, rate limits, spike protection, or what happens at the quota, which is the question I always ask first. 11 10 5 2
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
Role-based access with SAML SSO, organisation-wide two-factor enforcement, audit logs with configurable retention, AES-256 at rest and TLS 1.2+ in transit, ISO 27001:2022 with issuer and expiry dates, SOC 2 Type II reports on request under NDA, plus annual third-party penetration tests and SAST/SCA — that is a solid audit story for client reviews. I found no public information on a status page or incident history, a published availability SLA with credits, SCIM provisioning, a bug bounty programme, or SDK behaviour when the vendor itself is down. 2 12 13
The SaaS CTO
The trust center carries weight: ISO 27001:2022 with the certifying body and a 2027 expiry, SOC 2 Type II with the report available on request, annual third-party penetration tests, SAML, LDAP and Active Directory SSO, role-based access, audit logs and organization-wide two-factor enforcement. I found no public information on SCIM provisioning, an availability SLA with credits, a public status page with incident history, or how the SDKs behave when Atatus itself is down. 12 2 13
The Mobile Team Lead
The trust center publishes SOC 2 Type II with the report available on request under NDA, an ISO 27001:2022 certificate from the Standards Institution of Israel valid to 15 September 2027, AES-256 at rest and TLS 1.2+ in transit, annual third-party penetration tests, SAML, LDAP and Active Directory SSO with role-based access control, audit logs with configurable retention, and two-factor authentication enforceable organisation-wide. We found no public status page or incident history, no SCIM provisioning, no availability SLA with credits, and no documentation of SDK behaviour during a vendor outage. 12 2 13
The Site Reliability Engineer
For the auditors there is substance: role-based access with SAML, LDAP and Active Directory single sign-on, organisation-wide two-factor enforcement, audit logs with configurable retention, AES-256 at rest and TLS 1.2 or higher in transit, SOC 2 Type II with the report available under NDA, annual third-party penetration tests, and an ISO 27001:2022 certificate naming the Standards Institution of Israel with a 2027 expiry. We found no public information on the vendor's own status page, an availability commitment with credits, incident history, or SDK behaviour when Atatus itself is down. 2 12 13
The Data Protection Officer
The trust centre shows ISO 27001:2022 with issuer and expiry, SOC 2 Type II reports available under NDA, AES-256 at rest with TLS 1.2 or higher, annual third-party penetration tests, SAML, LDAP and Active Directory SSO, organisation-wide two-factor enforcement and audit logs with configurable retention — an auditable posture. We found no public information on a public status page, incident history, an availability SLA with credits, SCIM provisioning, or a vulnerability disclosure programme. 2 12 13
The Skeptic
SAML SSO, role-based access control, audit logs with configurable retention, organisation-wide two-factor enforcement, AES-256 and TLS 1.2+, and ISO 27001:2022 with SOC 2 Type II reports available under NDA — a respectable audit posture — but there is no public status page or incident history in these captures, no availability SLA with credits, and nothing on how ingestion behaves when the vendor has a bad day. 12 13 2 6
European sovereignty
panel opinion
panel disagrees
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 entity is named as NamLabs Technologies Pvt Ltd but its jurisdiction is not stated on the captured pages, and hosting location, a chosen EU region for the SaaS product and the subprocessor list — including any AI model — are all unstated. The documented on-premises edition stores telemetry entirely within our own network perimeter with zero external routing, which on my EU-hosted servers is the customer-controlled chain; the trust page promises regional processing for cloud monitoring but names no region. 2 3 12
The SaaS CTO
The route my enterprise customers would accept is documented and real: on-premises deployment stores all telemetry inside my network perimeter with zero external routing, Helm charts ship under an Apache licence, and RUM data is processed on my own servers with no third-party exposure. For the SaaS edition the contracting entity is NamLabs Technologies Pvt Ltd and I found no public information on subprocessors or an EU data region, but the documented self-hosted chain is mine to run in Berlin. 2 3 12 10
The Mobile Team Lead
The contracting entity is named as NamLabs Technologies Pvt Ltd but its jurisdiction is not stated on the captured pages, SaaS hosting location is not stated, and no subprocessor list appears; a data protection agreement link and GDPR page do exist. What lifts the score: the on-premises edition is documented to store all telemetry entirely inside the customer's network perimeter with zero external data transfer and unlimited retention, which would keep our chain on our own European servers. 2 6 12 8
The Site Reliability Engineer
The on-premises route is documented thoroughly — telemetry stored entirely within our network perimeter, zero external data transfer, internal-only agent communication, unlimited retention — so on European servers the chain is ours, with a Data Protection Addendum page and GDPR data-handling guidance referenced. For the SaaS route the contracting entity is NamLabs Technologies Pvt Ltd with jurisdiction unstated, and we found no public information on hosting location, an EU data region, or the subprocessors behind email, support, payment or the AI features. 2 8 10 12
The Data Protection Officer
A self-hosted edition with Helm charts, a stated zero external data transfer and telemetry stored entirely within the customer's perimeter lets a European operator run the chain on its own servers, and a Data Protection Addendum plus a regional-processing guarantee are referenced for the SaaS side. But the contracting entity's jurisdiction is not stated, no subprocessor list is published, no EU region for the SaaS edition appears on these pages, and the AI features do not say which model explains errors or where it runs. The chain is only as sovereign as the edition the customer chooses to operate. 2 3 12 13
The Skeptic
The contracting entity is NamLabs Technologies Pvt Ltd — by its name an Indian private company — and the captured pages state no hosting location for the SaaS service and name no subprocessors, though regional processing and on-premises, hybrid and bring-your-own-cloud deployment are claimed; the data protection addendum appears only as a link without published text. 8 10 12 2
Pricing transparency
not rated — the vendor publishes no price
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
Per-product prices are public with both annual and monthly figures — APM at "Per host/month (billed annually; $69/month billed monthly)" for "$49", Log Management at "Per ingested GB (billed annually; $1/GB billed monthly)" for "$0.75", RUM at "Per 250k views/month (billed annually; $69/month billed monthly)" for "$59" — and the model is stated as flat rate with no per-user pricing. I found no public information on overage rates and what happens at the quota, priced retention add-ons, which plan SSO requires, VAT, and the on-premises price, which appears only as a fixed annual contract. 2 3 6
The SaaS CTO
The published per-unit table is unusually concrete — APM at $49 per host per month billed annually or $69 monthly, logs at $0.75 per ingested GB annually or $1 monthly, RUM at $59 per 250k views per month, Kubernetes at $15 per node plus $0.84 per pod — which lets me estimate the SaaS bill from public pages. I found no public information on overage behaviour at the quota, retention pricing, which plan gates SSO, the price of the on-premises fixed annual contract, or VAT. 6 2 3
The Mobile Team Lead
Eight modules are priced publicly with unit rates and dual terms — APM at $49 per host/month (billed annually; $69/month billed monthly), RUM at $59 per 250k views/month (billed annually; $69/month billed monthly), Log Management at $0.75 per ingested GB (billed annually; $1/GB billed monthly) — with a free tier and flat-rate rather than per-user billing. But we found no public figures for overage, retention durations per plan, the on-premises licence beyond 'Fixed Annual Contract', or VAT and billing terms, and crash reporting is described as a separate product with no price shown. 6 3 2
The Site Reliability Engineer
Per-unit prices are public with both billing terms — APM at "$49 per host/month (billed annually; $69/month billed monthly)", logs at "$0.75 per ingested GB (billed annually; $1/GB billed monthly)", RUM at "$59 per 250k views/month (billed annually; $69/month billed monthly)", Kubernetes at "$15 per node/month + $0.84/pod (billed annually)", plus a free way to start. We found no public information on overage per unit, what happens at the quota, retention durations per plan, VAT, or the price of the on-premises edition beyond "Fixed Annual Contract", so a real annual bill is not computable. 2 3 6
The Data Protection Officer
Eight modules carry public unit prices with annual and monthly figures — APM at $49 per host/month billed annually and $69/month billed monthly, log management at $0.75 per ingested GB billed annually — plus a free entry point. Retention steps, the plan gating of SSO or audit logs, overage behaviour at the quota, VAT and the price of the on-premises fixed annual contract are not published, so an annual total for a given volume is not computable from the public pages alone. 2 3 6
The Skeptic
Per-unit prices for eight modules are published with annual and monthly figures — APM at $49 per host/month billed annually, logs at $0.75 per ingested GB, RUM at $59 per 250k views/month — which is more than most vendors show, but no error-tracking volume limit, no overage rate, no cap behaviour at the quota, and no price for the on-premises edition appear anywhere on these pages. 6 2 3
European sovereignty — proven facts
2 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 | Not determined | — | uncited Report an error |
|---|---|---|---|
| Hosting location | Not determined | — | uncited Report an error |
| Hosting options | Self-hostable | 1/1 pts | 2 Report an error |
| Open source | Not determined | — | uncited Report an error |
| Data processing agreement |
Published, self-serve
unverified
Why unverified?Only the link to the Data Protection Addendum page is shown; the excerpts do not include the agreement text itself, so it cannot be confirmed that the linked page publishes the full agreement. |
1/1 pts | 12 Report an error |
| Transfer impact assessment | Not determined | — | uncited Report an error |
Questions about Atatus
Is Atatus European?
Not determined: the vendor’s pages as captured do not say where Atatus is based.
Where does Atatus store data?
Not stated on the vendor’s pages as of 17 Nov 2026.
Does Atatus have a free plan?
Yes. Atatus has a free plan, per the vendor’s page captured 17 Nov 2026.
What are the best alternatives to Atatus?
As of 18 Nov 2026, the panel rates Sentry (3.5/5), Datadog APM & Error Tracking (3.5/5) and Dynatrace (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: Atatus alternatives.
Where this could be wrong
- Evidence ages. The oldest capture behind this page is from 17 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.
- 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.
- 36 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
- 6 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
- 2 hosting 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 data 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 legal 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
Sources (13)
The pages every claim on this page was read from — each one checked, dated, and kept verifiable.
- 1 Vendor page www.atatus.com Checked 17 Nov 2026 Details →
- 2 Self-hosting / on-premises installation docs — found from the homepage www.atatus.com Checked 17 Nov 2026 Details →
- 3 Code repository (open-source licence) — found from the homepage github.com Checked 17 Nov 2026 Details →
- 4 Error capture, grouping & triage — found from sitemap docs.atatus.com Checked 17 Nov 2026 Details →
- 5 Error capture, grouping & triage — found from sitemap docs.atatus.com Checked 17 Nov 2026 Details →
- 6 APM, tracing & profiling — found from sitemap www.atatus.com Checked 17 Nov 2026 Details →
- 7 APM, tracing & profiling — found from sitemap docs.atatus.com Checked 17 Nov 2026 Details →
- 8 Alerting, integrations & developer workflow — found from sitemap docs.atatus.com Checked 17 Nov 2026 Details →
- 9 Alerting, integrations & developer workflow — found from sitemap docs.atatus.com Checked 17 Nov 2026 Details →
- 10 Data scrubbing, retention & volume control — found from sitemap docs.atatus.com Checked 17 Nov 2026 Details →
- 11 Data scrubbing, retention & volume control — found from sitemap docs.atatus.com Checked 17 Nov 2026 Details →
- 12 Access control, security & the vendor's reliability — found from sitemap www.atatus.com Checked 17 Nov 2026 Details →
- 13 Access control, security & the vendor's reliability — found from sitemap docs.atatus.com Checked 17 Nov 2026 Details →