Panel rating · 6 judges · How to read the stars

Category median

Sovereignty: 3 of 6 dimensions proven

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

by Facade BV · flareapp.io

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

Link to this page

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

Flare at a glance

Vendor
Facade BV
Headquarters
Incorporated in Belgium source, captured 6 Nov 2026
Data hosting
Not stated on the vendor’s pages as of 6 Nov 2026
Free plan
Not stated on the vendor’s pages as of 6 Nov 2026
Panel verdict
The AI panel rates Flare 2.5/5, the mean of 6 judges. Flare, by Facade BV (Spatie) of Antwerp, tracks errors, performance and logs for Laravel, PHP and JavaScript applications. how scores are made
As of
Vendor pages captured 6 Nov 2026; evaluated by the panel 6 Nov 2026. all sources

Flare alternatives, European ones first →

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

The panel's verdict

Flare, by Facade BV (Spatie) of Antwerp, tracks errors, performance and logs for Laravel, PHP and JavaScript applications. Pricing transparency earned the top score, a flat 7: every plan's yearly price is public — €99 for the single-user Hobby plan up to €3,069 for Premium — with exact monthly quotas, and data stops at limits rather than billing overage. Performance tracing and workflow and integrations scored flat 6s, error tracking 5-6, crediting documented trace sampling, notifications across email, Slack, Teams, Discord, SMS and webhooks, and issue sync with GitHub, GitLab, Jira and Linear. Security and reliability is the weak spot and drew the widest spread, 2 to 4, the low end resting on unanswered audit questions: nothing public found on two-factor authentication, single sign-on, encryption, ISO 27001 or SOC 2, or an SLA, with support best-efforts only. Data controls scored 4-5: nothing public on scrubbing of passwords or tokens; retention a flat 30 days. Sovereignty scored 6-7: Belgian law, Antwerp courts, terms stating all data is processed within the European Union, a downloadable DPA, hosting unnamed and subprocessor locations unstated.

Report an error

Speaks for it

  • Every plan's yearly price is public with exact monthly quotas, an email at 80 percent of a limit, and a stop on new data rather than overage billing.
  • Trace sampling is documented in depth — a 10 percent default, per-route and per-queue rules, custom samplers — with runtime overhead stated.
  • Issues are created and closed in sync with GitHub, GitLab, Jira and Linear, with stack frames opening directly on GitHub.
  • Spike protection saves one error per minute during spikes, with the trigger threshold, kept occurrences and check interval configurable.
  • The terms state all data is processed within the European Union, under Belgian law with the courts of Antwerp, and a DPA is downloadable for signature.

Report an error

Held against it

  • We found no public information on two-factor authentication, single sign-on, audit logs, encryption, ISO 27001 or SOC 2, or an SLA, and the terms put support on a best-efforts basis.
  • We found no public information on scrubbing of passwords, tokens or card numbers, or on IP anonymisation, and retention is a flat 30 days on every plan.
  • Coverage is Laravel, PHP and JavaScript, with no public information found on mobile SDKs, source maps or symbolication.
  • We found no public information on PagerDuty or Opsgenie, alerts on performance thresholds, or scheduled reports.
  • We found no public information on monthly prices or VAT treatment, and the captured pages give different figures for the free trial length — fourteen days in the terms, ten on the pricing page, which advertises no credit card required.

Report an error

Best for

  • You run Laravel, PHP or JavaScript applications and want framework-native context such as decompiled Blade templates and queue-job errors.
  • You want predictable costs, with public yearly prices, hard quotas, spike protection and no overage billing.
  • You are a European buyer who wants a Belgian vendor whose terms state all data is processed within the European Union and a DPA available for signature.
  • You manage many client projects and need unlimited users and projects on team plans, with read-only access for clients.

Report an error

Avoid if

  • Your stack includes Go, Python or mobile platforms; every captured page frames coverage around Laravel, PHP and JavaScript.
  • Your procurement requires two-factor authentication, single sign-on, ISO 27001 or SOC 2, or guaranteed response times, for which we found no public information.
  • You need retention beyond 30 days, as the stated retention is 30 days on every plan.
  • You need self-hosting; the terms explicitly withhold on-premises rights.

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

