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 Burke Software and Consulting LLC · glitchtip.com

Report an error on this page Is this your product? →

Link to this page

GlitchTip: AI-assisted analysis on whats-best.ai GlitchTip: 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.

GlitchTip at a glance

Vendor
Burke Software and Consulting LLC
Headquarters
Incorporated in the United States source, captured 6 Nov 2026
Data hosting
Outside the EU by default; pages mention the US and the EU source, captured 6 Nov 2026
Free plan
Yes, per the vendor’s own page source, captured 6 Nov 2026
Panel verdict
The AI panel rates GlitchTip 2/5, the mean of 6 judges. GlitchTip is an open-source, Sentry-client-SDK-compatible error tracking service from Burke Software and Consulting LLC. how scores are made
As of
Vendor pages captured 6 Nov 2026; evaluated by the panel 6 Nov 2026. all sources

GlitchTip alternatives, European ones first →

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

The panel's verdict

GlitchTip is an open-source, Sentry-client-SDK-compatible error tracking service from Burke Software and Consulting LLC. The scoring favors it on sovereignty, at 6 to 7, where judges credit a Frankfurt EU instance available on all plans, separate from the US instance with no cross-region copying, an automatic data processing agreement with Standard Contractual Clauses, and a published subprocessor list; and on pricing transparency, at 5 to 6, with all four plans public from Free ($0, up to 1,000 events per month) to Large at $250 per month for 3 million events. Performance tracing and workflow and integrations are the weak spots, scored 3 at minimum and maximum: the pages name performance, logs and uptime without detail on distributed tracing or OpenTelemetry, and we found no public information on alert rules or notifications. Data controls draw the widest split of any criterion, 4 to 6: retention is documented per data type and spend-cap billing is precise, we found no public information on scrubbing, IP anonymisation or filters, and the judges weighed those two halves differently.

Report an error

Speaks for it

  • Frankfurt EU instance available on all plans, kept separate from the US instance with no copying between them
  • Open-source, self-hostable edition documented for running the source on a server you control
  • All four plans public with exact prices and event volumes, with on-demand events past the limit billed only for the extra until a monthly spend cap stops billing
  • Data processing agreement applies automatically, incorporating EU Standard Contractual Clauses with the UK addendum and Swiss safeguards, and subprocessors are published with 10 business days' notice of changes
  • Retention documented per data type — 90 days by default for event data, 35-day encrypted backup expiry — with self-service deletion of organizations and accounts

Report an error

Held against it

  • We found no public information on alert rules or notifications to email, Slack or on-call tools
  • We found no public information on data scrubbing, IP anonymisation, sampling or filters before ingestion
  • The vendor states it performs internal self-assessments and does not undergo independent third-party audits
  • We found no public information on customer-side single sign-on, two-factor authentication, team roles or audit logs
  • The per-event overage rate, annual price figure and VAT are not published, so a full annual cost cannot be computed from the public pages

Report an error

Best for

  • You already ship Sentry client SDKs and want a compatible receiving service with a genuine European hosting path and an automatic data processing agreement
  • You need predictable spend — published plan prices, on-demand billing with a monthly spend cap, and cancellation back to the free plan
  • You can run the open-source edition on your own servers to keep every event in a chain you control
  • Your need is error capture and triage rather than trace-based performance work or alert-driven operations

Report an error

Avoid if

  • You must hand a client or auditor an ISO 27001 or SOC 2 certification — the vendor states it performs internal self-assessments and does not undergo independent third-party audits
  • You need an unbroken European legal chain — the contracting entity is a New York LLC under New York law and EU-instance data may be accessed from the US for support
  • Your error payloads may carry special category data — the terms prohibit it and place responsibility for excluding it on you as the customer
  • Your on-call rotation depends on documented alert routing — the integrations page lists GitLab, an API, a beta CLI and an MCP AI integration

Report an error

The scores

Panel median The median of the judges’ scores per criterion. Each label opens its reasoning below.

Error capture, grouping & triage

Show 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.

Report an error

The Agency Tech Lead

