Panel rating · 6 judges · How to read the stars

Category median

Sovereignty: 1 of 6 dimensions proven

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

by Airbrake.io (a LogicMonitor company) · airbrake.io

Report an error on this page Is this your product? →

Link to this page

Airbrake: AI-assisted analysis on whats-best.ai Airbrake: AI-assisted analysis on whats-best.ai (dark)

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

Airbrake at a glance

Vendor
Airbrake.io (a LogicMonitor company)
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
Not stated on the vendor’s pages as of 17 Nov 2026
Panel verdict
The AI panel rates Airbrake 2/5, the mean of 6 judges. Airbrake, an error tracking and APM product from Airbrake.io (a LogicMonitor company), is strongest where its documentation is deepest — capturing and grouping errors and controlling their volume — and weakest on sovereignty and pricing openness. how scores are made
As of
Vendor pages captured 17 Nov 2026; evaluated by the panel 18 Nov 2026. all sources

Airbrake alternatives, European ones first →

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

The panel's verdict

Airbrake, an error tracking and APM product from Airbrake.io (a LogicMonitor company), is strongest where its documentation is deepest — capturing and grouping errors and controlling their volume — and weakest on sovereignty and pricing openness. Error tracking scores span 4 to 6, the widest range among the seven criteria: the higher scores credit documented notifiers, grouping criteria spelled out, breadcrumbs and a REST API covering the group lifecycle, while the lower scores weigh undocumented symbolication, custom fingerprinting and crash-free metrics. Data controls span 4 to 5 for the same shape of reason — usage caps per account and project, quota alerts and notifier-side sampling are documented; server-side scrubbing rules and per-plan retention are not. Performance tracing, workflow and integrations, and security and reliability hold at 4: route, query and queue timing and thorough two-factor documentation on one side, undocumented distributed tracing, OpenTelemetry, webhooks and SAML on the other. Sovereignty sits at 3, with AWS named as host and no region stated, and pricing transparency at 2 — the low point, with no price figures on the captured pages.

Report an error

Speaks for it

  • Automatic error grouping with published criteria — error type, message, file and environment — plus breadcrumbs shown in the occurrences tab
  • A documented REST API covering groups, notices, deploys, source maps and project statistics
  • Usage caps per account and per project, quota threshold alerts, and a stated 429 response above the monthly error quota
  • Two-factor authentication available on all plans, enforceable account-wide, with recovery codes and email notification when an admin disables it
  • Per-route performance breakdowns into database, view, cache and external-request time, with SQL query and background-queue stats

Report an error

Held against it

  • AWS is named as the hosting provider with no region stated, and the Data Processing Addendum is offered only to EU customers, only on request by email
  • We found no public information on subprocessors, the contracting entity's jurisdiction or a chosen EU data region
  • We found no public information on distributed tracing across services, OpenTelemetry ingestion, latency percentiles or code-level profiling
  • We found no public information on webhooks, issue-tracker integrations, on-call routing or SAML single sign-on
  • The captured pages show no price figure for any plan, quota size or on-demand rate, so no annual cost is computable from them

Report an error

Best for

  • You run Rails, Express, Go, Django or Flask services and want grouped errors plus route, SQL and background-queue timing bundled into the same notifier
  • Your error volume spikes unpredictably and you need hard limits — per-account and per-project usage caps with quota alerts, blocking or on-demand overage
  • You want two-factor authentication enforceable account-wide, with recovery codes, available on all plans
  • You automate triage from CI — deploy tracking, source-map uploads and group muting or deletion through a documented REST API

Report an error

Avoid if

  • Your procurement review needs a published subprocessor list, a named data region or a self-service agreement before signing — the Data Processing Addendum is offered only to EU customers on email request
  • You follow one trace from the browser click to the slow database call across services — the documented performance view stops at route, query and queue level
  • Your incident response depends on pager routing or webhook alerting — documented notifications are email-based, with Slack mentioned only in passing
  • Your organisation requires SAML or OIDC single sign-on, SCIM or audit logs — only GitHub single sign-on is documented

Report an error

The scores

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

Error capture, grouping & triage

Show reasoning
How this is scored

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

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

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

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

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

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

Report an error

The Agency Tech Lead

