Panel rating · 6 judges · How to read the stars

Category median

Sovereignty: not determined

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

by Inspector S.R.L. · inspector.dev

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

Link to this page

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

Inspector at a glance

Vendor
Inspector S.R.L.
Headquarters
Not stated on the vendor’s pages as of 6 Nov 2026
Data hosting
Not stated on the vendor’s pages as of 6 Nov 2026
Free plan
Yes, per the vendor’s own page source, captured 6 Nov 2026
Panel verdict
The AI panel rates Inspector 2/5, the mean of 6 judges. Inspector is code execution monitoring from Inspector S.R.L. how scores are made
As of
Vendor pages captured 6 Nov 2026; evaluated by the panel 6 Nov 2026. all sources

Inspector alternatives, European ones first →

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

The Agency Tech Lead

Weighted verdict

Technical lead at a web agency in Cologne with fourteen developers and forty client sites on Laravel, Shopware and WordPress, most on maintenance contracts. Wants every client in its own project with its own alert channel, PHP stack traces that show the query and the queued job, slow pages found before the client calls, request data scrubbed because the shops hold customer addresses, and a monthly bill that does not jump when one client's cron job throws the same exception a million times.

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

Scored by The Agency Tech Lead

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

Error capture, grouping & triage

How this is scored

What happens to an exception or crash: SDKs for the languages, frameworks and platforms a team runs (PHP and Laravel, JavaScript in the browser and Node, Python, Ruby, Java, .NET, Go, iOS, Android, Flutter, React Native), stack traces with source maps and symbolication, context (request, user, breadcrumbs, environment, local variables), grouping and custom fingerprints, deduplication, issue states (resolved, ignored, regressed), releases and deploy tracking, suspect commits, crash-free sessions and users for mobile apps, and search and filters over issues.

0 — Catches no application errors or crashes; a log viewer or an external check only.

3 — Errors from one or two platforms arrive with a stack trace and are grouped; context, issue states, releases and source maps are basic or not described.

5 — SDKs for the common web and backend platforms, stack traces with source maps, request and user context and breadcrumbs, automatic grouping with issue states and regression detection, release and deploy tracking, and issue search and filters.

8 — SDKs across backend, frontend and mobile with symbolication documented, custom fingerprinting and merge or split of issues, suspect commits or code owners, crash-free users and sessions, local variables or source context per frame, and every SDK documented with its configuration options.

10 — Error tracking a large engineering organisation standardises on: every platform it runs covered with parity stated, grouping rules editable and explained, release health with adoption and regression per version, and the full issue lifecycle reachable by API.

Report an error

The Agency Tech Lead

The documented SDKs are the PHP family — Laravel, Symfony, CakePHP, CodeIgniter, Drupal, Slim and Tempest — and in a Laravel app every exception is reported by default, grouped with its stack trace, the source code around the failure and its hit frequency, plus manual and global exception handlers. Grouping patterns are a named, documented feature. We found no public information on issue states like resolved or regressed, release and deploy tracking, or request, user and breadcrumb context. 2 3 8 10

Report an error

APM, tracing & profiling

How this is scored

How the product shows where time goes: transaction and endpoint timings with percentiles, slow database queries and N+1 detection, background jobs and queues, external HTTP calls, distributed tracing across services, OpenTelemetry ingestion, code-level profiling, frontend performance and Core Web Vitals (real user monitoring), host or container metrics beside the traces, anomaly detection on throughput and latency, and the link from a slow trace to the error it caused.

0 — No performance data of any kind; errors only.

3 — Response times per endpoint or a simple performance view; tracing across services, query analysis and profiling are basic or not described.

5 — Transaction timings with percentiles per endpoint, slow query and N+1 detection, background job monitoring, distributed tracing across services, a link between traces and errors, and frontend performance or Web Vitals offered.

8 — OpenTelemetry ingestion documented, code-level or continuous profiling, real user monitoring with Web Vitals, host and container metrics beside the traces, anomaly detection on latency and throughput, and sampling of traces configurable with its effect explained.