Error tracking is documented as accepting exceptions, log messages and Content Security Policy violations for triage and resolution, with the homepage stating plainly that the app is compatible with Sentry client SDKs, so my Laravel and Shopware stacks would have a path in. But the captured pages stop there: we found no public information on grouping, issue states, regression detection, releases, source maps or request context, so I cannot place this above basic capture. 1 2

Report an error

The SaaS CTO

Error tracking is the product's core, and compatibility with Sentry client SDKs means exceptions, log messages and Content Security Policy violations can arrive from many platforms, with stack traces listed among the data processed. We found no public information on grouping and issue states, source maps and symbolication, release and deploy tracking or suspect commits, so I cannot credit the triage flow my teams run on. 1 2 7

Report an error

The Mobile Team Lead

Compatibility with Sentry client SDKs is the hook for my iOS, Android and Flutter team — our existing SDKs should in principle be able to send events — and the captured pages confirm stack traces, device metadata and OS and browser versions arrive with the telemetry. But we found no public information on symbolication, grouping and issue states, release tracking, or crash-free users per release, which is the release-health picture I need before halting a store rollout. 1 2 7

Report an error

The Site Reliability Engineer

Error tracking is documented for exceptions, log messages and Content Security Policy violations, arriving through Sentry-compatible client SDKs, which covers a broad set of platforms on the client side. The captured pages describe triage only in general terms; we found no public information on source maps, grouping and custom fingerprints, issue states, releases and deploy tracking, or mobile crash-free metrics, so the depth past capture is undescribed. 1 2

Report an error

The Data Protection Officer

Error tracking is confirmed and compatible with Sentry client SDKs, so exceptions, log messages and Content Security Policy violations arrive from the platforms those SDKs cover, and the documented telemetry already includes stack traces, HTTP request parameters, device metadata and IP addresses. We found no public information on grouping and custom fingerprints, issue states, releases and deploy tracking, source maps or issue search, so how a stack trace carrying a member number gets triaged is not documented. 1 2 7

Report an error

The Skeptic

Error tracking is the product's core: exceptions, log messages and Content Security Policy violations are accepted, and the app is documented as compatible with Sentry client SDKs. The captured pages stop there — grouping, issue states, releases, source maps and per-platform SDK configuration are basic or not described, and I found no public information on mobile crash reporting or release health. 1 2 5

Report an error

APM, tracing & profiling

Show 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.

Report an error

The Agency Tech Lead

Performance monitoring is named as a capability alongside logs and uptime, but we found no public information on endpoint percentiles, slow query or N+1 detection, queue and job timings, distributed tracing, OpenTelemetry or profiling — the depth I would need to find a slow Shopware page before a client calls. A named performance feature with no described substance lands at the simple-view level. 2 5

Report an error

The SaaS CTO

Performance monitoring, logs and uptime monitoring are named as capabilities, which reads as a simple performance view. We found no public information on distributed tracing across services, OpenTelemetry ingestion, percentiles per endpoint, slow-query or N+1 detection, profiling or real user monitoring — exactly what I need to follow one trace from a browser click to a slow database call three services down. 2 5

Report an error

The Mobile Team Lead

Performance monitoring, logs and uptime monitoring are all listed as capabilities of the platform. Beyond that the captured pages give no detail — nothing on transaction timings, slow query detection, distributed tracing or real-user monitoring — so it reads as a basic performance view. 2 5

Report an error

The Site Reliability Engineer

The documentation names performance monitoring, uptime monitoring and logs alongside error tracking, so some performance view is offered. We found no public information on endpoint timings with percentiles, distributed tracing, OpenTelemetry ingestion, profiling, slow-query analysis or real-user monitoring, which is what I would need to see before trusting latency pages here. 2 5

Report an error

The Data Protection Officer

Performance monitoring, logs and uptime monitoring are named as capabilities beside error tracking, with documentation topics covering performance and uptime monitoring. We found no public information on transaction and endpoint timings, slow-query detection, tracing across services, OpenTelemetry or profiling, which leaves a simple performance view rather than the trace-based monitoring our portal team needs. 2 5

Report an error

The Skeptic

Performance and uptime monitoring are offered as documented capabilities, so there is more than errors alone. But the pages give no detail on transaction timings, distributed tracing, slow query analysis, profiling or web vitals, and I found no public information on OpenTelemetry ingestion or host metrics. 2 5