Grouping criteria are spelled out, breadcrumbs are automatic from the JavaScript notifier and shown in the occurrences tab, per-notice context is rich (user, route, session, params, environment, severity), and source map upload plus deploy tracking are all documented, with notifiers evidenced for Ruby, JavaScript and Node, Python, Go, PHP and.NET and the REST API covering the group lifecycle from muting to permanent deletion. We found no public information on custom fingerprinting, merge or split of issues, local variables per frame or symbolication for the mobile crash report endpoint, which is what would push it higher for our stack. 1 2 3 5 8

Report an error

The SaaS CTO

Grouping criteria, breadcrumbs, rich notice context and a source-map and deploy-tracking API are all documented, which covers the core triage loop for my Go, Python and TypeScript services. I found no public information on release health, suspect commits or custom fingerprinting, so it reads as a solid mid-level error tracker rather than the standard a large organisation standardises on. 1 2 5 6

Report an error

The Mobile Team Lead

Notifiers are documented for the web and backend stack beside our apps (Ruby, JavaScript, Python, Go, Java, PHP,.NET) with rich per-error context, automatic grouping by error type, message, file and environment, unresolved/muted/archived states, deploy tracking and version-filtered occurrences. Breadcrumbs are documented only for the JavaScript notifier, and while there is an API endpoint to submit iOS crash reports, we found no public information on symbolication, crash-free users and sessions per release, or Android and Flutter notifiers — the mobile half of my checklist is essentially undocumented. 1 2 5 8

Report an error

The Site Reliability Engineer

Error grouping is documented down to its criteria — type, message with extracted data fields, file and environment — and notices arrive with rich request, user and session context, an automatic breadcrumb timeline in the JavaScript notifier, and deploy and source map handling through the API. We found no public information describing stack trace symbolication beyond an iOS crash-report endpoint, custom fingerprinting, full issue lifecycle states like resolved and regressed, or crash-free user metrics, which sits this just under the level a team standardises on. 1 2 5

Report an error

The Data Protection Officer

Notifiers are documented for Ruby, JavaScript, Python, Go, PHP,.NET and Java with an iOS crash-report endpoint, automatic grouping by error type, message, file and environment, deploy tracking by API, and notice context carrying user id, name, email, session and params, with browser breadcrumbs captured automatically and strippable in the notifier. The issue lifecycle is reachable by API — list, mute, delete groups, per-group statistics, source-map upload and deletion — which I value for automated cleanup. I found no public information on symbolication, custom fingerprints, merging or splitting issues, suspect commits, local variables per frame or crash-free session figures. 1 2 3 5 8

Report an error

The Skeptic

Grouping is automatic with its criteria explained — error type, message with extracted data fields, file, environment — and the documented API reaches the whole issue lifecycle including mute, unmute, delete and per-group stats. Breadcrumbs with their recorded event types and a strip option, rich notice context (user, request, session, environment) and source map uploads are all documented, with notifiers evidenced for Ruby, Python, Go, PHP,.NET, Java and Node. What I could not find: custom fingerprinting, merge or split of issues, mobile symbolication, suspect commits, or crash-free users and sessions. 1 2 3 5 8

Report an error

APM, tracing & profiling

Show reasoning
How this is scored

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

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

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

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

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

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

Report an error

The Agency Tech Lead

Route-level timings with breakdowns into database, view, cache and external request time, automatic SQL query stats, queue tracking for Sidekiq, Resque, DelayedJob and Celery, unlimited environments, Apdex and a click-through from a route to its linked errors give me most of what my maintenance clients need. We found no public information on percentiles, distributed tracing across services, OpenTelemetry ingestion, code-level profiling or frontend Web Vitals, so this reads as a single-service performance view rather than end-to-end tracing. 3 4 5

Report an error

The SaaS CTO

Route timings with a breakdown into database, view and cache time, per-query stats and background job tracking for Celery and Sidekiq are documented, with a click-through from a route to its linked errors. I found no public information on distributed tracing across services, OpenTelemetry ingestion, profiling, percentiles or real-user monitoring, which is exactly what I need to follow one trace from the browser click to the slow database call. 3 4 5

Report an error

The Mobile Team Lead

Route stats with per-route breakdowns into database, view, cache and external-request time, per-query SQL stats, background queue stats, Apdex and a click-through from a route to its linked errors are documented across Rails, Express, Go, Django and Flask. We found no public information on distributed tracing across services, percentile views, real user monitoring or Web Vitals, profiling, OpenTelemetry ingestion or host metrics, so this sits between a simple endpoint view and full transaction monitoring. 3 4 5

Report an error

The Site Reliability Engineer

