European Alternatives to Sentry and Bugsnag - Error Tracking (2026) | European Purpose

European Error Tracking Alternatives

An error tracker receives the single most sensitive stream a running application produces: the stack trace, the local variables around the crash, the request body, the headers, the user id and whatever personal data happened to be in scope at the moment things broke.

These European alternatives to Sentry and Bugsnag cover automatic exception capture for PHP, .NET, Ruby, Elixir, Node, Python and mobile, plus self-hosting, from vendors established in the Netherlands, Germany, Belgium, Denmark, Italy, Austria and the United Kingdom.

How we rank these tools — 4-step process
  1. 1
    European ownership, verified

    The company is headquartered and incorporated in the EU, EEA or Switzerland, and processes customer data in Europe. A US parent company disqualifies a tool from this page regardless of where its servers are.

  2. 2
    Category fit and hands-on review

    What the tool actually does, who it suits, and where it falls short — checked against the vendor’s own documentation, changelog and pricing page rather than its marketing copy.

  3. 3
    Compliance and pricing check

    GDPR posture, hosting location and the prices quoted on this page are verified against the vendor’s public pricing before publication, and re-checked when we revisit the category.

  4. 4
    Position on this page

    Placement on this page can be paid, and that can affect the order tools appear in. It never buys a listing: a tool that fails the checks above is not here at any price, and payment does not change the shortcomings we write about. A vendor can ask us to correct a factual error — not to remove a criticism.

Vendors can pay for visibility on this page. It never changes what an entry says about a product, including the criticism, and we earn nothing when you click through to a vendor. Paid placement can affect the order in which tools appear; it never affects whether a tool is listed. Editorial policy

10 European Error Tracking

AppSignal

Amsterdam APM with error tracking for Ruby, Elixir, Node, Python and front-end JavaScript, stored in the EU

Netherlands Free plan (50K requests) / €219 per year for 250K requests a month
Errors, performance, logs and uptime in oneISO 27001 and SOC 2Hosted at Worldstream in the Netherlands

Tideways

Bonn profiler and exception tracker built only for PHP, with all data in SysEleven data centres in Berlin

Germany Team from €69/month, Business from €159/month
Error and exception tracking plus profilerNamed German data centre, SysEleven Berlin14-day trial, no credit card

Bugsink

Utrecht error tracker you run yourself, speaking the Sentry SDK protocol so existing clients point straight at it

Netherlands Free self-hosted, unlimited users / hosted from €16 per month
Works with existing Sentry SDKsSource-available, PolyForm Shield 1.0.0Free hosted tier, 15K events a month

Flare

Antwerp error tracking for Laravel, PHP and front-end JavaScript, built by the team behind Spatie

Belgium From €9/month (Hobby), €29 Standard, €69 Growth, €279 Premium
First-class Laravel queues, jobs and LivewireErrors, performance and logging togetherAll processing inside the European Union

elmah.io

Danish error logging for .NET and ASP.NET Core, from the company that turned the ELMAH library into a service

Denmark $26/month Small Business, $44 Business, $89 Business+, $269 Enterprise
Every .NET web and logging frameworkUptime and heartbeat monitoring included21-day trial, no credit card

Inspector

Italian monitoring for PHP applications with a free tier that is a monthly quota rather than a countdown

Italy Free up to 30K transactions / €15, €39 and €69 per month
Laravel, Symfony, CodeIgniter and DrupalFree plan with no time limitUnlimited users on every paid plan

Bugfender

German remote logging and crash reporting for mobile and web apps, keeping logs even when nothing has crashed

Germany Free plan (100K log lines a day) / Team from $39, Pro from $89 per month
iOS, Android, Flutter, React and UnityCrash stack traces with symbolicationISO 27001, EU data storage

Countly

London product analytics platform whose crash module catches errors alongside the usage data, self-hostable

United Kingdom Flex from $175/month / Enterprise self-hosted on request
Crashes and errors next to product analyticsTen SDKs across mobile, web and desktopSelf-host on your own infrastructure

Gleap

Austrian in-app bug reporting that attaches console logs, screenshots and a session replay to what a user reports

Austria From $49/month (annual) for Starter, $149 Team, $299 Pro
Console logs and replay with each reportServers in Frankfurt, GermanyWebsites and mobile apps

Marker.io

Brussels website bug reporting that pushes annotated reports with console logs into Jira, Linear or GitHub

Belgium $39/month Starter billed annually, $149 Team, Business on request
Session replay beside the console logFeeds your existing issue tracker15-day trial, no credit card

Key takeaways

  • AppSignal ranks #1 among the European error tracking tools in this directory, because AppSignal is the only one that pairs broad language coverage — Ruby, Elixir, Node, Python and front-end JavaScript — with ISO 27001 and SOC 2 and a hosting stack that stays Dutch down to the hardware, at Worldstream in the Netherlands.
  • Only two vendors here name the data centre their customers' errors land in. Tideways stores everything at SysEleven in Berlin; AppSignal runs on Worldstream in the Netherlands with backups on AWS EMEA. Flare and Bugsink say "the European Union" without naming a provider, Inspector says nothing at all, and elmah.io names Microsoft Azure without a region.
  • Bugsink is the only tool here you can run entirely on your own machines, and it speaks the Sentry SDK protocol, so an application already instrumented with a Sentry client points at a Bugsink URL and keeps working. It is source-available under the PolyForm Shield License 1.0.0, not open source — the licence forbids competing with Bugsink, which matters if you planned to resell it.
  • The language split decides most of this category before price does. Tideways, Flare and Inspector are PHP tools, elmah.io is .NET only, Bugfender and Countly are aimed at mobile, and only AppSignal and Bugsink cover a general spread of back-end languages.
  • Three tools have a genuinely free tier rather than a countdown: Inspector at 30,000 transactions a month, Bugfender at 100,000 log lines a day, and AppSignal at 50,000 requests. Flare, elmah.io, Gleap and Marker.io have trials only, and Countly starts at $175 per month.
  • Gleap and Marker.io are in this category but do not replace Sentry. They capture bugs a human reports, with the console log and a session replay attached — useful next to an error tracker, useless instead of one, because nothing reaches them unless somebody presses a button.

