Panel rating · 6 judges · How to read the stars

Category median

Sovereignty: 4 of 6 dimensions proven

0–5 in half steps. 5 means the rubric's top anchor is met on the evidence.

by Bugsink B.V. · www.bugsink.com

Compare with Sentry → Report an error on this page Is this your product? →

Link to this page

Bugsink: AI-assisted analysis on whats-best.ai Bugsink: AI-assisted analysis on whats-best.ai (dark)

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.

Bugsink at a glance

Vendor
Bugsink B.V.
Headquarters
Incorporated in the Netherlands source, captured 6 Nov 2026
Data hosting
In the EU; pages mention the Netherlands 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 Bugsink 2.5/5, the mean of 6 judges. Bugsink is a Sentry-SDK-compatible error tracker from Bugsink B.V. how scores are made
As of
Vendor pages captured 6 Nov 2026; evaluated by the panel 6 Nov 2026. all sources

Bugsink alternatives, European ones first →

Read this page as one judge. Each weighs the same scores by what they care about.

The Site Reliability Engineer

Weighted verdict

Site reliability engineer on the on-call rota of a payments platform in Amsterdam, woken at night when checkout latency climbs. Wants alerts on error rates and latency percentiles, not on every single exception, routed to PagerDuty with the trace attached, spike protection so an incident does not also blow the quota, SSO and audit logs for the auditors, and a vendor whose own status page and SLA say what happens when the monitoring is the thing that is down.

Same scores as the panel view — this lens weights them the way this judge cares.

Scored by The Site Reliability Engineer

Panel median The Site Reliability Engineer This judge’s scores over the panel median. Each label opens its reasoning below.
Scores per criterion, in stars out of 5
Criterion Panel median The Site Reliability Engineer
Error capture, grouping & triage 3.5 of 5 3.5 of 5
APM, tracing & profiling 0 of 5 0 of 5
Alerting, integrations & developer workflow 2.5 of 5 2.5 of 5
Data scrubbing, retention & volume control 2 of 5 2 of 5
Access control, security & the vendor's reliability 2 of 5 2 of 5
European sovereignty 4 of 5 4 of 5
Pricing transparency 2.5 of 5 2.5 of 5

Error capture, grouping & triage

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.

Report an error

The Site Reliability Engineer

Sentry SDK compatibility brings the mainstream backend and browser platforms in by a DSN change, and the grouping work is unusually deep: custom fingerprints, value-by-value normalization of identifiers and addresses, a per-project algorithm switch with a 30-day transition, and a grouping tab that shows the automatic keys. Stack traces sit at the center of the interface with code, local variables and full request context, sourcemaps and debug-file bundles are documented down to the debug-ID lookup, and resolve, mute and regression states are reachable through the API. We found no public information on mobile crash-free metrics, suspect commits or code owners, or merging and splitting issues. 1 2 3 12 13 14

Report an error

APM, tracing & profiling

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.

Report an error

The Site Reliability Engineer

The vendor's own SDK-compatibility page positions Bugsink as error tracking "without the overhead of full APM", and nothing captured shows endpoint timings, percentiles, distributed traces or profiling — the only performance-adjacent detail is a transaction name folded into the grouping key. For a buyer needing latency and throughput views this is an errors-only tool by the vendor's own statement. 3 12

Report an error

Alerting, integrations & developer workflow

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.

Report an error

The Site Reliability Engineer

Alerts fire on new issues, regressions and mute-condition crossings rather than every event, with email resolved across user, team and project levels and per-project destinations for Slack, Microsoft Teams, Mattermost, Discord, Telegram or a custom JSON webhook, backed by an outbound allow/deny policy and a test-delivery button. The REST API is genuinely well documented — OpenAPI schema and Swagger UI served by every installation, scoped bearer tokens, issues resolvable and mutable by API, sentry-cli uploads working. We found no public information on PagerDuty or Opsgenie routing, issue tracker sync such as Jira or GitHub, or scheduled digests, which is what keeps me from scoring the on-call workflow higher. 5 14 15

Report an error

Data scrubbing, retention & volume control

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.

Report an error

The Site Reliability Engineer

Retention and volume are documented well: a 60-day raw event period recorded in the DPA with deletion or return within 30 days on termination, a self-hosted decay model with an optional hard age cap, and per-project five-minute and hourly rate limits with documented 429 back-off. Full event payloads are retrievable through the API, and the self-hosted edition keeps everything on the customer's own servers. We found no public information on scrubbing of secrets or personal data, IP anonymisation, sampling, or what happens to a managed plan at its event cap. 4 9 11 14 16

Report an error

Access control, security & the vendor's reliability

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.

Report an error

The Site Reliability Engineer