The APM side covers what I need at 3am: per-route breakdowns into database, view, cache and external request time, SQL query stats, automatic background-job tracking for the Ruby and Python queue libraries we run, span timing around code blocks, Apdex, and a click-through from a slow route to its linked errors. We found no public information on latency percentiles per endpoint, distributed tracing across services, OpenTelemetry ingestion, profiling or frontend real-user monitoring, so the end-to-end picture stops at the process boundary. 3 5

Report an error

The Data Protection Officer

Route timings per endpoint, per-SQL-query timing, background job stats for Sidekiq, Resque, Celery and more, an Apdex measure and a click-through from a slow route to its linked errors are documented for Rails, Node, Go, Django and Flask, with automatic tracking in Django, Flask and Express and manual spans in Go and Java. I found no public information on percentiles, N+1 detection, distributed tracing across services, OpenTelemetry ingestion, profiling or frontend Web Vitals, so the documented picture stays at endpoint, query and queue level. 3 4 5

Report an error

The Skeptic

Route timings with breakdowns into database, view, cache and external-request time, background job and queue tracking, SQL query stats, Apdex and a click-through from a route to its linked errors are all documented, with automatic tracking for Django, Flask, Celery and a long list of Python and Go frameworks. But this is a notifier-bundled, per-request view: we found no public information on distributed tracing across services, percentiles, OpenTelemetry, code-level profiling or frontend Web Vitals. Java and Go background job tracking is manual, and Java middleware support is stated as still to be added. 3 4 5

Report an error

Alerting, integrations & developer workflow

Show reasoning
How this is scored

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

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

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

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

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

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

Report an error

The Agency Tech Lead

Email notifications are configurable in ways I like — new exception groups, errors becoming unresolved, production-only filtering, daily and weekly digests and a digest-only mode — and the REST API plus deploy tracking are documented in real depth. We found no public information on issue tracker integrations, PagerDuty or Opsgenie, webhooks, alert rules on frequency or performance, or a CLI; Slack appears only as an example of integration notification settings, and single sign-on is documented only as part of GitHub sign-in. 5 6 9

Report an error

The SaaS CTO

Email notifications are well worked out — new and unresolved groups, comments, production-only filtering and daily or weekly digests — plus a documented REST API with deploy tracking and Slack named as an integration. I found no public information on issue-tracker sync, on-call routing, webhooks or a CLI, so the path from an error to the person who owns the service is incomplete. 5 6 9

Report an error

The Mobile Team Lead

A documented REST API covers projects, error groups, occurrences, deploys, source map uploads and statistics, and email notifications fire on new groups and on errors becoming unresolved, with a production-only filter and daily or weekly digest modes; Slack appears only as a passing pointer to a separate integrations section. We found no public information on issue tracker integrations, webhooks, on-call tooling, a CLI, or AI explanations of errors, so this lands between basic notifications and the full alerting workflow I would want for a two-week release cadence. 5 6

Report an error

The Site Reliability Engineer

Notifications cover new exception groups and groups becoming unresolved, with a production-only filter, digest-only email mode and comment notifications; a Slack integration is named for its notification settings and the REST API is genuinely documented across groups, notices, deploys and source maps. We found no public information on PagerDuty or Opsgenie routing, issue tracker sync, webhooks, frequency or performance-based alert rules, or a CLI — the pager routing I rely on is simply not documented. 5 6

Report an error

The Data Protection Officer

Email notifications are configurable — new exception groups, errors becoming unresolved, production-only environments, comments, daily and weekly digests — on top of a thoroughly documented REST API covering deploys, source maps, groups and project statistics, plus automatic alerts as the monthly quota reaches thresholds. Slack is mentioned only in passing, and I found no public information on webhooks, issue tracker integrations that create or sync tickets, an on-call tool, a CLI, or an AI feature that explains errors and names its model — the last point matters to me because I must know which model sees the data. 5 6 7 9

Report an error

The Skeptic

Email notification rules are genuinely configurable — new exception groups, errors becoming unresolved, comments, production-only filtering, daily and weekly digests — and the REST API is thorough, with deploy tracking (repository, revision, version) reachable from CI. Slack appears only in passing and GitHub single sign-on is documented; we found no public information on issue tracker integrations, webhooks, on-call routing, performance alert rules, a CLI or AI features in the captured pages. 5 6 9

Report an error

Data scrubbing, retention & volume control

Show reasoning
How this is scored

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

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

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

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

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

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

Report an error

The Agency Tech Lead

