As of 6 Nov 2026, the panel rates AppSignal 3/5 and Honeybadger 3/5 in Error Tracking & APM. Weighted by what each judge cares about, 4 of the 6 judges pick AppSignal and 2 pick Honeybadger. AppSignal scores higher on 3 of 7 criteria (European sovereignty, APM, tracing & profiling and Data scrubbing, retention & volume control). Honeybadger scores higher on 4 of 7 criteria (Access control, security & the vendor's reliability, Alerting, integrations & developer workflow, Pricing transparency, plus 1 more). Provenance — AppSignal: EU-Made; Honeybadger: Rest of world, United States. Ratings are the AI panel’s opinion, formed from public evidence: how scores are made.
The short answer
On weighted totals the benches split: the data protection officer (6.7 vs 6.0), the skeptic (5.8 vs 5.3), the SaaS CTO (5.9 vs 5.8) and the mobile team lead (5.6 vs 5.5) favor AppSignal; the SRE (6.0 vs 5.6) and the agency tech lead (5.7 vs 5.4) favor Honeybadger. The table has AppSignal ahead on sovereignty (7.2 vs 4.0, 6 judges lean its way) — its verdict states data is stored only in ISO-certified facilities in the Netherlands, while Honeybadger is a US LLC with primary data centres in the United States — plus performance tracing (5.8 vs 4.7, 5 leans, 1 tie) and data controls (6.3 vs 6.2, 1 lean, 5 ties). Honeybadger leads workflow and integrations (7.0 vs 6.0, 6 leans), security and reliability (6.8 vs 5.0, 6 leans), pricing transparency (4.7 vs 4.0, 4 leans) and error tracking (6.0 vs 5.5, 3 leans, 3 ties). No overall winner emerges.
Choose AppSignal if
You need application data kept in the Netherlands: AppSignal's verdict states it is stored only in ISO-certified facilities there, and 6 judges lean AppSignal on sovereignty, 7.2 vs 4.0.
You need documented filtering of parameters, sessions and query strings per language before a compliance review: 1 judge leans AppSignal on data controls, 6.3 vs 6.2, with 5 ties.
Your team weights performance tracing heavily in the purchase: 5 judges lean AppSignal, 5.8 vs 4.7, with 1 tie.
You need the data protection officer's sign-off: their weighted total is AppSignal 6.7 vs Honeybadger 6.0.
Choose Honeybadger if
You need alerts routed to Slack, PagerDuty and SMS and issues auto-created in GitHub Issues, Jira, Linear or Shortcut: 6 judges lean Honeybadger on workflow and integrations, 7.0 vs 6.0.
You weigh security and reliability heavily: 6 judges lean Honeybadger, 6.8 vs 5.0, and AppSignal's verdict notes its terms state uptime is not guaranteed.
You need a published price before committing: Honeybadger's Business plan is public at $80/mo, $960/yr and $880/yr, and 4 judges lean Honeybadger on pricing transparency, 4.7 vs 4.0.
You need broad SDK coverage for error tracking: the verdict counts eleven documented SDKs, and 3 judges lean Honeybadger with 3 ties, 6.0 vs 5.5.
Your setup can accept non-EU data residency if an EU region is available: the sovereignty attributes list Honeybadger's data residency as non-EU, and its verdict documents EU storage as a choice, with production on AWS in us-east-1 and eu-central-1 and a Data Processing Addendum with Standard Contractual Clauses in the standard terms.
Read this comparison as one judge. Each weighs the same scores by what they care about.
The Data Protection Officer
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.
AppSignal
This judge's pick
Honeybadger
Criterion by criterion
Error capture, grouping & triage
AppSignal
Exceptions from six platforms (Ruby, Elixir, Node.js, Python, PHP and browser JavaScript) arrive with full backtraces, request metadata, tags and browser breadcrumbs, are grouped into issues with state, severity and assignee, and can be filtered per deploy, revision or new-only with saved views. I found no public information on mobile SDKs, symbolication or source maps, which keeps this below the top band.
Honeybadger
SDKs span Ruby, JavaScript, PHP, Python, Elixir, Java, Go, Cocoa and.NET, with grouping defaults, custom fingerprints and source-map handling documented in the PHP and JavaScript guides, and the tour shows automatic grouping, breadcrumbs, request and environment context, deploy tracking with resolution and return notices, and search with filters. We found no public information on native-mobile symbolication, merging or splitting grouped issues, suspect commits or crash-free session and user rates, which keeps this a step below the top.
APM, tracing & profiling
AppSignal
Transaction timings with 90th percentiles, slow query and N+1 detection, background job monitoring, host metrics and per-minute anomaly triggers are documented, and distributed tracing is built on OpenTelemetry across services, though it is flagged as a beta feature that Elixir and Node.js do not yet support. Sampling is documented as favouring errors and the slowest traces; I found no public information on code-level profiling or configurable sampling rates.
Honeybadger
The product tracks response times, slow queries and background jobs with framework instrumentation for Rails, Django, Flask, Laravel, Phoenix, Sidekiq and others, ingests OpenTelemetry traces, metrics and logs at documented endpoints, and shows host metrics and correlated trace IDs. We found no public information on percentile breakdowns per endpoint, code-level profiling, real user monitoring with Web Vitals, or configurable trace sampling, so it does not reach the upper level.
Alerting, integrations & developer workflow
AppSignal
Alerts go to email, Slack, Teams, PagerDuty and OpsGenie with thresholds at app, namespace, action and job level and routing per trigger; issues go to GitHub, GitLab, Jira, Linear and others, and webhook payloads are signed and verifiable with example code. The tracker integrations are personal per user, and I found no public information on two-way sync, scheduled reports, or an AI explanation feature with a named model — the MCP server only exposes our data to agents I would have to vet myself.
Honeybadger
Alerting includes routing, rate-based escalation and volume anomaly alerts, notifications reach Slack, PagerDuty, SMS and on-call tools, issue trackers (GitHub Issues, Jira, Linear, Shortcut) create and update issues automatically, webhooks are documented with retry, verification token and payload versions, a data API and a CLI exist, and weekly summary emails are offered. The AI assistance runs through the customer's own coding-agent clients such as Claude Code and Codex via an MCP server, and the vendor names no model provider of its own; we found no public information on alerting for two-way status sync beyond the Jira transition options.
Data scrubbing, retention & volume control
AppSignal
Scrubbing is genuinely documented per language: parameter and session-data key filtering with a global off switch, query parameters removed by default, and a server-side header allowlist that strips anything not on it; server-side filtering exists but only for a fixed list (password, password confirmation) that cannot be customised. Retention is stated per plan, traces are deleted on request by email, data can be removed in the app settings and exported via the API, and overages are never billed — a relief when a spike follows an incident. Session data is collected by default for supported frameworks, which I would switch off before any member data flows.
Honeybadger
Passwords, tokens and card numbers are scrubbed by default on the service side, client libraries avoid sending passwords and most environment variables by default, and the PHP guide documents request and environment filtering with configurable keys; error retention is stated per plan (15, 90 or 180 days) and shorter periods are configurable per project, per-project rate limits exist, ignored and discarded events do not count against the quota, an EU storage region is a documented choice, self-hosted deployments are offered on request, and data is exportable via the API. We found no public information on IP address anonymisation, sampling, deletion of individual events or users in the application, or how overage is billed.
Access control, security & the vendor's reliability
AppSignal
ISO 27001 with regular penetration tests, two-factor authentication with team-wide enforcement, encrypted backups, tenant isolation in separate databases, a public status page with incident history, and a DPA signable in the account give me a workable audit basis. The terms state there is no uptime guarantee, however, and I found no public information on single sign-on, SCIM, audit logs or SOC 2, which caps the score.
Honeybadger
Access can be restricted by role, team and per resource, SAML SSO is offered on Business and Enterprise with two-factor authentication and audit logs, encryption in transit and at rest is stated, SOC 2 Type II is claimed with the report on request, vulnerability scans run weekly and penetration tests annually, and the public status page shows incident history, ninety-day uptime at 100 percent for the API and web app, plus operational controls like SSH only via VPN, multi-zone failover and quarterly restore tests. We found no public information on SCIM provisioning, a published SLA with credits, or how the SDKs behave while the vendor is unavailable.
European sovereignty
AppSignal
AppSignal B.V. is an Amsterdam company under Dutch law, application data is stated to be stored only in certified facilities in the Netherlands, and the subprocessors are named — Worldstream for hosting, AWS EMEA for backups, Hetzner for the optional collector — with safeguards stated for any transfer outside the EEA and a DPA signable digitally. No self-hosted edition is offered and the ownership structure is not documented, which keeps it short of a fully sovereign chain; the US region is only announced as coming, so the European chain is the default.
Honeybadger
The contracting entity is a US LLC governed by Washington law with primary data centres in the United States, and no subprocessor list is published — dependencies such as Twilio, Stripe, PagerDuty, Slack, Pusher and Atlassian Statuspage surface only on the status page, which is not the list our data protection review requires. Points in its favour: an EU storage region is a documented choice, production runs on named AWS regions including eu-central-1, and a Data Processing Addendum incorporating the Standard Contractual Clauses is part of the standard terms for EEA customers; with no EU contracting entity or representative and no subprocessor register, this stays below what our procurement could approve.
Pricing transparency
AppSignal
The free plan is priced at €0 with its limits (30K requests, 1GB logging, 5-day retention), overages are never charged, and billing terms, currencies and VAT treatment are stated. The captured pages show no price for any paid plan, and the Business add-ons (the HIPAA agreement, long-term log storage) and the coming US hosting are unpriced, so I cannot compute an annual cost from what was captured.
Honeybadger
The pricing page publishes the Business plan at $80 /mo, $960/yr and $880/yr together with volume limits per tier for errors per month, logging megabytes per day, teams, users, dashboards, alarms, uptime monitors and retention, SSO is tied to named plans, AWS Marketplace billing is offered, and the trial needs no credit card. Overage rates, the price of the single-tenant or self-hosted option, Enterprise pricing and VAT treatment are not covered on the captured pages, so a buyer cannot compute the full annual cost from public pages alone.
Sovereignty, side by side
Dimension
AppSignal
Honeybadger
Legal entity
Not determined
Incorporated in US
Hosting location
EU only
Outside the EU
Hosting options
Not determined
Self-hostable
Open source
Proprietary
Not determined
Data processing agreement
Published, self-serve
Published, self-serve
Transfer impact assessment
Not determined
Not determined
Facts, side by side
Only facts both products carry under the same definition — anything else would not be a fair row.
As of 6 Nov 2026, the panel rates both 3/5. Weighted by what each judge cares about, 4 of the 6 judges pick AppSignal and 2 pick Honeybadger. Which one fits depends on the criteria that matter to you; the table on this page shows both side by side, and each judge’s reading has its own page. Both were scored by the same AI bench under the same rubric, from public evidence only, as the methodology describes.
Is AppSignal or Honeybadger European?
AppSignal is European (EU-Made). Honeybadger is not European by provenance (Rest of world, United States). Provenance is read from each company’s own legal pages: who builds it and who owns it.
Where do AppSignal and Honeybadger store customer data?
Per the vendors’ own pages as captured — AppSignal: In the EU; pages mention Europe. Honeybadger: Outside the EU by default.
Do AppSignal and Honeybadger have a free plan?
As of 6 Nov 2026, AppSignal’s own pages state a free plan; Honeybadger’s pages as captured do not. Each product page links the pricing page it was read from.