Exception capture with stack traces, request and user context, and genuinely Laravel-native context — queue job errors with the affected queue, decompiled Blade templates, and grouping that understands a failed query — is exactly what my PHP teams need. Grouping is documented better than most: two algorithms with their exact criteria explained, switchable per project, and customizable by targeting exception classes, on top of a long list of search directives for errors and individual occurrences. We found no public information on source maps, regression detection or deploy tracking from CI, so it sits above the basic level but short of the full-lifecycle tier. 5 12 13 2

Report an error

The SaaS CTO

Exception capture with grouping, stack traces and request and user context is documented, and the grouping is unusually well explained — two switchable algorithms with their exact criteria plus custom grouping by exception class — alongside a rich search grammar, resolve and snooze states, and filtering and snoozing by application version. But coverage is Laravel, PHP and JavaScript only, so my Go and Python services would send nothing here, and we found no public information on source maps, symbolication, suspect commits or mobile platforms. 5 12 13 2 9

Report an error

The Mobile Team Lead

Exceptions arrive with stack traces, request and user context, and grouping documented down to per-exception-class rules with two switchable algorithms, plus a deep search syntax covering issue states, app version, users affected and occurrence counts. As the lead of an iOS/Android/Flutter team I have to be blunt: every captured page frames the platform around Laravel, PHP and JavaScript, and we found no public information on mobile SDKs, native symbolication or crash-free sessions per release — the release story that exists is a version filter and Git context on PHP errors. 2 5 12 13

Report an error

The Site Reliability Engineer

Exception capture with stack traces, request and user context, and grouping are documented in unusual depth: two grouping algorithms with their criteria explained per exception type, grouping customizable per exception class, JavaScript and PHP exceptions from the same request grouped together, plus a rich search language over errors and occurrences. Coverage is deliberately narrow — Laravel, PHP and JavaScript with React, Vue and Svelte — and we found no public information on platforms beyond those, on source maps, on regression detection or on crash-free users and sessions; the documented issue states are resolved, unresolved and snoozed, with snoozing by count, timeframe or until the next app version. 5 12 13 2 1

Report an error

The Data Protection Officer

Exception capture with stack traces, request and user context is documented for Laravel, PHP and JavaScript, and the grouping documentation is unusually thorough: two explained algorithms, switchable per project, customizable by targeting exception classes, with resolved, unresolved and snoozed states plus a rich search syntax down to the individual occurrence. We found no public information on mobile SDKs, source maps or symbolication, or regression detection, so the platform set stays narrow for a house that runs more than PHP and JavaScript. 5 12 13 16

Report an error

The Skeptic

Grouping is documented deeper than most vendors bother: two explained algorithms, customization per exception class, occurrence-level search with a long list of filters, resolve and snooze states, and Laravel context down to decompiled Blade templates. But the platform list is Laravel, PHP and JavaScript only, and we found no public information on mobile SDKs, source maps for the JavaScript side, merging or splitting issues, or release health statistics. Strong triage inside that one stack. 2 5 12 13

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

Routes, jobs and queries each get p95 and average timings with slowest-query lists, n+1 detection is named, exceptions are marked on the span timeline, and traces can follow a command through several queued jobs — the find-the-slow-page-before-the-client-calls workflow is covered, with frontend Core Web Vitals too. Trace sampling is documented unusually honestly, down to the runtime overhead of a sampled trace, with per-URL, per-route, per-queue rules and W3C traceparent propagation. We found no public information on code-level profiling, host or container metrics, or anomaly detection, and the OpenTelemetry statement covers log-level parsing rather than full trace ingestion. 14 15 19 1

Report an error

The SaaS CTO

Routes, jobs and queries come with p95 and average timings, traces with span timelines where exceptions are marked, slow-query and N+1 detection, Core Web Vitals for the JavaScript frontend, and W3C traceparent propagation with dynamic sampling documented down to its runtime overhead — the sampling documentation is the best I have seen at this vendor size. It stays below the top because distributed tracing is documented within one application and its queued jobs rather than across services, and we found no public information on code-level profiling, host or container metrics, or anomaly detection; OpenTelemetry compatibility is documented for log levels rather than full trace ingestion. 14 15 19 1 4

Report an error

The Mobile Team Lead