European error tracking software captures exceptions, crashes and stack traces from running applications, and is built by a company established in Europe and hosted on European infrastructure — so that the stack trace, the local variables around the failure, the request body and the user id inside it stay under European jurisdiction rather than being shipped to a US processor every time production breaks.

European error tracking compared

European error tracking tools compared on position, country, entry price and best use
PositionToolEstablishedEntry priceBest for
#1 AppSignal Netherlands Free plan (50K requests) / €219 per year for 250K requests a month, logging add-on €89/month Teams running more than one language who want errors, performance and logs in one EU-hosted tool
#2 Tideways Germany Team from €69/month, Business from €159/month, both rising in tiers with request volume; Enterprise on request PHP teams that need to know why a request threw and why it was slow, on a named German host
#3 Bugsink Netherlands Free self-hosted with unlimited users / hosted free up to 15K events a month, then €16, €50 and €158 per month Teams that need error tracking on their own hardware without running a Sentry cluster
#4 Flare Belgium Hobby €9/month, Standard €29, Growth €69, Premium €279; annually €99, €319, €759 and €3,069 Laravel and PHP teams who want error tracking from people who write Laravel packages
#5 elmah.io Denmark Small Business $26/month, Business $44, Business+ $89, Enterprise $269, always billed in USD .NET teams that want error logging, uptime and heartbeats from one Danish vendor
#6 Inspector Italy Free up to 30K transactions a month / Beginner €15, Developer €39, Team €69 per month Small PHP teams that want real monitoring on a free tier that never expires
#7 Bugfender Germany Free plan (100K log lines a day, 2,000 devices) / Team from $39/month, Pro from $89/month; overage €3.25 per extra million logs Mobile teams that need the log leading up to the crash, not just the crash
#8 Countly United Kingdom Flex private cloud from $175/month, usage-based; Enterprise self-hosted on request Mobile product teams that want crash data and usage analytics in the same system, self-hosted if needed
#9 Gleap Austria Starter $49/month billed annually ($59 monthly), Team $149, Pro $299, Enterprise from $999 Product teams that want user-reported bugs to arrive with the console log already attached
#10 Marker.io Belgium Starter $39/month billed annually ($59 monthly), Team $149 ($199 monthly), Business on request Agencies and QA teams pushing client-reported website bugs into an existing issue tracker

Every European error tracking tool reviewed

#1 AppSignal

Amsterdam, Netherlands Founded 2012 Free plan (50K requests) / €219 per year for 250K requests a month, logging add-on €89/month 30-day free trial, no credit card, plus a permanent free plan

Best for: Teams running more than one language who want errors, performance and logs in one EU-hosted tool

  • Operating company. AppSignal B.V.
  • Jurisdiction. EU (Netherlands)
  • Where the data sits. Netherlands, on Worldstream B.V., with backups on Amazon Web Services EMEA SARL; an optional US region exists
  • Independent checks. ISO 27001, SOC 2, GDPR; HIPAA as a paid add-on
  • Source code. Closed source
  • Replaces. Sentry, Bugsnag, New Relic

AppSignal is the only tool in this category that does not make you choose a runtime first.

First-party integrations cover Ruby with Rails, Sinatra and Sidekiq, Elixir with Phoenix, Ecto and Oban, Node.js with Express, NestJS and Next.js, Python with Django, FastAPI, Flask and Celery, and front-end JavaScript for React, Vue, Angular and Ember, with Go, Java, PHP and Rust arriving through OpenTelemetry. Around the error tracking sit performance monitoring, host metrics, uptime checks, log management, anomaly detection and cron monitoring, so a small team can stop at one contract.

AppSignal B.V. is registered with the Dutch Chamber of Commerce in Amsterdam under number 62960407, and the hosting is the part that separates it from most European branding: the service runs on Worldstream B.V., a Dutch hosting company, with Amazon Web Services EMEA SARL used for backups and Mailgun for email — three subprocessors in total, published.

The company states ISO 27001 and SOC 2 certification, GDPR compliance and HIPAA as a paid add-on, runs regular pentests and operates a bug bounty. An optional US region exists for customers who want one.

Pricing is per request rather than per seat, which suits teams more than it suits high-traffic single-purpose apps: the free plan covers 50,000 requests a month with 1GB of logging and five-day retention, and the paid plan is €219 a year for 250,000 requests a month, with long-term log storage a separate €89 add-on.

Users, teams, applications and dashboards are unlimited on both. The stated upgrade policy only charges after you exceed limits in two of three months, and monitoring is not cut off when you go over.

What AppSignal does well

  • First-party support for Ruby, Elixir, Node.js, Python and front-end JavaScript
  • ISO 27001 and SOC 2, GDPR, HIPAA available as an add-on
  • Hosted on Worldstream in the Netherlands, with only three published subprocessors
  • Errors, performance, logs, uptime and cron monitoring in one product
  • Unlimited users and applications on every plan, including the free one

Where AppSignal falls short

  • Backups sit on Amazon Web Services EMEA SARL, so the stack is not European end to end
  • No self-hosting option at any price
  • Per-request pricing punishes high-traffic, low-value endpoints
  • Long-term log retention is a separate €89 per month add-on
  • Go, Java, PHP and Rust arrive only through OpenTelemetry, not a first-party SDK

Standout feature. Three subprocessors, all named: AppSignal is the only tool here whose primary hosting is a European company rather than a European region of a US cloud.

#2 Tideways