10 — Full application performance management evidenced: traces, profiles, frontend and backend joined end to end, service maps, SLOs on endpoints, and every signal documented with its retention and sampling per plan.

Report an error

The Agency Tech Lead

Transactions are exactly what I watch on maintenance contracts: every HTTP request, queued job and artisan command with the database queries, cache calls and external calls inside, a timeline that shows the ORM behind the scenes so an N+1 or a slow join is visible in the request that caused it, and custom segments for arbitrary code blocks. Per-endpoint duration and memory metrics are documented, with alerts when execution time or memory crosses a chosen limit. We found no public information on percentiles, distributed tracing across services, OpenTelemetry, code-level profiling, or real user monitoring with Core Web Vitals. 1 2 9 10 11

Report an error

Alerting, integrations & developer workflow

How this is scored

How an error reaches the person who fixes it: alert rules on new issues, regressions, frequency and performance thresholds, notifications to email, Slack, Microsoft Teams, PagerDuty or Opsgenie, issue tracker integrations (Jira, GitHub, GitLab, Linear) that create and sync issues, source code links to the repository, deploy and release hooks from CI, a documented REST API and webhooks, a CLI, AI features that explain an error or suggest a fix (and which model runs them), and digest or weekly reports.

0 — No notifications and no integrations; errors are only visible by logging in.

3 — Email or chat notifications for new errors and one or two integrations; alert rules, the issue tracker link and the API are basic or not described.

5 — Configurable alert rules for new, regressed and frequent errors, Slack and email and an on-call tool, issue tracker integrations with GitHub, GitLab or Jira, deploy tracking from CI, a documented REST API and webhooks.

8 — Two-way sync with issue trackers, source code and commit links, alerts on performance thresholds and anomalies with routing per team or project, a CLI for releases and source maps, AI explanations or fix suggestions with the model provider named, and scheduled reports.

10 — A workflow a large team runs on: ownership rules routing issues to teams, every setting reachable by API or infrastructure as code, alert noise controls documented, and every AI feature documented with its data handling and an opt-out.

Report an error

The Agency Tech Lead

Notifications reach my teams where they work — email, Slack, Teams, Discord, Telegram, PagerDuty and more — attached per application so each client can have its own channel, with rules for new errors, 10th/100th/1000th occurrences, frequency spikes, new transactions and violations of performance limits on execution time or memory. A REST API over transactions and segments is documented, and an MCP server gives coding agents like Claude Code and Cursor read-only access to errors and performance data, with an AI Bug Fix feature alongside. We found no public information on issue tracker integrations like Jira or GitHub, deploy tracking from CI, a CLI, or which model runs the AI features. 1 2 9 11 12 15

Report an error

Data scrubbing, retention & volume control

How this is scored

What the product does with the personal and secret data an error carries and how volume is kept in check: scrubbing of passwords, tokens, card numbers and personal data in the SDK and on the server with configurable rules, IP address anonymisation, opting out of request bodies and user data, data retention per plan and deletion on request, sampling of errors and traces, rate limits, spike protection and quota caps per project, filters that drop events before they count, data export, and a self-hosted edition that keeps every event on the customer's own servers.

0 — No control over what is captured, no retention period stated, no limit on volume.

3 — Some default filtering of passwords and a retention period stated for one plan; server-side scrubbing, sampling and spike protection are basic or not described.

5 — Configurable data scrubbing in the SDK and default server-side scrubbing of common secrets, IP anonymisation, retention stated per plan, sampling and rate limits per project, a quota cap or spike protection, and event filters before ingestion.

8 — Custom server-side scrubbing rules with examples, per-project retention settings and deletion of individual events or users, spike protection documented with how overage is billed, data export by API, and a self-hosted edition or a documented option to keep data in the customer's chosen region.

10 — Data minimisation by design and evidenced: personal data off by default in every SDK, scrubbing rules auditable, retention and deletion controllable per data type, volume controls that never surprise the invoice, and a supported self-hosted edition with feature parity stated.

Report an error

The Agency Tech Lead