Report an error

Alerting, integrations & developer workflow

Show 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.

Report an error

The Agency Tech Lead

A documented API, a GitLab integration, a beta CLI and an MCP AI integration are listed in the documentation, which is a start. But we found no public information on alert rules, email or chat notifications, on-call routing or issue tracker sync, and for an agency running forty client sites I need per-project alert channels — nothing captured shows how an error reaches the person who fixes it. 1 2

Report an error

The SaaS CTO

The documentation names an integrations section with GitLab, API documentation, a CLI in beta and an MCP AI integration. We found no public information on alert rules, notifications to email, Slack or an on-call tool, issue tracker sync, release hooks from CI or webhooks, so how an error reaches the team that owns the service is not evidenced. 1 2

Report an error

The Mobile Team Lead

There is a documented API, a GitLab integration, a CLI in beta, an MCP AI hook, and social sign-in through Google, Microsoft, GitHub and GitLab. But we found no public information on alert rules or notifications — no email, chat or on-call delivery, nothing that would flag when a new release crashes more than the last — and issue-tracker sync beyond the GitLab mention is not described. 1 2 6

Report an error

The Site Reliability Engineer

An integrations section documents GitLab, an API with documentation, a beta CLI and an MCP AI integration. We found no public information on alert rules, or notifications to email, Slack or an on-call tool such as PagerDuty, which is the piece an on-call rotation actually depends on; support runs over email and Mastodon. 1 2

Report an error

The Data Protection Officer

The integrations page documents GitLab, API documentation, a beta CLI and an MCP AI integration. We found no public information on alert rules, notifications to Slack or on-call tools, or two-way issue-tracker sync, and the AI integration names neither model nor provider — before it reads any error from our member portal I need to know which model explains the errors and where it runs. 2

Report an error

The Skeptic

The visible workflow surface is a documented API, a GitLab integration, a CLI in beta and an MCP AI integration. I found no public information on alert rules, email or chat notifications, on-call routing or two-way issue tracker sync, and the model behind the AI integration is never named. 2 1

Report an error

Data scrubbing, retention & volume control

Show 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.

Report an error

The Agency Tech Lead

Retention is stated per plan and per data type with self-service deletion of organizations and accounts, and spike protection is explicit and friendly to my invoice: on-demand events past the plan limit are billed only for the extra, with a monthly spend cap that stops billing the moment it is reached. The hole is scrubbing — we found no public information on password or token scrubbing, IP anonymisation, sampling or event filters before ingestion, which matters because our shops send customer addresses in request data. 3 6 7

Report an error

The SaaS CTO

Retention is published per plan tier — 30 days on the free plan, 90 days on paid, with deleted data expiring from encrypted backups within 35 days — and volume control is documented precisely: on-demand events past the plan limit keep being collected and billing stops the moment a monthly spend cap is reached. Organization and account deletion are self-service paths, and a self-hosted edition plus an EU instance exist, but we found no public information on data scrubbing, IP anonymisation, sampling or event filters before ingestion. 1 3 5 6 7

Report an error

The Mobile Team Lead

Retention is stated per plan — 30 days of event retention on the free tier, 90 days by default, deleted data out of encrypted backups within 35 days — with self-service deletion of an organization or account, and on-demand billing past the limit is documented with a spend cap that stops billing once it is reached. Scrubbing appears only as a passing reference to reasonable scrubbing of special categories, and we found no public information on configurable SDK scrubbing, IP anonymisation, sampling or filters before ingestion. 3 5 6 7

Report an error

The Site Reliability Engineer

Retention is stated per plan — 30 days of event retention on the free tier and 90 on the Small plan — with self-service deletion for organizations and accounts and automatic event deletion after 90 days by default under 35-day encrypted backups. Spike protection is unusually explicit: on-demand billing keeps collecting events past the plan limit and stops the moment a monthly spend cap is reached, so an incident never surprises the invoice. We found no public information on data scrubbing, IP anonymisation, sampling or pre-ingestion filters. 1 3 6 7

Report an error

The Data Protection Officer