Bonn, Germany Founded 2014 Team from €69/month, Business from €159/month, both rising in tiers with request volume; Enterprise on request 14-day free trial, no credit card or phone number

Best for: PHP teams that need to know why a request threw and why it was slow, on a named German host

  • Operating company. Tideways GmbH
  • Jurisdiction. EU (Germany)
  • Where the data sits. Germany, in SysEleven data centres in Berlin, where account, monitoring and profiling data are all stored
  • Source code. Closed source
  • Replaces. Sentry, Bugsnag, New Relic, Blackfire

Tideways is the most specialised tool in this category and better for it.

It is built for PHP alone, extending the engine rather than sitting on top of it, which is why the profiler produces callgraphs and flamegraphs with data on SQL queries, external HTTP calls, caches and framework internals out of the box. Error and exception tracking runs alongside, so the same tool that tells you a checkout endpoint is throwing also shows the call path that got there. Laravel, Symfony, Magento, WordPress and Drupal are all covered.

Tideways GmbH sits at Königswinterer Straße 116 in Bonn, registered at Amtsgericht Bonn under HRB 22127, and has been at this since 2014. The hosting answer is the most specific in this category: everything — account data, monitoring data and profiling traces — is stored in SysEleven data centres in Berlin, Germany. No US cloud sits underneath, and the vendor names the host rather than a continent.

Pricing scales with request volume in tiers, starting at €69 a month for Team and €159 for Business at the five-million-request level, rising through nine steps to a billion requests, with 10% off for annual payment.

Team gives 5-day lookback and a single team; Business adds 30-day lookback, 15 months of history, distributed profiling, advanced alerting with PagerDuty and Opsgenie, and up to five teams. Projects, services and users are unlimited on both. There is a 14-day trial and no free plan.

What Tideways does well

  • Error tracking and a real PHP profiler in the same tool
  • All data stored at SysEleven in Berlin, the most specific residency claim here
  • Unlimited projects, services and users on every plan
  • Deep framework instrumentation for Laravel, Symfony, Magento and Drupal
  • 14-day trial with no credit card or phone number

Where Tideways falls short

  • PHP only — useless for any other runtime in your stack
  • No free plan, and €69 a month is a high floor for a small site
  • Team plan keeps only five days of lookback
  • No published security certification
  • Alerting on the Team plan is limited to ten transactions and a ten-minute resolution

Standout feature. A named data centre: Tideways is one of only two vendors here that says which building your stack traces are in, and the only one where nothing is subcontracted to a US cloud.

#3 Bugsink

Utrecht, Netherlands Free self-hosted with unlimited users / hosted free up to 15K events a month, then €16, €50 and €158 per month Free self-hosted edition and a free hosted tier of 15K events a month

Best for: Teams that need error tracking on their own hardware without running a Sentry cluster

  • Operating company. Bugsink B.V.
  • Jurisdiction. EU (Netherlands)
  • Where the data sits. Hosted application data is stored and processed within the European Union; no provider or region is named. Self-hosted, wherever you put it
  • Independent checks. Source-available under the PolyForm Shield License 1.0.0
  • Source code. Closed source
  • Replaces. Sentry (self-hosted), GlitchTip

Bugsink exists because self-hosting Sentry became a project in itself. It is a single application with a database, installed by Docker, that speaks the Sentry SDK protocol — so whatever Sentry client your language already has keeps working, and the only change is the DSN. You get stack traces with local variable inspection, issue grouping and the things an error tracker is for, and none of the queueing, search and streaming infrastructure that makes the alternative a cluster.

Bugsink B.V. is at Peter Schathof 41 in Utrecht, the Netherlands, the terms are governed by Dutch law with disputes in Dutch courts, and the privacy policy states that hosted application data is stored and processed within the European Union.

The self-hosted edition is free with unlimited users and all features; the hosted plans run free to 15,000 events a month, then €16 for 75,000, €50 for 600,000 and €158 for 3 million, with premium support at €15 per user per month on top.

The licence deserves a careful read. Bugsink is source-available under the PolyForm Shield License 1.0.0, not an OSI open-source licence: you may read, modify and run it internally at no cost, but you may not use it to build something that competes with Bugsink. Parts of the repository carry other licences, including BSD-3-Clause code from Sentry itself. For internal use none of this bites; for anyone planning to offer it as a service, it is the whole document.

What Bugsink does well

  • Drop-in for existing Sentry SDKs — change the DSN and nothing else
  • Free self-hosted with unlimited users and no feature gate
  • Deliberately simple to run: one application, one database, Docker
  • Hosted tier is free to 15,000 events a month and starts at €16
  • Dutch company, Dutch law, EU processing stated in the privacy policy

Where Bugsink falls short

  • Source-available under PolyForm Shield 1.0.0, not open source — competing use is forbidden
  • Error tracking only: no APM, no profiler, no log management around it
  • The hosted service names no provider or region beyond "the European Union"
  • Self-hosting means sizing for the worst deploy, not the average day
  • A young single-vendor product with a small ecosystem around it

Standout feature. Sentry protocol compatibility: Bugsink is the only tool here that an already-instrumented application can adopt by changing one configuration string.

#4 Flare

Antwerp, Belgium Hobby €9/month, Standard €29, Growth €69, Premium €279; annually €99, €319, €759 and €3,069 10-day free trial, no credit card; no free plan

Best for: Laravel and PHP teams who want error tracking from people who write Laravel packages

  • Operating company. Facade BV (Spatie)
  • Jurisdiction. EU (Belgium)
  • Where the data sits. All data is processed within the European Union; the vendor names no provider or region
  • Source code. Closed source
  • Replaces. Sentry, Bugsnag, Rollbar

Flare is built by Spatie, the Antwerp shop behind a long shelf of Laravel packages, and it shows in what the product understands.

