AppSignal
EU-Made Report an errorPanel rating · 6 judges · How to read the stars
Category median
Sovereignty: 3 of 6 dimensions proven
0–5 in half steps. 5 means the rubric's top anchor is met on the evidence.
by AppSignal B.V. · www.appsignal.com
Compare with Honeybadger → 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.
AppSignal at a glance
- Vendor
- AppSignal B.V.
- Headquarters
- Not stated on the vendor’s pages as of 6 Nov 2026
- Data hosting
- In the EU source, captured 6 Nov 2026
- Free plan
- Yes, per the vendor’s own page source, captured 6 Nov 2026
- Panel verdict
- The AI panel rates AppSignal 3/5, the mean of 6 judges. AppSignal is an error tracking and APM platform from AppSignal B.V. 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
AppSignal is an error tracking and APM platform from AppSignal B.V. of Amsterdam. It scores highest on sovereignty, 7 to 8, and on data controls, 6 to 7: application data is stated to be stored only in ISO-certified facilities in the Netherlands, hosting subprocessors are named, a DPA is signable digitally, and filtering of parameters, sessions and query strings is documented per language. Workflow and integrations sits at 6 with no spread. Pricing transparency is the low point at 4: the free plan is public at €0 with 30K requests, 1GB logging and 5-day retention, we found no public information on the price of any paid plan, and the captured pages give different accounts of the quota — a 30-day usage review on the pricing page versus the terms' requirement to upgrade after exceeding the limit by more than 10% for two months. Security and reliability draws the widest range, 4 to 6: ISO 27001 and a public status page are documented, while we found no public information on single sign-on, SCIM or audit logs, and the terms state uptime is not guaranteed.
Speaks for it
- Sovereignty scores 7 to 8, with application data stated to be stored only in ISO-certified facilities in the Netherlands, named hosting subprocessors and a DPA signable digitally via the account
- Data controls score 6 to 7, with parameter, session and query-string filtering documented per language, server-side filtering of password keys, and trace retention of 30, 45 or 60 days depending on plan
- Workflow and integrations holds at 6 with no spread, spanning notifiers including Slack, Teams and PagerDuty, SHA256-signed webhooks with verification examples, GitHub, GitLab, Jira and Linear issue trackers, a CLI, a GraphQL API and an MCP server for AI agents
- Volume is managed by policy rather than invoice: monitoring never stops at the plan limit and no overage is charged
- The free plan is priced at €0 with 30K requests, 1GB logging and 5-day retention, the 30-day free trial needs no credit card, and all plans include unlimited users, teams and applications
Held against it
- Pricing transparency scores 4 with no spread: we found no public information on the price of any paid plan, and the HIPAA agreement and long-term log storage add-ons are handled through the Customer Success team
- The captured pages give different accounts of the quota — a 30-day usage review on the pricing page versus the terms' upgrade requirement after exceeding the limit by more than 10% for two months, with automatic upgrade after 7 days without a response
- Security and reliability spans 4 to 6, the widest range: we found no public information on single sign-on, SCIM, audit logs or SOC 2, login is email-and-password or a GitHub account, and the terms state uptime is not guaranteed
- Liability is capped at EUR 100.00 per event and EUR 1,000.00 in aggregate, and claims lapse one year after the occurrence
Best for
- You run web and backend apps on Ruby, Elixir, Node.js, Python, PHP or browser JavaScript and want errors tightly coupled to their traces
- Your procurement requires a Dutch legal entity, application data stored in certified facilities in the Netherlands and a DPA signable digitally via the account
- You fear surprise bills after traffic spikes — monitoring never stops at the plan limit and no overage is charged
- You want to evaluate before paying, on a €0 free plan and a 30-day free trial with no credit card required
Avoid if
- Your product runs on native mobile clients — the documented SDKs are Ruby, Elixir, Node.js, Python, PHP and browser JavaScript
- Your contract requires an uptime guarantee or liability terms beyond EUR 1,000.00 in aggregate — the terms state uptime is not guaranteed and cap liability at that amount
- You must compute an annual cost from published prices before committing — pricing transparency scores 4 across the range and the Business add-ons are quoted through the Customer Success team
- You depend on distributed tracing across Elixir or Node.js services — the documentation states those languages are not supported yet in the beta feature
The scores
| Criterion | Panel median |
|---|---|
| Error capture, grouping & triage | 3 of 5 |
| APM, tracing & profiling | 3 of 5 |
| Alerting, integrations & developer workflow | 3 of 5 |
| Data scrubbing, retention & volume control | 3 of 5 |
| Access control, security & the vendor's reliability | 2.5 of 5 |
| European sovereignty | 3.5 of 5 |
| Pricing transparency | 2 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
SDKs for Ruby, Elixir, Node.js, Python, PHP and browser JavaScript are documented with handled-exception helpers, full backtraces, request metadata and tags, and issues group by error type, action and namespace with state, severity, assignee, deploy markers, revision filters and saved views. Browser breadcrumbs are documented but in beta, and we found no public information on source maps, symbolication, regression detection or mobile SDKs. 2 4 15 16
The SaaS CTO
Exceptions are captured and grouped into issues by error type, action and namespace, each with state, severity, assignee, its own notification settings, deploy markers and revision filters, and handled-exception helpers are documented for Ruby, Elixir, Node.js, Python, PHP and browser JavaScript. Browser breadcrumbs are documented in unusual depth, from categories and buffer limits to redaction hooks, and Go support arrives through OpenTelemetry rather than a first-party SDK. We found no public information on mobile SDKs, source maps, symbolication or custom fingerprinting. 2 4 15 16
The Mobile Team Lead
Exception capture with automatic grouping by error type, action and namespace, issue states with severity and assignee, deploy revision filters and saved views is well documented for Ruby, Elixir, Node.js, Python, PHP and browser JavaScript, including browser breadcrumbs and a per-issue notification setting. As the mobile lead I have to flag that we found no public information on native iOS, Android or Flutter SDKs, on symbolication, or on crash-free sessions and users per release, so this reaches the common web-and-backend level rather than the mobile depth our store rollouts need. 2 4 15 16
The Site Reliability Engineer
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. 2 4 15 16
The Data Protection Officer
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. 15 16 2 4
The Skeptic
SDKs for Ruby, Elixir, Node.js, Python, PHP and browser JavaScript are documented with handled-error helpers, full backtraces, grouping by error type, action and namespace, deploy markers with a revision filter, issue states with severity and assignees, saved and remembered filters, and browser breadcrumbs (flagged beta, 25 per error). We found no public information on mobile SDKs, source maps or symbolication, custom fingerprinting, merge and split of issues, or regression states, which keeps this below the next level. 2 4 15 16
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
Slow queries and N+1 detection, background job monitoring, per-action performance with 90th percentiles, host metrics beside the traces, OpenTelemetry ingestion and anomaly detection on error rates, throughput and slow actions are all documented, with sampling that favours errors and the slowest requests. Distributed tracing is a beta feature requiring the hosted collector and Elixir and Node.js are not supported yet, and we found no public information on code-level profiling or real user monitoring with Core Web Vitals. 3 4 7 17 18
The SaaS CTO
Traces are built on OpenTelemetry and the browser SDK starts the trace with a traceparent header into the API, with a service map and timeline per trace — the browser-to-database path I want — though distributed tracing is documented as a beta Labs feature requiring the hosted collector, and the docs state Elixir and Node.js are not supported yet. Around it sit 90th percentiles, slow query and N+1 detection, host metrics per sample, anomaly detection on error rates, throughput and slow actions with a documented alert state machine, and trace-to-log linking. We found no public information on code-level profiling, Core Web Vitals or real user monitoring, and sampling is described only as favouring errors and the slowest requests. 3 4 7 17 18
The Mobile Team Lead
Transaction timings with 90th percentiles, slow query and N+1 detection, background job monitoring, host metrics and anomaly alerts on error rates, throughput and slow actions are all documented, built on OpenTelemetry with a stated path for Go and Java, and trace sampling is described as favouring errors and the slowest requests. Distributed tracing across services is labelled a beta Labs feature that does not yet cover Elixir or Node.js, and we found no public information on code-level profiling or real-user Web Vitals, which keeps it below the upper band. 3 4 7 17 18
The Site Reliability Engineer
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. 3 4 7 17 18
The Data Protection Officer
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. 17 3 18 7
The Skeptic
Traces are built on OpenTelemetry with slow query and N+1 detection, background job monitoring, 90th percentiles, host metrics beside the samples, anomaly detection on error rates, throughput, slow actions and queue time with warm-up and cooldown, and errors coupled to their traces with a service map and trace timeline. 3 4 7 17 18 23
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 runs at app, namespace, action and job level plus metric triggers with warm-up, cooldown and per-trigger notifier routing, and Slack, email, PagerDuty, OpsGenie, Teams and Discord sit alongside issue tracker links to GitHub, GitLab, Jira, Linear and more, plus a documented REST and GraphQL API, a CLI, an MCP server for AI agents, and webhooks with signature verification and examples. We found no public information on two-way issue tracker sync, scheduled digest reports or routing per team. 4 5 6 15 18 19 20
The SaaS CTO
Notifications reach Slack, Microsoft Teams, Discord, PagerDuty, Opsgenie and webhooks signed with a SHA256 header and verification examples in four languages, issues go to GitHub, GitLab, Jira, Linear and more, and a documented REST API, a CLI, an MCP server for agents like Claude Code, and anomaly alerts routed per trigger with warm-up and cooldown are all in the docs. Deploy markers and per-issue notification settings are documented too. We found no public information on two-way issue tracker sync, source code and commit links, scheduled reports, or AI error explanations with a model provider named. 5 6 18 19 20
The Mobile Team Lead
Notifications reach Slack, Microsoft Teams, PagerDuty, Opsgenie and Discord, webhooks are signed with verification examples and selectable per event type, issue trackers include GitHub, GitLab, Jira and Linear, and a documented API, a CLI and an MCP server for AI coding agents round it out. Issue tracker links are set up per person and appear to be one-way, alert routing works per trigger rather than per team, and we found no public information on two-way tracker sync, on which AI model explains errors, or on scheduled digest reports. 4 5 15 18 19 20
The Site Reliability Engineer
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. 4 5 6 18 19 20
The Data Protection Officer
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. 19 20 5 4 18 12
The Skeptic
Notifiers span Slack, Teams, Discord, PagerDuty, Opsgenie and webhooks with SHA256 signature verification and worked examples in four languages; issue trackers include GitHub, GitLab, Jira and Linear (set up per person, per app), anomaly triggers route to selected notifiers, and there is a CLI, an MCP server for AI agents with a named tool, a GraphQL API and a push endpoint. We found no public information on two-way tracker sync, source code and commit links, or scheduled digest reports. 4 5 15 18 19 20
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
Every integration has a configurable parameter key filter with switches to disable all parameters and session data, a server-side filter for password keys, a header allowlist that strips other headers, trace retention of 30 to 60 days per plan, trace removal on request, deletion in app settings and export via the API. Volume is handled by spike forgiveness — no overage charges, monitoring never stops — with a 30-day usage review before any forced upgrade; we found no public information on per-project retention settings, rate limits or a self-hosted edition. 1 7 10 21 22 23
The SaaS CTO
Parameter filtering is configurable per integration with examples, session data has a denylist and an off switch per language, query parameters are dropped by default in the browser SDK, and the processor additionally filters password keys server-side, though that server-side list is documented as not customizable. Retention is stated per plan (traces 30, 45 or 60 days), traces can be removed on request, all collected data is retrievable through the API, and volume is managed by policy rather than invoice: monitoring never stops, overages are never charged, spike forgiveness applies and a 30-day usage review precedes any upgrade. We found no public information on IP anonymisation or a self-hosted edition. 7 10 16 17 21 22 23
The Mobile Team Lead
Every documented SDK filters parameters and session data with configurable key lists plus an option to switch them off entirely, a server-side filter replaces password keys before storage, trace retention is stated as 30, 45 or 60 days depending on plan, and the volume story is unusually clear: monitoring never stops, no overage is charged, and the forced-upgrade rules after sustained excess use are published. The server-side filter list is fixed rather than custom, and we found no public information on IP anonymisation or a self-hosted edition, which keeps it off the top band. 7 10 13 21 22 23
The Site Reliability Engineer
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. 1 7 10 21 22 23
The Data Protection Officer
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. 21 22 16 10 7 23
The Skeptic
SDK-level filtering of parameters, session keys and query strings (removed by default, with a beforeBreadcrumb hook) plus server-side removal of password keys — a fixed list stated as not customizable — trace retention of 30, 45 or 60 days by plan, deletion of app data and individual traces on request, sampling biased toward errors and slowest traces, and export through the API. Spike protection is documented in full: no overage is ever charged and monitoring never stops, but the terms require an upgrade after exceeding the limit by more than 10% for two months, with auto-upgrade if you do not respond within 7 days; we found no public information on a self-hosted edition or per-project retention settings. 7 10 13 16 21 22
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
Two-factor enforcement, ISO 27001 certification, regular penetration tests, bug rewards, SSL in transit, encrypted backups, tenant separation across databases, a security contact and a public status page with incident history are all documented. We found no public information on single sign-on, SCIM provisioning, audit logs or SOC 2, and the terms state plainly that uptime is not guaranteed. 8 9 11 13 23
The SaaS CTO
ISO 27001 certification with regular penetration tests, a bug reward, two-factor authentication with team-wide enforcement, a DPA signable in-account and a public status page with history (last incident February 2026) are all documented. The terms state AppSignal does not guarantee uptime, and we found no public information on single sign-on, SCIM provisioning, audit logs or role-based access; login is email-and-password or GitHub. For an enterprise security review that is the gap. 9 11 13 14
The Mobile Team Lead
ISO 27001 certification, regular penetration tests, encrypted backups, enforced two-factor authentication and a public status page with incident history and a status API give us a defensible audit story, and the HIPAA agreement is offered as an add-on. We found no public information on single sign-on, SCIM provisioning or audit logs, and the terms explicitly disclaim any uptime guarantee, so enterprise access controls and an SLA are not evidenced. 9 11 13 14 24
The Site Reliability Engineer
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. 9 11 13 14 23
The Data Protection Officer
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. 9 11 13 24 23
The Skeptic
ISO 27001 with penetration tests in line with it, 2FA with team enforcement, SSL in transit, encrypted backups, storage in ISO-certified Netherlands facilities with tenant separation, a signable DPA, a BAA for HIPAA, a public status page with history and a status API, and rewards for reported bugs. We found no public information on single sign-on, SCIM, audit logs or SOC 2, and the terms state plainly that AppSignal does not guarantee accessibility, cap aggregate liability at EUR 1,000, and let claims lapse after one year — honest, but the vendor carries its own bad day on your budget. 7 8 9 11 13 14
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
AppSignal B.V. is a Dutch company with a Chamber of Commerce number and Amsterdam address, application data sits in certified facilities in the Netherlands, Dutch law governs the contract, and hosting runs through Worldstream B.V. with AWS EMEA for backups and Hetzner for the optional collector, plus a data processing agreement signable digitally from the account. The marketing, newsletter and payment subprocessors are listed by name but without stated locations, though transfers outside the EEA are described as carrying appropriate safeguards. 3 9 13 14
The SaaS CTO
The contracting entity is AppSignal B.V. in Amsterdam with a Dutch Chamber of Commerce number, application data is stated to be stored only in certified facilities in the Netherlands, hosting subprocessors are named as Worldstream B.V., Hetzner Online GmbH and Amazon Web Services EMEA SARL, and Dutch law governs. A DPA can be signed digitally via the account and ISO 27001 plus GDPR compliance are stated; a US hosting option is presented as coming soon. The privacy policy names further subprocessors for payments, analytics, forms and newsletters without their locations, saying only that appropriate safeguards apply where their data centres sit outside the EEA, so the chain is European but not documented end to end. 8 9 13 14
The Mobile Team Lead
The contracting entity is AppSignal B.V. in Amsterdam with a Dutch Chamber of Commerce number, application data is stated to sit in certified facilities in the Netherlands under Dutch law, and subprocessors are named — Worldstream for hosting, AWS EMEA for backups, Hetzner for the optional collector, Stripe and Moneybird for payments — with safeguards stated for transfers outside the EEA and a data processing agreement signable via the account. Individual subprocessor locations and SOC 2 are not stated and no self-hosted edition is documented, so we land just below the fully sovereign band. 3 9 13 14
The Site Reliability Engineer
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. 3 8 9 13 14
The Data Protection Officer
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. 14 9 13 8
The Skeptic
AppSignal B.V. of Amsterdam, Dutch Chamber of Commerce 62960407, under Dutch law with exclusive jurisdiction in 's-Hertogenbosch; application data stays in certified facilities in the Netherlands, hosting subprocessors are named (Worldstream B.V., AWS EMEA SARL for backups, Hetzner for the optional collector), a DPA is signable digitally from the account, and ISO 27001 is stated. Not every listed subprocessor — analytics, payments, newsletters, marketing — carries a stated location, only a general safeguards statement for transfers outside the EEA, which keeps this just short of the top band. 1 3 9 13 14
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 free plan is published at €0 with 30K requests, 1GB logging and 5-day retention, all plans include unlimited users, teams and applications, billing runs monthly or yearly in EUR or USD, prices are exclusive of VAT, and overage is stated as never charged with a 30-day usage review before any upgrade. The captured pricing material gives no prices for the paid plans, and the logging add-on, long-term log storage and the HIPAA agreement are unpriced, with Business features handled through the Customer Success team. 1 4 7 13
The SaaS CTO
The free plan is priced at €0 with 30K requests, 1GB logging and 5-day retention, all plans include unlimited users, teams, applications and dashboards, monthly and yearly billing is offered in EUR or USD, and quota behaviour is unusually clear: monitoring never stops, overages are never charged, and a 30-day usage review precedes any plan upgrade. Prices are exclusive of VAT and payment is in advance by bank transfer or credit card. We found no public information on the price of the paid plans or of the Business Add-Ons such as the HIPAA agreement and long-term log storage, so an annual cost is not computable from the captured pages. 1 4 7 13
The Mobile Team Lead
The free plan is priced at €0 with its volumes (30K requests, 1GB logging, 5-day retention), unlimited users, teams and applications on all plans, VAT-exclusive prices, non-refundable advance billing in EUR or USD, and a clear no-overage policy with published upgrade rules. But we found no public price for any paid plan on the captured pages, and the HIPAA agreement and long-term log storage add-ons go through the Customer Success team, so we cannot compute a real annual cost for our request volume. 1 4 7 10 13
The Site Reliability Engineer
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. 1 4 7 10 13
The Data Protection Officer
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. 7 1 13 4
The Skeptic
The free plan is public at "€0" with 30K requests, 1GB logging and 5-day retention, unlimited users, teams and applications on all plans, EUR or USD and monthly or yearly billing, VAT-exclusive prices, and a promise of no overage charges and no dropped data. We found no public information on the price of any paid plan or of the Business add-ons (HIPAA agreement, long-term log storage), and the captured pages give different accounts of the quota: the pricing page describes a 30-day usage review, while the terms require an upgrade after exceeding the limit by more than 10% for two months and allow automatic upgrade after 7 days of notice. 1 4 7 13
European sovereignty — proven facts
3 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 | Not determined | — | uncited Report an error |
|---|---|---|---|
| Hosting location |
EU only
unverified
Why unverified?The plans page advertises a "US Hosting" business add-on to store application data in the United States, whose dedicated page still says "coming soon", which may move some customers' data outside the EU. |
4/4 pts | 14 Report an error |
| Hosting options | Not determined | — | uncited Report an error |
| Open source |
Proprietary
unverified
Why unverified?Only the agent is explicitly called closed-source; the client libraries are described as "public code" hosted on GitHub without any licence being named. |
0/1 pts | 23 Report an error |
| Data processing agreement | Published, self-serve | 1/1 pts | 9 Report an error |
| Transfer impact assessment | Not determined | — | uncited Report an error |
Questions about AppSignal
Is AppSignal European?
Yes. whats-best.ai classifies AppSignal as EU-Made.
Where does AppSignal store data?
AppSignal stores customer data in the EU, per the vendor’s page captured 6 Nov 2026.
Does AppSignal have a free plan?
Yes. AppSignal has a free plan, per the vendor’s page captured 6 Nov 2026.
What are the best alternatives to AppSignal?
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: AppSignal 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 — Open source. Only the agent is explicitly called closed-source; the client libraries are described as "public code" hosted on GitHub without any licence being named.
- Weak sourcing — Hosting location. The plans page advertises a "US Hosting" business add-on to store application data in the United States, whose dedicated page still says "coming soon", which may move some customers' data outside the EU.
- 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.
- 23 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
- 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 hosting facts could not be confirmed on the vendor’s page as captured and were left out of this page and of the panel’s material. 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
- 1 compliance fact could not be confirmed on the vendor’s page as captured and was left out of this page and of the panel’s material. Know more? Tell us
- 1 integrations fact could not be confirmed on the vendor’s page as captured and was left out of this page and of the panel’s material. Know more? Tell us
- 1 legal fact could not be confirmed on the vendor’s page as captured and was left out of this page and of the panel’s material. 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 (24)
The pages every claim on this page was read from — each one checked, dated, and kept verifiable.
- 1 Vendor homepage www.appsignal.com Checked 6 Nov 2026 Details →
- 2 Features page (error tracking) www.appsignal.com Checked 6 Nov 2026 Details →
- 3 Features page (performance monitoring) www.appsignal.com Checked 6 Nov 2026 Details →
- 4 Documentation docs.appsignal.com Checked 6 Nov 2026 Details →
- 5 Integrations page docs.appsignal.com Checked 6 Nov 2026 Details →
- 6 API documentation docs.appsignal.com Checked 6 Nov 2026 Details →
- 7 Pricing page www.appsignal.com Checked 6 Nov 2026 Details →
- 8 Features page (hosting regions) www.appsignal.com Checked 6 Nov 2026 Details →
- 9 Security / trust page www.appsignal.com Checked 6 Nov 2026 Details →
- 10 GDPR page docs.appsignal.com Checked 6 Nov 2026 Details →
- 11 Public status page status.appsignal.com Checked 6 Nov 2026 Details →
- 12 About page www.appsignal.com Checked 6 Nov 2026 Details →
- 13 Terms of service www.appsignal.com Checked 6 Nov 2026 Details →
- 14 Privacy policy www.appsignal.com Checked 6 Nov 2026 Details →
- 15 Error capture, grouping & triage — found from sitemap docs.appsignal.com Checked 6 Nov 2026 Details →
- 16 Error capture, grouping & triage — found from sitemap docs.appsignal.com Checked 6 Nov 2026 Details →
- 17 APM, tracing & profiling — found from sitemap docs.appsignal.com Checked 6 Nov 2026 Details →
- 18 APM, tracing & profiling — found from sitemap docs.appsignal.com Checked 6 Nov 2026 Details →
- 19 Alerting, integrations & developer workflow — found from sitemap docs.appsignal.com Checked 6 Nov 2026 Details →
- 20 Alerting, integrations & developer workflow — found from sitemap docs.appsignal.com Checked 6 Nov 2026 Details →
- 21 Data scrubbing, retention & volume control — found from sitemap docs.appsignal.com Checked 6 Nov 2026 Details →
- 22 Data scrubbing, retention & volume control — found from sitemap docs.appsignal.com Checked 6 Nov 2026 Details →
- 23 Access control, security & the vendor's reliability — found from sitemap docs.appsignal.com Checked 6 Nov 2026 Details →
- 24 Access control, security & the vendor's reliability — found from sitemap docs.appsignal.com Checked 6 Nov 2026 Details →