Client-side ignore rules and sampling in the notifier (Ruby, JavaScript, Go, PHP,.NET), breadcrumbs strippable via filter, the reporter IP suppressible per notice, SQL queries and URLs stripped of sensitive information, and usage caps per account and per project that can block errors at the quota instead of on-demand billing give me the volume protection I need when a client's cron job explodes. We found no public information on server-side scrubbing rules for passwords or card numbers, per-project retention configuration (custom retention is only "just email support@airbrake.io"), or a self-hosted edition — a real gap for shops holding customer addresses. 2 4 5 7 8

Report an error

The SaaS CTO

Volume control is the strongest part: usage caps per account and project, quota alerts, a blocking cap option, on-demand overage and client-side sampling to conserve quota are all documented. Scrubbing is thinner — SQL and URLs are stripped automatically and the reporter IP can be suppressed per notice — but I found no public information on configurable scrubbing rules, and retention is a three-month default with custom periods only by email. 4 5 7 8

Report an error

The Mobile Team Lead

Client-side controls are real — ignoring and sampling noisy errors, stripping breadcrumbs, suppressing the reporter IP address, and SQL queries and URLs stripped of sensitive information and normalised before being reported — alongside a default three-month retention for performance data (a custom period by emailing support), per-account and per-project usage caps, quota threshold alerts and on-demand billing beyond the plan quota. We found no public information on configurable server-side scrubbing rules, per-project retention settings, a self-hosted edition, or a chosen data region. 2 4 5 7 8

Report an error

The Site Reliability Engineer

Volume control is well handled: usage caps per account and per project, the quota enforced with a 429 response, on-demand billing for overage, automatic alerts as the quota fills, and notifier-side filtering plus sampling so a noisy error storm does not eat the quota. Data handling is thinner — SQL and URLs are stripped of sensitive information before reporting, the reporter IP can be suppressed per notice and breadcrumbs stripped by filter, with retention stated as 3 months by default and custom periods on request — but we found no public information on configurable scrubbing of passwords or tokens, data export, or deletion of individual records. 4 5 7 8

Report an error

The Data Protection Officer

Volume is well governed: usage caps per account and per project, automatic alerts at quota thresholds, a documented 429 rejection above the monthly quota, an on-demand rate for excess errors, notifier-side sampling and error filters for five languages, and performance data retained 3 months by default with a custom period available by email. For personal data the evidence is thinner — SQL queries and URLs are stripped of sensitive information before reporting, breadcrumbs and the reporter IP can be suppressed — but I found no public information on configurable server-side scrubbing rules, IP anonymisation, request-body opt-out or retention stated per plan, while notices can carry user id, name, email, session and params. 2 4 5 7 8

Report an error

The Skeptic

Volume control is the strong suit: usage caps per account and per project, automatic alerts at quota thresholds, a stated choice between blocking at the cap until the next billing cycle or paying an on-demand rate, notifier-side sampling of noisy errors, filters before events count, and a documented 429 when the quota is hit. On the privacy side, SQL and URLs are stripped and normalized before reporting and the reporter IP can be suppressed per notice, but custom retention for performance data is arranged by emailing support against a three-month default. We found no public information on configurable server-side scrubbing rules, account-level IP anonymisation, or a self-hosted edition. 2 4 5 7 8

Report an error

Access control, security & the vendor's reliability

Show reasoning
How this is scored

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

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

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

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

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

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

Report an error

The Agency Tech Lead

Two-factor authentication is documented better than most — TOTP, recovery codes, account-wide enforcement, admin notification when it is disabled — and encryption in transit and at rest including backups is stated, with GitHub single sign-on alongside. We found no public information on SAML or OIDC single sign-on, SCIM, roles and teams, audit logs, a vendor-held ISO 27001 or SOC 2 certification (the security page cites only the compliance of the AWS facilities), a public status page or an SLA, and that page itself states there is no bug bounty programme. 9 10

Report an error

The SaaS CTO

Two-factor authentication is properly done — TOTP with recovery codes, account-wide enforcement and notification when an admin disables it — and encryption in transit and at rest including backups is stated, with GitHub single sign-on available. The security pages state plainly that there is no bug bounty and no payment for unsolicited disclosures, and I found no public information on the vendor's own certifications, roles, a status page or an SLA. 5 9 10

Report an error

The Mobile Team Lead

