Honeybadger
Rest of world Report an errorPanel rating · 6 judges · How to read the stars
Category median
Sovereignty: 4 of 6 dimensions proven
0–5 in half steps. 5 means the rubric's top anchor is met on the evidence.
by Honeybadger Industries LLC · www.honeybadger.io
Compare with AppSignal → Report an error on this page Is this your product? →
Link to this page
Add ?theme=dark to the image address for dark backgrounds.
The badge shows the category and the month of the latest evaluation, and EU-Made where
that is the product’s provenance. It never shows a score.
Honeybadger at a glance
- Vendor
- Honeybadger Industries LLC
- Headquarters
- Incorporated in the United States source, captured 6 Nov 2026
- Data hosting
- Outside the EU by default source, captured 6 Nov 2026
- Free plan
- Not stated on the vendor’s pages as of 6 Nov 2026
- Panel verdict
- The AI panel rates Honeybadger 3/5, the mean of 6 judges. Honeybadger Industries LLC sells error tracking with logging, uptime and status pages. how scores are made
- As of
- Vendor pages captured 6 Nov 2026; evaluated by the panel 6 Nov 2026. all sources
Read this page as one judge. Each weighs the same scores by what they care about.
The panel's verdict
Honeybadger Industries LLC sells error tracking with logging, uptime and status pages. Workflow and integrations scored 7, the table's highest — alerts to Slack, PagerDuty and SMS, automatic issue creation in GitHub Issues, Jira, Linear and Shortcut, webhooks documented down to retries — and error tracking clustered at 6 on eleven documented SDKs. Weakest is sovereignty, flat at 4: a US LLC governed by Washington law, primary data centres in the United States, and no public information on a subprocessor list or an EU representative, though EU storage is a documented choice, production runs on AWS in us-east-1 and eu-central-1, and a Data Processing Addendum with Standard Contractual Clauses is part of the standard terms. Performance tracing and pricing transparency each split between 4 and 5 — the skeptic and the mobile team lead at the low end — over missing endpoint percentiles, profiling and real user monitoring, and over only the Business plan at $80/mo, $960/yr and $880/yr being publicly priced. Security and reliability and data controls varied by a single point. The flagged splits flagged none.
Speaks for it
- Workflow and integrations scored 7, the highest number awarded, with Slack, PagerDuty and SMS alerts, rate-based escalation and automatic issue creation in GitHub Issues, Jira, Linear and Shortcut.
- Error tracking scores cluster at 6 on eleven documented SDKs with automatic grouping, custom fingerprints, deploy resolution and regression re-alerting.
- Security and reliability scored 6 to 7 on SOC 2 Type 2 with the report on request, a BAA, SAML SSO on Business and Enterprise, and a public status page showing 100 percent API uptime over 90 days.
- Passwords, tokens and credit cards are scrubbed by default, per-plan retention is published at 15, 90 and 180 days, and discarded errors do not count against the quota.
- The Business plan is priced publicly at $80/mo, $960/yr and $880/yr with volume limits from 5,000 to 50,000 errors per month and a free trial the vendor says needs no credit card.
Held against it
- Sovereignty sat flat at 4: a US LLC under Washington law, primary data centres in the United States, and we found no public information on a subprocessor list or an EU representative.
- Performance tracing scored 4 to 5, with no public information on percentiles per endpoint, code-level profiling, real user monitoring or Web Vitals.
- Pricing transparency scored 4 to 5, as only the Business plan price was captured, with no public information on Developer and Team prices, overage rates or VAT.
- The SDK list shows only Cocoa on the mobile side, with no public information on Android, Flutter or React Native, native symbolication, or crash-free users and sessions.
- We found no public information on SCIM provisioning, a published SLA with credits, or deletion of individual events.
Best for
- You run a web or backend stack in a documented SDK language such as Ruby, PHP, Python, Go or Elixir and want grouped errors tied to deploys with Slack or PagerDuty alerting.
- You already emit OpenTelemetry signals and want traces, metrics and logs ingested over OTLP alongside error tracking.
- Your security review requires SOC 2 Type 2, a BAA and SAML SSO on Business and Enterprise, and a US contracting entity is acceptable.
- Your team uses coding agents such as Claude Code or Codex and wants them querying errors read-only next to the code.
Avoid if
- You need EU procurement approval — the contracting entity is a US LLC under Washington law and we found no public information on a subprocessor list or an EU representative.
- You need full APM depth — the captured pages do not document percentiles per endpoint, code-level profiling or real user monitoring, and the bench scored performance tracing 4 to 5.
- You ship native mobile apps for Android, Flutter or React Native — ask the vendor: the public pages we read do not show it
- You must compute a full annual cost from published prices before committing — only the Business plan price was captured, and overage rates and VAT are not public.
The scores
| Criterion | Panel median |
|---|---|
| Error capture, grouping & triage | 3 of 5 |
| APM, tracing & profiling | 2.5 of 5 |
| Alerting, integrations & developer workflow | 3.5 of 5 |
| Data scrubbing, retention & volume control | 3 of 5 |
| Access control, security & the vendor's reliability | 3.5 of 5 |
| European sovereignty | 2 of 5 |
| Pricing transparency | 2.5 of 5 |
Error capture, grouping & triage
Show reasoningHide reasoning
How this is scored
What happens to an exception or crash: SDKs for the languages, frameworks and platforms a team runs (PHP and Laravel, JavaScript in the browser and Node, Python, Ruby, Java, .NET, Go, iOS, Android, Flutter, React Native), stack traces with source maps and symbolication, context (request, user, breadcrumbs, environment, local variables), grouping and custom fingerprints, deduplication, issue states (resolved, ignored, regressed), releases and deploy tracking, suspect commits, crash-free sessions and users for mobile apps, and search and filters over issues.
0 — Catches no application errors or crashes; a log viewer or an external check only.
3 — Errors from one or two platforms arrive with a stack trace and are grouped; context, issue states, releases and source maps are basic or not described.
5 — SDKs for the common web and backend platforms, stack traces with source maps, request and user context and breadcrumbs, automatic grouping with issue states and regression detection, release and deploy tracking, and issue search and filters.
8 — SDKs across backend, frontend and mobile with symbolication documented, custom fingerprinting and merge or split of issues, suspect commits or code owners, crash-free users and sessions, local variables or source context per frame, and every SDK documented with its configuration options.
10 — Error tracking a large engineering organisation standardises on: every platform it runs covered with parity stated, grouping rules editable and explained, release health with adoption and regression per version, and the full issue lifecycle reachable by API.
The Agency Tech Lead
The PHP side our Laravel and Shopware clients run on is documented in depth: the PHP library filters request keys like password by default, supports custom fingerprints, and lets grouping be changed by error class, component or stack trace, while JavaScript source maps have upload plugins for webpack, Rollup, esbuild and GitHub Actions. Client libraries are listed for Ruby, JavaScript, PHP, Python, Elixir, Java, Go, Cocoa,.NET/C#, Crystal and Clojure, with breadcrumbs, deploy tracking, ignore states and cross-project search described. We found no public information on mobile symbolication, crash-free users and sessions, suspect commits, or local variables per frame, which keeps this mid-scale. 2 5 13 14 18
The SaaS CTO
SDKs cover every language we run — Go, Python, JavaScript — plus Java, PHP, Elixir, Cocoa and more, with documented source maps, custom fingerprints and separating application frames from vendor code. I found no public information on issue merge and split, suspect commits, crash-free sessions, or mobile beyond Cocoa, so it sits above the basics but short of what a large organisation standardises on. 2 5 13 14
The Mobile Team Lead
Grouping is genuinely documented — default grouping on file, class and component, with custom fingerprints and ignored states, plus breadcrumbs, request context, backtraces linked to source, deploy tracking that resolves errors when we ship the fix and alerts if they return, and search across projects. The SDK list covers web and backend well but shows only Cocoa on the mobile side; we found no public information on Android, Flutter or React Native SDKs, native symbolication, or crash-free users and sessions per release, which is exactly what I need to stop a bad store rollout. 2 5 13 14
The Site Reliability Engineer
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. 2 5 13 14 18
The Data Protection Officer
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. 2 5 13 14
The Skeptic
SDKs are documented for Ruby, JavaScript, PHP, Python, Elixir, Java, Go, Cocoa,.NET/C#, Crystal and Clojure, with source-map upload plugins, revision matching and automatic source-code linking for JavaScript. Grouping is documented down to its defaults (file, method, line, class, component) with custom fingerprints, deploys resolve errors and regressions alert again, and there are breadcrumbs, tags and cross-project search. We found no public information on suspect commits, crash-free sessions and users, or mobile symbolication, which is what separates the top tier. 2 5 13 14
APM, tracing & profiling
Show reasoningHide reasoning
How this is scored
How the product shows where time goes: transaction and endpoint timings with percentiles, slow database queries and N+1 detection, background jobs and queues, external HTTP calls, distributed tracing across services, OpenTelemetry ingestion, code-level profiling, frontend performance and Core Web Vitals (real user monitoring), host or container metrics beside the traces, anomaly detection on throughput and latency, and the link from a slow trace to the error it caused.
0 — No performance data of any kind; errors only.
3 — Response times per endpoint or a simple performance view; tracing across services, query analysis and profiling are basic or not described.
5 — Transaction timings with percentiles per endpoint, slow query and N+1 detection, background job monitoring, distributed tracing across services, a link between traces and errors, and frontend performance or Web Vitals offered.
8 — OpenTelemetry ingestion documented, code-level or continuous profiling, real user monitoring with Web Vitals, host and container metrics beside the traces, anomaly detection on latency and throughput, and sampling of traces configurable with its effect explained.
10 — Full application performance management evidenced: traces, profiles, frontend and backend joined end to end, service maps, SLOs on endpoints, and every signal documented with its retention and sampling per plan.
The Agency Tech Lead
Their 'Just Enough APM' tracks response times, slow queries and background jobs, with framework instrumentation listed for Laravel, Rails, Sidekiq, Solid Queue, Celery and more, and OpenTelemetry traces, metrics and logs can be ingested directly over OTLP with documented endpoints and authentication. Host metrics are supported, a correlated trace ID follows a request's lifecycle, and alarms can be built on any query in their query language. We found no public information on percentiles per endpoint, N+1 detection, code-level profiling, real-user monitoring or Core Web Vitals, so I could not promise a client we will catch their slow shop page before they call. 2 3 5 15
The SaaS CTO
Response times, slow queries and background job monitoring are documented, and — the part that decides it for me — traces, metrics and logs are ingested directly over the OpenTelemetry Protocol, so our instrumentation stays portable, with a correlated trace ID joining events across a request. I found no public information on percentiles per endpoint, real user monitoring with Web Vitals, code-level profiling, or configurable trace sampling, so I cannot call this full APM. 2 3 5 15
The Mobile Team Lead
Response times, slow queries and background-job latency are tracked with dashboards, host metrics are offered, OpenTelemetry traces, metrics and logs are ingested via documented endpoints, and a correlated trace ID ties events to a request. We found no public information on percentiles per endpoint, code-level profiling, real-user monitoring or Web Vitals, so this is enough APM rather than full tracing. 2 3 5 15
The Site Reliability Engineer
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. 2 3 5 15
The Data Protection Officer
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. 2 3 5 15
The Skeptic
The product calls it Just Enough APM and that is honest: response times, slow queries and background jobs are tracked for Rails, Sidekiq, Celery, Oban, Laravel and company, and OpenTelemetry traces, metrics and logs are ingested over OTLP and queried with correlated trace IDs. But we found no public information on percentiles per endpoint, N+1 detection, code-level profiling, Web Vitals or real user monitoring, or how trace sampling is configured. 2 3 5 15
Alerting, integrations & developer workflow
Show reasoningHide reasoning
How this is scored
How an error reaches the person who fixes it: alert rules on new issues, regressions, frequency and performance thresholds, notifications to email, Slack, Microsoft Teams, PagerDuty or Opsgenie, issue tracker integrations (Jira, GitHub, GitLab, Linear) that create and sync issues, source code links to the repository, deploy and release hooks from CI, a documented REST API and webhooks, a CLI, AI features that explain an error or suggest a fix (and which model runs them), and digest or weekly reports.
0 — No notifications and no integrations; errors are only visible by logging in.
3 — Email or chat notifications for new errors and one or two integrations; alert rules, the issue tracker link and the API are basic or not described.
5 — Configurable alert rules for new, regressed and frequent errors, Slack and email and an on-call tool, issue tracker integrations with GitHub, GitLab or Jira, deploy tracking from CI, a documented REST API and webhooks.
8 — Two-way sync with issue trackers, source code and commit links, alerts on performance thresholds and anomalies with routing per team or project, a CLI for releases and source maps, AI explanations or fix suggestions with the model provider named, and scheduled reports.
10 — A workflow a large team runs on: ownership rules routing issues to teams, every setting reachable by API or infrastructure as code, alert noise controls documented, and every AI feature documented with its data handling and an opt-out.
The Agency Tech Lead
Alerting goes well beyond email: plan-level alarm counts with advanced alert routing and rate-based escalation, notifications across Slack, PagerDuty, SMS and more, and errors automatically create and update issues in GitHub Issues, Jira, Linear or Shortcut; webhooks are documented down to retries, timeouts and a verification header, and the Data API covers faults, projects, teams and deployments. The coding-agent plugin works with Claude Code, Codex or any MCP client, starts read-only, and can draft a fix next to the code — a genuine workflow for fourteen developers. Two gaps hold it back: we found no public information on full two-way issue-tracker sync, and the AI assistance runs through the customer's own coding agent rather than a vendor-run model we could see documented. 1 2 4 6 7 17
The SaaS CTO
Slack and PagerDuty plus on-call tools, Jira in two variants with OAuth and Linear and GitHub issues created and updated automatically, webhooks with documented payload versions and retry semantics, a REST API with a v3 preview, weekly summary emails, and an MCP server for coding agents — close to the workflow my team would run on. I found no public information on ownership routing per team or alerts on performance thresholds, which is what would take it further. 1 2 4 6 17
The Mobile Team Lead
Alerts reach the team in Slack, PagerDuty and SMS with configurable alarms, advanced alert routing, rate-based escalation and weekly summary emails, issues auto-create and update in GitHub, Jira, Linear or Shortcut, webhooks are documented down to retries and a verification token, and a REST API plus a coding-agent integration are public. Two-way tracker sync is not described in the captured pages, and I found no release-health alerting that would tell me a new version crashes more than the last. 2 3 4 6 7 16 17
The Site Reliability Engineer
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. 1 2 4 6 7 16 17
The Data Protection Officer
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. 1 2 3 4 16 17
The Skeptic
Alerts route to Slack, PagerDuty, SMS and webhooks with rate-based escalation, per-project alarm counts and alarms built from any query; GitHub Issues, Jira, Linear and Shortcut create and update issues automatically; and the data API and webhooks are documented down to retry, disable-on-failure and a verification token. The coding-agent integration is read-only by default and names the clients it works with, and weekly summaries arrive by email. What we did not find documented is full two-way tracker sync, or a command-line tool for releases and source maps beyond the install command. 2 3 4 6 16 17
Data scrubbing, retention & volume control
Show reasoningHide reasoning
How this is scored
What the product does with the personal and secret data an error carries and how volume is kept in check: scrubbing of passwords, tokens, card numbers and personal data in the SDK and on the server with configurable rules, IP address anonymisation, opting out of request bodies and user data, data retention per plan and deletion on request, sampling of errors and traces, rate limits, spike protection and quota caps per project, filters that drop events before they count, data export, and a self-hosted edition that keeps every event on the customer's own servers.
0 — No control over what is captured, no retention period stated, no limit on volume.
3 — Some default filtering of passwords and a retention period stated for one plan; server-side scrubbing, sampling and spike protection are basic or not described.
5 — Configurable data scrubbing in the SDK and default server-side scrubbing of common secrets, IP anonymisation, retention stated per plan, sampling and rate limits per project, a quota cap or spike protection, and event filters before ingestion.
8 — Custom server-side scrubbing rules with examples, per-project retention settings and deletion of individual events or users, spike protection documented with how overage is billed, data export by API, and a self-hosted edition or a documented option to keep data in the customer's chosen region.
10 — Data minimisation by design and evidenced: personal data off by default in every SDK, scrubbing rules auditable, retention and deletion controllable per data type, volume controls that never surprise the invoice, and a supported self-hosted edition with feature parity stated.
The Agency Tech Lead
For shops holding customer addresses this is workable: request keys like password are filtered by default in the PHP library with configurable filtering and an environment-key whitelist, sensitive data such as passwords, tokens and card numbers is scrubbed by default on the service, and retention is stated per plan — 15, 90 or 180 days — with shorter per-project periods configurable. Per-project rate limits exist, and ignored or discarded errors do not count against the quota, which directly answers my fear of a cron job throwing a million duplicates. We found no public information on IP anonymisation, sampling, spike protection with its overage billing, or deletion of individual events. 7 8 18 19 21
The SaaS CTO
Passwords, tokens and card numbers are scrubbed by default, the PHP SDK documents request and environment filters with examples, retention is stated per plan and configurable per project, and discarded events do not count against the quota. I found no public information on IP anonymisation, sampling, deletion of individual events, or how overage at the quota is billed, which keeps this at solid rather than enterprise-grade. 7 8 18 19 21
The Mobile Team Lead
Passwords, tokens and card numbers are scrubbed by default on the server, the client libraries filter request and environment keys with documented configuration, retention is stated per plan at 15, 90 and 180 days and configurable per project, and discarded or ignored events never count against quota, with per-project rate limits capping volume. We found no public information on sampling, IP anonymisation, custom server-side scrubbing rules, overage billing, or deletion of individual events. 7 8 18 19 21
The Site Reliability Engineer
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. 7 8 18 19 21
The Data Protection Officer
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. 6 7 8 18 19 21
The Skeptic
Passwords, tokens and credit cards are scrubbed by default on the server, the PHP library documents environment whitelisting and request filtering with examples, and retention is stated per plan at 15, 90 and 180 days with per-project limits and shorter periods configurable. Per-project rate limits exist, discarded errors do not count against the quota, and data can be exported by API or archived to S3. What no captured page answers is what happens when the quota is hit — cap, spike protection or a bill — nor sampling, IP anonymisation, or deletion of a single event. 6 7 8 18 19 21
Access control, security & the vendor's reliability
Show reasoningHide reasoning
How this is scored
Whether the service holds up in an audit and on the vendor's own bad day: organisations, teams and projects with roles, single sign-on (SAML or OIDC) and SCIM, two-factor authentication, audit logs, encryption in transit and at rest, security certifications and reports (ISO 27001, SOC 2), a security page and a vulnerability disclosure policy, the vendor's own public status page and incident history, a stated availability or SLA, and how ingestion behaves when the vendor is down (SDK buffering, no impact on the app).
0 — Nothing on access control, security or the vendor's own availability.
3 — User accounts with two-factor authentication and a security page; roles, SSO, certifications and a status page are basic or not described.
5 — Organisations and projects with roles, two-factor authentication, single sign-on offered on some plan, encryption in transit and at rest stated, a public status page, and a security page naming certifications or audits.
8 — SAML SSO and SCIM provisioning, audit logs, ISO 27001 or SOC 2 with its scope stated, an SLA with credits published, the incident history public, a vulnerability disclosure or bug bounty programme, and SDK behaviour during vendor outages documented.
10 — Enterprise-grade operation evidenced: granular roles per project and team, audit logs exportable to a SIEM, independent audit reports available on request, published uptime history over years, and ingestion designed and documented never to slow the customer's application.
The Agency Tech Lead
Access can be restricted by user role, team membership or per resource, two-factor authentication is available, SAML single sign-on comes with Business and Enterprise, audit controls log user activity, SOC 2 Type 2 is certified with the report available on request, encryption in transit and at rest is stated, and the public status page shows component-level status with 90-day uptime and incident history. Weekly vulnerability scans, annual pen tests and a detailed security-policies page back this up. We found no public information on SCIM provisioning, a published SLA with credits, or documented SDK behaviour during a vendor outage. 7 8 9 20 21
The SaaS CTO
SOC 2 Type 2 with the report on request, HIPAA with a BAA, SAML SSO on Business and Enterprise, audit logs, role- and resource-level access, encryption in transit and at rest, and a public status page showing 100 percent API uptime over the past 90 days — this would survive a customer audit. The gaps I would probe: I found no public information on SCIM provisioning, on a published SLA with credits (SLAs are offered as custom, on request), or on how the SDKs behave when the vendor itself is down. 7 8 9 20 21
The Mobile Team Lead
Role-based access by team and per resource, SAML SSO with Okta, OneLogin or Google, two-factor authentication and an audit log are documented alongside SOC 2 Type II with the report available on request, AES at rest, TLS in transit, weekly vulnerability scans and a public status page showing 100% API uptime over 90 days. SCIM provisioning, a published SLA with credits and documented SDK behaviour during a vendor outage are not described in the captured pages. 7 8 9 20 21
The Site Reliability Engineer
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. 7 8 9 20 21
The Data Protection Officer
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. 7 8 9 20 21
The Skeptic
Access is restricted by role, team membership or per resource, two-factor authentication and SAML single sign-on on the Business and Enterprise plans (Okta, OneLogin, Google) are documented, and an audit log of user activity, AES at rest, TLS in transit and SOC 2 Type II with the report on request are stated. The status page is public with 90-day uptime and incident history, and the vendor documents its own redundancy, backup restore tests and on-call rotation. We found no public information on SCIM provisioning, a published SLA, the SOC 2 scope, or what the SDK does when the vendor is down. 7 8 9 20 21
European sovereignty
panel opinion
Show reasoningHide reasoning
How this is scored
Who the contracting entity and the parent company are, where error events, stack traces, request data, traces, profiles, session data and account data are stored and processed, and who the subprocessors are (hosting, email and chat delivery, AI models that explain errors, support and payment tools). Independently sourced by the sovereignty pipeline. An EU data region the customer can choose counts for the product; a US default without a stated EU option does not. A self-hosted edition the customer runs on its own European servers counts as the customer's chain, whatever the vendor's seat.
0 — Non-EU vendor and contracting entity, hosting unstated, subprocessors unnamed, and no data processing agreement offered.
3 — A privacy policy and a data processing agreement exist, but hosting location is unstated or non-EU and the subprocessors are not listed.
5 — An EU data region available and an EU contracting entity or EU representative, but parts of the chain (AI features, email, support, payment) run through non-EU providers without a stated safeguard.
8 — EU hosting on named infrastructure, EU contracting entity, subprocessors listed with their locations, a data processing agreement published, and security certifications (ISO 27001, SOC 2) stated — or a self-hosted edition documented that keeps every event on the customer's own servers.
10 — Sovereign end to end and evidenced: European ownership, entity, hosting and every subprocessor including the AI models, or a self-hosted edition with no call home, data export and deletion documented, and certifications published with their scope rather than implied.
The Agency Tech Lead
Customers can choose to store their data in the European Union, production infrastructure runs in AWS eu-central-1 as well as us-east-1, and the Data Processing Addendum is part of the standard terms and incorporates the Standard Contractual Clauses — a combination I can defend to a German client. But the contracting entity is Honeybadger Industries LLC governed by the law of the State of Washington, and we found no public information on a subprocessor list with locations or an EU representative. Single-tenant or self-hosted deployments are only mentioned as something to ask about, not documented as an edition I could run on our own servers. 8 11 12 21
The SaaS CTO
An EU storage region is documented — customers can choose to store data in the European Union — production runs in AWS eu-central-1 alongside us-east-1, and the Data Processing Addendum with Standard Contractual Clauses is part of the standard terms, which answers the question my enterprise customers ask. But the contracting entity is a US LLC under Washington law with US primary data centres as the default, and I found no public information on subprocessors and their locations beyond the Twilio, Stripe, PagerDuty and Slack dependencies visible on the status page. 8 9 11 12 21
The Mobile Team Lead
A European data region is a documented choice, production infrastructure runs in AWS eu-central-1 as well as us-east-1, and a Data Processing Addendum incorporating Standard Contractual Clauses is part of the standard terms for customers in the EEA. The contracting entity is a US LLC under Washington law with no EU representative shown, however, and no subprocessor list is published — Twilio and Stripe appear only as dependencies on the status page. 8 11 12 21
The Site Reliability Engineer
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. 8 11 12 21
The Data Protection Officer
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. 8 9 11 12 21
The Skeptic
The contracting entity is Honeybadger Industries LLC, governed by Washington law, with primary data centres in the United States — but customers can choose European Union storage, production runs on AWS in us-east-1 and eu-central-1, and a Data Processing Addendum incorporating the Standard Contractual Clauses is part of the standard terms for EEA customers. No EU entity or representative is named, and no subprocessor list with locations is published, so the chain beyond AWS cannot be verified. 7 8 11 12 21
Pricing transparency
Show reasoningHide reasoning
How this is scored
Whether a buyer can compute the real annual cost from public pages alone: price per plan, what is included (errors or events, spans or transactions, replays, profiles, logs, seats, projects, retention), what overage costs per unit and whether it is capped, which features (SSO, audit logs, longer retention, EU region, AI) need a higher plan, host or seat based pricing for suites, the price of the self-hosted edition, annual versus monthly terms, and VAT.
0 — No public prices at all; every customer is a sales call.
3 — A starting price exists, but what volume it covers and what overage, retention and add-ons cost is unclear.
5 — Plans are public with their price and main volume limits, but at least one commonly needed piece (overage per event or span, longer retention, SSO, the EU region or AI features) is unpriced or "contact sales".
8 — Every plan priced publicly with its volume limits and overage rates, a price calculator or table per unit, add-ons and retention priced, the behaviour at the quota (cap or overage) stated, and VAT and billing terms stated.
10 — Complete price computability: annual cost derivable for a given volume of errors, traces, seats and projects, with every add-on, retention step, support level and the self-hosted licence priced and the cancellation terms published.
The Agency Tech Lead
The plans page shows the Business plan at '$80 /mo $960/yr $880/yr' with volume limits per tier — 5,000 or 50,000 errors a month, retention of 15, 90 or 180 days, and stated alarm, dashboard, team, user and project counts — and it says discarded data does not count against the usage quota. We found no public information on the price of the other tiers, on overage rates or whether the quota caps or bills over, on VAT, or on the cost of single-tenant or self-hosted deployments. So for a maintenance client I cannot compute the real annual cost from the captured pages alone, which is the number my invoice review needs. 7 11 19
The SaaS CTO
The plans page publishes volume limits per tier — errors per month, logging megabytes per day, retention days, uptime monitors, dashboards — and prices the Business plan at $80/mo, $960/yr, $880/yr, with SAML SSO included in Business and Enterprise and discarded data free. Overage pricing, VAT, the cost of the EU region, and the Enterprise and self-hosted options are unpriced or available only on request, so I cannot compute a real annual bill from public pages alone. 7 19 20
The Mobile Team Lead
The Business plan is shown at $80/mo, $960/yr and $880/yr with error, logging, retention and alarm limits per tier, unlimited projects and users, and a no-credit-card trial, and discarded data never counts toward the quota. Only the Business price is captured, though; overage per event and behaviour at the quota are unpriced, self-hosted and single-tenant deployments are ask-us, and VAT and billing terms are not stated. 2 7 19
The Site Reliability Engineer
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. 7 16 17 19 20
The Data Protection Officer
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. 7 19 20
The Skeptic
The captured pricing page shows the Business plan at $80 /mo, $960/yr, $880/yr, with unusually clear volume limits per tier (5,000 to 50,000 errors per month, 50 to 100 MB per day of logging, retention of 15, 90 or 180 days) and the annual discount visible. But the prices for the Developer and Team tiers were not captured, and no page states what overage costs, whether the quota caps or bills, what single-tenant or self-hosted deployment costs, or how VAT is handled — Enterprise is an ask-us conversation. 7 19 20
European sovereignty — proven facts
4 of 6 dimensions provenBuilt only from facts shown on the vendor's own pages. A dimension we could not prove is left open, not scored as zero.
| Legal entity |
Incorporated in US
unverified
Why unverified?The terms state the service is administered from US offices, but no page names a state of incorporation or a company register entry. |
0/2 pts | 11 Report an error |
|---|---|---|---|
| Hosting location |
Outside the EU
unverified
Why unverified?US is only the default; the security page's multi-region hosting lets customers choose EU storage instead, and infrastructure also runs in AWS eu-central-1. |
0/4 pts | 12 Report an error |
| Hosting options |
Self-hostable
unverified
Why unverified?Self-hosting appears only as a "talk to sales" item with no deployment details, and the security page separately offers selectable EU hosting ("Multi-region hosting"). |
1/1 pts | 7 Report an error |
| Open source | Not determined | — | uncited Report an error |
| Data processing agreement |
Published, self-serve
unverified
Why unverified?The DPA document itself is not reproduced in these excerpts; it is only referenced as incorporated into the standard terms. |
1/1 pts | 21 Report an error |
| Transfer impact assessment | Not determined | — | uncited Report an error |
Questions about Honeybadger
Is Honeybadger European?
No. whats-best.ai classifies Honeybadger as Rest of world. Its vendor, Honeybadger Industries LLC, is incorporated in the United States, per the vendor’s page captured 6 Nov 2026.
Where does Honeybadger store data?
Honeybadger stores customer data outside the EU by default, per the vendor’s page captured 6 Nov 2026.
Does Honeybadger have a free plan?
Not stated on the vendor’s pages as of 6 Nov 2026.
What are the best alternatives to Honeybadger?
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: Honeybadger alternatives.
Where this could be wrong
- Evidence ages. The oldest capture behind this page is from 6 Nov 2026. Vendors change pricing and policies without notice; every fact reflects its source as of the capture date shown in the registry.
- Weak sourcing — Data processing agreement. The DPA document itself is not reproduced in these excerpts; it is only referenced as incorporated into the standard terms.
- Weak sourcing — Legal entity. The terms state the service is administered from US offices, but no page names a state of incorporation or a company register entry.
- Weak sourcing — Hosting location. US is only the default; the security page's multi-region hosting lets customers choose EU storage instead, and infrastructure also runs in AWS eu-central-1.
- Weak sourcing — Hosting options. Self-hosting appears only as a "talk to sales" item with no deployment details, and the security page separately offers selectable EU hosting ("Multi-region hosting").
- AI can misread a source. Extraction and judgement are automated; a citation guarantees traceability, not infallibility. If something here is wrong, say so — no account needed, every report is decided within 5 business days, and accepted corrections are published.
What we left out
A claim that does not survive our checks costs us the claim, not the page. This is what was taken off this one.
- 30 product facts could not be confirmed on the vendor’s page as captured and were left out of this page and of the panel’s material. Know more? Tell us
- 14 integrations facts could not be confirmed on the vendor’s page as captured and were left out of this page and of the panel’s material. Know more? Tell us
- 4 compliance facts could not be confirmed on the vendor’s page as captured and were left out of this page and of the panel’s material. Know more? Tell us
- 4 pricing facts could not be confirmed on the vendor’s page as captured and were left out of this page and of the panel’s material. Know more? Tell us
- 2 support facts could not be confirmed on the vendor’s page as captured and were left out of this page and of the panel’s material. Know more? Tell us
- 6 of the readings below were written against an earlier fact sheet — a fact has been corrected, added or pulled since. Until the panel next runs on this product you are reading the older judgement. Know more? Tell us
Sources (21)
The pages every claim on this page was read from — each one checked, dated, and kept verifiable.
- 1 Vendor homepage www.honeybadger.io Checked 6 Nov 2026 Details →
- 2 Features page (error tracking) www.honeybadger.io Checked 6 Nov 2026 Details →
- 3 Features page (logging and performance insights) www.honeybadger.io Checked 6 Nov 2026 Details →
- 4 Integrations page www.honeybadger.io Checked 6 Nov 2026 Details →
- 5 Documentation docs.honeybadger.io Checked 6 Nov 2026 Details →
- 6 API documentation docs.honeybadger.io Checked 6 Nov 2026 Details →
- 7 Pricing page www.honeybadger.io Checked 6 Nov 2026 Details →
- 8 Security / trust page www.honeybadger.io Checked 6 Nov 2026 Details →
- 9 Public status page status.honeybadger.io Checked 6 Nov 2026 Details →
- 10 About page www.honeybadger.io Checked 6 Nov 2026 Details →
- 11 Terms of service (names the operating company) www.honeybadger.io Checked 6 Nov 2026 Details →
- 12 Privacy policy www.honeybadger.io Checked 6 Nov 2026 Details →
- 13 Error capture, grouping & triage — found from sitemap docs.honeybadger.io Checked 6 Nov 2026 Details →
- 14 Error capture, grouping & triage — found from sitemap docs.honeybadger.io Checked 6 Nov 2026 Details →
- 15 APM, tracing & profiling — found from sitemap docs.honeybadger.io Checked 6 Nov 2026 Details →
- 16 Alerting, integrations & developer workflow — found from sitemap docs.honeybadger.io Checked 6 Nov 2026 Details →
- 17 Alerting, integrations & developer workflow — found from sitemap docs.honeybadger.io Checked 6 Nov 2026 Details →
- 18 Data scrubbing, retention & volume control — found from sitemap docs.honeybadger.io Checked 6 Nov 2026 Details →
- 19 Data scrubbing, retention & volume control — found from sitemap www.honeybadger.io Checked 6 Nov 2026 Details →
- 20 Access control, security & the vendor's reliability — found from sitemap www.honeybadger.io Checked 6 Nov 2026 Details →
- 21 Access control, security & the vendor's reliability — found from sitemap www.honeybadger.io Checked 6 Nov 2026 Details →