Retention is documented per data type — event data 90 days by default, encrypted backups expiring within 35 days, service logs 90 days, support conversations 60 days — with self-service deletion of organizations and accounts, GDPR rights answered within one month, and volume held by per-plan event limits plus on-demand billing that bills only for the extra and stops at a spend cap. Scrubbing appears only as "reasonable scrubbing" inside a prohibition clause, with the customer responsible for excluding special category data, and we found no public information on configurable server-side scrubbing rules or IP anonymisation. The documented self-hosted edition and the Frankfurt EU instance both let us keep events in a chain we control. 3 5 6 7

Report an error

The Skeptic

Retention is stated plainly — 30 days of events on the free plan, 90 days on paid, deleted data gone from encrypted backups within 35 — and self-service deletion of organizations and accounts is documented, with on-demand billing and a spend cap that stops charging the moment it is reached. But I found no public information on scrubbing of secrets or personal data, IP anonymisation, sampling, or filters that drop events before they count, which is the half of this criterion that decides an audit; the self-hosted open-source edition, licensed for customers to run and modify, is the strongest escape hatch. 1 3 5 6

Report an error

Access control, security & the vendor's reliability

Show 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.

Report an error

The Agency Tech Lead

Encryption in transit (TLS 1.2 or higher) and at rest on encrypted DigitalOcean storage, staff-only production access behind single sign-on with hardware-backed MFA, and a public status page with separate US and EU services are all documented. But we found no public information on customer-side SSO, SCIM, two-factor authentication or audit logs, and the vendor states plainly that it performs internal self-assessments and does not undergo audits by independent third-party auditors, so there is no ISO 27001 or SOC 2 to hand a client. 4 5 7

Report an error

The SaaS CTO

Encryption in transit (TLS 1.2 or higher) and at rest on DigitalOcean, hardware-backed MFA for the vendor's own production access, and a public status page for the US and EU instances are documented. The data processing agreement states the vendor performs internal self-assessments and does not undergo audits by independent third-party auditors, and we found no public information on customer-side two-factor authentication, single sign-on, roles, audit logs, or a service level agreement. 4 5 7

Report an error

The Mobile Team Lead

Encryption in transit at TLS 1.2 or higher, encrypted storage and backups on DigitalOcean, a public status page covering the US and EU instances, and hardened vendor-side production access with single sign-on and hardware-backed multi-factor authentication are all documented. Against that, the vendor itself states it performs internal self-assessments and does not undergo independent third-party audits, and we found no public information on customer-side two-factor authentication, SAML single sign-on, role-based access or audit logs. 4 5 7

Report an error

The Site Reliability Engineer

A public status page covers the US and EU web servers, the security documentation states TLS 1.2 or higher in transit and encrypted DigitalOcean storage at rest, and provider production access requires single sign-on with hardware-backed multi-factor authentication. The same documentation states the provider performs internal security self-assessments and does not undergo audits by independent third-party auditors, and the terms provide the service as is; we found no public information on customer single sign-on, two-factor authentication, team roles or audit logs. 4 5 7

Report an error

The Data Protection Officer

Encryption in transit at TLS 1.2 or higher and encrypted storage at rest are stated, production access requires single sign-on with hardware-backed multi-factor authentication, infrastructure is version-controlled and deployed through CI/CD, and a public status page covers the US and EU instances. The vendor states plainly that it performs internal self-assessments and undergoes no independent third-party audits, offering a summary once per calendar year on request — honest, but short of ISO 27001 or SOC 2. We found no public information on user roles, customer single sign-on, audit logs or a service level for paid plans, and the free plan is explicitly without any uptime or support commitment. 4 5 7

Report an error

The Skeptic

Encryption in transit (TLS 1.2 or higher) and at rest on encrypted storage are stated, a public status page covers both the US and EU instances, and the vendor restricts its own production access with SSO and hardware-backed multi-factor authentication. But the vendor itself states it performs internal self-assessments and does not undergo independent third-party audits, no certification is claimed, and I found no public information on customer-side roles, two-factor authentication, SSO, SCIM or audit logs; the only stated service-level position is that the free plan carries none. 4 7 3 5

Report an error

European sovereignty panel opinion

Show 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.

Report an error

The Agency Tech Lead