Two-factor authentication is documented in depth — TOTP with recovery codes, account-wide enforcement, admin notification when it is turned off — together with GitHub single sign-on with 2FA, encryption in transit and at rest including backups, TLS 1.2/1.3, GDPR compliance with a Data Protection Addendum for EU customers, AWS hosting and a security contact; the vendor also states it maintains no bug bounty programme and does not pay for unsolicited disclosures. We found no public information on project and team roles, SAML or SCIM, audit logs, certifications in the vendor's own name, a public status page, an SLA, or how the notifiers behave during a vendor outage — that last one matters when every release depends on the pipeline. 9 10

Report an error

The Site Reliability Engineer

Two-factor authentication is better documented than most — enforceable account-wide, TOTP with recovery codes, email alerts when an admin disables it — alongside TLS 1.2 and 1.3, encryption at rest including backups, GitHub single sign-on, scoped API keys with time-limited tokens, and a security disclosure address, though the page states outright that there is no bug bounty program and no payment for unsolicited disclosures. We found no public information on SAML or SCIM, audit log export, ISO 27001 or SOC 2 in the vendor's own name, a public status page, an SLA, or how the notifiers behave when Airbrake itself is down — that last gap matters most on call. 5 9 10

Report an error

The Data Protection Officer

Two-factor authentication is handled seriously — TOTP with recovery codes, account-wide enforcement, admin notification when someone disables it, available on all plans — beside encryption in transit and at rest including backups, TLS 1.2 and 1.3, per-user API keys with time-limited tokens, and GitHub single sign-on. I found no public information on organisations and roles, SAML or OIDC single sign-on, audit logs, an SLA, a status page or certifications held by Airbrake itself rather than its AWS facilities, and the security page states plainly that there is no bug bounty and unsolicited disclosures are not paid. 5 9 10

Report an error

The Skeptic

Two-factor authentication is documented better than most — TOTP, recovery codes, account-wide enforcement, and email alerts to other admins if someone disables the requirement — and encryption in transit (TLS 1.2/1.3) and at rest including backups is stated, hosted on AWS. But the security page points at AWS facility certifications rather than naming Airbrake's own audits, and it states plainly that no bug bounty is maintained and unsolicited disclosures are not paid. We found no public information on a status page, an SLA, SAML or OIDC single sign-on, SCIM, audit logs, or how the notifiers behave when the vendor is down. 5 9 10

Report an error

European sovereignty panel opinion

Show reasoning
How this is scored

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

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

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

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

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

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

Report an error

The Agency Tech Lead

The security page names AWS as the hosting provider with no region stated, claims GDPR compliance, and offers a Data Protection Addendum to EU customers on request by email rather than published for self-service conclusion. We found no public information on the contracting entity's jurisdiction, an EU data region the customer can choose, or any subprocessor list, so I could not vouch for this chain to a German client on maintenance. 9

Report an error

The SaaS CTO

Airbrake states GDPR compliance, offers a Data Protection Addendum to EU customers on request by email, and states hosting on AWS without naming a region. The contracting entity, an EU data region and the subprocessors are not documented on the captured pages, so I cannot tell my enterprise customers where their data actually sits. 9

Report an error

The Mobile Team Lead

The captured security page states hosting on Amazon Web Services without naming a region, and offers a Data Protection Addendum only to EU customers and only on request by email. We found no public information on the contracting entity's jurisdiction, an EU data region choice, or any named subprocessors, which is thin comfort for a Hamburg retailer's procurement review. 9

Report an error

The Site Reliability Engineer

Hosting is on Amazon Web Services with no region stated on the captured pages, the contracting entity and subprocessors are not published, and the data processing addendum is offered only to EU customers and only by email request rather than self-service. GDPR compliance is claimed, but we found no public information proving an EU data region or a European chain for events, traces or account data. 9

Report an error

The Data Protection Officer

The only chain fact I can pin down is hosting on Amazon Web Services with no region named; the captured pages give no contracting entity jurisdiction, no subprocessor list, no EU data region and no self-hosted edition. A Data Processing Addendum exists but only on request by email and only for EU customers — for an insurer that needs a signed agreement before the first SDK reaches production, GDPR compliance claimed on an FAQ page is not a chain I can audit. 9

Report an error

The Skeptic

Hosting is named as AWS with no region stated, and the captured pages give no information on the contracting entity's jurisdiction, the subprocessor chain, or an EU data region a customer can choose. A Data Protection Addendum is offered, but only to EU customers and only on request by email — it is not published for self-service conclusion — which is the bare-minimum GDPR posture. Nothing here evidences a European processing chain end to end. 9

Report an error

Pricing transparency not rated — the vendor publishes no price