Per-route, per-query and per-job timings with the slowest 5% and averages, slow-query and N+1 detection in traces, queue-job spans, Core Web Vitals for the frontend, and a refreshingly honest sampling write-up with a 10% default, dynamic rules per route, queue or command, and a stated runtime overhead. We found no public information on code-level profiling, host or container metrics or anomaly detection, and cross-service tracing rests on W3C traceparent propagation. 1 14 15 19

Report an error

The Site Reliability Engineer

Per-endpoint p95 and average timings for routes, queued jobs, commands and queries, slow-query and N+1 detection, traces with exceptions marked on the span timeline, and Core Web Vitals for the frontend are all documented. Trace sampling is exceptionally well documented — a default of 10 percent, dynamic rules per URL, route, command, queue or connection, custom samplers, W3C traceparent propagation across services and queued jobs, and the runtime overhead stated honestly. We found no public information on code-level profiling, service maps, anomaly detection on latency or throughput, or host and container metrics beside the traces. 14 15 19 1

Report an error

The Data Protection Officer

Slowest-5% and average timings per route, query and job, slow-query and N+1 detection, exceptions marked directly on the span timeline and Core Web Vitals for the frontend cover what a Laravel application needs, and trace sampling is documented with a stated ten percent default, rule types, deferred decisions and honest wording on runtime overhead. We found no public information on code-level profiling, host or container metrics, or anomaly detection on throughput and latency. 1 14 15 19

Report an error

The Skeptic

Routes, queries and jobs each get p95 and average timings, traces show span timelines with exceptions marked on them, slow queries and N+1 patterns are called out, Core Web Vitals are monitored on the JavaScript side, and the sampling docs are unusually honest about runtime overhead. We found no public information on code-level profiling, host or container metrics, or anomaly detection, and the OpenTelemetry statement covers log levels rather than trace ingestion. What a Laravel and PHP team needs, without the surrounding APM machinery. 1 3 14 15 19

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

Notifications go to email, Slack, Teams, Discord, SMS and webhooks and are configurable at account, team and project level, so each of my forty client projects can carry its own channel — rare to see spelled out this clearly. GitHub, GitLab, Jira and Linear issues are created and closed in sync, stackframes link straight to GitHub, and there is an AI assistant for fixing errors plus a CLI, an API and an MCP server. We found no public information on an on-call tool like PagerDuty or Opsgenie, alerts on performance thresholds, scheduled digests, or which model runs the assistant. 16 2 5 1

Report an error

The SaaS CTO

Errors reach people through email, Slack, Discord, Microsoft Teams, SMS and webhooks with triggers on each occurrence, the tenth and on resolutions, configurable at account, team and project level; GitHub, GitLab, Jira and Linear create and close issues in sync, stackframes open directly on GitHub, and there is a CLI, a documented API, an MCP server and an AI assistant that fixes errors and slow routes. We found no public information on PagerDuty or Opsgenie on-call routing, alerts on performance thresholds, scheduled digests, or which model provider runs the AI features. 16 2 5 1 17

Report an error

The Mobile Team Lead

Email, Slack, Discord, Teams, SMS and webhook notifications with triggers per error, per Nth occurrence and on resolve or snooze, configured at account, team and project level, plus create-and-close issue sync with GitHub, GitLab, Jira and Linear, GitHub stackframe links, and a CLI, MCP server and API. We found no public information on on-call routing tools, performance or release-regression alert rules, deploy hooks from CI, or the model behind the AI assistant — nothing here would flag a crashing store rollout for my team. 2 5 16

Report an error

The Site Reliability Engineer

Notifications go to email, Slack, SMS through Vonage, Discord, Microsoft Teams and webhooks, configurable at account, team and project level with triggers on each error, the tenth occurrence, resolution and snoozing — but we found no public information on PagerDuty or Opsgenie, which is how I would page an engineer at 3am. Issue tracker sync with GitHub, GitLab, Jira and Linear creates and closes issues, stackframes link straight to GitHub, and a CLI, API, MCP server and an AI assistant that suggests fixes for errors and slow routes are documented, though we found no public information naming the model behind the assistant. We found no public information on alerts on performance thresholds or on scheduled and digest reports. 16 2 5 1

Report an error

The Data Protection Officer