Exceptions are handled with first-class knowledge of queues, jobs and Livewire rather than as generic stack traces, which is the difference between an error report that names the failing job and one that names the worker process. Performance monitoring for slow requests and backed-up queues and real-time log streaming sit alongside, and the front-end side covers JavaScript, React, Vue and Svelte. GitHub, GitLab, Jira and Linear are the integrations.

The operating entity is Facade BV, Kruikstraat 22/12, 2018 Antwerp, Belgium, registered under BE0729.961.919, and the terms of use state plainly that all data is processed within the European Union. What the terms do not say is which provider or which region, and the DPA is a downloadable PDF rather than a published subprocessor list — so the commitment is contractual and the detail is not public.

Pricing is a straight ladder: Hobby at €9 a month for one user and one project, Standard at €29 with unlimited users and projects, Growth at €69 and Premium at €279 for high-volume work, with annual payment at €99, €319, €759 and €3,069 respectively. The trial is 10 days with no credit card, and there is no free plan — the shortest trial and the lowest paid entry point in this category at the same time.

What Flare does well

  • Laravel-native: understands queues, jobs and Livewire rather than generic traces
  • Errors, performance monitoring and log streaming in one product
  • Front-end coverage for JavaScript, React, Vue and Svelte
  • EU-only processing written into the terms of use
  • Entry plan at €9 a month, the lowest paid floor here

Where Flare falls short

  • No free plan and only a 10-day trial, the shortest in this category
  • No provider or region named behind the EU commitment
  • Hobby plan is capped at one user and one project
  • PHP and front-end JavaScript only — nothing for Ruby, Python, .NET or Go
  • No published security certification

Standout feature. Built by Spatie: the Laravel handling comes from the team whose packages are already in the application you are instrumenting.

#5 elmah.io

Laasby, Denmark Small Business $26/month, Business $44, Business+ $89, Enterprise $269, always billed in USD 21-day free trial, no credit card; no free plan

Best for: .NET teams that want error logging, uptime and heartbeats from one Danish vendor

  • Operating company. elmah.io ApS
  • Jurisdiction. EU (Denmark)
  • Where the data sits. Microsoft Azure; the vendor does not state which region
  • Independent checks. PCI DSS, GDPR
  • Source code. Closed source
  • Replaces. Sentry, Raygun, Airbrake

elmah.io is the commercial descendant of ELMAH, the error logging library that a generation of ASP.NET applications shipped with, and it has stayed in that lane.

It supports every .NET web and logging framework, including ASP.NET Core and .NET Lambda, plus JavaScript, and adds the pieces a .NET shop otherwise buys separately: uptime monitoring with SSL certificate validation, heartbeat monitoring for scheduled jobs, deployment tracking across versions, and bot detection to keep crawler noise out of the issue list. An AI assistant explains stack traces and suggests fixes, and an MCP server exposes it to editors like Cursor.

elmah.io ApS is at J M Knudsens Vej 14, 8670 Laasby, Denmark, and the terms are governed by Danish law. The security page states PCI DSS compliance, GDPR, DDoS protection, end-to-end 256-bit TLS, continuous penetration testing and two-factor authentication.

It also states that the service runs on Microsoft Azure — and stops there. Which Azure region holds your exceptions is not published anywhere on the site, which is a gap worth closing with the vendor before signing if residency is in your requirements.

Pricing runs Small Business at $26 a month, Business at $44, Business+ at $89 and Enterprise at $269, with a 21-day trial, no credit card and a 14-day money-back guarantee. Note the currency: a Danish company that always bills in USD, with tax added in USD for some countries, which puts an exchange-rate line into a European budget for no obvious reason. Discounted or free access exists for startups, non-profits, user groups and open-source projects.

What elmah.io does well

  • Covers every .NET web and logging framework, plus JavaScript
  • Uptime, SSL and heartbeat monitoring bundled with error logging
  • Danish company under Danish law, PCI DSS and GDPR stated
  • Bot detection keeps crawler noise out of the issue list
  • 21-day trial, no card, plus free access for open source and non-profits

Where elmah.io falls short

  • Names Microsoft Azure as its platform but never states the region
  • .NET and JavaScript only
  • Always billed in USD despite being a Danish company
  • No free plan
  • Azure underneath means US cloud ownership regardless of the Danish letterhead

Standout feature. The ELMAH lineage: for a .NET team, this is the hosted version of the library the codebase probably already used.

#6 Inspector

Naples and Florence, Italy Free up to 30K transactions a month / Beginner €15, Developer €39, Team €69 per month Free plan with no time limit and no card required

Best for: Small PHP teams that want real monitoring on a free tier that never expires

  • Operating company. Inspector S.R.L.
  • Jurisdiction. EU (Italy)
  • Source code. Closed source
  • Replaces. Sentry, Bugsnag, New Relic

Inspector is the cheapest honest way into this category. The free plan is 30,000 transactions a month with unlimited events, hosts and applications and up to three team members, and the vendor is explicit that it is a monthly quota rather than a countdown — you can run it on a production workload indefinitely without paying.

Above that, Beginner is €15 a month for 300,000 transactions, Developer €39 for 800,000 and Team €69 for 1.5 million, all with unlimited users, REST API access and live chat support.

The product is real-time monitoring for PHP applications with errors and performance together, covering Laravel, Symfony, CodeIgniter and Drupal, plus the Neuron AI framework, with an AI bug fixer on the paid tiers and zero-configuration installation. Inspector S.R.L. is an Italian company with a VAT number of 09552901218 and offices at Via Guantai ad Orsolone 178 in Naples and Via Ippolito Pindemonte 6 in Florence, started with support from the Italian government's Resto al SUD scheme.

The gap is documentation of the things this directory exists to check. Inspector publishes no data residency statement, names no hosting provider or region, and lists no security certification on the pages checked. The company is demonstrably Italian, so the jurisdiction question is settled; where the servers are is not, and for a regulated buyer that is a question to put in writing before signing rather than an assumption to make from the address.

