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 Site Reliability Engineer
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.
AppSignal
Honeybadger
This judge's pick
Criterion by criterion
Error capture, grouping & triage
AppSignal
Exceptions from Ruby, Elixir, Node.js, Python, PHP and browser JavaScript arrive with full backtraces, grouped by error type, action and namespace, and triaged with states, severity, assignees, deploy-scoped filters and saved views; every occurrence is kept and each issue carries request metadata, tags and host metrics. Breadcrumbs exist only in the beta browser package, and I found no public information on source maps, custom fingerprints, regression detection or any mobile SDK, so a team running Java, Go or mobile clients has no documented error capture.
Honeybadger
Eleven SDKs from Ruby and JavaScript through Java, Go,.NET and Cocoa are listed, with automatic grouping, breadcrumbs, deploy tracking that resolves on ship and re-alerts on regression, issue search with filters and tags, and source maps documented for JavaScript down to webpack, Rollup and esbuild plugins plus custom fingerprints and grouping rules documented for PHP. The gap to the top band is mobile depth: we found no public information on crash-free sessions or users, symbolication, suspect commits, or merging and splitting issues.
APM, tracing & profiling
AppSignal
Performance comes with averages and 90th percentiles, slow-query and N+1 detection, background job monitoring, host metrics per sample, memory allocation tracking and anomaly triggers on error rates, throughput, slow actions, queue time and host metrics; traces are built on OpenTelemetry, sampled with a documented bias toward errors and the slowest requests, and errors are tightly coupled to their traces with a service map and timeline. The documentation states distributed tracing is a beta Labs feature needing the hosted collector and that Elixir and Node.js are not supported yet, and I found no public information on code-level profiling or Core Web Vitals.
Honeybadger
Their "Just Enough APM" tracks response times, slow queries and background jobs with framework integrations for Rails, Sidekiq, Celery, Laravel, Phoenix and more, OpenTelemetry ingestion of traces, metrics and logs is documented with endpoints and authentication, and host metrics and correlated trace IDs are shown. We found no public information on percentile breakdowns per endpoint, N+1 detection, code-level profiling, or real user monitoring with Web Vitals.
Alerting, integrations & developer workflow
AppSignal
Alerts route to PagerDuty, documented down to the Events API v2 key, a test hook and notification on both errors and performance issues, plus Slack, Teams, Discord, Opsgenie, Squadcast and signed webhooks with SHA-256 verification examples in four languages; issues flow to GitHub, GitLab, Jira, Linear, Asana, Trello and Shortcut, and there is a documented JSON API, a CLI and an MCP server that lets coding agents read incident lists. Alert routing is per trigger rather than per team, and I found no public information on two-way issue tracker sync, commit and source links, scheduled reports or AI explanations of errors with a named model.
Honeybadger
Errors reach the right people: real-time alerts to Slack and PagerDuty with advanced alert routing, rate-based escalation and a documented "won't alert again until resolved" noise control, GitHub Issues, Jira, Linear and Shortcut integrations that automatically create and update issues, a documented Data API, and webhooks with retry, token verification and versioned payloads, plus weekly summary emails and a coding-agent plugin (Claude Code, Codex, any MCP client) that queries and drafts fixes. Held below the top band because alerting on performance thresholds and a CLI for releases and source maps are only partly evidenced, and the AI features' data handling is not described.
Data scrubbing, retention & volume control
AppSignal
Every integration filters parameters by configurable key lists, the server-side processor scrubs password and password confirmation by default, session data and headers are covered by a denylist and a default header allowlist, and traces are retained 30, 45 or 60 days depending on plan with deletion in app settings and trace removal on request. Volume surprises are handled well for an on-call team — monitoring never stops at the limit, overages are never charged, spike forgiveness is claimed and a 30-day review precedes any upgrade — but the server-side filter list is fixed rather than customizable, and I found no public information on rate limits or per-project retention settings.
Honeybadger
Passwords, tokens and card numbers are scrubbed by default, the PHP SDK documents an environment key whitelist and configurable request filtering, retention is public per plan (15/90/180 days) with configurable per-project retention limits, and per-project rate limits mean discarded or ignored events do not count against the quota, with a Data API for export. We found no public information on IP address anonymisation, sampling of errors, or how overage at the quota cap is billed.
Access control, security & the vendor's reliability
AppSignal
The vendor publishes ISO 27001 certification with aligned penetration tests, 2FA enforcement, a bug bounty, encrypted backups, SSL transport, a public status page with incident history and monitored components, a signable DPA and a HIPAA BAA. The terms state plainly that uptime is not guaranteed and cap liability at EUR 100.00 per event and EUR 1,000.00 in aggregate, and I found no public information on single sign-on, SCIM, audit logs or how the SDK behaves when ingestion is unavailable.
Honeybadger
SAML single sign-on ships on Business and Enterprise (Okta, OneLogin, Google), access can be restricted by role, team or resource, an audit log of user activity is provided, data is AES-encrypted at rest and TLS in transit, SOC 2 Type 2 is stated with the report on request, and the public Atlassian Statuspage shows per-component 90-day uptime including dependencies like the PagerDuty events APIs, Twilio and Stripe. SLAs are offered as custom enterprise options rather than published with credits, and we found no public information on SCIM provisioning or on SDK behaviour when the vendor itself is down.
European sovereignty
AppSignal
AppSignal B.V. is an Amsterdam company with Dutch Chamber of Commerce number 62960407, contracting under Dutch law, and application data is stored in ISO-certified facilities in the Netherlands, with hosting and backup through named parties including Worldstream and Amazon Web Services EMEA and an optional Hetzner-hosted collector; a DPA can be signed digitally and non-EEA transfers carry stated safeguards. Subprocessor locations are implied by entity names rather than stated, I found no public information on SOC 2, and the US region appears only as coming soon on the captured hosting page, which holds this below the top level.
Honeybadger
The contracting entity is a US LLC under Washington law with primary data centres in the United States, but customers can choose to store data in the European Union, production runs on named AWS infrastructure in eu-central-1, and a Data Processing Addendum with Standard Contractual Clauses forms part of the standard terms. We found no published subprocessor list and no EU contracting entity or representative, so only the storage leg of the chain is European.
Pricing transparency
AppSignal
The free plan is public at €0 with 30K requests, 1GB logging and 5-day retention, all plans include unlimited users, teams, applications and dashboards, overage charges never apply, a 30-day usage review precedes any forced upgrade, prices are exclusive of VAT, and billing is monthly or yearly in EUR or USD. I found no public information on what any paid plan costs or what request volume each covers, and add-ons such as the HIPAA agreement and long-term log storage are unpriced, so the annual cost of a production workload cannot be computed from public pages.
Honeybadger
The Business plan is priced publicly at $80 /mo, $960/yr or $880/yr with per-plan quotas for errors per month, daily ingest MB, users, teams, uptime monitors, dashboards, alarms and retention, and the annual-versus-monthly difference is visible, while single sign-on requires Business or Enterprise and Jira and webhooks gate to Team and above. We found no public information on the Team and Developer plan prices or per-unit overage costs, high-volume, self-hosted and custom SLA options are "ask us", and VAT is not stated.
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.