Notifications reach email, Slack, Microsoft Teams, Discord, SMS and webhooks with triggers on each error, the tenth occurrence, resolution and snoozing, configured at account, team and project level, and GitHub, GitLab, Jira and Linear issues are created and closed in sync; a CLI, API and MCP server are also named. The AI assistant is an advertised feature on every plan, but we found no public information on which model runs it or where, and no on-call tool or scheduled reports are named. 1 2 5 6 16

Report an error

The Skeptic

Notifications go out via email, Slack, Teams, Discord, SMS and webhooks with triggers like every error, the tenth, resolved and snoozed, configurable at account, team and project level, and GitHub, GitLab, Jira and Linear issues are created and closed in sync with stack frames linking straight to GitHub. There is a CLI, an API and an AI assistant with an MCP server — but the model behind the assistant is never named, and we found no public information on performance alerts, scheduled reports, or PagerDuty and Opsgenie. Good reach; the on-call and reporting edges are thin. 1 2 5 16

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

The volume side is the most agency-friendly I have seen: spike protection that activates above a configurable sixty errors a minute and then saves one per minute, quotas that stop accepting new data at the limit with an email at eighty percent, separate counters for errors, spans and logs, and a flat thirty-day retention — a runaway cron exception cannot inflate the bill. Trace sampling is configurable in depth. We found no public information on scrubbing of passwords, tokens or request bodies in the SDK or on the server, which is what I need before pointing this at shops holding customer addresses, and the terms state that on-premises licences are not granted. 18 6 19 9

Report an error

The SaaS CTO

Volume control is genuinely strong: monthly quotas per error, span and log type with separate counters, an email at 80 percent, a hard stop on new data rather than an overage invoice, spike protection whose mechanism and settings are fully documented, and sampling from a default 10 percent up to per-queue rules and custom samplers; retention is 30 days on every plan with permanent deletion 30 days after cancellation and export beforehand. But we found no public information on scrubbing of passwords, tokens or personal data in the SDK or on the server, IP anonymisation, or filters that drop events before they count toward quota. 6 18 19 9 2

Report an error

The Mobile Team Lead

Volume control is the strong half: quotas that stop ingestion at the limit with an 80% warning email, separate counters for errors, spans and logs, configurable spike protection (a default trigger of 60 errors per minute, one error per minute saved while active), and dynamic trace sampling. We found no public information on SDK or server-side scrubbing of passwords, tokens or card numbers, IP anonymisation, or opting out of request bodies and user data, and retention is one 30-day figure on every plan rather than a setting. 3 6 18 19

Report an error

The Site Reliability Engineer

Volume control is the strongest part: spike protection is documented down to its behaviour — one error per minute kept while active, checks every three minutes, all three settings configurable, notification on activation, a five-entry trigger history — quotas stop accepting new data at the limit with an email at 80 percent, error, span and log counters are separate, and SDK-side trace sampling is configurable with its overhead stated. This is exactly the protection I want so an incident does not also become a billing incident. We found no public information on scrubbing of passwords, tokens or card numbers, on IP anonymisation, or on opting out of request bodies and user data; retention is a flat 30 days on every plan, with self-service account deletion and export of error reports before cancelling. 18 6 19 2

Report an error

The Data Protection Officer

Volume controls are genuinely well documented — configurable spike protection that saves one error per minute while active, a hard stop at each quota with email at eighty percent, and trace sampling with its overhead explained — and retention is a stated thirty days with deletion on request and self-service account deletion. But we found no public information on scrubbing of passwords, tokens or personal data either in the SDK or on the server, nor on IP anonymisation or opting request bodies out, which is exactly the question I would put before any member-facing application ships here. 6 9 10 18 19

Report an error

The Skeptic

The volume side is honest: a default 10 percent sample rate with rules you can write yourself, spike protection that drops to one error a minute with the trigger, saved-error count and check interval all configurable, an email at 80 percent of quota and a hard stop at the limit — no surprise overage bill, though no new data either until reset or upgrade. Retention is a flat 30 days on every plan, data is exportable and deleted on request, and errors, spans and logs have separate counters. What I could not find: any documented scrubbing of passwords, tokens or card numbers, IP anonymisation, or per-project retention — and the terms explicitly withhold on-premises rights, with no self-hosted edition priced or described on the captured pages. 6 9 10 18 19

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