The permissions model is documented — teams and projects with admin members, superusers, and API tokens scoped by capability — though flagged as beta, and TLS, restricted production access, security updates, security logging, per-customer database separation and automatic backups are stated, with a DPA covering breach notification and audits under conditions. We found no public information on two-factor authentication, single sign-on, encryption at rest, certifications such as ISO 27001 or SOC 2, a public status page, or a stated SLA; as the person woken at night I would want the vendor's own incident posture on record before betting the rota on it. 4 10 11 14 17

Report an error

European sovereignty

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.

Report an error

The Site Reliability Engineer

The chain is European and named: Bugsink B.V. of Utrecht as contracting entity under Dutch law and Dutch courts, hosted application data stored and processed in the EU on Hetzner, with Scaleway for transactional email and Stripe confined to payment processing with no error data shared, all listed in a published DPA that sets a 60-day retention period and advance notice of subprocessor changes. A documented self-hosted edition keeps every event on the customer's own servers with vendor access disclaimed. What holds it below the top level is that no security certifications are published and self-hosted instances do send periodic phone-home messages carrying usage, deployment and licence metadata. 4 8 9 10 11

Report an error

Pricing transparency

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.

Report an error

The Site Reliability Engineer

Six managed tiers are public with price and event volume — free at 15K monthly events, then €16 a month for 75K up to €1,288 for 50M, unlimited users and teams on paid plans, a 28-day paid-plan trial, and higher volumes on request, with flat pricing and no per-event billing claimed for self-hosting. A buyer still cannot compute the full annual cost: we found no public information on overage or cutoff behaviour at the cap, VAT, annual versus monthly terms, or the price of the self-hosted licence that the phone-home messages imply exists. 1 3 4 9

Report an error

European sovereignty — proven facts

4 of 6 dimensions proven

Built only from facts shown on the vendor's own pages. A dimension we could not prove is left open, not scored as zero.

Hosting location EU only unverified
Why unverified?

Stripe is listed as a subprocessor for payment processing without its location being stated, though the DPA says no error events, logs or application data are shared with it.

4/4 pts 11 Report an error
Hosting options Self-hostable 1/1 pts 1 Report an error
Open source Not determined — uncited Report an error
Data processing agreement Not determined — uncited Report an error
Transfer impact assessment Not needed, no transfer outside the EU/EEA unverified
Why unverified?

No transfer impact assessment is mentioned anywhere; the EU-only claim leaves the payment subprocessor Stripe's location unstated, though the DPA says no application data is shared with it.

1/1 pts 11 Report an error

Questions about Bugsink

Is Bugsink European?

Yes. whats-best.ai classifies Bugsink as EU-Made. Its vendor, Bugsink B.V., is incorporated in the Netherlands, per the vendor’s page captured 6 Nov 2026.

Where does Bugsink store data?

Bugsink stores customer data in the EU, per the vendor’s page captured 6 Nov 2026. The vendor’s pages mention the Netherlands as hosting location, per the vendor’s page captured 6 Nov 2026.

Does Bugsink have a free plan?

Yes. Bugsink has a free plan, per the vendor’s page captured 6 Nov 2026.

What are the best alternatives to Bugsink?

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: Bugsink alternatives.

Where this could be wrong

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.

Sources (17)

The pages every claim on this page was read from — each one checked, dated, and kept verifiable.

  1. 1 Vendor homepage (with pricing) www.bugsink.com Checked 6 Nov 2026 Details →
  2. 2 Features page (error tracking) www.bugsink.com Checked 6 Nov 2026 Details →
  3. 3 Features page (SDK compatibility) www.bugsink.com Checked 6 Nov 2026 Details →
  4. 4 Features page (managed hosting) www.bugsink.com Checked 6 Nov 2026 Details →
  5. 5 Documentation www.bugsink.com Checked 6 Nov 2026 Details →
  6. 6 Documentation (self-hosting) www.bugsink.com Checked 6 Nov 2026 Details →
  7. 7 Security / trust page www.bugsink.com Checked 6 Nov 2026 Details →
  8. 8 About page www.bugsink.com Checked 6 Nov 2026 Details →
  9. 9 Terms of service www.bugsink.com Checked 6 Nov 2026 Details →
  10. 10 Privacy policy www.bugsink.com Checked 6 Nov 2026 Details →
  11. 11 Data processing agreement (dpa) www.bugsink.com Checked 6 Nov 2026 Details →
  12. 12 Error capture, grouping & triage — found from sitemap www.bugsink.com Checked 6 Nov 2026 Details →
  13. 13 Error capture, grouping & triage — found from sitemap www.bugsink.com Checked 6 Nov 2026 Details →
  14. 14 Alerting, integrations & developer workflow — found from sitemap www.bugsink.com Checked 6 Nov 2026 Details →
  15. 15 Alerting, integrations & developer workflow — found from sitemap www.bugsink.com Checked 6 Nov 2026 Details →
  16. 16 Data scrubbing, retention & volume control — found from sitemap www.bugsink.com Checked 6 Nov 2026 Details →
  17. 17 Access control, security & the vendor's reliability — found from sitemap www.bugsink.com Checked 6 Nov 2026 Details →