What Inspector does well

  • Free plan of 30,000 transactions a month with no time limit
  • Unlimited users on every paid plan, from €15 a month
  • Laravel, Symfony, CodeIgniter and Drupal covered out of the box
  • Errors and performance monitoring in one product
  • Italian company with published offices in Naples and Florence

Where Inspector falls short

  • No data residency statement anywhere on the site — no provider, no region
  • No published security certification
  • PHP-centric; other runtimes are not covered
  • Free plan caps the team at three members
  • Smallest vendor here, with the thinnest public documentation

Standout feature. A free tier that is a quota, not a trial: Inspector is the only paid-tier vendor here that lets a production application run on the free plan forever.

#7 Bugfender

Walldorf, Germany Free plan (100K log lines a day, 2,000 devices) / Team from $39/month, Pro from $89/month; overage €3.25 per extra million logs Free plan, no credit card

Best for: Mobile teams that need the log leading up to the crash, not just the crash

  • Operating company. Beenario GmbH
  • Jurisdiction. EU (Germany)
  • Where the data sits. European Union, on storage from Wasabi Technologies, Inc.; Cloudflare and Intercom also process data
  • Independent checks. ISO 27001, GDPR
  • Source code. Closed source
  • Replaces. Bugsnag, Sentry, Firebase Crashlytics

Bugfender inverts the usual model. Instead of waking up when an exception is thrown, it logs continuously — 24 hours a day, whether or not anything has gone wrong — and keeps those logs per device, so when a user reports that something behaved strangely you can read what the app actually did rather than guess.

Crash reporting sits on top, with stack traces and automatic symbolication, alongside a user feedback channel that arrives with the device context already attached. That combination is aimed squarely at the mobile bug that does not crash.

Coverage is iOS, Android, JavaScript, React, Angular, Flutter, Unity, Ionic, Xamarin, Cordova and PhoneGap. The operator is Beenario GmbH, Altrottstraße 31, 69190 Walldorf, Germany, VAT DE299463958, registered at Amtsgericht Stuttgart under HRB 752438. The privacy policy is unusually specific about subprocessors: data storage is provided by Wasabi Technologies, Inc. with the data stored in the EU, with StatusPage.io for incidents, Cloudflare for traffic filtering and Intercom for chat. ISO 27001 and GDPR compliance are stated.

Pricing is by log volume, which is the meter to model before signing.

The free plan covers 100,000 log lines a day across up to 2,000 devices with 24-hour retention; Team starts at $39 a month for 10 million monthly log lines with 7-day retention and unlimited devices; Pro starts at $89 with 30-day retention; Enterprise is custom and is where on-premises deployment and a choice of server geography live. Overage runs €3.25 per additional million logs, billed in one-million batches, and annual billing takes 30% off.

What Bugfender does well

  • Continuous remote logging, not only crash capture
  • Crash stack traces with automatic symbolication
  • Eleven platforms covered, including Flutter, Unity and Xamarin
  • German company, ISO 27001 stated, EU data storage
  • Free plan with 100,000 log lines a day and unlimited app installs

Where Bugfender falls short

  • EU storage sits on Wasabi Technologies, Inc., a US corporation
  • Free plan retains logs for only 24 hours
  • Priced per log line, so a chatty debug build is a budget event
  • Choosing your server geography is an Enterprise-only option
  • Mobile and front-end oriented; not a back-end error tracker

Standout feature. The log before the crash: Bugfender is the only tool here that records what a device was doing when nothing had gone wrong yet.

#8 Countly

London, United Kingdom Flex private cloud from $175/month, usage-based; Enterprise self-hosted on request 14-day free trial of Flex

Best for: Mobile product teams that want crash data and usage analytics in the same system, self-hosted if needed

  • Operating company. Countly Ltd
  • Jurisdiction. United Kingdom
  • Where the data sits. Google Cloud, in a region you choose (EU available); the self-hosted Enterprise edition runs wherever you put it
  • Independent checks. GDPR
  • Source code. Closed source
  • Replaces. Firebase Crashlytics, Bugsnag, Mixpanel

Countly treats crashes as one module inside a product analytics platform rather than as the product. That is either the point or the problem depending on who is buying: a product manager gets crash rates sitting next to funnels, retention, cohorts and A/B tests, so "this release crashes" and "this release converts worse" are the same chart. An engineer looking only for stack traces is paying for a great deal of machinery they will not open.

Countly Ltd is incorporated in England and Wales under number 8568329, with a registered office at 1 Bow Churchyard, London EC4M 9DQ and VAT number GB168599344.

Ten SDKs cover iOS, Android, Flutter, JavaScript, React, Node.js, Windows, C++, Java and Unity, with a write API for anything else. Hosting is Google Cloud, in a region the customer picks, with EU regions available; the Enterprise edition is deployed on customer infrastructure with the data location fully customer-defined and, as the vendor puts it, zero vendor access.

That self-hosted route is the reason Countly appears in this directory at all: it is one of only two tools here that can run entirely on your own machines. The cost of entry is high.

Flex private cloud starts at $175 a month on usage-based pricing with a 14-day trial, and Enterprise is quoted rather than listed. Subprocessors for the hosted service include OpenAI for the AI assistant, Intercom for support, Postmark for email and Paddle for payments — a longer list than the specialists here publish.

What Countly does well

  • Crash and error data alongside funnels, retention and cohorts
  • Ten SDKs across mobile, web and desktop, plus a write API
  • Enterprise edition self-hosted with customer-defined data location
  • Choose your Google Cloud region, including EU regions
  • UK company with a published registered office and VAT number

