Sentry
Rest of world Report an errorPanel rating · 6 judges · How to read the stars
Category median
Sovereignty: 2 of 6 dimensions proven
0–5 in half steps. 5 means the rubric's top anchor is met on the evidence.
by Functional Software, Inc. · sentry.io
Compare with Bugsink → 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.
Sentry at a glance
- Vendor
- Functional Software, Inc.
- Headquarters
- Not stated on the vendor’s pages as of 6 Nov 2026
- Data hosting
- Default not stated; pages mention the US, the EU, the United States and Germany 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 Sentry 3.5/5, the mean of 6 judges. Sentry is an error tracking and application monitoring platform sold by Functional Software, Inc. 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
Sentry is an error tracking and application monitoring platform sold by Functional Software, Inc. of San Francisco. It is strongest on error tracking, workflow and integrations, and pricing transparency, each scoring 7 to 8: alerts route to Slack, Microsoft Teams, PagerDuty and Opsgenie, Jira issues are created and synced, and prices are public, from a free Developer plan for one user with 5k errors to Team at $26/mo. Performance tracing and security and reliability hold at 7, where rationales credit distributed tracing, SOC 2 Type II and ISO 27001, but found no published SLA with credits. The bench genuinely splits twice. Data controls span 6 to 8: the Skeptic saw scrubbing only as headings, with no public server-side rules or worked examples, while the Site Reliability Engineer credited spend caps, stated retention and a documented self-hosting option. Sovereignty spans 6 to 7 on the same facts — an EU region in Frankfurt beside a US contracting entity and US-stored accounts and audit logs — with judges weighing how far strong disclosure offsets the mixed chain.
Speaks for it
- Pricing transparency scores 7 to 8, with plans, tiered pay-as-you-go error rates from $0.0003625 at the lowest band to $0.0001500 at 20M+, and priced add-ons such as Seer at $40/active contributor/month all published.
- Error tracking scores 7 to 8, with grouping documented in depth — SDK fingerprint overrides, project-level fingerprint and stack-trace rules — plus suspect commits, code owners and auto-assignment to the committing developer.
- Workflow and integrations score 7 to 8, routing alerts to Slack, Microsoft Teams, PagerDuty, Opsgenie and SMS, creating and syncing Jira issues, and exposing a REST API, CLI and MCP server.
- Security documentation covers SAML SSO with SCIM on Business and Enterprise, MFA with YubiKey or TOTP, AES-256 encryption in transit and at rest, SOC 2 Type II and ISO 27001 available on request, and a status page with 90 days of uptime.
- Spend stays predictable through plan quotas, spike-protection notifications and a maximum spend setting on top of tiered pay-as-you-go error rates.
Held against it
- Sovereignty scores 6 to 7 over a mixed chain: the contracting entity is Functional Software, Inc. of San Francisco under California law, user accounts, audit logs and SSO metadata stay in the US regardless of region choice, and the AI, email delivery and support subprocessors are US-based.
- The terms provide the service AS IS, and the bench found no published SLA with credits and no public information on SDK behaviour when ingestion is down.
- Data controls spread 6 to 8, and we found no public worked examples of custom server-side scrubbing rules, no per-project retention settings and no documented deletion of a single event or user.
- A year's bill is not fully computable: span overage pricing sits in the docs rather than the pricing page, Enterprise is Custom, and we found no public price for the self-hosted edition.
- Performance tracing scores 7, and we found no public information on host and container metrics beside the traces, Web Vitals naming or response-time percentiles per endpoint.
Best for
- You need errors routed to whoever committed the broken code, with grouping you can override per project through fingerprint and stack-trace rules.
- You want to compute most of a year's cost from public pages, using published quotas, tiered pay-as-you-go error rates and priced add-ons.
- Your compliance review requires SAML SSO with SCIM, MFA, audit logs, SOC 2 Type II and ISO 27001 available on request.
- You need service data — error events, spans, profiles, logs, metrics, session replays and their backups — stored in the EU, and can accept a US contracting entity.
Avoid if
- You need an end-to-end European chain: the contracting entity and governing law sit in California, and user accounts, audit logs and SSO metadata are stored in the US regardless of the region you choose.
- You require a contractual availability commitment with credits: the terms provide the service AS IS, and support promises reasonable efforts during business hours.
- You must lock in renewal pricing: fees for renewal terms revert to Sentry's then-current rates, regardless of any discounted pricing in a prior order.
The scores
| Criterion | Panel median |
|---|---|
| Error capture, grouping & triage | 3.5 of 5 |
| APM, tracing & profiling | 3.5 of 5 |
| Alerting, integrations & developer workflow | 4 of 5 |
| Data scrubbing, retention & volume control | 3.5 of 5 |
| Access control, security & the vendor's reliability | 3.5 of 5 |
| European sovereignty | 3.5 of 5 |
| Pricing transparency | 4 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
Stack traces with local variables, breadcrumbs, release health with crash-free sessions, and alerts when an error first happens, regresses or escalates are all documented, and grouping is properly controllable — SDK fingerprint overrides are explained with examples for the Python and JavaScript SDKs and project-level fingerprint rules are described as always available, which is what keeps forty client sites from collapsing into one noisy issue. Suspect commits, code owners and ownership rules are listed as workflow features. The captured pages market support for 'any language or framework' but document fingerprinting only for the Python and JavaScript SDKs, and we found no public information on merging or splitting issues. 2 17 18 9
The SaaS CTO
Grouping is documented in real depth: SDK-level fingerprint overrides, project-level fingerprint and stack trace rules, and an explained default algorithm, alongside suspect commits, code owners and auto-assignment of issues to whoever committed the broken code. Stack traces with local variables, breadcrumbs, release and environment context, and release health with crash-free sessions and version adoption are all on the product pages. The gap to the very top of the scale is that the captured pages do not show merging or splitting of issues or symbolication per platform. 2 17 18 9 4 13
The Mobile Team Lead
Release health with crash-free sessions, version adoption and failure rate per release is exactly what I need to stop a bad rollout, and it sits beside stack traces with local variables, breadcrumbs, release and environment context, and suspect-commit plus code-owner attribution. Custom fingerprints work in the SDK and as server-side fingerprint and stack-trace rules, documented in depth for the Python and JavaScript SDKs, with mobile crash reporting a named solution and debug symbols and source maps stored per region. I found no public information on crash-free users specifically or on merging and splitting issues. 1 2 8 9 17 18
The Site Reliability Engineer
Stack traces with local variables, breadcrumbs and release context are documented, and grouping is genuinely controllable: the default fingerprinting from stack trace, exception and message is explained, and it can be overridden in the SDK or with project-level fingerprint and stack trace rules. Suspect commits, code owners and auto-assignment to the committing developer cover triage, with release health reporting crash-free sessions, version adoption and failure rate. We found no public information on merging or splitting issues or on per-platform SDK parity, which holds it below the top level. 2 6 9 17 18
The Data Protection Officer
Errors arrive with detailed stack traces, local variables, breadcrumbs, release and environment context, user-impact views and release health with crash-free sessions, and grouping is documented in real depth: built-in algorithms, custom fingerprints set in the SDK, and server-side fingerprint and stack-trace rules that can override grouping entirely. Suspect commits, code owners and ownership rules are named features, and debug symbols and source maps are stored per region. I found no public information on merge and split of issues or on per-platform SDK configuration parity, which keeps this just below the top of the scale. 2 6 8 9 17 18
The Skeptic
Stack traces with local variables, breadcrumbs, release health with crash-free sessions, and suspect-commit linking are documented, and custom fingerprinting is explained in unusual depth for both the Python and JavaScript SDKs, default algorithm and all. We found no public information on mobile symbolication, merging or splitting issues, or crash-free users, which is what holds it below the top anchors. 2 6 9 17 18
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
N+1 query detection is documented in unusual depth — detector criteria, configurable detector settings in project settings, and how the issue fingerprint is computed — and slow SQL queries and API calls are connected to the exact line of code, with distributed tracing, waterfall views and Trace Explorer filtering on top; OpenTelemetry ingestion, continuous and UI profiling are documented and priced, trace sampling is configurable, and background job debugging is a named use case. That is most of what I need to find a slow Shopware page before the client calls. We found no public information on host or container metrics beside the traces, and Core Web Vitals are not named on the captured pages. 19 4 3 9
The SaaS CTO
Distributed tracing follows a request across services with waterfall views, N+1 detection is documented down to the detector criteria with adjustable limits, slow queries connect to the exact line of code, background jobs and AI agents are traced, and OpenTelemetry traces can be routed in without adopting the vendor's SDKs — the vendor-neutral instrumentation I want for twelve services. Continuous and UI profiling are priced per hour, anomaly detection is listed, and errors, logs, replays, spans, profiles and metrics sit on one trace. Missing for the top of the scale: Web Vitals naming, host and container metrics beside traces, and an explanation of what sampling choices cost you. 4 3 19 9 1
The Mobile Team Lead
Distributed tracing with waterfall views, slow-query and N+1 detection documented down to its detection criteria, background jobs through cron monitors, configurable trace sampling, OpenTelemetry ingestion without an SDK migration, and pay-as-you-go continuous and UI profiling give me the mobile picture too, including slow app starts in production. Anomaly detection and metric monitors ship on the paid plans and tracing covers every supported platform. I found no public information on Web Vitals, host and container metrics beside the traces, or response-time percentiles per endpoint. 3 4 9 19
The Site Reliability Engineer
Distributed tracing, slow queries pinned to the exact line of code, and an N+1 detector documented down to its span criteria, configurable detection levels and waterfall evidence cover most of what I need at 3 a.m. OpenTelemetry ingestion, continuous and UI profiling, configurable trace sampling and anomaly detection are all evidenced. We found no public information on host or container metrics beside the traces, or on Web Vitals by name, so it sits below the highest level. 3 4 9 19
The Data Protection Officer
Tracing across services is documented with waterfall views, slow-SQL detection tied to the exact line of code, and an unusually detailed N+1 detector with tunable detection settings and its own fingerprinting, beside OpenTelemetry ingestion, configurable trace sampling, continuous and UI profiling, cron monitoring and trace-to-error linking. Real user monitoring is sold as a solution and anomaly detection is listed among the alerting features. I found no public information on percentiles per endpoint, Web Vitals naming, or host and container metrics beside the traces, so this sits below the strongest level. 1 3 4 9 19
The Skeptic
Distributed tracing, slow-query and N+1 detection with the detector's criteria and configurable limits spelled out, OpenTelemetry ingestion without SDK migration, priced continuous and UI profiling, and trace sampling configuration are all documented. We found no public information on host or container metrics beside the traces, and Core Web Vitals are never named, so it sits short of the full application performance management anchor. 1 3 4 9 19
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
Alerts go out over Slack, Microsoft Teams, Discord, PagerDuty, Opsgenie and SMS, Jira issues are created and synced from Sentry, GitHub brings suspect commits and PR comments, and releases are announced from GitHub Actions, Netlify and Vercel with source map uploads — enough channel choice to give each client its own alerting. A documented REST API with token authentication, a CLI beside the MCP server, and ownership rules that route issues to teams round it out. The Seer AI debugger is documented with a privacy overview and a published price, but the captured pages do not name the model behind it, and we found no public information on scheduled digest reports. 5 6 7 9
The SaaS CTO
The routes an error takes to the person who fixes it are all documented: Slack, Microsoft Teams, Discord, PagerDuty and Opsgenie, create-and-sync with Jira and Azure DevOps, GitHub with suspect commits and PR comments, GitLab, Linear, deploy notifications from GitHub Actions, Vercel and Netlify, a full REST API over issues, releases, SCIM and teams, plus a CLI and an MCP server for agent workflows. Ownership rules, code owners, cross-project issues and anomaly detection are listed as workflow features, and the Seer AI debugger is documented with Anthropic and OpenAI named as the AI and machine-learning subprocessors. We found no public information on scheduled digest or weekly reports. 5 6 7 9 16
The Mobile Team Lead
Jira issues can be created and synced from Sentry, GitHub gets suspect commits and stack traces, Slack, Microsoft Teams, PagerDuty and Opsgenie all deliver alerts, and releases and source maps go up through the Sentry CLI or CI integrations. Ownership rules route issues to the right team, metric monitors and anomaly detection alert on performance, and the Seer AI debugger is a priced add-on with a published privacy overview, with Anthropic and OpenAI named as the AI and ML subprocessors. I found no public information on scheduled digest or weekly reports. 5 6 9 16
The Site Reliability Engineer
Alerts fire on first occurrence, regression and escalation and route to PagerDuty, Opsgenie, Slack and Microsoft Teams, which is exactly the routing I want on call, with ownership rules assigning issues to code owners. Jira issues are created and synced, GitHub and GitLab link commits and pull requests, deploy notifications arrive from CI, and the CLI, MCP server and a broad REST API cover automation. Seer's AI debugging has a published privacy overview and the AI providers appear in the subprocessor list, though we found no public information on scheduled digest or weekly reports. 2 5 6 9 11 16
The Data Protection Officer
The routing to the person who fixes it is broad: Slack, Microsoft Teams, Discord, PagerDuty, Opsgenie and SMS notifications, create-and-sync Jira integration, GitHub with suspect commits and PR comments, GitLab, Linear and Azure DevOps, deploy notifications from GitHub Actions, Netlify and Vercel, a documented REST API with webhooks, a CLI, and ownership rules that auto-assign issues to the committer. The AI debugger's providers appear by name in the subprocessor list as AI/ML services, and a dedicated AI privacy overview exists. I found no public information on scheduled digest reports or an opt-out from AI processing, which is the one thing I would want in writing before an agency turns it on. 2 5 6 7 9 16
The Skeptic
Notifications reach Slack, Teams, Discord, PagerDuty, Opsgenie and SMS, Jira issues are created and synced, deploys arrive from GitHub Actions, Netlify and Vercel with source map uploads, and a documented REST API covers alerts, releases and SCIM, with Seer generating fixes under a published privacy overview and the AI providers named in the subprocessor list. We found no public information on scheduled digest or weekly reports, and the captured pages do not tie a named model to Seer itself. 5 6 7 9 11 16
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
SDK-side data filtering, PII scrubbing named in the data processing agreement, inbound filters that drop events before they count, and IP address storage that can be switched off entirely give me the controls I need for shop customer addresses. Retention is stated per plan, trace sampling is configurable, spike protection notifications exist, and a maximum spend setting on top of tiered pay-as-you-go error rates keeps one client's runaway cron job from detonating the invoice; export, deletion and a self-hosted edition are documented too. We found no public information on server-side scrubbing rules with worked examples or on retention settings per project. 10 9 13 8 15
The SaaS CTO
SDK-side data filtering, PII scrubbing, disabling IP storage and inbound filters that drop events before they count are documented, retention is stated per plan from a 30-day lookback up to 90 days with custom on Enterprise, and spend notifications with a maximum spend limit sit on top of base-quota-plus-pay-as-you-go billing. Export and deletion are described in the documentation, event data becomes inaccessible within 24 hours of account deletion, and both a Frankfurt data region and a self-hosted edition exist. We found no public information on custom server-side scrubbing rules with examples, per-project retention, or stated feature parity for self-hosting. 10 9 13 8 6 15
The Mobile Team Lead
SDK-side filtering, disabling IP storage, PII scrubbing, inbound filters that drop events before they count, spend caps, spike-protection notifications, retention from thirty up to ninety days depending on plan, hourly encrypted backups deleted after ninety days, and documented export and deletion features cover most of what our privacy officer asks me for, and a self-hosted edition exists. I found no public information on custom server-side scrubbing rules with examples or on retention configured per project. 6 9 10 13
The Site Reliability Engineer
PII scrubbing, documented SDK-side filtering, switchable IP storage and inbound filters that drop events before they count give me real control over what a payment stack sends. Retention is stated per plan from a 30-day to a 90-day lookback with custom at the top, spike protection has its own API notifications, spend caps and pay-as-you-go overage keep the invoice predictable mid-incident, and account deletion makes event data inaccessible within 24 hours alongside a documented self-hosting option. We found no public information giving worked examples of custom server-side scrubbing rules. 6 7 9 10 15
The Data Protection Officer
Scrubbing is documented on the SDK side with configuration to filter data for security and privacy purposes, PII scrubbing is named in the data processing agreement, IP address storage can be disabled, and inbound filtering drops events before they count; retention is stated per plan with 30-day and 90-day lookbacks, backups are deleted after 90 days, account deletion makes event data inaccessible within 24 hours, and export and deletion are contractual. Volume is controlled by plan quotas, spike-protection notifications, pay-as-you-go rates and a maximum spend setting. I found no public information with worked examples of custom server-side scrubbing rules, per-project retention settings, or deletion of individual events, which is what my audit trail for member data would need. 6 7 8 9 10 13 15
The Skeptic
Retention is stated per plan, sampling is configurable, inbound filtering and spike protection exist, spend can be capped with notifications, overage is billed per unit at published tiered rates, and export plus deletion are documented. Scrubbing, though, appears only as headings — SDK filtering configuration and "PII Scrubbing" — with no custom server-side rules or examples shown, and we found no per-project retention settings or documented deletion of a single event or user. 3 7 9 10 13 15
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
Organisation roles, two-factor with YubiKey or TOTP, SAML single sign-on with SCIM on the Business and Enterprise plans, audit logs and AES-256 encryption in transit and at rest are all stated, and behind them sit SOC 2 Type II and ISO 27001 available on request, an annual third-party penetration test and a public status page with ninety days of uptime and incident history. The captured terms provide the service 'AS IS' and state no service levels for no-charge products, and we found no public information on an uptime commitment with credits or on SDK behaviour during a vendor outage. 10 12 13
The SaaS CTO
The audit story holds up: organisation roles from Member to Owner, MFA with YubiKey and TOTP, SAML SSO with SCIM on Business and Enterprise, an audit log of every user action with time and IP, AES-256 in transit and at rest, SOC 2 Type II and ISO 27001 available through the account or on request, annual third-party penetration tests, and a public status page with 90 days of uptime history, component-level status and past incidents. For the vendor's own bad day there is region-wide failover to a duplicate environment and hourly encrypted backups across regions. We found no published SLA with credits, no bug bounty, and no documentation of what the SDKs do while ingestion is down. 10 12 11 15 13
The Mobile Team Lead
SAML single sign-on with SCIM on Business and Enterprise, two-factor with YubiKeys, organisation roles, a chronological audit log, AES-256 encryption in transit and at rest, SOC 2 Type II and ISO 27001 available to customers, annual independent penetration tests, a vulnerability disclosure contact, hourly multi-region backups with region failover, and a status page publishing ninety days of uptime with an incident history is most of an audit pack in one place. The captured terms provide the service as is with no service levels, and I found no documentation of how the SDKs behave when Sentry itself is down. 10 12 13
The Site Reliability Engineer
SAML SSO and SCIM on Business and Enterprise, YubiKey MFA, roles, audit logs and AES-256 encryption in transit and at rest will pass our auditors, backed by SOC 2 Type II and ISO 27001 available on request and annual third-party penetration tests. The status page publishes 90-day per-component history and an incident archive, and there is a vulnerability contact with a PGP key. But the terms deliver the service "AS IS" with no published availability commitment or credits, and we found no public information on how the SDK behaves when ingestion itself is down. 10 11 12 13
The Data Protection Officer
This survives a compliance review: five organisation roles, SAML single sign-on with SCIM on Business and Enterprise, YubiKey or TOTP two-factor, an audit log recording every action with time and IP address, AES-256 encryption in transit and at rest, SOC 2 and ISO 27001 available on request, annual independent penetration tests, a vulnerability disclosure contact with a PGP key, region failover on Google Cloud, and a public status page with 90-day uptime and past incidents. I found no public information on a published service level agreement with credits or on how the SDKs behave when the vendor's ingestion is down, so I stop short of the highest level. 10 11 12 13
The Skeptic
SAML SSO with SCIM on Business and Enterprise, five organisation roles, audit logs with IP addresses, AES-256 in transit and at rest, SOC 2 Type II and ISO 27001 available to customers, annual third-party penetration tests, a vulnerability contact with a PGP key, and a status page with 90-day component history and a public incident archive. We found no published SLA with credits — the terms promise only reasonable efforts during business hours — and no documentation of how the SDK behaves when ingestion itself is down. 10 12 13
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
An EU region is chosen when the organisation is created — de.sentry.io in Frankfurt, Germany, on Google Cloud — with a published data processing agreement, a subprocessor list naming locations including Anthropic, OpenAI, SendGrid and Intercom in the United States, and ISO 27001 and SOC 2 stated. However the contracting entity is Functional Software, Inc. of San Francisco under California governing law, and the documentation states that user accounts, audit logs, SSO metadata and detailed usage data are stored in the United States regardless of the chosen region. The transparency is unusually strong; the chain itself is only partly European. 8 16 14 11
The SaaS CTO
The EU story is answerable for enterprise customers: a customer-selected EU region at de.sentry.io in Frankfurt covering error events, transactions, spans, profiles, logs, metrics and session replays with their backups, a published subprocessor list with locations, a data processing addendum, and ISO 27001 and SOC 2 stated. The pages state plainly that user accounts, organisation settings, audit logs and SSO metadata stay in the US regardless of the chosen region, that support interactions are stored in the US, and that the AI models, email delivery and support subprocessors are US companies — with standard contractual clauses and Data Privacy Framework self-certification as the stated safeguards. The contracting entity is Functional Software, Inc. of San Francisco with an Amsterdam EU representative, so the chain is disclosed and safeguarded rather than European, and self-hosting remains the documented way to keep everything on my own servers. 8 16 14 10 11 6
The Mobile Team Lead
An EU region in Frankfurt on Google Cloud with its own domain and a detailed data-storage-location page, a published data processing agreement built on standard contractual clauses plus Data Privacy Framework certification, an EU representative in the Netherlands, and a subprocessor list naming every provider with its location, including Anthropic and OpenAI in the United States for AI, are all documented. The contracting entity and governing law remain in the United States, and user accounts, audit logs, single sign-on metadata and support interactions are stored in the US regardless of the region I choose, so the chain is mixed rather than European. 8 13 14 15 16
The Site Reliability Engineer
A Frankfurt EU region chosen at organization creation keeps service data in the EU, subprocessors are listed with their locations, a data processing agreement is published with standard contractual clauses and Data Privacy Framework safeguards, and SOC 2 and ISO 27001 are stated. However the contracting entity is Functional Software, Inc. of San Francisco with only a Dutch EU representative, user accounts, audit logs, SSO metadata and support interactions stay in the US regardless of region choice, and the AI, email and support subprocessors are all US-based. That is more than a bare EU-region option but well short of an EU-owned chain. 8 10 14 15 16
The Data Protection Officer
An EU region on named Google Cloud infrastructure in Frankfurt, chosen when the organisation is created, holds error events, transactions, spans, profiles, logs, metrics, replays, debug symbols and their backups in the EU; the subprocessor list names every entity with purpose and location and offers an RSS feed for changes, the data processing addendum is published with standard contractual clauses and Data Privacy Framework self-certification, and ISO 27001 and SOC 2 are stated. But the contracting party is Functional Software, Inc. of San Francisco under California law, the AI models (Anthropic, OpenAI), email delivery (SendGrid) and support tooling (Intercom) sit in the United States, and with the EU region selected user accounts, organisation audit logs, detailed usage data and SSO metadata are still stored in the US, as is anything shared in a support ticket. A mixed chain I can contract around, not a sovereign one. 7 8 13 14 15 16
The Skeptic
An EU region on Google Cloud in Frankfurt with its own domain is chosen at organisation creation, the subprocessor list is public with locations, a DPA is published with standard contractual clauses, and SOC 2 and ISO 27001 are stated. But the contracting entity is Functional Software, Inc. of San Francisco under California law with only a representative in Amsterdam, and even with the EU region selected, user accounts, audit logs, SSO metadata and detailed usage stay in the US while support, email delivery and the AI features run through US providers — credit to them for publishing exactly which data escapes the region, including uptime checks. 8 10 13 14 15 16
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
Plans, quotas and overage are public: Developer Free with 5k errors for one user, Team at $26/mo with 50k errors, 5M spans, 50 replays and up to a 90-day lookback, Business at $80/mo, Enterprise Custom, plus a tiered pay-as-you-go table for error overage and priced add-ons for logs, cron monitors, uptime alerts, profiling and the Seer AI debugger at $40/active contributor/month. Annual billing is shown at $26.00/mo with an annual total of $312.00/yr, taxes are stated as excluded in the terms, and a spend calculator alongside the maximum spend setting lets me model a client's real annual cost. We found no public information on span or replay overage rates or on the price of the self-hosted edition. 9 13
The SaaS CTO
A buyer can compute most of a year from public pages: Developer free with 5k errors, Team $26/mo with an annual total of $312.00/yr for 50k errors, 5M spans and up to a 90-day lookback, Business $80/mo adding SAML and SCIM, tiered pay-as-you-go error rates from $0.0003625 per error, and priced add-ons — Seer at $40/active contributor/month, Continuous Profiling at +$0.0315/hr, UI Profiling at +$0.25/hr, logs at +$0.50/GB. The calculator states it is an estimate only, overage is base quota plus pay-as-you-go, fees are exclusive of applicable taxes, invoices fall due in 30 days, and refund and cancellation terms are published. What blocks full computability: Enterprise is Custom, and we found no public price for the self-hosted edition or a per-span overage rate. 9 13 3
The Mobile Team Lead
Plan prices, quotas and overage are public in unusual detail: Developer free with 5k errors, Team $26/mo and Business $80/mo with 50k errors and 5M spans each, tiered per-error rates down to $0.0001500, logs at +$0.50/GB additional, cron monitors at +$0.78/monitor additional, uptime alerts at +$1.00/uptime alert additional, continuous profiling at +$0.0315/hr, the Seer add-on at $40/active contributor/month, an estimate calculator, annual and monthly terms, taxes excluded and thirty-day invoice terms. The per-span overage rate points to the docs rather than a number, Enterprise is custom, and I found no public price for the self-hosted edition. 3 9 13
The Site Reliability Engineer
Plans are priced publicly — a free Developer plan, Team at $26/mo with an annual total of $312.00/yr, Business at $80/mo — with per-plan quotas for errors, spans, logs, replays and monitors, tiered pay-as-you-go error rates, and add-on prices for Seer at $40/active contributor/month, continuous profiling at +$0.0315/hr and extra logs at +$0.50/GB. Billing terms are published: taxes excluded, 30-day invoices, auto-renewal and cancellation from account settings. Span overage pricing sits in the docs rather than the pricing page, Enterprise is "Custom", and we found no public price for the self-hosted edition or any EU-region surcharge. 3 9 13
The Data Protection Officer
The pricing pages publish plan prices with their volume limits (a free Developer plan for one user with 5k errors, Team at $26/mo and Business at $80/mo), quotas for spans, logs, replays, cron and uptime monitors, tiered pay-as-you-go error rates from $0.0003625 at the lowest band to $0.0001500 at 20M+, priced add-ons (logs at +$0.50/GB, the AI debugger at $40/active contributor/month, profiling by the hour), a calculator, and VAT and billing terms including auto-renewal, non-refundable fees and 30-day invoices. Span overages are deferred to the docs for their pricing, retention past the plan lookback is unpriced, Enterprise is Custom, and I found no public information on the self-hosted edition's licence. The annual cost is nearly computable from public pages, not fully. 3 9 13
The Skeptic
Plan prices with quotas, tiered per-error overage rates, add-on prices for Seer at $40/active contributor/month, Continuous Profiling at +$0.0315/hr and UI Profiling at +$0.25/hr, logs at +$0.50/GB, monitors at +$0.78 and +$1.00, annual totals, spend caps and cancellation mechanics are all public. Enterprise is "Custom", span overage pricing points to the docs rather than the pricing page, renewals revert to Sentry's then-current rates regardless of prior discounts, and we found no public price for the self-hosted edition — so a second-year total is not computable for a large buyer. 3 9 13
European sovereignty — proven facts
2 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 | Not determined | — | uncited Report an error |
| Hosting options |
Self-hostable
unverified
Why unverified?Self-hosting appears only in a migration note in the docs without deployment details, and an EU storage region is additionally selectable, which this value subsumes. |
1/1 pts | 8 Report an error |
| Open source | Not determined | — | uncited Report an error |
| Data processing agreement |
Published, self-serve
unverified
Why unverified?Acceptance works through Sentry's instructed process ('Follow our instructions to enter into our DPA') rather than a one-click flow, and the excerpt ends before the subprocessor list and schedules. |
1/1 pts | 15 Report an error |
| Transfer impact assessment | Not determined | — | uncited Report an error |
Questions about Sentry
Is Sentry European?
No. whats-best.ai classifies Sentry as Rest of world.
Where does Sentry store data?
The default storage location for customer data is not stated on the vendor’s pages as of 6 Nov 2026. The vendor’s pages mention the US, the EU, the United States and Germany as hosting locations, per the vendor’s page captured 6 Nov 2026.
Does Sentry have a free plan?
Yes. Sentry has a free plan, per the vendor’s page captured 6 Nov 2026.
What are the best alternatives to Sentry?
As of 18 Nov 2026, the panel rates Datadog APM & Error Tracking (3.5/5), Dynatrace (3/5) and Tideways (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: Sentry 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. Acceptance works through Sentry's instructed process ('Follow our instructions to enter into our DPA') rather than a one-click flow, and the excerpt ends before the subprocessor list and schedules.
- Weak sourcing — Hosting options. Self-hosting appears only in a migration note in the docs without deployment details, and an EU storage region is additionally selectable, which this value subsumes.
- 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.
- 8 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
- 6 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
- 2 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
- 2 subprocessors 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 pricing 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
- We read 19 of the 26 pages we planned to read for this product; the others could not be captured yet. Everything on this page rests on the pages we read. 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 (19)
The pages every claim on this page was read from — each one checked, dated, and kept verifiable.
- 1 Vendor homepage sentry.io Checked 6 Nov 2026 Details →
- 2 Features page (error monitoring) sentry.io Checked 6 Nov 2026 Details →
- 3 Features page (tracing) sentry.io Checked 6 Nov 2026 Details →
- 4 Features page (APM) sentry.io Checked 6 Nov 2026 Details →
- 5 Integrations page sentry.io Checked 6 Nov 2026 Details →
- 6 Documentation docs.sentry.io Checked 6 Nov 2026 Details →
- 7 API documentation docs.sentry.io Checked 6 Nov 2026 Details →
- 8 Documentation (data storage location) docs.sentry.io Checked 6 Nov 2026 Details →
- 9 Pricing page sentry.io Checked 6 Nov 2026 Details →
- 10 Security / trust page sentry.io Checked 6 Nov 2026 Details →
- 11 Trust center sentry.io Checked 6 Nov 2026 Details →
- 12 Public status page status.sentry.io Checked 6 Nov 2026 Details →
- 13 Terms of service sentry.io Checked 6 Nov 2026 Details →
- 14 Privacy policy sentry.io Checked 6 Nov 2026 Details →
- 15 Data processing agreement (dpa) sentry.io Checked 6 Nov 2026 Details →
- 16 Subprocessor list sentry.io Checked 6 Nov 2026 Details →
- 17 Error capture, grouping & triage — found from sitemap docs.sentry.io Checked 6 Nov 2026 Details →
- 18 Error capture, grouping & triage — found from sitemap docs.sentry.io Checked 6 Nov 2026 Details →
- 19 APM, tracing & profiling — found from sitemap docs.sentry.io Checked 6 Nov 2026 Details →