Bugsink
EU-Made Report an errorPanel rating · 6 judges · How to read the stars
Category median
Sovereignty: 4 of 6 dimensions proven
0–5 in half steps. 5 means the rubric's top anchor is met on the evidence.
by Bugsink B.V. · www.bugsink.com
Compare with Sentry → 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.
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
Read this page as one judge. Each weighs the same scores by what they care about.
The panel's verdict
Bugsink is a Sentry-SDK-compatible error tracker from Bugsink B.V. of Utrecht, offered managed or self-hosted. Sovereignty is the strongest verdict, scored 8 with no variation: a Dutch contracting entity, Dutch law and courts, hosted application data stated to be stored and processed in the EU, named subprocessors, and a public data processing agreement. Error tracking scores cluster at 6 to 7 on documented grouping and a stacktrace-first interface; performance tracing is scored 0 throughout, matching the vendor's own positioning as error tracking "without the overhead of full APM". The flagged splits report none, though workflow and integrations spans 4 to 6 — the top score credits the alerting design and REST API, the lowest notes no public information on issue-tracker or on-call integrations. Data controls spans 4 to 5 and pricing transparency 5 to 6, both one-point gaps. Judges repeatedly found no public information on data scrubbing, two-factor authentication, certifications, or the self-hosted licence price.
Speaks for it
- Sovereignty scored 8 with no variation in the table, on a Dutch legal entity under Dutch law and courts, hosted application data stated to be stored and processed in the EU, and subprocessors named in a public DPA (Hetzner, Scaleway, Stripe for payment only).
- Error tracking scored 6 to 7, on Sentry-SDK compatibility by DSN change, stacktraces with local variables and full request data, and grouping documented with custom fingerprints, value normalisation and a grouping tab.
- Alerts fire on new issues, regressions and unmutes and deliver to email, Slack, Mattermost, Discord, Microsoft Teams, Telegram and custom webhooks, with per-project destinations, an outbound allow/deny policy and a test button.
- Managed pricing is published in full — free at 15K monthly events with 5K retained, paid plans from €16 for 75K to €1,288 for 50M events per month, unlimited users and teams on paid plans, and a 28-day trial of a paid plan.
- Retention and volume controls are documented in depth — 60-day raw event retention in the DPA, per-project 5-minute and hourly rate limits that return 429, an optional hard event-age cap, and a self-hosted edition documented to keep every event on your own servers.
Held against it
- Performance tracing scored 0, and the captured pages describe no transaction timings, traces, profiling or real-user monitoring — the vendor states it is error tracking "without the overhead of full APM".
- We found no public information on scrubbing of passwords, tokens or personal data, IP anonymisation, sampling or filters before ingestion, while error payloads can carry request bodies, headers and local variables.
- We found no public information on two-factor authentication, single sign-on, encryption at rest, ISO 27001 or SOC 2, a public status page or an SLA, and the permissions model is explicitly flagged as beta.
- We found no public information on issue-tracker integrations, on-call routing such as PagerDuty or Opsgenie, CI deploy hooks or scheduled digests.
- We found no public information on the self-hosted licence price, quota-exceed behaviour, annual versus monthly terms or VAT, so the full annual cost of either route is not computable from the captured pages.
Best for
- Your team already runs Sentry SDKs and wants error tracking with hosted application data stated to be stored and processed in the EU, adoptable with a DSN change.
- You need a public DPA with named subprocessors for procurement, plus a self-hosted option documented to keep every event on your own servers.
- You want error tracking and alerting only, and have no need for traces, profiling or real-user monitoring.
- You want published flat pricing with unlimited users and teams on paid plans.
Avoid if
- You need performance tracing, distributed traces or profiling — the criterion scored 0 and the vendor states the product is error tracking without the overhead of full APM.
- Your workflow depends on issue-tracker sync or on-call paging — workflow and integrations scored 4 to 6, and the captured pages describe neither.
- Your procurement requires published certifications, single sign-on or two-factor authentication — security and reliability scored 4 and we found no public information on these.
- You must compute a full annual cost before committing — quota behaviour, VAT, annual terms and the self-hosted licence price are undocumented, and pricing transparency spans 5 to 6 on exactly this gap.
The scores
| Criterion | Panel median |
|---|---|
| Error capture, grouping & triage | 3.5 of 5 |
| APM, tracing & profiling | 0 of 5 |
| Alerting, integrations & developer workflow | 2.5 of 5 |
| Data scrubbing, retention & volume control | 2 of 5 |
| Access control, security & the vendor's reliability | 2 of 5 |
| European sovereignty | 4 of 5 |
| Pricing transparency | 2.5 of 5 |
Error capture, grouping & triage
Show reasoningHide reasoning
How this is scored
What happens to an exception or crash: SDKs for the languages, frameworks and platforms a team runs (PHP and Laravel, JavaScript in the browser and Node, Python, Ruby, Java, .NET, Go, iOS, Android, Flutter, React Native), stack traces with source maps and symbolication, context (request, user, breadcrumbs, environment, local variables), grouping and custom fingerprints, deduplication, issue states (resolved, ignored, regressed), releases and deploy tracking, suspect commits, crash-free sessions and users for mobile apps, and search and filters over issues.
0 — Catches no application errors or crashes; a log viewer or an external check only.
3 — Errors from one or two platforms arrive with a stack trace and are grouped; context, issue states, releases and source maps are basic or not described.
5 — SDKs for the common web and backend platforms, stack traces with source maps, request and user context and breadcrumbs, automatic grouping with issue states and regression detection, release and deploy tracking, and issue search and filters.
8 — SDKs across backend, frontend and mobile with symbolication documented, custom fingerprinting and merge or split of issues, suspect commits or code owners, crash-free users and sessions, local variables or source context per frame, and every SDK documented with its configuration options.
10 — Error tracking a large engineering organisation standardises on: every platform it runs covered with parity stated, grouping rules editable and explained, release health with adoption and regression per version, and the full issue lifecycle reachable by API.
The Agency Tech Lead
Sentry-SDK compatibility covers my PHP, JavaScript, Python and Go apps with the documented official SDKs, and the stacktrace-first view shows local variables, full request data and sourcemaps resolved by debug ID. Grouping is documented in real depth — normalization of IDs, emails, URLs and numbers, custom fingerprints with a grouping tab, regression detection and release-tied resolution — though we found no public information on breadcrumbs, merging or splitting issues, suspect commits or mobile crash-free reporting. 1 2 3 12 13 14
The SaaS CTO
Sentry SDK compatibility means my Go, Python and TypeScript services keep their instrumentation with a DSN change, and the core capture is strong: stack traces centred in the UI with local variables and source context, sourcemaps resolved through debug IDs and artifact bundles, request, header, environment and custom context, issue states with regression detection, and grouping documentation deeper than most vendors — custom fingerprinting with the default key, normalization of UUIDs, emails, IPs and numbers, and a grouping tab that explains the key. I found no public information on suspect commits tying a regression to the change that caused it, on merging or splitting issues, on mobile symbolication and crash-free sessions, or on breadcrumbs, which is where a large team would feel it. 2 3 12 13 14
The Mobile Team Lead
Grouping is the strongest part: events are auto-grouped with value normalization, custom fingerprints and a grouping tab, and issues carry resolved, resolved-in-next-release, muted and regressed states. Stacktraces arrive with local variables, full request info and tags across release, environment and user, sourcemaps and debug-file upload via sentry-cli are documented, and every Sentry SDK — including the ones our iOS, Android and Flutter apps already use — points at Bugsink with a DSN change. What I found no public information on is crash-free users or sessions per release, breadcrumbs, suspect commits, and merging or splitting issues, which is what would stop a bad store rollout for us. 2 3 12 13 14
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
The Data Protection Officer
Sentry-compatible SDKs cover the common web and backend languages, and the stack trace is the centre of the interface with local variables, request data and sourcemaps resolved through debug-ID matching. Grouping is automatic with custom fingerprints, a grouping tab that exposes the keys, and issue states including resolved-in-next-release and regression alerts. We found no public information on mobile crash reporting, native symbolication, or crash-free session and user metrics. 2 3 12 13
The Skeptic
Standard Sentry SDKs connect by a DSN change, so platform coverage comes from Sentry's own SDKs, and the stack trace is the centre of the interface with local variables, request data, tags and source maps resolved by debug-ID lookup. Grouping is documented deeper than most: value normalisation rules with the exact patterns recognised, custom fingerprints with a default-key token, resolve/mute/regression states, a grouping tab showing the keys, and a 30-day transition when you switch grouping algorithm. We found no public information on mobile crash metrics, suspect commits or merging and splitting of issues. 1 2 3 12 13 14
APM, tracing & profiling
Show reasoningHide reasoning
How this is scored
How the product shows where time goes: transaction and endpoint timings with percentiles, slow database queries and N+1 detection, background jobs and queues, external HTTP calls, distributed tracing across services, OpenTelemetry ingestion, code-level profiling, frontend performance and Core Web Vitals (real user monitoring), host or container metrics beside the traces, anomaly detection on throughput and latency, and the link from a slow trace to the error it caused.
0 — No performance data of any kind; errors only.
3 — Response times per endpoint or a simple performance view; tracing across services, query analysis and profiling are basic or not described.
5 — Transaction timings with percentiles per endpoint, slow query and N+1 detection, background job monitoring, distributed tracing across services, a link between traces and errors, and frontend performance or Web Vitals offered.
8 — OpenTelemetry ingestion documented, code-level or continuous profiling, real user monitoring with Web Vitals, host and container metrics beside the traces, anomaly detection on latency and throughput, and sampling of traces configurable with its effect explained.
10 — Full application performance management evidenced: traces, profiles, frontend and backend joined end to end, service maps, SLOs on endpoints, and every signal documented with its retention and sampling per plan.
The Agency Tech Lead
The vendor states the scope itself: "Bugsink is error tracking without the overhead of full APM." We found no public information on transaction timings, query analysis, distributed tracing, profiling or web vitals; the server monitoring described is the vendor watching its own managed infrastructure, not a feature for my applications. 3 4
The SaaS CTO
The vendor's own page positions this as error tracking "without the overhead of full APM", and no captured page shows transaction timings, distributed traces, OpenTelemetry ingestion, profiling or real-user monitoring — the monitoring described covers the vendor's own service, not my application. For me, wanting one trace from the click in the browser to the slow database call three services down, the product states itself it is not that tool. 3 8
The Mobile Team Lead
The vendor states Bugsink is error tracking "without the overhead of full APM", so there are no transactions, traces, spans or profiles to evaluate. The only monitoring described is of the vendor's own servers for the hosted service — server load, memory, response times, ingestion and worker queues — which tells me nothing about my apps' performance. I found no public information on endpoint timings, distributed tracing, OpenTelemetry ingestion or profiling. 3 4
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
The Data Protection Officer
The captured pages state the product is "error tracking without the overhead of full APM", so no transaction timings, traces or profiling of customer applications are documented; the server monitoring the vendor describes covers its own managed service, not the customer's app. This is a deliberate positioning of the product as a different kind of tool. 3 4
The Skeptic
The vendor states the focus is "error tracking without the overhead of full APM", and the captured pages describe no transaction timings, traces, profiling or real-user monitoring — the monitoring mentioned is of the vendor's own servers. That is a stated scope decision, and for this criterion it sits at the bottom: errors only. 3 4
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 fire on new issues, regressions and unmuted issues, deliverable per project to email, Slack, Mattermost, Discord, Teams, Telegram or a custom JSON webhook with outbound allow/deny controls, validation and a test button — that per-project destination model is exactly what a forty-site maintenance shop needs. The REST API is solid, with OpenAPI served per installation, scoped tokens and the full issue lifecycle reachable, but we found no public information on issue tracker integrations, an on-call service, AI error explanations or scheduled reports. 2 14 15
The SaaS CTO
Alerting is genuinely well designed — triggers on new issues, regressions and mute conditions, email preferences resolved per project, team and user, delivery to Slack, Mattermost, Discord, Microsoft Teams, Telegram and custom webhooks with validation and an outbound allow/deny policy, and delivery failures recorded and cleared — and the REST API is first class: OpenAPI schema with Swagger UI, scoped bearer tokens, Sentry-compatible paths and issue resolution reachable end to end. I found no public information on issue-tracker integrations such as Jira, GitHub or GitLab, on on-call routing to PagerDuty or Opsgenie, on source-code and commit links or scheduled digests, and sentry-cli support covers only the standard upload endpoints. 5 13 14 15
The Mobile Team Lead
Alerts fire on new issues, regressions and unmute conditions — including conditional rules like alerting only above five events a day — and reach email, Slack, Teams, Discord, Telegram and custom webhooks with validation and outbound allow/deny controls, on top of a documented REST API with an OpenAPI schema and scoped tokens. There is no issue tracker integration, no on-call tool like PagerDuty, no CI deploy hooks and no scheduled digests described, so a fix still has to be carried into Jira by hand. The regression alert gets close to my "new release crashes more" need, but nothing compares release against release automatically. 2 13 14 15
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
The Data Protection Officer
Alerts fire on new issues, regressions and unmutes, with time-based and volume-based mute conditions, delivered by email or Slack, Mattermost, Discord, Microsoft Teams, Telegram and custom webhooks, under an outbound allow/deny policy with destination validation. The REST API is documented with its own OpenAPI schema and Swagger UI, plus sentry-cli uploads for releases and debug files. We found no public information on issue tracker integrations, an on-call tool, scheduled reports, or AI fix suggestions with a named model. 2 14 15
The Skeptic
Alerting is genuinely worked out — new issue, regression and unmute triggers, email plus Slack, Mattermost, Discord, Teams, Telegram and custom webhooks, per-project routing, a test button, delivery-failure recording and an outbound allow/deny policy — and the REST API is well documented with OpenAPI, scoped bearer tokens and cursor pagination. But we found no public information on issue tracker integrations, an on-call tool or deploy hooks from CI, and sentry-cli support covers only the standard upload endpoints. No AI features are described. 5 13 14 15
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
Retention and volume are documented unusually well — 60 days raw by the DPA, a decay model that can extend retention for low-volume issues, an optional hard age cap, and per-project rate limits with 5-minute and hourly windows — and the self-hosted edition keeps every event on our own servers with no vendor access. But my shops hold customer addresses in request bodies, and we found no public information on scrubbing rules, IP anonymisation, sampling or filters before ingestion; the privacy policy lists IP addresses and user identifiers among the data processed. 9 10 11 16
The SaaS CTO
Volume and retention controls are documented in real depth — per-project five-minute and hourly rate limits that answer with a 429, a decay-based retention model with an optional hard cap on maximum event age, sixty-day raw event retention written into the DPA, deletion or return within thirty days on termination, issue deletion via the API, and a self-hosted edition that keeps every event on our own servers. For a product that captures request bodies, headers and local variables, though, I found no public information on scrubbing of secrets or personal data, IP anonymisation, or filters that drop events before they count. 9 11 14 16
The Mobile Team Lead
Retention is unusually well documented: 60 days for raw event data under the DPA, a decay model that can stretch low-volume data to years, and an optional hard maximum event age for legal or privacy reasons. Per-project rate limits with 5-minute and hourly windows cap volume, issues and full event payloads are reachable and deletable through the API, and the self-hosted edition keeps every event on our own servers. I found no public information on scrubbing of passwords or tokens, IP anonymisation, sampling, or filters that drop events before ingestion. 9 11 14 16
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
The Data Protection Officer
Raw event data — which the vendor itself says can include IP addresses, user identifiers and application data in error payloads — is retained 60 days, aggregated data is held until the controller removes it, return or deletion happens within 30 days of termination, rate limits are configurable per project, an optional hard event-age cap exists for legal or privacy reasons, and a self-hosted edition keeps events on our servers with the vendor stating it has no access. What I could not find is scrubbing: no server-side or SDK rule for passwords, tokens or personal data, no IP anonymisation, no sampling and no pre-ingestion filters are documented, which is what I would ask about before a member portal sends request bodies there. 9 10 11 16
The Skeptic
Retention is documented properly — 60 days for raw hosted event data in the DPA, a decay model with an optional hard maximum event age for installations that need an absolute cap, and deletion or return within 30 days of termination — and there are per-project rate limits that answer with a 429, plus a self-hosted edition documented as the same product keeping every event on your own servers. What I could not find is any scrubbing story: no server-side or SDK scrubbing of passwords, tokens or card numbers, no IP anonymisation and no event filters before ingestion are described anywhere in the captured pages. 4 9 10 11 16
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
Teams, projects, admin and member roles plus scoped API tokens are documented (the permissions model is flagged as beta), alongside TLS, restricted production access, security logging, automatic backups and a separate database per customer. We found no public information on two-factor authentication, single sign-on, certifications, a public status page, an SLA or encryption at rest, and it is a solo founder's operation — fine for us, but worth knowing before an audit. 4 8 11 17
The SaaS CTO
Teams and projects with admin members and superusers are documented, but the permissions model is marked beta and offers no granularity beyond admin; the DPA and managed-service pages state TLS, restricted production access, security logging, automatic backups, updates and a separate database per customer. I found no public information on single sign-on, two-factor authentication, customer-facing audit logs, encryption at rest, ISO 27001 or SOC 2, a public status page or an SLA — and it is a solo-founder operation, which matters when I weigh a vendor's bad day. 4 7 11 17
The Mobile Team Lead
Teams, projects, admin members and superusers are documented, and the DPA commits to TLS, restricted production access, security updates, security logging, breach notification and pre-agreed audits. The permissions model is explicitly beta and deliberately simple, run on Django's superuser flag. I found no public information on two-factor authentication, single sign-on or SCIM, ISO or SOC certifications, a public status page, an SLA, or how the SDKs behave when the vendor is unreachable. 4 7 11 17
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
The Data Protection Officer
Teams, projects, admin members and superusers are documented alongside scoped API tokens with per-capability 403 enforcement, TLS, restricted production access, security and incident logging, backups, and breach notification without undue delay. The permissions model is explicitly flagged as beta, and we found no public information on two-factor authentication, single sign-on, SCIM, encryption at rest, ISO 27001 or SOC 2, a status page or an SLA. 4 11 14 17
The Skeptic
Teams, projects, admin members and superusers are documented in a dedicated permissions page (explicitly in beta), TLS is stated, and the DPA lists restricted production access, regular security updates, security logging and breach notification without undue delay, with backups and per-customer storage separation described. We found no public information on two-factor authentication, single sign-on, encryption at rest, certifications, a public status page or an SLA — thin for a service holding your production errors. 4 11 17
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
Bugsink B.V. of Utrecht contracts under Dutch law, hosted application data is stated to be stored and processed in the EU, and the published DPA names the subprocessors — Hetzner for hosting, Scaleway for email, Stripe for payment only — with the relevant subprocessors stated to be EU-based. The self-hosted edition is documented to keep every event on our own servers with no vendor access, though it phones home usage, deployment and licence metadata, and no certifications are published. 4 8 9 10 11
The SaaS CTO
Bugsink B.V. of Utrecht contracts under Dutch law with Dutch courts, stores and processes hosted application data in the European Union, names its subprocessors — Hetzner for infrastructure, Scaleway for transactional email, Stripe for payment only — and publishes a DPA with breach notification, subprocessor change notice and objection rights. Add a self-hosted edition documented to keep error events on our own servers, and this covers what my enterprise customers ask about; no ISO 27001 or SOC 2 is published and the self-hosted edition does phone home usage and licence metadata, so it is not sovereign end to end. 8 9 10 11
The Mobile Team Lead
This is the strongest card for a Hamburg buyer: Bugsink B.V. in Utrecht supplies the service, hosted on European infrastructure with application data stored and processed in the EU, under a published DPA governed by Dutch law, with named subprocessors — Hetzner for infrastructure hosting, Scaleway for transactional email, and Stripe for payments only, with no error events or application data shared. Self-hosting is documented to keep every event on our own servers with no vendor access. The self-hosted software does send phone-home messages with usage metadata, and no ISO or SOC certification is published with its scope, which keeps it short of the top level. 4 8 9 11
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
The Data Protection Officer
The contracting entity is Bugsink B.V. of Utrecht under Dutch law with disputes in Dutch courts, the DPA is published and names Hetzner for infrastructure hosting, Scaleway for transactional email and Stripe for payment only, with relevant subprocessors stated EU-based and event data stored and processed in the EU. Self-hosting keeps every event on our own servers with the vendor stating it does not access them, though the software phones home usage, deployment and licence metadata; no certifications are stated. 4 8 9 11
The Skeptic
The contracting entity is Bugsink B.V. of Utrecht under Dutch law and Dutch courts, hosted application data is stated to be stored and processed in the EU, the subprocessors are published by name and purpose (Hetzner for hosting, Scaleway for email, Stripe for payment only, with no error data shared), and a data processing agreement is public with advance notice and objection rights on subprocessor changes. The self-hosted edition keeps every event on your own servers with vendor access disclaimed — though it does send periodic phone-home metadata about usage, deployment settings and licence information, so it is not silent, and no certifications are stated. 4 9 10 11
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
Six managed tiers are public with their event volumes — Free, then 75K at €16, 600K at €50, 3M at €158, 15M at €568 and 50M at €1,288 monthly — with unlimited users and teams on paid plans, a 28-day paid trial and higher volumes on request, which reads as flat pricing without per-event surprises. We found no public information on the price or licence of the self-hosted edition, what happens when a quota is hit, annual terms or VAT, so I cannot yet compute the full annual cost of either route. 1 3 4
The SaaS CTO
The managed ladder is public and refreshingly simple — free at 15,000 events a month for a single user with 5,000 retained, then €16 for 75K, €50 for 600K, €158 for 3M, €568 for 15M and €1,288 for 50M, each with unlimited users and teams, higher volumes on request and a 28-day trial of a paid plan. I found no public information on the price of a self-hosted licence, on what happens when a plan's monthly volume is exceeded, on annual terms or on VAT, so I cannot compute a full year from the pages alone. 1 3 4
The Mobile Team Lead
The managed plans are plainly published: 15K monthly events free for a single user and one team, then €16 for 75K, €50 for 600K, €158 for 3M, €568 for 15M and €1,288 for 50M events per month, each with unlimited users and teams, a 28-day trial of any paid plan, and flat pricing with no per-event billing. What a buyer still cannot compute: the price of the self-hosted licence, annual versus monthly terms, VAT, and what happens when a monthly volume is exceeded — higher volumes are only offered on request. 1 3 4
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
The Data Protection Officer
Every managed tier is public with its monthly price and event volume — Free at 15K monthly events for a single user with 5K events retained, up to €1,288 for 50M — with unlimited users and teams on paid plans, a 28-day trial and flat pricing without per-event billing. What happens at the quota, VAT, annual versus monthly terms and the price of the self-hosted edition are not documented, so the real annual cost is not fully computable from the public pages. 1 3 4
The Skeptic
Five managed tiers are public with exact prices and volumes — 75K events at €16, 600K at €50, 3M at €158, 15M at €568, 50M at €1,288 per month, plus a free tier of 15K monthly events with 5K retained — and paid plans include unlimited users and teams, with a 28-day paid-plan trial. But we found no public information on what happens when a quota is hit, annual versus monthly terms, VAT, or what a self-hosted licence costs; "flat pricing, with no event-based surprises" is a claim, not an overage policy. 1 3 4
European sovereignty — proven facts
4 of 6 dimensions provenBuilt only from facts shown on the vendor's own pages. A dimension we could not prove is left open, not scored as zero.
| Legal entity | Incorporated in NL | 2/2 pts | 10 Report an error |
|---|---|---|---|
| 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
- 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 — Transfer impact assessment. 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.
- Weak sourcing — Hosting location. 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.
- 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.
- 2 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
- 1 hosting 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 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
- 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 (17)
The pages every claim on this page was read from — each one checked, dated, and kept verifiable.
- 1 Vendor homepage (with pricing) www.bugsink.com Checked 6 Nov 2026 Details →
- 2 Features page (error tracking) www.bugsink.com Checked 6 Nov 2026 Details →
- 3 Features page (SDK compatibility) www.bugsink.com Checked 6 Nov 2026 Details →
- 4 Features page (managed hosting) www.bugsink.com Checked 6 Nov 2026 Details →
- 5 Documentation www.bugsink.com Checked 6 Nov 2026 Details →
- 6 Documentation (self-hosting) www.bugsink.com Checked 6 Nov 2026 Details →
- 7 Security / trust page www.bugsink.com Checked 6 Nov 2026 Details →
- 8 About page www.bugsink.com Checked 6 Nov 2026 Details →
- 9 Terms of service www.bugsink.com Checked 6 Nov 2026 Details →
- 10 Privacy policy www.bugsink.com Checked 6 Nov 2026 Details →
- 11 Data processing agreement (dpa) www.bugsink.com Checked 6 Nov 2026 Details →
- 12 Error capture, grouping & triage — found from sitemap www.bugsink.com Checked 6 Nov 2026 Details →
- 13 Error capture, grouping & triage — found from sitemap www.bugsink.com Checked 6 Nov 2026 Details →
- 14 Alerting, integrations & developer workflow — found from sitemap www.bugsink.com Checked 6 Nov 2026 Details →
- 15 Alerting, integrations & developer workflow — found from sitemap www.bugsink.com Checked 6 Nov 2026 Details →
- 16 Data scrubbing, retention & volume control — found from sitemap www.bugsink.com Checked 6 Nov 2026 Details →
- 17 Access control, security & the vendor's reliability — found from sitemap www.bugsink.com Checked 6 Nov 2026 Details →