Where Countly falls short

  • Hosted service runs on Google Cloud, a US provider
  • Starts at $175 a month, by far the highest floor in this category
  • An analytics platform first; error tracking is one module of many
  • Longer subprocessor list than the specialists, including OpenAI and Intercom
  • UK jurisdiction rather than EU, so the transfer question is adequacy rather than intra-EEA

Standout feature. Crashes inside the analytics: the only tool here where a crash rate and a conversion rate can be plotted against the same release.

#9 Gleap

Schwarzach, Austria Starter $49/month billed annually ($59 monthly), Team $149, Pro $299, Enterprise from $999 14-day free trial; no free plan

Best for: Product teams that want user-reported bugs to arrive with the console log already attached

  • Operating company. Gleap GmbH
  • Jurisdiction. EU (Austria)
  • Where the data sits. Germany, on DigitalOcean managed databases and application servers in Frankfurt, with Cloudflare for static files and video calls
  • Source code. Closed source
  • Replaces. Usersnap, Instabug, Jira issue collectors

Gleap is not an error tracker and should not be bought as one.

It is an in-app feedback and bug reporting layer: a user presses a button, and the report arrives with console logs, a screenshot, session replay and the technical context around the moment, so the ticket is reproducible instead of being three sentences and a guess. That closes a real gap — the bug a user can see and the tracker cannot, because nothing threw — but it only ever fires when a human decides to press the button.

Gleap GmbH is at Am Dorfplatz 3, 6858 Schwarzach, Austria, registered at the Regional Court of Feldkirch under FN 534390 v with VAT ATU 75671417. The hosting is described precisely in the privacy policy: the main infrastructure and production MongoDB database run on DigitalOcean managed databases and application servers in Frankfurt, Germany, with Cloudflare providing static file hosting for screenshots and attachments and the video-call infrastructure. Azure and AWS are named as providers no longer used.

The AI features are where the subprocessor list gets long and worth reading before enabling them: ElevenLabs, MongoDB/Voyage AI, OpenAI Ireland Ltd and Grok are routed through EU endpoints, but the policy states that Anthropic may process in the US or the EU without an EU-only guarantee, OpenRouter may route to the EU, US or China, and DeepSeek processes in China.

Pricing starts at $49 a month billed annually for Starter, $149 for Team, $299 for Pro and from $999 for Enterprise, with a 14-day trial and no free plan.

What Gleap does well

  • Bug reports arrive with console logs, screenshot and session replay attached
  • Servers in Frankfurt, Germany, named down to the provider and database
  • Austrian GmbH with full register and VAT details published
  • Covers websites and mobile apps from one SDK
  • Unusually candid privacy policy about where each AI subprocessor runs

Where Gleap falls short

  • Not an error tracker: nothing is captured unless a user reports it
  • Infrastructure is DigitalOcean and Cloudflare, both US companies
  • Some AI features route to Anthropic, OpenRouter or DeepSeek outside the EU
  • No free plan and $49 a month is a high floor for the job it does
  • No published security certification

Standout feature. A precise hosting statement: Gleap names the provider, the service and the city, which most vendors in this category do not.

#10 Marker.io

Brussels, Belgium Starter $39/month billed annually ($59 monthly), Team $149 ($199 monthly), Business on request 15-day free trial, no credit card; no free plan

Best for: Agencies and QA teams pushing client-reported website bugs into an existing issue tracker

  • Operating company. Marker.io SRL
  • Jurisdiction. EU (Belgium)
  • Where the data sits. Amazon Web Services, described by the vendor only as ISO 27001-certified infrastructure; no region is stated
  • Independent checks. Hosting infrastructure ISO 27001-certified (AWS)
  • Source code. Closed source
  • Replaces. BugHerd, Usersnap, Jira issue collectors

Marker.io sits between the person who found the bug and the developer who has to fix it.

A reporter annotates the page, and the issue lands in Jira, Linear, GitHub or the tracker the team already uses, carrying session replay, console logs and the technical context of the session rather than a screenshot pasted into an email. For agencies collecting feedback from clients who will never have a tracker login, that routing is the entire product, and it is done well.

Marker.io SRL is a Belgian company registered under number 0556685968 with its registered office at Avenue Louise 231, 1050 Brussels. The DPA states that hosting is on AWS and describes it as ISO 27001-certified infrastructure — which is AWS's certificate rather than Marker.io's, and no region is named. So the company is Belgian and the servers are a US cloud in an unstated location: the ownership question is answered and the residency question is not.

Pricing is $39 a month for Starter billed annually ($59 monthly) with three users and unlimited feedback, $149 for Team ($199 monthly) with fifteen users, and Business on request with yearly billing only. An agency plan gives fifteen members, fifty projects and fifty guests at $99 a month annually. The trial is fifteen days with no credit card, all prices are in USD, and there is no free plan.

What Marker.io does well

  • Reports land directly in Jira, Linear, GitHub or your existing tracker
  • Session replay and console logs attached to each report
  • Guests can report without a licence in your issue tracker
  • Belgian company with published registration and registered office
  • 15-day trial with no credit card, plus a dedicated agency plan

Where Marker.io falls short

  • Not an error tracker: nothing is captured unless a human submits it
  • Hosted on AWS with no region stated anywhere
  • The ISO 27001 claim belongs to AWS, not to Marker.io
  • Priced in USD with no free plan, from $39 a month for three users
  • Web only — no mobile SDK

Standout feature. It never becomes a second backlog: Marker.io deliberately files into the tracker you already run rather than asking the team to watch another inbox.

Why does an error tracker deserve more scrutiny than the rest of your stack?

Because of what is inside the payload. An error report is not a metric; it is a snapshot of your application at the moment it failed.

Depending on the SDK and its configuration that includes the full stack trace, the values of local variables in every frame, the request body, HTTP headers including cookies, the session, the user id and often the email address of whoever hit the bug. Teams that carefully avoid sending personal data to their analytics tool send all of it to their error tracker without noticing.