Show reasoning
How this is scored

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

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

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

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

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

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

Report an error

The Agency Tech Lead

The billing mechanics are public — payment per request rather than per host, a free monthly amount of usage whose size is not stated, plan quotas refilled each billing period with quota usage alerts, and additional errors charged an on-demand rate "based on your selected plan" — but we found no public plan prices, no stated overage rate, and no pricing for retention, seats or add-ons on the captured pages. I could not compute an annual bill for even one small client from this, let alone forty. 4 7

Report an error

The SaaS CTO

The billing model is documented — a monthly error quota with on-demand overage, performance monitoring paid per request rather than per host, a 30-day free trial and a free monthly usage amount. The captured pages show no plan prices and no stated on-demand rate, so I cannot compute an annual cost from what I read. 4 7

Report an error

The Mobile Team Lead

The billing mechanics are public — pay per request rather than per host for performance monitoring, a monthly error quota per plan refilled each billing period, additional errors charged at an on-demand rate "based on your selected plan", a 30-day free trial including all Performance Monitoring usage, and an unspecified free monthly amount — but we found no public information on any actual plan price, per-request rate, seat or project limits, annual versus monthly terms, or VAT. A buyer cannot compute an annual cost from these pages. 4 7

Report an error

The Site Reliability Engineer

The pricing model is public — performance monitoring is billed per request rather than per host, each month includes a free amount of usage, a 30-day trial includes all performance monitoring usage, and errors beyond the quota are charged an "on-demand" rate based on the plan — but we found no public figures for any plan price, the free-usage amount, quota sizes or the on-demand rate, so a real annual cost cannot be computed from public pages alone. 4 7

Report an error

The Data Protection Officer

The commercial model is public — performance monitoring is billed per request rather than per host, each month includes a free amount whose size is not stated, a 30-day trial includes performance usage, and errors above the monthly quota are charged at an on-demand rate based on the selected plan. I found no public prices on the captured pages: no figure for any plan, no quota size per plan, no on-demand rate and no VAT or billing terms, so an annual cost is not computable from what was captured. 4 7

Report an error

The Skeptic

The billing mechanics are explained — pay per request rather than per host, a monthly error quota refilled each billing period, on-demand charging above quota, free usage each month with a 30-day trial — but we found no price figure for any plan in the captured pages, and the on-demand rate is named without a number. As it stands no annual cost is computable from public documentation, and VAT terms, plan-gated features and the price of longer retention are not addressed anywhere captured. 4 7

Report an error

European sovereignty — proven facts

1 of 6 dimensions proven

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

Hosting location Not determined — uncited Report an error
Hosting options Not determined — uncited Report an error
Open source Not determined — uncited Report an error
Data processing agreement On request unverified
Why unverified?

The addendum is offered only to EU customers and must be requested by email; it is not published for self-service conclusion online.

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

Questions about Airbrake

Is Airbrake European?

Not determined: the vendor’s pages as captured do not say where Airbrake is based.

Where does Airbrake store data?

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

Does Airbrake have a free plan?

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

What are the best alternatives to Airbrake?

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: Airbrake alternatives.

Where this could be wrong

What we left out

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

Sources (10)

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

  1. 1 Error capture, grouping & triage — found from sitemap docs.airbrake.io Checked 17 Nov 2026 Details →
  2. 2 Error capture, grouping & triage — found from sitemap docs.airbrake.io Checked 17 Nov 2026 Details →
  3. 3 APM, tracing & profiling — found from sitemap docs.airbrake.io Checked 17 Nov 2026 Details →
  4. 4 APM, tracing & profiling — found from sitemap docs.airbrake.io Checked 17 Nov 2026 Details →
  5. 5 Alerting, integrations & developer workflow — found from sitemap docs.airbrake.io Checked 17 Nov 2026 Details →
  6. 6 Alerting, integrations & developer workflow — found from sitemap docs.airbrake.io Checked 17 Nov 2026 Details →
  7. 7 Data scrubbing, retention & volume control — found from sitemap docs.airbrake.io Checked 17 Nov 2026 Details →
  8. 8 Data scrubbing, retention & volume control — found from sitemap docs.airbrake.io Checked 17 Nov 2026 Details →
  9. 9 Access control, security & the vendor's reliability — found from sitemap docs.airbrake.io Checked 17 Nov 2026 Details →
  10. 10 Access control, security & the vendor's reliability — found from sitemap docs.airbrake.io Checked 17 Nov 2026 Details →