Billing is per transaction with unlimited queries, exceptions and segments inside, and the behaviour at the quota is stated: new data is dropped until the next monthly cycle unless you enable usage-based billing at a published rate per 50,000 transactions — so one client's runaway cron cannot ambush my invoice. Retention is published per plan and the middleware lets me choose which routes get recorded. My shops hold customer addresses and we found no public information on scrubbing of request data, IP anonymisation, sampling or deletion on request; the pricing page and a later announcement also give different figures for free-tier retention (3 days versus a week). 4 10 13

Report an error

Access control, security & the vendor's reliability

How this is scored

Whether the service holds up in an audit and on the vendor's own bad day: organisations, teams and projects with roles, single sign-on (SAML or OIDC) and SCIM, two-factor authentication, audit logs, encryption in transit and at rest, security certifications and reports (ISO 27001, SOC 2), a security page and a vulnerability disclosure policy, the vendor's own public status page and incident history, a stated availability or SLA, and how ingestion behaves when the vendor is down (SDK buffering, no impact on the app).

0 — Nothing on access control, security or the vendor's own availability.

3 — User accounts with two-factor authentication and a security page; roles, SSO, certifications and a status page are basic or not described.

5 — Organisations and projects with roles, two-factor authentication, single sign-on offered on some plan, encryption in transit and at rest stated, a public status page, and a security page naming certifications or audits.

8 — SAML SSO and SCIM provisioning, audit logs, ISO 27001 or SOC 2 with its scope stated, an SLA with credits published, the incident history public, a vulnerability disclosure or bug bounty programme, and SDK behaviour during vendor outages documented.

10 — Enterprise-grade operation evidenced: granular roles per project and team, audit logs exportable to a SIEM, independent audit reports available on request, published uptime history over years, and ingestion designed and documented never to slow the customer's application.

Report an error

The Agency Tech Lead

Two-factor authentication is documented in real depth — TOTP via Google Authenticator, the current password required to disable it, recovery through support, and device management that lists logged-in devices and can enforce single-device logins. Encryption in transit and at rest is stated, and the public status page publishes 90-day uptime per service (99.997% for the ingest pipeline, 99.935% for the API) with an incident history. We found no public information on single sign-on, SCIM, audit logs, ISO 27001 or SOC 2, an SLA, or a vulnerability disclosure policy. 3 5 15 16

Report an error

European sovereignty

How this is scored

Who the contracting entity and the parent company are, where error events, stack traces, request data, traces, profiles, session data and account data are stored and processed, and who the subprocessors are (hosting, email and chat delivery, AI models that explain errors, support and payment tools). Independently sourced by the sovereignty pipeline. An EU data region the customer can choose counts for the product; a US default without a stated EU option does not. A self-hosted edition the customer runs on its own European servers counts as the customer's chain, whatever the vendor's seat.

0 — Non-EU vendor and contracting entity, hosting unstated, subprocessors unnamed, and no data processing agreement offered.

3 — A privacy policy and a data processing agreement exist, but hosting location is unstated or non-EU and the subprocessors are not listed.

5 — An EU data region available and an EU contracting entity or EU representative, but parts of the chain (AI features, email, support, payment) run through non-EU providers without a stated safeguard.

8 — EU hosting on named infrastructure, EU contracting entity, subprocessors listed with their locations, a data processing agreement published, and security certifications (ISO 27001, SOC 2) stated — or a self-hosted edition documented that keeps every event on the customer's own servers.

10 — Sovereign end to end and evidenced: European ownership, entity, hosting and every subprocessor including the AI models, or a self-hosted edition with no call home, data export and deletion documented, and certifications published with their scope rather than implied.

Report an error

The Agency Tech Lead

The contracting entity is genuinely European — Inspector S.R.L., VAT 09552901218, Naples, with a second office in Florence — so I would be contracting inside the EU. The infrastructure is described only as AWS ARM instances with no region named, and the AI integrations name Claude, ChatGPT and Gemini; we found no public information on where monitoring data is stored and processed, on a data processing agreement, or on a subprocessor list. 1 6 13