The failure mode is specific and common: a payment handler throws, and the exception payload carries the order, the address and a partially masked card reference off to a third party for thirty or ninety days of retention. A background job retries against an API and the bearer token sits in a local variable in frame three. None of this is malice, and none of it appears in a data map drawn from the architecture diagram.

That is why jurisdiction is the first question here rather than the fifth. With a processor established in the EU — AppSignal in Amsterdam, Tideways in Bonn, Flare in Antwerp, Bugsink in Utrecht, elmah.io in Laasby, Inspector in Naples — the processing is intra-EEA and there is no transfer to assess. With a US-established provider, the transfer runs on the EU-US Data Privacy Framework, and somebody has to verify that the specific entity is certified and keep that verification current.

The cheapest mitigation is not a vendor change at all: strip the payload at the SDK before it leaves. Every tool here supports scrubbing fields and headers. Do that first, then choose where the remainder lands.

Which language do you actually write? That decides this category.

This is the category where the shortlist is set by the runtime rather than by preference. Tideways is PHP and nothing else — it extends the PHP engine, which is exactly why its profiler is good and exactly why it is useless to a Django team. Flare is Laravel and PHP first, with front-end JavaScript, React, Vue and Svelte alongside. Inspector covers Laravel, Symfony, CodeIgniter and Drupal. elmah.io is .NET only, across every .NET web and logging framework, plus JavaScript.

AppSignal is the broadest: first-party integrations for Ruby, Elixir, Node.js, Python and front-end JavaScript, with Go, Java, PHP and Rust reaching it through OpenTelemetry. If you run more than one language in production, it is the only tool here that will not force a second contract.

Bugsink sidesteps the question entirely by implementing the Sentry SDK protocol. Whatever Sentry client already exists for your language — and that is most of them — can point at a Bugsink instance instead. That is a different kind of coverage: Bugsink does not write the SDKs, it receives what they send.

On mobile, Bugfender and Countly are the two options. Bugfender covers iOS, Android, Flutter, React, Unity, Xamarin and Cordova with crash stack traces and automatic symbolication; Countly ships ten SDKs across mobile, web and desktop and treats crashes as one module inside a product analytics platform.

European company or European infrastructure — which one are you buying?

They are not the same claim, and this category shows the gap clearly. Tideways stores account, monitoring and profiling data at SysEleven in Berlin: a German company on a German host. AppSignal runs on Worldstream B.V., a Dutch hosting company, with backups on Amazon Web Services EMEA SARL — European at the primary, US-owned at the backup, and the vendor says so.

Below that line it gets thinner. Bugfender is a German company, Beenario GmbH in Walldorf, but its storage subprocessor is Wasabi Technologies, Inc. with data in the EU — US corporate ownership, European region. Gleap is an Austrian GmbH running on DigitalOcean in Frankfurt. Countly is a UK company on Google Cloud in whichever region you select. Marker.io is a Belgian SRL on AWS and does not say which region at all.

Then there is what nobody states. Inspector publishes no residency information anywhere on its site. elmah.io names Microsoft Azure but not a region. Flare and Bugsink both commit to "the European Union" in writing without naming a provider. A written EU commitment in the terms is enforceable and a marketing sentence is not, so read where the claim appears before treating it as a control.

None of this makes the weaker options unusable. It makes them unusable for the specific buyer — a hospital, a ministry, a bank — whose requirement is a named data centre in a named country. For everybody else, "processed in the EU, in the contract" is the line that matters.

Self-hosting error tracking: what it costs and what it saves

Bugsink is the only tool in this category you can run on your own hardware, and it is deliberately small: a single Django application with a database, installable by Docker, with unlimited users and every feature in the free self-hosted edition. That is a direct answer to the reason people stopped self-hosting Sentry, which grew into a multi-service cluster that needs a team to keep alive.

What self-hosting saves is the transfer question. No processor, no DPA, no retention policy to audit, no sampling decision driven by a billing tier. For a team whose exceptions routinely carry regulated data, that is the whole argument, and the licence fee of zero is beside the point.

What it costs is the thing nobody budgets. Error volume is spiky by nature — one bad deploy generates a million events in an hour — so the box has to be sized for the worst day, the disk has to be watched, and somebody has to be responsible when the ingestion endpoint is the thing that falls over during an incident.

An error tracker that is down during an outage is worse than no error tracker, because you believe it.

Note also that Bugsink's PolyForm Shield License 1.0.0 is source-available rather than open source. You may read it, modify it and run it internally without paying; you may not use it to build a competing product. For internal use the distinction is academic, and for anyone planning to resell it is the whole document. Countly Enterprise is the other self-hosted route here, but it is a commercial licence on request rather than a free download.

Where error tracking rollouts go wrong

The first failure is alerting on every exception. A tracker that emails on each event trains the team to filter the mailbox, and within a month nobody reads any of it. Group by fingerprint, alert on new issues and on regressions, and leave the long tail to the weekly review.

The second is pricing by the wrong unit. This category prices on at least four different meters: AppSignal and Tideways per request, Inspector per transaction, Bugsink per event, Bugfender per log line, Countly per usage on a $175 floor. A retry storm that is cheap on one meter is a budget incident on another, so model your worst hour, not your average month.

The third is leaving source maps and symbols out of the deploy pipeline. A minified front-end stack trace or an unsymbolicated iOS crash tells you that something failed, which you already knew. Bugfender symbolicates automatically; for the JavaScript tools, uploading source maps on deploy is a five-line CI step that most teams add only after the first unreadable incident.

The fourth is buying a bug-reporting tool when you needed an error tracker. Gleap and Marker.io produce excellent reports with console logs and session replay attached — but only when a human notices and submits one. The silent 2% failure rate on a checkout flow will never generate a single report, and that is precisely the failure you bought monitoring to find.

How we selected and ranked these 10 tools

