# Atatus — Error Tracking & APM

Atatus by Atatus holds a panel rating of 3/5 from 6 AI judges (category median 2.5/5), as of 2026-11-18. Provenance: provenance unknown; sovereignty: 2 of 6 dimensions proven.

- Vendor: Atatus (https://www.atatus.com)
- Category: [Error Tracking & APM](https://whats-best.ai/software/error-tracking.md)
- Provenance (editorial classification): provenance unknown
- Canonical page: https://whats-best.ai/software/error-tracking/atatus
- Alternatives: https://whats-best.ai/software/error-tracking/atatus/alternatives ([markdown](https://whats-best.ai/software/error-tracking/atatus/alternatives.md))
- Data as of: 2026-11-21 · evaluated 2026-11-18 · oldest source captured 2026-11-17

**AI-generated.** Every score, rationale and verdict here is written by a panel of AI judges from public evidence — an analysis, not a hands-on test. Every fact quotes the vendor page it was read from. No score can be bought. How scores are made: https://whats-best.ai/methodology

## 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 [S3]

## 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

## Scores by judge and criterion

Scores out of 5, each judge scoring independently against the published rubric (v1). "n/r" = not rated: the vendor publishes no price, or the judge found no public information on that criterion.

| Criterion | The Agency Tech Lead | The SaaS CTO | The Mobile Team Lead | The Site Reliability Engineer | The Data Protection Officer | The Skeptic |
| --- | --- | --- | --- | --- | --- | --- |
| Error capture, grouping & triage | 3/5 | 3/5 | 3/5 | 3/5 | 3/5 | 3/5 |
| APM, tracing & profiling | 3.5/5 | 3.5/5 | 3.5/5 | 3.5/5 | 3.5/5 | 3.5/5 |
| Alerting, integrations & developer workflow | 2.5/5 | 2.5/5 | 2.5/5 | 3/5 | 2.5/5 | 2.5/5 |
| Data scrubbing, retention & volume control | 3/5 | 3/5 | 2.5/5 | 2/5 | 3/5 | 2.5/5 |
| Access control, security & the vendor's reliability | 3.5/5 | 3/5 | 3.5/5 | 3/5 | 3/5 | 3/5 |
| European sovereignty | 3/5 | 4/5 | 3.5/5 | 3/5 | 3.5/5 | 1.5/5 |
| Pricing transparency | n/r | n/r | n/r | n/r | n/r | n/r |
| **Weighted verdict** | **3/5** | **3/5** | **3/5** | **3/5** | **3/5** | **2.5/5** |

### The judges

- **The Agency Tech Lead** (v1.0): Technical lead at a web agency in Cologne with fourteen developers and forty client sites on Laravel, Shopware and WordPress, most on maintenance contracts. Wants every client in its own project with its own alert channel, PHP stack traces that show the query and the queued job, slow pages found before the client calls, request data scrubbed because the shops hold customer addresses, and a monthly bill that does not jump when one client's cron job throws the same exception a million times.
- **The SaaS CTO** (v1.0): CTO of a B2B SaaS company in Berlin with thirty-five engineers, twelve services in Go, Python and TypeScript on Kubernetes and a React frontend. Wants one trace from the click in the browser to the slow database call three services down, OpenTelemetry so the instrumentation is not locked to one vendor, errors routed to the team that owns the service, releases linked to the commits that broke them, and an EU region because the enterprise customers ask where their data goes.
- **The Mobile Team Lead** (v1.0): Leads the six-person app team of a fashion retailer in Hamburg, with an iOS and an Android app and a Flutter rewrite under way, released every two weeks. Wants native crashes symbolicated without a manual upload, crash-free users per release so a bad version is stopped in the store rollout, the device, OS and the last screens before the crash, logs from a customer's phone when support asks, and alerts when a new release crashes more than the last.
- **The Site Reliability Engineer** (v1.0): Site reliability engineer on the on-call rota of a payments platform in Amsterdam, woken at night when checkout latency climbs. Wants alerts on error rates and latency percentiles, not on every single exception, routed to PagerDuty with the trace attached, spike protection so an incident does not also blow the quota, SSO and audit logs for the auditors, and a vendor whose own status page and SLA say what happens when the monitoring is the thing that is down.
- **The Data Protection Officer** (v1.0): Data protection officer of a statutory health insurer whose member portal and app are built by an in-house team and two agencies. Knows that a stack trace or a request body can carry a member number, a diagnosis code or an IBAN. Reads the subprocessor list, asks where events are stored and for how long, wants scrubbing on the server and not only in the SDK, asks which AI model explains the errors and where, and needs a DPA before the first SDK goes into production.
- **The Skeptic** (v1.0): Has seen a "free tier" that ran out on the first busy Monday, an overage bill larger than the plan after one deploy looped on an exception, "EU hosting" with the support desk and the AI assistant in the US, and an SDK that slowed the app it was meant to watch. Asks what happens at the quota, how long events are really kept, whether the instrumentation works with another vendor after leaving, what the self-hosted edition leaves out — and what the second year costs.

## European sovereignty — proven facts

Built only from facts on the vendor's own pages; a dimension we could not prove is left open, never scored as zero. Headline: 2 of 6 dimensions proven.

| Dimension | Finding | Points | Source |
|---|---|---|---|
| Legal entity | Not determined | — | — |
| Hosting location | Not determined | — | — |
| Hosting options | Self-hostable | 1/1 | [S2] |
| Open source | Not determined | — | — |
| Data processing agreement | Published, self-serve | 1/1 | [S12] |
| Transfer impact assessment | Not determined | — | — |

## Key facts

Each fact is the vendor's own statement, cited to the source page it was read from ([S*n*] → Sources).

**Compliance**
- Access control: yes · SAML · LDAP · Active Directory [S2]
- Audit: yes [S7]
- Audit logs: yes [S2]
- Audited controls: yes [S6]
- Baa: yes [S12]
- Certifications: yes [S4]
- Certifications: SOC 2 Type II · ISO 27001 · HIPAA · GDPR [S5]
- Certifications: SOC 2 Type II · ISO 27001 · HIPAA · GDPR [S7]
- Certifications: SOC 2 Type II · ISO 27001 · HIPAA · GDPR [S8]
- Certifications: SOC 2 Type II · ISO 27001 · HIPAA · GDPR [S13]
- Certifications: SOC 2 Type II · ISO 27001 · HIPAA · GDPR [S11]
- Certifications: SOC 2 Type II · ISO 27001 · HIPAA · GDPR [S9]
- DPA: yes [S12]
- GDPR: yes [S2]
- GDPR: yes [S6]
- GDPR: yes [S12]
- GDPR badge: yes [S10]
- GDPR no pii: no [S10]
- GDPR reference: yes [S10]
- HIPAA: yes [S2]
- HIPAA: yes [S6]
- HIPAA: yes [S10]
- HIPAA: yes [S12]
- HIPAA measures: yes [S12]
- ISO 27001: yes [S2]
- ISO 27001: yes [S6]
- ISO 27001: yes [S10]
- ISO 27001: ISO 27001:2022 · yes [S12]
- ISO 27001 expiry: 2027-09-15 [S12]
- PCI DSS: yes [S2]
- Pentest: annual · yes [S12]
- Sast sca: yes [S12]
- SOC 2: yes [S2]
- SOC 2: SOC 2 Type II · yes [S6]
- SOC 2 type2: yes [S10]
- SOC 2 type2: yes · upon request under NDA [S12]

**Data**
- Deleted not restorable: no [S10]
- Expiry automatic purge: yes [S10]
- Retention per plan: yes [S10]

**Hosting**
- Agentless: yes [S12]
- Data residency: yes [S12]
- Deployment options: saas · on_premises · hybrid · byoc [S6]
- On premise available: yes [S3]

**Integrations**
- API query builders: yes [S3]
- Count 200 plus: 200 [S3]
- Helm charts: Helm charts for Atatus [S3]
- Jira auth: email/username and API token (password for older version) [S8]
- Jira custom fields: yes [S8]
- Jira issue linking: JIRA button on Error page to create or link existing issues [S8]
- Jira issue types: Task · Bug · Improvement · Epic · New Feature · Task [S8]
- Jira purpose: Alerts in Atatus can be used to create issues in Jira [S8]
- Jira setup location: project Settings » Ticketing Integrations » JIRA [S8]
- Jira summary variable: custom summary supported with {{summary}} variable [S8]

**Legal**
- Company: NamLabs Technologies Pvt Ltd [S8]
- Company name: NamLabs Technologies Pvt Ltd [S10]
- Copyright entity: NamLabs Technologies Pvt Ltd [S5]
- Copyright entity: NamLabs Technologies Pvt Ltd [S9]
- Copyright holder: NamLabs Technologies Pvt Ltd [S2]
- Copyright holder: NamLabs Technologies Pvt Ltd [S4]
- Copyright holder: NamLabs Technologies Pvt Ltd · 2026 [S11]
- Entity: 2026 · NamLabs Technologies Pvt Ltd [S7]
- Entity: NamLabs Technologies Pvt Ltd [S6]
- Entity: NamLabs Technologies Pvt Ltd [S13]
- Entity: 2026 · NamLabs Technologies Pvt Ltd [S12]

**Pricing**
- Per user pricing: flat rate · no [S2]
- Price range: 0 · 99 · USD [S1]
- Price range: 0 · 99 · USD [S6]

**Product**
- Additional modules: APM · logs · RUM · infrastructure · SIEM [S2]
- AI agent: yes [S6]
- AI insights: yes [S3]
- Alert operators: above · below · equal [S9]
- Alert severity: Warning · Critical · yes [S9]
- Alert target scoping: Alert rules scoped by application; multiple targets evaluated independently [S9]
- Android error tracking summary: Android error tracking covers crashes, ANRs, handled exceptions and R8 mapping upload [S5]
- Anonymization supported: anonymization · yes [S11]
- Apdex configurable: yes [S6]
- Apm: yes [S3]
- Apm alert scope: APM alerts cover web transactions, background jobs, database queries, external service calls, and exceptions [S9]
- Apm masking filters: data masking · exclusion filters [S11]
- Apm no pii default: APM · no [S11]
- App hang detection: no · AppHang · yes [S4]
- App hang thresholds: 2.5 · 0.1 · 30 [S4]
- Background job metrics: Background Response Time · Background Throughput [S9]
- Baseline alerts: yes [S9]
- Baseline metrics supported: Web Response Time · Web Throughput · Exception Count · External Request Response Time · External Request Throughput · Database Query Time · Database Throughput [S9]
- Capabilities: apm · infrastructure_monitoring · kubernetes_container_visibility · log_management · rum · error_tracking [S2]
- Competitor comparison: comparison pages for Datadog, New Relic, Dynatrace [S6]
- Crash captured types: SIGSEGV · SIGABRT · SIGBUS · SIGILL · SIGFPE · SIGTRAP · yes [S4]
- Crash consent requirement: yes · 1 [S4]
- Crash enablement: yes · CrashReporting.enable() must come after RUM.enable() [S4]
- Crash persistence: persist to disk, upload next launch [S5]
- Crash reporting: iOS SDK reports crashes, app hangs, watchdog terminations, memory warnings, and handled errors [S4]
- Crash reporting default: yes [S5]
- Crash upload timing: written to disk, sent on next launch [S4]
- Data isolation: no · yes [S2]
- Data retention comparison: unlimited · fixed annual contract · unlimited [S2]
- Database capture: PostgreSQL · MySQL · MongoDB · Redis · Elasticsearch [S6]
- Database metrics: Database Query Time · Database Throughput [S9]
- Database monitoring: yes [S3]
- Deobfuscate server side: yes [S5]
- Deobfuscation mapping upload: version name and build number · RUM application settings in dashboard [S5]
- Deploy tracking: yes · 15 [S6]
- Deployment modes: on-premises · saas · hybrid · byoc [S2]
- Description: Next-gen observability platform combining APM, infrastructure monitoring, and user experience monitoring [S3]
- Distributed tracing: transaction traces, slow database queries, inefficient network calls, real-time metrics [S6]
- Dsyl symbolication: server-side symbolication using dSYMs; without matching dSYMs a report shows addresses only [S4]
- Encryption: AES-256 · TLS 1.2+ [S12]
- Error event mapper: error event mapper for redaction or dropping; crashes cannot be dropped; fatal hangs and watchdog terminations skip the mapper [S4]
- Error event mapper: yes [S5]
- Error fingerprint: custom fingerprint grouping via RUM.Attributes.errorFingerprint; SDK-grouped failure types cannot be fingerprinted [S4]
- Error grouping: Errors grouped into issues by root cause [S5]
- Error metrics: Exception Count [S9]
- Error session attribution: yes [S5]
- Error sources: SOURCE · NETWORK · WEBVIEW · CONSOLE [S5]
- Evaluation windows: 5 · 10 · 15 · 30 · 60 [S9]
- External service metrics: External Request Response Time · External Request Throughput [S9]
- Fatal anr reporting: yes [S5]
- Flame graph: flame graph visualizes CPU time, aggregating thousands of stack samples [S7]
- Flexible retention: yes [S3]
- Framework list: supported frameworks across Node.js, Python, Java, PHP, Go, Ruby [S6]
- Frameworks guides: 47 [S6]
- Free tier: yes [S3]
- Free trial: yes [S6]
- Go agent: Atatus APM Agent for Go [S3]
- Grouping requires throwable: stack_trace [S5]
- Handled exception API: addError [S5]
- Handled exception example: GlobalRumMonitor.get().addError · yes [S5]
- Infra no user info: Infrastructure Monitoring · no [S11]
- Infrastructure monitoring: yes [S3]
- Ios release: iOS agent release repository (Swift) [S3]
- Issue metadata: yes [S5]
- Kubernetes monitoring: yes [S3]
- Languages agents: 7 [S6]
- Laravel octane agent: Atatus APM for Laravel Octane [S3]
- Logs as errors: logger · error · critical [S4]
- Logs dashboards: yes [S3]
- Logs monitoring: yes [S3]
- Logs pii user responsibility: Analytics & Log Management · user [S11]
- Logs redaction features: filters · masking · redaction [S11]
- Manual error reporting: RUMMonitor.shared().addError · source · network · webview · console · logger · custom [S4]
- Mapping file persistence: yes [S5]
- Masking redaction traces logs: redaction_and_masking · traces · logs · analytics · yes [S11]
- Mcp server: yes [S6]
- Memory warnings tracking: yes · MemoryWarning · trackMemoryWarnings [S4]
- Network error instrumentation: AtatusInterceptor [S5]
- Network security: no · yes [S2]
- Nodejs agent: Node.js APM application monitoring and crash reporting [S3]
- Nonfatal anr default: no [S5]
- Objective c support: Objective-C supported; addError takes no error type, hang threshold 0 disables reporting [S4]
- Onboarding steps: 4 [S6]
- Opentelemetry support: yes [S3]
- Optimization ranking: total_time · long_tail · yes [S6]
- Platform combination: AI observability platform combining APM, logs, RUM, infrastructure monitoring and SIEM [S1]
- Platform support: supported with memory warning and press-based action notes · full support · crashes yes, app hangs and watchdog terminations no [S4]
- Platforms: Web · Linux · Windows · macOS · Docker · Kubernetes [S1]
- Platforms: Web · Linux · Windows · macOS · Docker · Kubernetes [S6]
- Profiling anomaly types: Memory Leak · Sudden Spike · Resource Exhaustion · Instability · Pattern Deviation · CPU Trend · Sudden Memory Spike [S7]
- Profiling compare: compare profiling data across time ranges, deployments, or configurations with baseline vs comparison functions [S7]
- Profiling insights: Service Name · ProcessId · Anomaly Type · Severity · Peak Value · Profile Type [S7]
- Profiling low overhead: low overhead [S7]
- Profiling metrics: CPU usage · memory allocations · lock wait time · I/O activity [S7]
- Profiling visibility: Continuous profiling captures stack traces at regular intervals to reveal CPU/memory hotspots, inefficient code paths, and resource-heavy operations [S7]
- Pseudonymization supported: pseudonymization · yes [S11]
- Quickstart no yaml: no [S6]
- Related modules: Mobile Vitals · Session Replay · Log Collection [S4]
- Reported error classes: crashes · ANRs · network_errors · handled_exceptions [S5]
- Rule types: Application Metric · External Service · Key Transaction · Response Time Percentile [S9]
- Rum error monitoring topics: atatus · apm · error-monitoring · monitoring · rum [S3]

**Support**
- Enterprise support: yes [S2]

18 more facts on the canonical page: https://whats-best.ai/software/error-tracking/atatus

## Questions

### 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](https://whats-best.ai/evidence/26383).

### What are the best alternatives to Atatus?

As of 18 Nov 2026, the panel rates [Sentry (3.5/5)](https://whats-best.ai/software/error-tracking/sentry), [Datadog APM & Error Tracking (3.5/5)](https://whats-best.ai/software/error-tracking/datadog) and [Dynatrace (3/5)](https://whats-best.ai/software/error-tracking/dynatrace) 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](https://whats-best.ai/software/error-tracking/tideways) (EU-Made). Ratings are the AI panel’s opinion, formed from public evidence: [how scores are made](https://whats-best.ai/methodology#ordering). The full list, with European products first: [Atatus alternatives](https://whats-best.ai/software/error-tracking/atatus/alternatives).

## What this page leaves out

- 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.
- 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.
- 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.
- 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.
- 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.
- 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.
- 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.

## Sources

- [S1] Vendor page: https://www.atatus.com (checked 2026-11-17)
- [S2] Self-hosting / on-premises installation docs — found from the homepage: https://www.atatus.com/on-premises/ (checked 2026-11-17)
- [S3] Code repository (open-source licence) — found from the homepage: https://github.com/atatus (checked 2026-11-17)
- [S4] Error capture, grouping & triage — found from sitemap: https://docs.atatus.com/rum-monitoring/mobile/ios/ios-error-tracking (checked 2026-11-17)
- [S5] Error capture, grouping & triage — found from sitemap: https://docs.atatus.com/rum-monitoring/mobile/android/android-error-tracking (checked 2026-11-17)
- [S6] APM, tracing & profiling — found from sitemap: https://www.atatus.com/product/apm/ (checked 2026-11-17)
- [S7] APM, tracing & profiling — found from sitemap: https://docs.atatus.com/profiling/overview (checked 2026-11-17)
- [S8] Alerting, integrations & developer workflow — found from sitemap: https://docs.atatus.com/product-guide/tool-integrations/jira (checked 2026-11-17)
- [S9] Alerting, integrations & developer workflow — found from sitemap: https://docs.atatus.com/alerting/apm-alerts (checked 2026-11-17)
- [S10] Data scrubbing, retention & volume control — found from sitemap: https://docs.atatus.com/product-guide/security-privacy/data-retention (checked 2026-11-17)
- [S11] Data scrubbing, retention & volume control — found from sitemap: https://docs.atatus.com/product-guide/security-privacy/pii-handling-and-data-privacy (checked 2026-11-17)
- [S12] Access control, security & the vendor's reliability — found from sitemap: https://www.atatus.com/trust-center/ (checked 2026-11-17)
- [S13] Access control, security & the vendor's reliability — found from sitemap: https://docs.atatus.com/product-guide/security-privacy/two-factor-authentication (checked 2026-11-17)

---

Cite as: whats-best.ai, "Atatus — Error Tracking & APM", AI panel analysis, as of 2026-11-21. https://whats-best.ai/software/error-tracking/atatus

Corrections: https://whats-best.ai/correct/1992?target=page