Multiple teams and projects with owner and admin roles, plus read-only access for clients and project managers, cover day-to-day agency access control, and there is a public status page with sixty-day uptime figures and an incident history. We found no public information on two-factor authentication, single sign-on, encryption in transit and at rest, certifications such as ISO 27001 or SOC 2, a security page, or an availability commitment; support is explicitly best efforts with no guaranteed response times. 2 7 16 9

Report an error

The SaaS CTO

Teams and projects come with fine-grained access control, read-only access for clients and admin-only notification settings, and there is a public status page with per-endpoint uptime over 60 days (the API at 99.628 percent) and an incident history. We found no public information on single sign-on, SCIM, two-factor authentication, encryption in transit and at rest, certifications such as ISO 27001 or SOC 2, or any availability commitment — the terms state support and response times are best-efforts only. 2 16 7 9

Report an error

The Mobile Team Lead

Teams and projects with fine-grained access control and read-only client access, a public status page showing 60-day uptime per endpoint with full incident history, a downloadable DPA and Belgian-law terms form a credible base for a small vendor. We found no public information on two-factor authentication, single sign-on, encryption in transit and at rest, ISO 27001 or SOC 2, audit logs or an SLA — the terms explicitly put support on a best-efforts footing with no guaranteed response times. 2 7 9 11

Report an error

The Site Reliability Engineer

Teams and projects with fine-grained access control, read-only access for clients or a PM, and owner and admin role separation are documented, and the vendor runs a public status page with 60-day uptime numbers per endpoint, incident history and subscription to updates — and Flare reports its own errors and traces into itself, which I respect. We found no public information on two-factor authentication, SAML or OIDC single sign-on, SCIM provisioning, audit logs, encryption in transit and at rest, ISO 27001 or SOC 2, or on how the SDK behaves when the vendor is down. The terms state support is best-efforts with no guaranteed response or intervention times, and we found no public information on an availability SLA with credits. 2 16 7 9 8

Report an error

The Data Protection Officer

Multiple teams with fine-grained access control, read-only project access and an owner-admin distinction are documented, and the vendor runs a public status page with per-endpoint uptime over sixty days and a full incident history. We found no public information on two-factor authentication, single sign-on, audit logs, encryption, certifications or an SLA — support is explicitly best-efforts without guaranteed response times — so this would not yet survive our vendor security review. 2 7 9 16

Report an error

The Skeptic

Teams and projects come with owner, admin and read-only roles, and there is a public status page publishing 60-day uptime per own endpoint (99.62 to 99.964 percent) with incident history and subscription. We found no public information on two-factor authentication, single sign-on, audit logs, encryption, ISO 27001 or SOC 2, a security page, or an SLA — support is explicitly best-efforts with no guaranteed response times. The vendor publishes its own uptime honestly; the rest of what an auditor asks first goes unanswered. 2 7 9 16

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

Facade BV in Antwerp, registered with a Belgian company number and governed by Belgian law with exclusive jurisdiction in Antwerp, states that all data is processed within the European Union, publishes a data processing agreement to sign, names the Belgian data protection authority for complaints, and has no outside investors — as a European agency that is the chain I want to buy from. The two named service providers (PostHog for analytics, Mailcoach for account emails) are given without locations, the hosting third party is not named, and no certifications are stated, so it falls short of the fully documented end-to-end chain. 9 11 10 8

Report an error

The SaaS CTO

This is the strongest suit for my EU-region requirement: Facade BV is registered in Antwerp under Belgian law with Antwerp courts, the terms state all data is processed within the European Union, a data processing agreement is published for download and signature, subprocessors are named (PostHog for product analytics, Mailcoach for account emails), and the company has no outside investors or shareholders. The open questions: the hosting infrastructure is not named, subprocessor locations and the provider behind the AI assistant are unstated, we found no public information on security certifications, and the terms themselves withhold on-premises rights, so there is no self-hosted chain. 9 10 11 8 1

Report an error

The Mobile Team Lead

