Inspector
EU-Made Report an error0–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
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
Read this page as one judge. Each weighs the same scores by what they care about.
The panel's verdict
Inspector is code execution monitoring from Inspector S.R.L. of Naples, Italy, documented for the PHP family — Laravel, Symfony, CakePHP, CodeIgniter, Drupal, Slim, Tempest — reporting every exception by default and grouping each with its stack trace and the source code around the failure. Strongest is pricing transparency, 6-7: every plan is public in euros — Free €0, Beginner €15, Developer €39, Team €69 and Enterprise €169 a month — with retention, drop-at-quota behaviour and per-plan overage prices stated. Weakest is sovereignty, 2-3: the counterparty is European, but hosting is described only as AWS ARM instances with no region stated, and we found no public information on a data processing agreement or a subprocessor list. The widest spread is workflow and integrations, 4-6: higher scores credit the documented REST API, the read-only MCP server and ten-plus notification channels including PagerDuty; lower scores cite no public information on issue-tracker sync, CI deploy hooks or a CLI. Error tracking runs 3-4, data controls 3-4, and performance tracing and security both sit at 4.
Speaks for it
- Every plan is priced publicly in euros — Free €0, Beginner €15, Developer €39, Team €69 and Enterprise €169 a month — with retention stated per plan, a published price for each additional 50K transactions from €2.50 down to €1.40, prorated plan changes and a 14-day 100% refund.
- Quota behaviour is explicit — past the monthly transaction cap new data drops until the next cycle unless usage-based billing is on — so a volume spike cannot inflate the invoice.
- The query timeline shows what the ORM does inside a request, exposing N+1s and slow joins, with per-endpoint duration and memory metrics and custom segments.
- Notifications route per application through ten-plus channels including PagerDuty, alongside a documented REST API, a read-only MCP server for coding agents such as Claude Code and Cursor, and an AI Bug Fix that proposes fixes for production errors.
- Two-factor authentication is documented down to requiring the current password to disable it, with device management, encryption at rest, 256-bit HTTPS in transit and a public status page showing 90-day uptime per service — 99.997% for the ingest pipeline.
Held against it
- The documented SDKs cover PHP frameworks only — we found no public information on SDKs for iOS, Android, Flutter, Go, Python or TypeScript.
- We found no public information on scrubbing of passwords or personal data, IP anonymisation, sampling or deletion on request.
- Hosting is described only as AWS ARM instances with no region stated, and we found no public information on a data processing agreement, a subprocessor list or a selectable EU data region.
- We found no public information on issue-tracker integrations such as Jira or GitHub, CI deploy hooks, a CLI, single sign-on, audit logs or an SLA.
- The captured pages give different figures for free-tier retention — 3 days on the pricing page, a week in the retention announcement — and for channel limits, 'Unlimited' on the pricing page against documentation stating channels are limited by subscription plan.
Best for
- You run a PHP or Laravel application and want per-endpoint duration and memory metrics with a query timeline showing the ORM's behaviour inside each request.
- You want a monthly cost you can compute from the public page, with stated quotas, drop-at-quota behaviour and a published price per additional 50K transactions.
- Your team already works through coding agents like Claude Code or Cursor and wants to give them read-only access to production errors and performance data.
- You monitor many applications from one account — unlimited hosts and apps, with notification channels assigned per application.
Avoid if
- Your stack includes iOS, Android, Flutter, Go, Python or TypeScript services — the documented SDKs are PHP frameworks only.
- Personal data such as member numbers or diagnosis codes can land in your stack traces and you need documented scrubbing, IP anonymisation or deletion on request.
- You must name a data region or a subprocessor chain in a contract — ask the vendor: the public pages we read do not show it
- Your on-call decisions need percentiles or distributed tracing across services — the documented alert metrics are count, min, max and average, and we found no public information on distributed tracing.
The scores
| Criterion | Panel median |
|---|---|
| Error capture, grouping & triage | 2 of 5 |
| APM, tracing & profiling | 2 of 5 |
| Alerting, integrations & developer workflow | 2.5 of 5 |
| Data scrubbing, retention & volume control | 2 of 5 |
| Access control, security & the vendor's reliability | 2 of 5 |
| European sovereignty | 1.5 of 5 |
| Pricing transparency | 3.5 of 5 |
Error capture, grouping & triage
Show reasoningHide reasoning
How this is scored
What happens to an exception or crash: SDKs for the languages, frameworks and platforms a team runs (PHP and Laravel, JavaScript in the browser and Node, Python, Ruby, Java, .NET, Go, iOS, Android, Flutter, React Native), stack traces with source maps and symbolication, context (request, user, breadcrumbs, environment, local variables), grouping and custom fingerprints, deduplication, issue states (resolved, ignored, regressed), releases and deploy tracking, suspect commits, crash-free sessions and users for mobile apps, and search and filters over issues.
0 — Catches no application errors or crashes; a log viewer or an external check only.
3 — Errors from one or two platforms arrive with a stack trace and are grouped; context, issue states, releases and source maps are basic or not described.
5 — SDKs for the common web and backend platforms, stack traces with source maps, request and user context and breadcrumbs, automatic grouping with issue states and regression detection, release and deploy tracking, and issue search and filters.
8 — SDKs across backend, frontend and mobile with symbolication documented, custom fingerprinting and merge or split of issues, suspect commits or code owners, crash-free users and sessions, local variables or source context per frame, and every SDK documented with its configuration options.
10 — Error tracking a large engineering organisation standardises on: every platform it runs covered with parity stated, grouping rules editable and explained, release health with adoption and regression per version, and the full issue lifecycle reachable by API.
The Agency Tech Lead
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
The SaaS CTO
Exception reporting with stack traces, source code context, grouping and occurrence frequency is documented in depth, but only for the PHP world — Laravel, Symfony, CakePHP, CodeIgniter, Drupal and Slim — and my Go, Python and TypeScript teams would have nothing to install. I found no public information on issue states, release and deploy tracking, suspect commits, source maps, or crash-free sessions for mobile. 1 2 3 8 10 12
The Mobile Team Lead
Decisive for my six-person mobile team: the documented SDKs are PHP frameworks only — Laravel, Symfony, CakePHP, Tempest, Slim — and we found no public information on iOS, Android or Flutter SDKs, native symbolication, crash-free users per release, or release and deploy tracking. Within PHP it looks competent: every exception reported by default, grouped with its stack trace, the source code around the failure and how often it happens. 2 3 8 10
The Site Reliability Engineer
Error grouping with stack trace, the source code around the failure and hit frequency is documented for a PHP-centred stack — Laravel, Symfony, CakePHP, CodeIgniter, Drupal, Slim — with every exception reported by default and a manual report call. The captured pages stop at that: I found no public information on issue states like resolved or regressed, releases and deploy tracking, or any non-PHP platform, which is thin for a night on-call. 2 3 8 10 12
The Data Protection Officer
Every exception is reported by default and grouped with its stack trace, the source code around the failure and how often it recurs, plus a global handler and a manual reporting call — solid for the PHP ecosystem the pages document (Laravel, Symfony, CakePHP and siblings). We found no public information on issue states like resolved or regressed, release and deploy tracking, or user and request context, so I place it just below the mid-level. 2 8 10 3
The Skeptic
Errors arrive from the PHP world — Laravel, Symfony, CakePHP, Drupal and friends — grouped with their stack trace, the source code around the failure and how often it happens, and every exception is reported by default with real-time alerts. But I found no public information on SDKs beyond the PHP ecosystem, and nothing on issue states, releases, deploy tracking, source maps or user context, so triage past grouping is undescribed. 2 3 8 10 12
APM, tracing & profiling
Show reasoningHide reasoning
How this is scored
How the product shows where time goes: transaction and endpoint timings with percentiles, slow database queries and N+1 detection, background jobs and queues, external HTTP calls, distributed tracing across services, OpenTelemetry ingestion, code-level profiling, frontend performance and Core Web Vitals (real user monitoring), host or container metrics beside the traces, anomaly detection on throughput and latency, and the link from a slow trace to the error it caused.
0 — No performance data of any kind; errors only.
3 — Response times per endpoint or a simple performance view; tracing across services, query analysis and profiling are basic or not described.
5 — Transaction timings with percentiles per endpoint, slow query and N+1 detection, background job monitoring, distributed tracing across services, a link between traces and errors, and frontend performance or Web Vitals offered.
8 — OpenTelemetry ingestion documented, code-level or continuous profiling, real user monitoring with Web Vitals, host and container metrics beside the traces, anomaly detection on latency and throughput, and sampling of traces configurable with its effect explained.
10 — Full application performance management evidenced: traces, profiles, frontend and backend joined end to end, service maps, SLOs on endpoints, and every signal documented with its retention and sampling per plan.
The Agency Tech Lead
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
The SaaS CTO
The transaction timeline with N+1 and slow-join detection, per-endpoint duration and memory, background jobs and custom segments is a real step above a simple response-time view, and the API returns duration and memory per transaction. I found no public information on OpenTelemetry ingestion, distributed tracing across my services, percentiles, code-level profiling, frontend Web Vitals, or host and container metrics beside the traces. 1 2 9 10 11
The Mobile Team Lead
Backend performance is real here: transactions grouped by endpoint with duration and memory, a query timeline that surfaces N+1s and slow joins, background jobs, commands and external calls recorded, custom timeline segments, and a REST API over transactions with host and name filters. We found no public information on percentiles, distributed tracing across services, frontend or Web Vitals monitoring, or code-level profiling. 1 2 9 10
The Site Reliability Engineer
Per-endpoint duration and memory metrics, a query timeline that spots N+1 and slow joins, background jobs and artisan commands, and custom segments give a genuine timeline view of a slow checkout. What I miss for paging decisions is around it: the metrics run on count, min, max and average with no percentiles shown, and I found no public information on distributed tracing, OpenTelemetry, profiling or real-user monitoring. 1 2 9 10 11
The Data Protection Officer
Transactions are grouped by endpoint with duration and memory metrics, the timeline exposes what the ORM does so a slow join or N+1 is visible inside the request that caused it, and jobs and commands are monitored. We found no public information on distributed tracing across services, percentiles, code profiling, or any frontend or Web Vitals view. 1 2 9 11
The Skeptic
Per-endpoint timings with memory usage, a query timeline that surfaces N+1 and slow joins inside the request that caused them, background jobs, custom segments and metric alerts on count, min, max and average are all documented. I found no public information on percentiles, distributed tracing across services, OpenTelemetry ingestion, code-level profiling or any frontend and Web Vitals monitoring. 1 2 9 10 11
Alerting, integrations & developer workflow
Show reasoningHide reasoning
How this is scored
How an error reaches the person who fixes it: alert rules on new issues, regressions, frequency and performance thresholds, notifications to email, Slack, Microsoft Teams, PagerDuty or Opsgenie, issue tracker integrations (Jira, GitHub, GitLab, Linear) that create and sync issues, source code links to the repository, deploy and release hooks from CI, a documented REST API and webhooks, a CLI, AI features that explain an error or suggest a fix (and which model runs them), and digest or weekly reports.
0 — No notifications and no integrations; errors are only visible by logging in.
3 — Email or chat notifications for new errors and one or two integrations; alert rules, the issue tracker link and the API are basic or not described.
5 — Configurable alert rules for new, regressed and frequent errors, Slack and email and an on-call tool, issue tracker integrations with GitHub, GitLab or Jira, deploy tracking from CI, a documented REST API and webhooks.
8 — Two-way sync with issue trackers, source code and commit links, alerts on performance thresholds and anomalies with routing per team or project, a CLI for releases and source maps, AI explanations or fix suggestions with the model provider named, and scheduled reports.
10 — A workflow a large team runs on: ownership rules routing issues to teams, every setting reachable by API or infrastructure as code, alert noise controls documented, and every AI feature documented with its data handling and an opt-out.
The Agency Tech Lead
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
The SaaS CTO
Notifications reach ten-plus channels including Slack, Teams, PagerDuty, webhooks and SMS, with alert rules on new errors, occurrence counts, frequency and performance thresholds on execution time and memory, a documented REST API, and a read-only MCP server that lets a coding agent read errors and performance data. I found no public information on issue tracker integrations such as Jira, GitLab or Linear, deploy hooks from CI, a CLI, scheduled digests, or which model provider powers AI Bug Fix — so the release-to-commit link and routing to owning teams my workflow needs are not visible here. 1 2 3 9 11 12 15
The Mobile Team Lead
Alert rules cover new errors, every tenth occurrence, rising error frequency and violations of execution-time or memory limits, delivered through Slack, Teams, PagerDuty, Telegram, SMS and webhooks with per-application routing, plus a documented REST API, an MCP server giving coding agents read-only production data, and an AI Bug Fix that proposes fixes. We found no public information on two-way issue tracker sync with Jira, GitHub or GitLab, deploy hooks from CI, or a CLI, which is where my biweekly release routine would strain. 1 2 3 11 12
The Site Reliability Engineer
Notifications route to PagerDuty, Slack, email, Teams and webhooks with rules for new errors, repeated occurrences, rising frequency and violations on execution time and memory — the bones of a workable on-call loop. The documented REST API, the read-only MCP server for coding agents and AI Bug Fix are modern touches, though the model behind the AI is unnamed, and I found no public information on issue-tracker sync, CI deploy hooks or a CLI. 1 2 9 11 12 15
The Data Protection Officer
Alert rules cover new errors, error frequency, every occurrence and violations of limits set on execution time or memory, routed through more than ten channels including PagerDuty and webhooks, with a documented REST API and a read-only MCP server for coding agents. We found no public information on issue tracker integrations, deploy hooks from CI, or which AI model powers AI Bug Fix and where it runs. 1 9 11 12 15
The Skeptic
Alert rules on transaction and segment metrics, ten notification channels including PagerDuty, a documented REST API, webhooks, an AI bug-fix feature and a read-only MCP server for coding agents are all evidenced. But nowhere in the pages I read is there an issue tracker integration, a CI deploy hook, a CLI or a scheduled report, and the model behind the AI fix is not named. 1 2 9 11 12 15
Data scrubbing, retention & volume control
Show reasoningHide reasoning
How this is scored
What the product does with the personal and secret data an error carries and how volume is kept in check: scrubbing of passwords, tokens, card numbers and personal data in the SDK and on the server with configurable rules, IP address anonymisation, opting out of request bodies and user data, data retention per plan and deletion on request, sampling of errors and traces, rate limits, spike protection and quota caps per project, filters that drop events before they count, data export, and a self-hosted edition that keeps every event on the customer's own servers.
0 — No control over what is captured, no retention period stated, no limit on volume.
3 — Some default filtering of passwords and a retention period stated for one plan; server-side scrubbing, sampling and spike protection are basic or not described.
5 — Configurable data scrubbing in the SDK and default server-side scrubbing of common secrets, IP anonymisation, retention stated per plan, sampling and rate limits per project, a quota cap or spike protection, and event filters before ingestion.
8 — Custom server-side scrubbing rules with examples, per-project retention settings and deletion of individual events or users, spike protection documented with how overage is billed, data export by API, and a self-hosted edition or a documented option to keep data in the customer's chosen region.
10 — Data minimisation by design and evidenced: personal data off by default in every SDK, scrubbing rules auditable, retention and deletion controllable per data type, volume controls that never surprise the invoice, and a supported self-hosted edition with feature parity stated.
The Agency Tech Lead
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
The SaaS CTO
Retention is stated for every plan and the quota behaviour is explicit — new data drops until the next monthly cycle unless usage-based billing is on — with unlimited events and hosts inside each plan. I found no public information on scrubbing of passwords or personal data in the SDK or on the server, IP anonymisation, sampling, event filters before ingestion, or deletion on request, which is what my German enterprise customers ask about first. 4 13 14
The Mobile Team Lead
Retention is stated for every plan — three days on the free tier, seven to twenty-one paid, recently extended by a week — and volume behaviour is explicit: past the monthly transaction cap new data drops until the next cycle, or you switch to usage-based billing with each additional 50K transactions priced per plan. We found no public information on scrubbing of passwords, tokens or personal data, IP anonymisation, sampling, or filters that drop events before they are counted. 4 13
The Site Reliability Engineer
Volume behaviour is stated plainly: past the quota Inspector drops new data until the next cycle unless usage-based billing is on at a fixed price per extra 50K transactions, so an incident will not inflate my invoice. Retention is stated per plan, though the captured pages give different figures for the free tier (3 days on the pricing page, a week in the retention announcement), and I found no public information on scrubbing, IP anonymisation, sampling or deletion. 4 13
The Data Protection Officer
Retention is stated for every plan and the quota behaviour is explicit — new data is dropped until the next monthly cycle unless usage-based billing is on — which keeps the invoice predictable. But I found no public information on scrubbing of passwords, tokens or personal data in the SDK or on the server, IP anonymisation, sampling, or deletion on request, and those are precisely the controls a member number or diagnosis code in a stack trace depends on. 4 13 14
The Skeptic
Retention is stated per plan — 3 to 7 days free, up to 21 days on Enterprise — and behaviour at the quota is explicit: new data is dropped until the next cycle unless you turn on usage-based billing, so at least the invoice cannot surprise you. What I found no public information on is scrubbing of passwords and personal data, IP anonymisation, sampling, pre-ingestion filters, or any self-hosted edition — the Composer package only instruments, and the data still goes to their cloud. 3 4 13
Access control, security & the vendor's reliability
Show reasoningHide reasoning
How this is scored
Whether the service holds up in an audit and on the vendor's own bad day: organisations, teams and projects with roles, single sign-on (SAML or OIDC) and SCIM, two-factor authentication, audit logs, encryption in transit and at rest, security certifications and reports (ISO 27001, SOC 2), a security page and a vulnerability disclosure policy, the vendor's own public status page and incident history, a stated availability or SLA, and how ingestion behaves when the vendor is down (SDK buffering, no impact on the app).
0 — Nothing on access control, security or the vendor's own availability.
3 — User accounts with two-factor authentication and a security page; roles, SSO, certifications and a status page are basic or not described.
5 — Organisations and projects with roles, two-factor authentication, single sign-on offered on some plan, encryption in transit and at rest stated, a public status page, and a security page naming certifications or audits.
8 — SAML SSO and SCIM provisioning, audit logs, ISO 27001 or SOC 2 with its scope stated, an SLA with credits published, the incident history public, a vulnerability disclosure or bug bounty programme, and SDK behaviour during vendor outages documented.
10 — Enterprise-grade operation evidenced: granular roles per project and team, audit logs exportable to a SIEM, independent audit reports available on request, published uptime history over years, and ingestion designed and documented never to slow the customer's application.
The Agency Tech Lead
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
The SaaS CTO
Two-factor authentication is documented in detail — TOTP, device management, password confirmation on critical actions — encryption in transit and at rest is stated, and there is a public status page with 90-day uptime per service plus an incident history and asynchronous collection that adds no latency to my app. I found no public information on single sign-on, SCIM, audit logs, certifications such as ISO 27001 or SOC 2, a vulnerability disclosure policy, an SLA, or SDK behaviour during a vendor outage. 3 5 15 16
The Mobile Team Lead
The account side is decently documented: two-factor authentication via an authenticator app with the current password required to disable it, device management that can limit an account to one logged-in device, encryption at rest and 256-bit HTTPS in transit, and a public status page showing 90-day uptime per service (Ingest Pipeline 99.997%, API 99.935%) with a previous-incidents link. We found no public information on single sign-on, roles and teams, audit logs, ISO 27001 or SOC 2 certifications, or an SLA. 3 5 15 16
The Site Reliability Engineer
Two-factor authentication with device management and password re-confirmation, encryption in transit and at rest, and a public status page with per-service uptime over 90 days and a previous-incidents link — exactly what I open when the monitoring itself is the incident. For my auditors it stops there: I found no public information on single sign-on, SCIM, audit logs, certifications or a service level agreement. 3 5 15 16
The Data Protection Officer
Two-factor authentication with TOTP, password confirmation for critical actions, device session management, and encryption in transit and at rest are documented, and the public status page shows 90-day uptime per service with a link to previous incidents. We found no public information on single sign-on, SCIM provisioning, audit logs, or certifications such as ISO 27001 or SOC 2. 3 5 15 16
The Skeptic
Two-factor authentication is documented down to disabling it requiring the current password, encryption in transit and at rest are stated, device management exists, and there is a public status page with 90-day uptime per service and a previous-incidents link. I found no public information on single sign-on, audit logs, certifications, an SLA, or what the SDK does when their ingest pipeline is down. 3 5 15 16
European sovereignty
panel opinion
Show reasoningHide reasoning
How this is scored
Who the contracting entity and the parent company are, where error events, stack traces, request data, traces, profiles, session data and account data are stored and processed, and who the subprocessors are (hosting, email and chat delivery, AI models that explain errors, support and payment tools). Independently sourced by the sovereignty pipeline. An EU data region the customer can choose counts for the product; a US default without a stated EU option does not. A self-hosted edition the customer runs on its own European servers counts as the customer's chain, whatever the vendor's seat.
0 — Non-EU vendor and contracting entity, hosting unstated, subprocessors unnamed, and no data processing agreement offered.
3 — A privacy policy and a data processing agreement exist, but hosting location is unstated or non-EU and the subprocessors are not listed.
5 — An EU data region available and an EU contracting entity or EU representative, but parts of the chain (AI features, email, support, payment) run through non-EU providers without a stated safeguard.
8 — EU hosting on named infrastructure, EU contracting entity, subprocessors listed with their locations, a data processing agreement published, and security certifications (ISO 27001, SOC 2) stated — or a self-hosted edition documented that keeps every event on the customer's own servers.
10 — Sovereign end to end and evidenced: European ownership, entity, hosting and every subprocessor including the AI models, or a self-hosted edition with no call home, data export and deletion documented, and certifications published with their scope rather than implied.
The Agency Tech Lead
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
The SaaS CTO
The contracting entity is Inspector S.R.L. in Naples with a second office in Florence, so a European company stands behind the product, and it ships an Italian public-funding reference. Hosting is stated only as AWS ARM instances with no region named, and I found no public information on a data processing agreement, a subprocessor list, or where the AI features — connections to Claude, ChatGPT and Gemini — process customer data. 1 4 6 13
The Mobile Team Lead
A genuinely European vendor: Inspector S.R.L., VAT 09552901218, headquartered in Naples with a Florence office, Italian public funding under Resto al SUD, and a published privacy policy. Hosting is described only as AWS ARM instances with no region stated, and we found no public information on a selectable EU data region, the data processing agreement, or the subprocessor list — so from these pages I cannot tell where my customers' data would land. 6 13 15
The Site Reliability Engineer
The contracting entity is Inspector S.R.L. of Naples with a second office in Florence, and a privacy policy is published — a genuinely European vendor. But hosting is described only as AWS with no region stated, subprocessors are not listed, and I found no public information on a data processing agreement or a selectable EU data region. 4 6 13
The Data Protection Officer
The contracting entity is Inspector S.R.L. of Naples with an Italian VAT number, so the counterparty is European, and a privacy policy and terms are published. Storage runs on AWS ARM instances with no region named, and we found no public information on a data processing agreement, a subprocessor list, or a selectable EU data region — the chain a member's data travels is not provable from the captured pages. 3 6 13
The Skeptic
The contracting entity is Inspector S.R.L. of Naples, Italy with an Italian VAT number and Italian public funding, and a privacy policy exists. But hosting is described only as AWS ARM instances with no region stated, and I found no public information on a data processing agreement, a subprocessor list, or an EU data region option — the sovereignty pipeline itself marks every dimension unknown. 4 6 13 15
Pricing transparency
Show reasoningHide reasoning
How this is scored
Whether a buyer can compute the real annual cost from public pages alone: price per plan, what is included (errors or events, spans or transactions, replays, profiles, logs, seats, projects, retention), what overage costs per unit and whether it is capped, which features (SSO, audit logs, longer retention, EU region, AI) need a higher plan, host or seat based pricing for suites, the price of the self-hosted edition, annual versus monthly terms, and VAT.
0 — No public prices at all; every customer is a sales call.
3 — A starting price exists, but what volume it covers and what overage, retention and add-ons cost is unclear.
5 — Plans are public with their price and main volume limits, but at least one commonly needed piece (overage per event or span, longer retention, SSO, the EU region or AI features) is unpriced or "contact sales".
8 — Every plan priced publicly with its volume limits and overage rates, a price calculator or table per unit, add-ons and retention priced, the behaviour at the quota (cap or overage) stated, and VAT and billing terms stated.
10 — Complete price computability: annual cost derivable for a given volume of errors, traces, seats and projects, with every add-on, retention step, support level and the self-hosted licence priced and the cancellation terms published.
The Agency Tech Lead
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
The SaaS CTO
Every plan is public with its price in euro — €15, €39, €69 and €169 a month — its monthly transaction volume, retention, unlimited users and hosts, and the overage rate per additional 50K transactions, with the quota behaviour stated and a 14-day full refund plus prorated plan changes. I found no public information on VAT, annual versus monthly terms, or the price above the six-million-transaction tier, which is described as set up individually with an isolated datastore. 4 13
The Mobile Team Lead
Almost fully computable: Free €0, Beginner €15 a month, Developer €39 a month, Team €69 a month and Enterprise €169 a month, each with its monthly transaction volume, retention days, user and channel limits, the price of each additional 50K transactions (€2.50 down to €1.40 by plan), prorated plan changes, a 14-day 100% refund, and plain statement of the free plan's limits including no REST API. What stops a complete annual figure is that VAT is not stated, annual versus monthly terms are not shown, and above the top listed plan the data tier is arranged individually. 4 12
The Site Reliability Engineer
Every plan is public in euros with its monthly transaction volume, retention, the overage rate per extra 50K transactions, drop-at-quota behaviour and unlimited users, hosts and events inside a transaction — I can compute an annual cost for a known volume. What keeps it from full computability: I found no public information on VAT treatment, annual terms, or anything above the top plan beyond a custom data tier set up around your needs. 4 12
The Data Protection Officer
Every plan is priced in euros with its monthly transaction volume, retention days, seat and channel policy, and the price of each additional 50K-transaction slot, and the quota behaviour, prorated plan changes and a 14-day full refund are all stated. VAT treatment and annual versus monthly terms are not stated, and volumes above the top plan are bespoke, which keeps a fully computable annual cost just out of reach. 4 12 13
The Skeptic
Every plan is priced in euros with its monthly transaction volume, retention days and the price of each additional 50K slot, and quota behaviour is spelled out — drop new data or use optional usage-based billing — with prorated plan changes and a 14-day full refund. I found no public information on VAT, annual versus monthly terms or a price calculator, and the captured pages give different figures for notification channel limits — "Unlimited" on the pricing page against a docs statement that channels are limited by subscription plan. 4 12 13
European sovereignty — proven facts
0 of 6 dimensions provenBuilt only from facts shown on the vendor's own pages. A dimension we could not prove is left open, not scored as zero.
| Legal entity | Not determined | — | uncited Report an error |
|---|---|---|---|
| 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
- Evidence ages. The oldest capture behind this page is from 6 Nov 2026. Vendors change pricing and policies without notice; every fact reflects its source as of the capture date shown in the registry.
- AI can misread a source. Extraction and judgement are automated; a citation guarantees traceability, not infallibility. If something here is wrong, say so — no account needed, every report is decided within 5 business days, and accepted corrections are published.
What we left out
A claim that does not survive our checks costs us the claim, not the page. This is what was taken off this one.
- 1 pricing fact could not be confirmed on the vendor’s page as captured and was left out of this page and of the panel’s material. Know more? Tell us
- 1 product fact could not be confirmed on the vendor’s page as captured and was left out of this page and of the panel’s material. Know more? Tell us
Sources (16)
The pages every claim on this page was read from — each one checked, dated, and kept verifiable.
- 1 Vendor homepage inspector.dev Checked 6 Nov 2026 Details →
- 2 Features page inspector.dev Checked 6 Nov 2026 Details →
- 3 Documentation docs.inspector.dev Checked 6 Nov 2026 Details →
- 4 Pricing page inspector.dev Checked 6 Nov 2026 Details →
- 5 Public status page status.inspector.dev Checked 6 Nov 2026 Details →
- 6 About page (names the operating company) inspector.dev Checked 6 Nov 2026 Details →
- 7 Error capture, grouping & triage — found from sitemap inspector.dev Checked 6 Nov 2026 Details →
- 8 Error capture, grouping & triage — found from sitemap docs.inspector.dev Checked 6 Nov 2026 Details →
- 9 APM, tracing & profiling — found from sitemap docs.inspector.dev Checked 6 Nov 2026 Details →
- 10 APM, tracing & profiling — found from sitemap inspector.dev Checked 6 Nov 2026 Details →
- 11 Alerting, integrations & developer workflow — found from sitemap docs.inspector.dev Checked 6 Nov 2026 Details →
- 12 Alerting, integrations & developer workflow — found from sitemap docs.inspector.dev Checked 6 Nov 2026 Details →
- 13 Data scrubbing, retention & volume control — found from sitemap inspector.dev Checked 6 Nov 2026 Details →
- 14 Data scrubbing, retention & volume control — found from sitemap docs.inspector.dev Checked 6 Nov 2026 Details →
- 15 Access control, security & the vendor's reliability — found from sitemap inspector.dev Checked 6 Nov 2026 Details →
- 16 Access control, security & the vendor's reliability — found from sitemap docs.inspector.dev Checked 6 Nov 2026 Details →