Report an error

Pricing transparency

How this is scored

Whether a buyer can compute the real annual cost from public pages alone: price per plan, what is included (errors or events, spans or transactions, replays, profiles, logs, seats, projects, retention), what overage costs per unit and whether it is capped, which features (SSO, audit logs, longer retention, EU region, AI) need a higher plan, host or seat based pricing for suites, the price of the self-hosted edition, annual versus monthly terms, and VAT.

0 — No public prices at all; every customer is a sales call.

3 — A starting price exists, but what volume it covers and what overage, retention and add-ons cost is unclear.

5 — Plans are public with their price and main volume limits, but at least one commonly needed piece (overage per event or span, longer retention, SSO, the EU region or AI features) is unpriced or "contact sales".

8 — Every plan priced publicly with its volume limits and overage rates, a price calculator or table per unit, add-ons and retention priced, the behaviour at the quota (cap or overage) stated, and VAT and billing terms stated.

10 — Complete price computability: annual cost derivable for a given volume of errors, traces, seats and projects, with every add-on, retention step, support level and the self-hosted licence priced and the cancellation terms published.

Report an error

The Agency Tech Lead

I can compute a client's monthly cost from the public page alone: Free at €0 up to 30K transactions (3 team members, 1 channel, no REST API), Beginner at €15 a month for 300K, Developer €39 for 800K, Team €69 for 1.5M and Enterprise €169 for 6M, each with unlimited users and hosts, its own retention, and a published price per additional 50K transactions from €2.50 down to €1.40, with plan changes prorated and a 14-day 100% refund. Above Enterprise it says "we set up the data tier around your needs, usually with an isolated datastore". We found no public information on VAT treatment, annual versus monthly terms, or separate pricing for the AI features. 4

Report an error

European sovereignty — proven facts

0 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 Not determined — uncited Report an error
Open source Not determined — uncited Report an error
Data processing agreement Not determined — uncited Report an error
Transfer impact assessment Not determined — uncited Report an error

Questions about Inspector

Is Inspector European?

Yes. whats-best.ai classifies Inspector as EU-Made.

Where does Inspector store data?

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

Does Inspector have a free plan?

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

What are the best alternatives to Inspector?

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: Inspector 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 (16)

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

  1. 1 Vendor homepage inspector.dev Checked 6 Nov 2026 Details →
  2. 2 Features page inspector.dev Checked 6 Nov 2026 Details →
  3. 3 Documentation docs.inspector.dev Checked 6 Nov 2026 Details →
  4. 4 Pricing page inspector.dev Checked 6 Nov 2026 Details →
  5. 5 Public status page status.inspector.dev Checked 6 Nov 2026 Details →
  6. 6 About page (names the operating company) inspector.dev Checked 6 Nov 2026 Details →
  7. 7 Error capture, grouping & triage — found from sitemap inspector.dev Checked 6 Nov 2026 Details →
  8. 8 Error capture, grouping & triage — found from sitemap docs.inspector.dev Checked 6 Nov 2026 Details →
  9. 9 APM, tracing & profiling — found from sitemap docs.inspector.dev Checked 6 Nov 2026 Details →
  10. 10 APM, tracing & profiling — found from sitemap inspector.dev Checked 6 Nov 2026 Details →
  11. 11 Alerting, integrations & developer workflow — found from sitemap docs.inspector.dev Checked 6 Nov 2026 Details →
  12. 12 Alerting, integrations & developer workflow — found from sitemap docs.inspector.dev Checked 6 Nov 2026 Details →
  13. 13 Data scrubbing, retention & volume control — found from sitemap inspector.dev Checked 6 Nov 2026 Details →
  14. 14 Data scrubbing, retention & volume control — found from sitemap docs.inspector.dev Checked 6 Nov 2026 Details →
  15. 15 Access control, security & the vendor's reliability — found from sitemap inspector.dev Checked 6 Nov 2026 Details →
  16. 16 Access control, security & the vendor's reliability — found from sitemap docs.inspector.dev Checked 6 Nov 2026 Details →