There is a genuine EU option: all plans run on the Frankfurt eu.glitchtip.com instance on named infrastructure (DigitalOcean), the two instances are separate with no copying between them, a Data Processing Agreement applies automatically with Standard Contractual Clauses, and the subprocessor list is published with change notice. It stays mid-range because the contracting entity is a New York LLC, the privacy policy notes EU-instance data may be accessed from the US for support, and the vendor states it does not undergo independent audits — though the documented open-source self-hosting on our own servers is the escape hatch for sensitive clients. 1 3 6 7

Report an error

The SaaS CTO

There is a real EU offering: an EU instance hosted in Frankfurt on DigitalOcean and available on all plans, kept separate from the US instance with no cross-region copying, an automatic Data Processing Agreement incorporating the Standard Contractual Clauses, and subprocessors (Stripe for payment, Chatwoot for support chat on the US instance, Mailchimp for the newsletter, Plausible for site analytics) published with the region each serves. For my enterprise customers the chain is not clean end to end: the contracting entity is a New York LLC, the privacy policy notes EU-instance data may be accessed from the US for support, the agreement states there are no independent third-party audits, and running the open-source edition on our own European servers is the fallback — which the terms explicitly permit. 3 5 6 7

Report an error

The Mobile Team Lead

For a Hamburg team like mine there is a real European path: an EU instance in Frankfurt available on all plans, kept separate from New York with no copying between the two, on named DigitalOcean infrastructure, under a Data Processing Agreement that applies automatically and incorporates the Standard Contractual Clauses, with a published subprocessor list naming Stripe, Mailchimp, Chatwoot and Plausible. The chain still ends at a New York LLC under New York law, payment and newsletter run through US providers, and EU-instance data may be accessed from the US for support; the documented open-source self-hosted edition is the route that keeps every event in our own European chain. 1 3 5 6 7

Report an error

The Site Reliability Engineer

An EU instance in Frankfurt, Germany is available on all plans on named DigitalOcean infrastructure, the US and EU instances are separate with no copying between them, and the data processing agreement applies automatically with Standard Contractual Clauses, publishing subprocessors with their regions and ten business days' notice of changes. The contracting entity is a New York LLC under New York law and the security documentation states internal self-assessments rather than independent audits; an open-source self-hosted edition is documented for running every event on the customer's own server. 3 5 6 7

Report an error

The Data Protection Officer

A Frankfurt EU instance on named DigitalOcean infrastructure is available on all plans, the US and EU instances are separate with no cross-region copying, the data processing agreement applies automatically and incorporates Standard Contractual Clauses with the UK addendum and Swiss safeguards, and subprocessors — Chatwoot, Mailchimp, Plausible, Stripe — are published with regions and 10 business days' notice of changes. An open-source, self-hostable edition is documented for running the source on our own European servers. The gaps for a statutory insurer: the contracting entity and governing law are New York, no EU representative is documented, certifications are absent, the privacy policy discloses that EU-instance data may be accessed from the US for support, and the AI integration's model and its location are unnamed. 1 3 5 6 7

Report an error

The Skeptic

The EU instance (eu.glitchtip.com) runs in Frankfurt on named DigitalOcean infrastructure and is available on all plans, the US and EU instances are separate with no data copied between them, a data processing agreement applies automatically (free plans included) with EU Standard Contractual Clauses incorporated, and a subprocessor list is published with ten business days' notice of changes. On the other side of the ledger: the contracting entity is a New York LLC under New York law, the vendor's own caveat says EU-instance data may be accessed from the US for support, and independent audits and certifications are stated as not performed. The open-source, self-hostable edition customers run on their own servers is the strongest sovereign path documented. 3 6 7 5 1

Report an error

Pricing transparency

Show 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.

Report an error

The Agency Tech Lead

All four tiers are public with event volumes and retention (Free $0 with Up to 1,000 events/mo, Small $15 / month at 100k, Medium $50 / month at 500k, Large $250 / month at 3 million), and behaviour past the quota is stated rather than hidden — on-demand events billed only for the extra with a monthly spend cap. But the per-event overage rate, the annual price figure and VAT are not on the captured pages, so I still cannot compute the exact annual invoice for a client's volume from public information alone. 1 3 5

Report an error

The SaaS CTO