Every tool on this page is in the European Purpose directory, which means the operating company is established in Europe and we have verified that from the company register or the vendor's own legal notice rather than from a marketing page. Tools headquartered outside Europe are not eligible, however good they are.

  1. Feature verification (weight: 40%). We check each capability against the vendor's own documentation and product pages, and record what the tool does rather than what the category is assumed to include.
  2. Ease of adoption (weight: 30%). Integrations, published API access, trial availability and how much configuration stands between signing and a usable result.
  3. Value and transparency (weight: 30%). Published pricing counts in a vendor's favour; quote-only pricing is recorded as quote-only rather than estimated. We weigh what a buyer gets for the entry price, not the headline feature count.
  4. Editorial review. Three people touch every page: one writes it, a second edits it, and a third checks the compliance and pricing claims against the vendor's documentation. The three weights above decide the order; a position is a ranking against the other European tools in this category, not an absolute score.

Vendor-reported outcomes — ROI figures, margin uplift, time saved — are labelled as vendor claims wherever they appear on this page. We have not audited them, and neither has anyone else who quotes them. Read our full editorial process for how pages are re-verified.

Frequently asked questions

AppSignal holds #1 among the European error tracking tools in this directory, because AppSignal combines first-party support for Ruby, Elixir, Node.js, Python and front-end JavaScript with ISO 27001 and SOC 2, and hosts on Worldstream in the Netherlands rather than on a US cloud with a European label.

The right answer depends on the runtime: Tideways for PHP where you also want a profiler, Flare for Laravel, elmah.io for .NET, Inspector for a free PHP monitoring tier, Bugsink when the data must never leave your own machines, and Bugfender or Countly for mobile crashes.

Yes, and one of them is a drop-in. Bugsink, from Bugsink B.V. in Utrecht, implements the Sentry SDK protocol, so an application already instrumented with a Sentry client only needs its DSN changed to point at a self-hosted or EU-hosted Bugsink instance. For a hosted product with more around it, AppSignal in Amsterdam covers errors, performance, logs and uptime with all customer data stored in the European Union, and Flare in Antwerp does the same for Laravel and PHP teams.

Bugsink is free to self-host with unlimited users and every feature, and its hosted plan is free up to 15,000 events a month.

Inspector gives 30,000 transactions a month free with no time limit — a monthly quota rather than a trial. AppSignal has a free plan at 50,000 requests with 1GB of logging and five-day retention. Bugfender's free plan covers 100,000 log lines a day across up to 2,000 devices, with 24-hour retention. Flare, elmah.io, Gleap and Marker.io offer trials only.

Bugsink is the one built for it: a single application with a database, installable by Docker, free with unlimited users, and deliberately simpler than self-hosted Sentry.

It is source-available under the PolyForm Shield License 1.0.0, which permits internal use and modification but forbids building a competing product from it. Countly Enterprise is also customer-deployed, with the data location fully customer-defined, but it is a commercial licence priced on request rather than a free download. Every other tool here is cloud only.

AppSignal states ISO 27001 and SOC 2 certification alongside GDPR compliance, with HIPAA available as a paid add-on, and it runs regular penetration tests and a bug bounty.

Bugfender states ISO 27001 and GDPR compliance. elmah.io states PCI DSS compliance and GDPR. Marker.io claims ISO 27001 only for the hosting infrastructure it rents, which is AWS's certificate rather than its own — a distinction worth reading carefully. Tideways, Flare, Inspector, Countly and Gleap publish no certification claim on the pages checked.

Tideways stores account, monitoring and profiling data at SysEleven in Berlin, Germany. AppSignal stores customer data in the European Union on Worldstream B.V., with backups on Amazon Web Services EMEA SARL. Gleap runs on DigitalOcean in Frankfurt.

Bugfender stores in the EU on Wasabi Technologies, Inc. Countly runs on Google Cloud in a region you choose. Flare and Bugsink commit in writing to processing within the European Union without naming a provider. elmah.io names Microsoft Azure but not a region, and Inspector publishes no residency statement at all.

Three compete directly. Tideways is PHP-only by design and pairs error and exception tracking with a callgraph profiler, hosted in Berlin, from €69 a month.

Flare is Laravel-first, with proper handling of queues, jobs and Livewire plus front-end JavaScript, from €9 a month with a 10-day trial and no free plan. Inspector covers Laravel, Symfony, CodeIgniter and Drupal and is the only one with a permanent free tier, at 30,000 transactions a month. If you need to know why a request is slow as well as why it threw, Tideways is the one with the profiler.

elmah.io, from elmah.io ApS in Laasby, Denmark. It grew out of the ELMAH error logging library and supports every .NET web and logging framework, including ASP.NET Core and .NET Lambda, plus JavaScript, and bundles uptime and heartbeat monitoring.

Pricing runs from $26 to $269 a month with a 21-day trial and no free plan. Two caveats: it always bills in USD despite being a Danish company, and it names Microsoft Azure as its platform without stating which region your data sits in.

Bugfender, from Beenario GmbH in Walldorf, Germany, covers iOS, Android, Flutter, React, Unity, Xamarin and Cordova, with crash stack traces and automatic symbolication, and keeps logging continuously rather than only when something crashes — which is how you debug the bug that does not throw.

Countly, from Countly Ltd in London, treats crashes as one module beside product analytics across ten SDKs, and can be self-hosted. Bugfender's free plan makes it the easier one to start with; Countly starts at $175 a month.

No, and they should not be bought as if they did. Both capture a bug when a person reports one: Gleap attaches console logs, screenshots and a session replay from its SDK in websites and mobile apps, and Marker.io pushes annotated reports with console logs and replay into Jira, Linear or GitHub.

Neither watches production for exceptions nobody noticed. They belong next to an error tracker, closing the gap between "a user says checkout is broken" and a reproducible ticket — not in place of one.