Facade BV is registered in Antwerp, Flare is built by Spatie with no outside investors, the terms state that all data is processed within the European Union and are governed by Belgian law with Antwerp courts, and a DPA is published for signature with PostHog and Mailcoach named as subprocessors. The hosting provider is unnamed, the subprocessors' locations are not stated, we found no public information on security certifications, and the terms withhold on-premises rights — a solid European chain, not yet mapped end to end. 8 9 10 11

Report an error

The Site Reliability Engineer

The contracting entity is Facade BV in Antwerp with a Belgian enterprise number, Belgian law and the courts of Antwerp apply, the vendor states it has no outside investors or shareholders, the terms state all data is processed within the European Union, a data processing agreement is downloadable for signature, and the privacy policy names the Belgian data protection authority as complaint authority. Subprocessors PostHog for product analytics and Mailcoach for account emails are listed, but their locations are not stated in the captured pages, the hosting provider behind the SaaS is not named, and we found no public information on where the AI assistant's model runs or on security certifications. We found no public information on a self-hosted edition; the terms explicitly withhold on-premises rights. 9 10 11 1 8

Report an error

The Data Protection Officer

The chain is Belgian and European as far as it is documented: Facade BV in Antwerp with a CBE registration, Belgian law and Antwerp courts, no outside investors, a downloadable data processing agreement with controller-processor roles, and the terms state all data is processed within the European Union. The hosting provider is not named, the two listed subprocessors — PostHog for analytics and Mailcoach for account email — are given without locations, we found no public information on where the AI assistant's model runs, and on-premises use is excluded by the terms. 1 8 9 10 11

Report an error

The Skeptic

Facade BV, registered in Antwerp, Belgian law and Antwerp courts, all data processed within the European Union, a downloadable DPA, a Belgian data protection authority complaint route, and no outside investors — the entity and residency story is genuinely European. Two subprocessors are named, PostHog for product analytics and Mailcoach for account emails, but their locations are not, the third-party server hosting the service is unnamed, and where the AI assistant runs or which model it uses is not stated. A strong head of the chain; the tail is only half named. 8 9 10 11

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

Four plans carry exact yearly figures with exact monthly limits for errors, spans and logs, unlimited projects and users on team plans, no setup fees, and the behaviour at the quota is a hard stop with email warnings rather than overage — the annual cost is computable and cannot surprise me. Billing terms are published: upfront invoicing, credit card payment, prorated upgrades and downgrades, no refunds, and three months' notice before annual renewal. Monthly-term prices and VAT treatment are not stated, and the captured pages give different figures for the trial length — fourteen days in the terms and ten days elsewhere. 6 9 8

Report an error

The SaaS CTO

Every plan's yearly price is public — €99 for a single-user Hobby plan, then €319, €759 and €3,069 — each with exact monthly error, span and log quotas, unlimited projects and users, all modules including AI and integrations on every plan, and stated behaviour at the limit: an email at 80 percent and a stop on new data rather than overage billing. What keeps a buyer from computing everything: the captured pricing page shows yearly prices only, VAT treatment and add-on pricing are not stated, and the captured pages give different figures for the free trial (14 days in the terms, 10 days on the site). 6 9 8

Report an error

The Mobile Team Lead

Four plans are public with yearly prices and exact monthly volume per data type — Standard at € 319 and Premium at € 3,069 per year, each with stated error, span and log quotas — and the limit behaviour is spelled out: an email at 80%, ingestion stops at the cap with separate counters, so there is no overage to compute, and cancellation keeps data for 30 days with export. What remains open for a buyer: monthly price figures, VAT, and the captured pages give different figures for the free trial's length. 6 8 9

Report an error

The Site Reliability Engineer

Four plans carry public yearly prices with exact monthly quotas for errors, spans and logs on each, unlimited projects and users on team plans, a flat 30-day retention everywhere, and AI and MCP included rather than sold as an add-on; the behaviour at the limit is stated — an email at 80 percent, then data stops until reset or upgrade — so a spike cannot turn into a surprise invoice, with spike protection behind it. We found no public information on the monthly price, on VAT treatment, or on a longer-retention option, and the captured pages give different figures for the free trial length — fourteen days in one place, ten days in another. Billing terms are clear: invoiced up front per team, credit card unless otherwise agreed, no refunds, yearly plans equivalent to one month free. 6 9 18