All four plans are public with prices and event volumes — Free ($0) at up to 1,000 events/mo, $15 / month at up to 100k, $50 / month at up to 500k, $250 / month at up to 3 million — and behaviour at the quota is stated: on-demand events past the limit are billed only for the extra until a monthly spend cap stops billing. But we found no public information on the per-event overage rate, the annual price, the HIPAA add-on or VAT, so I cannot compute the real annual cost for a given volume. 1 3 5

Report an error

The Mobile Team Lead

Four plans are public with prices and event volumes — Free ($0) up to 1,000 events/mo, $15 / month up to 100k events/mo, $50 / month up to 500k events/mo, $250 / month up to 3 million events/mo — with retention per tier, monthly and annual billing, and behaviour past the limit stated: events keep being collected, you are billed only for the extra, and a spend cap stops it. What I still cannot compute is the per-event price of that on-demand extra, the annual discount, or VAT. 1 3 5

Report an error

The Site Reliability Engineer

Every plan is public with its price and event volume — Free ($0) with up to 1,000 events per month, then $15 / month, $50 / month and $250 / month up to 3 million events per month — with retention stated per plan, annual billing offered and cancellation back to the free plan documented. Behaviour at the quota is stated: on-demand events past the limit billed only for the extra and stopped at a monthly spend cap. We found no public information on the per-event overage rate, the annual price figure, VAT, or the price of the HIPAA hosting add-on, so a full annual cost cannot be computed from public pages alone. 1 3 5

Report an error

The Data Protection Officer

Every plan is public with its price and volume — Free ($0) with 1,000 events per month and 30 days retention, $15 per month with 100k events and 90 days retention, $50 with 500k, $250 with 3 million — in monthly and annual billing, and behaviour at the quota is stated: on-demand events past the limit billed only for the extra, stopping at a monthly spend cap. We found no public information on the per-event overage rate, the annual price, VAT or the price of the HIPAA add-on, so a full annual cost is not computable from the public pages. 1 3 5

Report an error

The Skeptic

Four plans are public with exact prices and event volumes — Free ($0) with up to 1,000 events a month and 30 days' retention, $15 / month up to 100k events with 90 days, $50 / month up to 500k, $250 / month up to 3 million — plus monthly or annual billing and documented behaviour at the limit: on-demand events are billed only for the extra and charges stop at a spend cap you set. What I still cannot compute is the real annual cost for a known volume: the per-event on-demand rate, the annual discount, VAT, and what performance and logs cost beyond 'events' are not stated, and the self-hosted edition has no listed licence price. 1 3 5

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 Outside the EU unverified
Why unverified?

The standard sign-up instance app.glitchtip.com is hosted in New York, and even EU-instance data may be accessed from the US for support; the vendor separately offers an opt-in EU instance (eu.glitchtip.com) in Frankfurt, Germany.

0/4 pts 6 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 Published, self-serve 1/1 pts 7 Report an error
Transfer impact assessment Not determined — uncited Report an error

Questions about GlitchTip

Is GlitchTip European?

No. whats-best.ai classifies GlitchTip as Rest of world. Its vendor, Burke Software and Consulting LLC, is incorporated in the United States, per the vendor’s page captured 6 Nov 2026.

Where does GlitchTip store data?

GlitchTip stores customer data outside the EU by default, per the vendor’s page captured 6 Nov 2026. The vendor’s pages mention the US and the EU as hosting locations, per the vendor’s page captured 6 Nov 2026.

Does GlitchTip have a free plan?

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

What are the best alternatives to GlitchTip?

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: GlitchTip 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 (7)

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

  1. 1 Vendor homepage glitchtip.com Checked 6 Nov 2026 Details →
  2. 2 Documentation glitchtip.com Checked 6 Nov 2026 Details →
  3. 3 Pricing page glitchtip.com Checked 6 Nov 2026 Details →
  4. 4 Public status page status.glitchtip.com Checked 6 Nov 2026 Details →
  5. 5 Terms of service (names the operating company) glitchtip.com Checked 6 Nov 2026 Details →
  6. 6 Privacy policy glitchtip.com Checked 6 Nov 2026 Details →
  7. 7 Data processing agreement (dpa) glitchtip.com Checked 6 Nov 2026 Details →