Report an error

The Data Protection Officer

Every plan is priced publicly with its error, span and log volumes — from € 99 a year for a single user and project to € 3,069 a year at the top tier — data simply stops rather than billing when a limit is reached, and the billing terms are stated: up-front invoicing, credit card, prorated upgrades, no refunds, three months' notice on annual renewal. We found no public information on VAT treatment or monthly prices for the team plans, and the captured pages give different figures for the free trial length, ten days in one place and fourteen in another. 6 8 9

Report an error

The Skeptic

Every plan is public with its yearly price and hard volume numbers for errors, spans and logs, and the quota behaviour is stated plainly: an email at 80 percent, then a stop — there is no overage to price. The terms add the second-year story a buyer needs: fees non-refundable, invoiced up front, yearly terms auto-renewing unless cancelled three months before term end. Monthly figures and VAT are not shown on the captured pages, the crossed-out prices are unexplained, nonprofit pricing is contact-only, and the captured pages give different figures for the free trial length — fourteen days in the terms, ten on the pricing page. 6 8 9

Report an error

European sovereignty — proven facts

3 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 Not determined — uncited Report an error
Hosting options Cloud service only unverified
Why unverified?

The terms describe the software as SaaS delivered on a server hosted by Flare and withhold on-premises rights, but no page explicitly states that no self-hosted option exists, and the open-source package customers install is only a conduit to the SaaS, not the product itself.

0/1 pts 9 Report an error
Open source Not determined — uncited Report an error
Data processing agreement Published, self-serve unverified
Why unverified?

Concluding the DPA requires downloading, signing and emailing a copy rather than accepting it fully online, and the agreement text itself is only linked, not reproduced on the page.

1/1 pts 11 Report an error
Transfer impact assessment Not determined — uncited Report an error

Questions about Flare

Is Flare European?

Yes. whats-best.ai classifies Flare as EU-Made. Its vendor, Facade BV, is incorporated in Belgium, per the vendor’s page captured 6 Nov 2026.

Where does Flare store data?

Not stated on the vendor’s pages as of 6 Nov 2026.

Does Flare have a free plan?

Not stated on the vendor’s pages as of 6 Nov 2026.

What are the best alternatives to Flare?

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: Flare 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 (19)

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

  1. 1 Vendor homepage flareapp.io Checked 6 Nov 2026 Details →
  2. 2 Features page (error tracking) flareapp.io Checked 6 Nov 2026 Details →
  3. 3 Features page (performance monitoring) flareapp.io Checked 6 Nov 2026 Details →
  4. 4 Features page (logging) flareapp.io Checked 6 Nov 2026 Details →
  5. 5 Documentation flareapp.io Checked 6 Nov 2026 Details →
  6. 6 Pricing page flareapp.io Checked 6 Nov 2026 Details →
  7. 7 Public status page status.flareapp.io Checked 6 Nov 2026 Details →
  8. 8 About page flareapp.io Checked 6 Nov 2026 Details →
  9. 9 Terms of service (names the operating company) flareapp.io Checked 6 Nov 2026 Details →
  10. 10 Privacy policy flareapp.io Checked 6 Nov 2026 Details →
  11. 11 Data processing agreement (dpa) flareapp.io Checked 6 Nov 2026 Details →
  12. 12 Error capture, grouping & triage — found from sitemap flareapp.io Checked 6 Nov 2026 Details →
  13. 13 Error capture, grouping & triage — found from sitemap flareapp.io Checked 6 Nov 2026 Details →
  14. 14 APM, tracing & profiling — found from sitemap flareapp.io Checked 6 Nov 2026 Details →
  15. 15 APM, tracing & profiling — found from sitemap flareapp.io Checked 6 Nov 2026 Details →
  16. 16 Alerting, integrations & developer workflow — found from sitemap flareapp.io Checked 6 Nov 2026 Details →
  17. 17 Alerting, integrations & developer workflow — found from sitemap flareapp.io Checked 6 Nov 2026 Details →
  18. 18 Data scrubbing, retention & volume control — found from sitemap flareapp.io Checked 6 Nov 2026 Details →
  19. 19 Data scrubbing, retention & volume control — found from sitemap flareapp.io Checked 6 Nov 2026 Details →