0–5 in half steps. 5 means the rubric's top anchor is met on the evidence.
by SigNoz Inc. · signoz.io
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.
SigNoz at a glance
- Vendor
- SigNoz Inc.
- Headquarters
- Not stated on the vendor’s pages as of 17 Nov 2026
- Data hosting
- Not stated on the vendor’s pages as of 17 Nov 2026
- Free plan
- Not stated on the vendor’s pages as of 17 Nov 2026
- Panel verdict
- The AI panel rates SigNoz 2.5/5, the mean of 6 judges. SigNoz Cloud, from SigNoz Inc., is an OpenTelemetry-native platform for traces, metrics and logs. how scores are made
- As of
- Vendor pages captured 17 Nov 2026; evaluated by the panel 18 Nov 2026. all sources
Read this page as one judge. Each weighs the same scores by what they care about.
The panel's verdict
SigNoz Cloud, from SigNoz Inc., is an OpenTelemetry-native platform for traces, metrics and logs. Security and reliability scores a flat 6, on SOC 2 Type II with five named principles, HIPAA, a 2025 penetration test, tested disaster recovery and role-based access with SAML SSO. Performance tracing scores 5 to 6 on percentiles to P99, flamegraph and waterfall views, and web vitals captured as traces. The floor is pricing transparency at 2 to 3: a usage-based model and a 30-day free trial with no credit card required are stated, but no plan, per-unit or overage figure appears on the pages. Error tracking and workflow and integrations sit at a flat 4 — exceptions group and link to full traces, but we found no public information on issue states, release tracking or notification channels. Sovereignty splits 4 to 6: higher scores credit the self-hosted edition and the EU residency choice, lower ones cite subprocessors listed without locations and no published processing agreement. Data controls spans 4 to 6, between documented scrubbing and retention and no public information on sampling or quotas.
Speaks for it
- OpenTelemetry-native traces, metrics and logs, with percentiles to P99, flamegraph and waterfall views, and query builder, PromQL and ClickHouse SQL.
- Security and reliability scored a flat 6, on SOC 2 Type II naming five principles, HIPAA, a 2025 penetration test attestation, tested disaster recovery and role-based access with SAML SSO.
- PII scrubbing documented with regular expressions in the OpenTelemetry transform processor, with worked examples for email, social security and card numbers, positioned for GDPR and CCPA.
- Retention published per signal — traces and logs 15, 30, 90, 180 days or 1 year, metrics 1, 3, 6 or 13 months — with permanent deletion at expiry and an AWS S3 route for infinite retention.
- Cloud servers sit on GCP with a choice of US, IN or EU residency, and a self-hosted edition runs under an active license with the cloud ingestion key optional.
Held against it
- Pricing transparency scores 2 to 3 — no plan price, per-unit rate, overage behaviour or VAT figure appears on the captured pages.
- Alert rules are documented, but we found no public information on notification channels like Slack, PagerDuty or email, on issue tracker integrations, webhooks or a CLI.
- Exception triage is trace-first: we found no public information on issue states like resolved or regressed, on release and deploy tracking or source maps, and the pages state cloud users cannot change the grouping strategy.
- The Noz AI teammate is advertised without a named model provider or processing location.
- We found no public information on sampling, rate limits, quota caps or spike protection, so the invoice effect of a traffic spike cannot be computed from the pages.
Best for
- You already emit OpenTelemetry telemetry and want percentiles to P99 with PromQL and ClickHouse SQL in one platform.
- You need an audit-ready vendor before signing — SOC 2 Type II, HIPAA and a 2025 penetration test are published.
- You want to run the platform yourself under an active license, with the cloud ingestion key optional and your own AWS S3 retention.
- Your frontend team tracks Core Web Vitals (LCP, INP, CLS, TTFB, FCP) as traces with browser, user ID and page URL enrichment.
Avoid if
- You must compute an annual cost before committing — ask the vendor: the public pages we read do not show it
- Your on-call rotation needs alerts routed to PagerDuty, Opsgenie or Slack — ask the vendor: the public pages we read do not show it
- Your workflow depends on resolved or regressed issue states and release tracking — ask the vendor: the public pages we read do not show it
- A traffic spike must not change your invoice — ask the vendor: the public pages we read do not show it
The scores
| Criterion | Panel median |
|---|---|
| Error capture, grouping & triage | 2 of 5 |
| APM, tracing & profiling | 3 of 5 |
| Alerting, integrations & developer workflow | 2 of 5 |
| Data scrubbing, retention & volume control | 2.5 of 5 |
| Access control, security & the vendor's reliability | 3 of 5 |
| European sovereignty | 2.5 of 5 |
| Pricing transparency | 1 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 exceptions documentation is thorough on mechanics: exceptions arrive as span events with stored type, message and stack trace, are grouped by service, exception type and message, filterable by environment, service and Kubernetes dimensions, and each links to its full trace with span and trace identifiers, plus documented OpenTelemetry agents for iOS, Android and Flutter. For my Laravel crews, though, the captured pages show no release or deploy tracking, no issue states like resolved or regressed, no source maps, and the pages themselves state that cloud users cannot change the grouping strategy today; nothing names PHP or Laravel SDKs specifically. 1 4 5
The SaaS CTO
The exceptions documentation is solid for a trace-native tool: exceptions are read from span events, grouped by service, type and message, with stack traces, Kubernetes-aware filters and sorting, and one click from an exception to the full trace waterfall; mobile arrives via OpenTelemetry for Android, iOS Swift and Flutter. Triage lifecycle is thin for my teams, though — the pages are silent on issue states like resolved or regressed, on release tracking, suspect commits and source maps, cloud users cannot change the grouping strategy, and log-based exception records don't reach the Exceptions view. 4 5 1
The Mobile Team Lead
Exceptions arrive as span events from the traces we already send, with stack traces, grouping by service, type and message, filters, and alerts when a new type appears or a known one gets more frequent, and iOS, Android and Flutter monitoring is documented. It is a trace-first exceptions view though: we found no public information on symbolication, crash-free users or sessions per release, issue states like resolved or regressed, or release and deploy tracking — exactly what I need before stopping a bad store rollout. 4 5
The Site Reliability Engineer
Exceptions arrive from the OpenTelemetry traces a service already sends, with type, message and stack trace stored, grouped by service, exception type and message, filterable by environment, service, host and Kubernetes dimensions, each one linking to its full trace — and mobile errors and crashes come through the documented Android, Swift and Flutter routes. The captured docs state that cloud users cannot change the grouping strategy today, and we found no public information on issue states, source maps, release tracking or crash-free users and sessions. 1 4 5
The Data Protection Officer
Exceptions are read from the traces our services already send, with stack traces when the instrumentation recorded one, grouping by service, exception type and message, filters and sorting, and a link to the full trace; mobile is covered for Android, iOS and Flutter through OpenTelemetry. The captured pages state that cloud users cannot change the grouping strategy today, and we found no public information on issue states such as resolved or ignored, release and deploy tracking, or source maps and symbolication. 4 5
The Skeptic
Exceptions arrive as OpenTelemetry span events with stack traces, grouped by service, exception type and message, filterable and sortable, and each one opens the full trace in a flamegraph or waterfall view; mobile errors and crashes are covered through OpenTelemetry SDKs for iOS, Android and Flutter. But the captured pages state that cloud users cannot change the grouping strategy today, and we found no public information on issue states like resolved or regressed, source maps and symbolication, breadcrumbs, or release and deploy tracking — the lifecycle a team actually works in. 4 5 1
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
Traces carry percentiles from P05 to P99, a query builder with post-aggregation filters like p99 above 500ms, flamegraph and waterfall views, trace-based alerts on latency spikes and error rates, and OpenTelemetry-native OTLP ingestion end to end; web vitals (LCP, INP, CLS, TTFB, FCP) land as child spans with RUM-like enrichment and an importable dashboard, which covers the frontend story before a client calls about a slow page. We found no public information on code-level profiling, slow-query or N+1 detection, host metrics beside traces, or sampling and its effect on the captured pages. 4 6 7
The SaaS CTO
This is the architecture I want: OpenTelemetry-native end to end, an OTLP ingestion endpoint documented with its key header, percentile aggregations through P99 in the query builder, flamegraph and waterfall trace views, and trace-based alerts on latency spikes and error rates. Web vitals (LCP, INP, CLS, TTFB, FCP) arrive as child spans of a trace with RUM-like enrichment, and errors link straight back to the trace. It stops short of the top tier: we found no public information on code-level profiling, host and container metrics beside traces, or trace sampling configuration and its effects. 1 6 7 4
The Mobile Team Lead
Distributed traces with flamegraph and waterfall views, percentile aggregations from P05 to P99 in a query builder plus PromQL and ClickHouse SQL, trace-based alerts on latency spikes and error rates, and Core Web Vitals captured as traces with browser, user ID and page URL enrichment are all documented. We found no public information on code-level profiling, host or container metrics beside the traces, or trace sampling and its effect. 1 6 7
The Site Reliability Engineer
Percentiles through P99 with rate and statistical functions, flamegraph and waterfall trace views, span-relationship matching, and web vitals (LCP, INP, CLS, TTFB, FCP) captured as traces with browser and user attributes for real-user-monitoring-style insight, all on documented OpenTelemetry ingestion with metrics queryable in PromQL and ClickHouse SQL. We found no public information on code-level profiling, slow-query or N+1 detection, background job monitoring, or configurable trace sampling and its effect. 1 6 7
The Data Protection Officer
Distributed tracing with flamegraph and waterfall views, percentile aggregations up to P99, trace-based alerts on latency spikes and error rate, and real-user web vitals (LCP, INP, CLS, TTFB, FCP) as OpenTelemetry traces are documented on an OpenTelemetry-native platform with an OTLP ingestion endpoint. We found no public information on code-level profiling, anomaly detection on throughput or latency, or how trace sampling is configured and what it means for visibility. 1 6 7
The Skeptic
Percentiles up to P99 with grouping and post-aggregation filters, span-matching operators, raw ClickHouse SQL against the trace tables, trace-based alerts on latency and error rate, all on an OpenTelemetry-native pipeline whose ingestion endpoint and port are documented. Web vitals (LCP, INP, CLS, TTFB, FCP) are captured as traces with RUM-like enrichment, and an exception links straight to its full trace. We found no public information on code-level profiling, slow query or N+1 detection, background job monitoring, or sampling and its effect on cost. 6 7 4 1
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
Alert rules are documented for new exception types, rising frequency, latency spikes and error-rate changes, a versioned API reference exists, and the Noz AI teammate is described for incident investigation and alert tuning, though the model behind it is not named on these pages. I need each of my forty client projects routing alerts to its own channel, and the captured pages name no notification channels beyond community Slack and in-product chat for cloud users, no issue tracker integrations, and no webhooks or CLI. 1 4 6 8
The SaaS CTO
Alert rules are documented on new and more frequent exception types and on latency spikes and error rate changes, a versioned API reference exists, and the Noz AI teammate is named — though no model provider is stated. What I could not see is how an alert reaches the person on call: we found no public information on notification channels like Slack, PagerDuty or email delivery of alerts, issue tracker integrations, deploy hooks from CI, webhooks or a CLI. 4 6 8 1
The Mobile Team Lead
Alert rules on new exception types, rising frequency, latency spikes and error-rate changes are documented, a versioned API reference exists, and the Noz AI teammate can investigate incidents and tune alerts. But we found no public information on notification channels like Slack, email or an on-call tool, issue tracker sync, deploy hooks from CI, a CLI, or which model powers the AI — so I cannot see how a page would actually reach my on-call engineer. 1 4 6 8
The Site Reliability Engineer
Alert rules are documented on new exception types, increased frequency, latency spikes and error rate changes, backed by a versioned API reference and a traces API, plus the Noz AI teammate for investigating incidents — though the model behind it is not named. We found no public information on PagerDuty, Opsgenie or other notification routing, issue tracker integrations, webhooks, or a CLI, which is exactly the leg that has to work when checkout latency climbs at 3 a.m. 1 4 6 8
The Data Protection Officer
Alert rules are documented for new exception types, increased frequency, latency spikes and error-rate changes, alongside a versioned API reference and a programmatic traces API. We found no public information on notification channels such as email, Slack, Microsoft Teams or on-call paging, on issue tracker integrations, webhooks or a CLI; the Noz AI teammate is described for incident investigation but no model provider is named, which is the first thing I ask before an AI tool reads error data. 1 4 6 8
The Skeptic
Alert rules are real and documented — new exception types, rising frequency, latency spikes, error-rate changes — and a versioned API plus a Traces API for programmatic search exist; the Noz AI teammate is advertised with no model provider or data handling named. We found no public information on notification channels such as email, Slack, Teams or PagerDuty, issue tracker integrations, webhooks, a CLI, or release hooks from CI — how an alert reaches the person on call is not shown on the pages we read. 4 6 8 1
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
PII scrubbing is documented with regular expressions in the OpenTelemetry transform processor, with worked examples for email, social security numbers and card numbers plus a companion guide for stripping resource attributes — since scrubbing happens in my own collector, the shops' customer addresses get cleaned before they ever leave the pipeline, and GDPR and CCPA support is claimed. Retention is public per signal with the pricing effect of changing it called out and TTL deletion described as permanent, and both an open-source self-hosted edition and an EU region option are documented. We found no public information on default server-side scrubbing, IP anonymisation, sampling, rate limits, spike protection or per-project quota caps — exactly the controls that keep the bill flat when one client's cron throws the same exception a million times. 2 10 11 13
The SaaS CTO
Scrubbing is documented with regex replace rules in the OpenTelemetry transform processor and concrete examples — email, social security number, credit card — plus removal of unwanted resource attributes, positioned for GDPR and CCPA. Retention is unusually well documented per signal (15 days to one year for traces and logs, 1 to 13 months for metrics) with permanent-deletion semantics and a pricing link, and the open-source self-hosted edition plus infinite retention on AWS S3 are documented. The gap is volume control: we found no public information on sampling, rate limits, spike protection or IP anonymisation. 10 11 13 3
The Mobile Team Lead
PII scrubbing is documented with regex examples for email, social security and card numbers in the OpenTelemetry Collector, retention is published per plan from 15 days to a year for logs and traces with permanent deletion at expiry, and a self-hosted deployment with its own grouping option is described. We found no public information on IP anonymisation, sampling, rate limits, quota caps or spike protection, so I cannot tell how a Christmas-season traffic spike would hit our invoice. 4 10 11
The Site Reliability Engineer
PII scrubbing is documented with worked examples — email, social security number and credit card patterns removed through the OpenTelemetry transform processor with regular expressions, in support of GDPR and CCPA — and retention is fully stated: 15 days default for traces and logs, 30 for metrics, up to a year or 13 months, permanent deletion at expiry, customer data deleted upon leaving, and an AWS S3 route for longer retention. We found no public information on IP anonymisation, sampling, rate limits, or spike protection and quota caps, which is what I need so an incident does not also blow the invoice. 2 10 11 13
The Data Protection Officer
PII scrubbing is documented with regular-expression rules and worked examples for email, social security and card numbers, but it runs in the OpenTelemetry Collector on my side of the wire, and we found no public information on server-side scrubbing or IP anonymisation in the cloud service. Retention is unusually well documented with tiers, defaults, permanent deletion at expiry and deletion of customer data upon leaving, traces are exportable programmatically, and a self-hosted edition keeps events on our own servers; on sampling, rate limits, quota caps and spike protection we found no public information. 2 6 10 11 13
The Skeptic
PII scrubbing is documented with regex examples for emails, SSNs and card numbers via the OpenTelemetry transform processor — in your own pipeline, before anything leaves — and retention is stated per signal (15, 30, 90, 180 days or a year for traces and logs), permanent once past its TTL, with changes priced through a calculator and customer data deleted upon leaving. But we found no public information on IP anonymisation, sampling, rate limits, spike protection, or what happens when the quota is hit — the bill on the first busy Monday is not computable from these pages. 10 11 13 2
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
SOC 2 Type II is stated with its five principles, a 2025 penetration test attestation is published alongside policies, encryption, background checks and tested disaster recovery, there is a security email, a public status page and a trust centre, and access control goes deep with four managed roles, custom roles with per-instance scopes and SAML SSO. That is something I can put in front of a client auditor. We found no public information on two-factor authentication, audit logs, SCIM provisioning, an SLA with credits, or how the SDK behaves when the vendor is down. 1 2 12 13
The SaaS CTO
The trust page is one of the better ones I have read: SOC 2 Type II with all five principles named, a 2025 penetration test report published, employee background checks, cybersecurity insurance, tested disaster recovery, a status page and a security contact. Access control goes deep — four managed roles plus custom roles with per-resource permission scopes, SAML SSO with group mapping, fine-grained control in beta. We found no public information on SCIM provisioning, audit logs, an SLA with credits, or how the SDKs behave when SigNoz itself is down. 2 12 13 1
The Mobile Team Lead
SOC 2 Type II attestation with the five principles named, a 2025 penetration test report, published security policies, SAML single sign-on and a role model from Admin to Viewer with custom roles in beta give me something to show our auditors. We found no public information on SCIM, audit logs, an availability or SLA commitment, two-factor authentication, or how the mobile SDK behaves when their cloud is down. 2 12 13
The Site Reliability Engineer
SOC 2 Type II covering five named principles, HIPAA compliance, a published 2025 penetration test attestation, tested disaster recovery, a recommended status page and a trust centre with security policies cover most of what an audit asks; access control runs four managed roles plus custom roles with per-resource scopes and SAML SSO, with fine-grained access control still in beta. We found no public information on audit logs, SCIM, two-factor authentication, an SLA with credits, a public incident history, or how SDKs behave while the vendor itself is down. 1 2 12 13
The Data Protection Officer
SOC 2 Type II with its five principles stated, HIPAA compliance, a 2025 penetration test with attestation letter and report, published security policies, tested disaster recovery, employee background checks and cybersecurity insurance give a solid audit picture, and roles with custom fine-grained access control plus SSO and SAML are documented. We found no public information on SCIM provisioning, audit logs, two-factor authentication, an SLA or availability figure, the public incident history, or how SDK ingestion behaves when the vendor is down. 1 2 12 13
The Skeptic
SOC 2 Type II with the five principles named, HIPAA, a 2025 penetration test with an attestation letter, published security policies, tested disaster recovery, and a trust page that lists subprocessors and points to a status page — a serious posture. Roles go beyond basic: four managed roles plus custom roles with scoped transactions in beta, and SAML SSO is offered. We found no public information on two-factor authentication, SCIM, audit logs, an SLA with credits, public incident history, or what ingestion does when the vendor is down. 2 12 13 1
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 trust page states servers sit in GCP with a data residency choice of US, IN or EU and names subprocessors — GitHub, Google Cloud Platform, Slack and Zoom — with their purposes, so the EU region on named infrastructure is real, and a self-hosted open-source edition is documented with its own retention and optional ingestion key. But the captured pages name no EU contracting entity, publish no data processing agreement, and list no subprocessor locations, so the chain's edges stay unclear for a GDPR-maintenance client. 2 3 7 11
The SaaS CTO
GCP hosting with a customer-selectable EU region is stated plainly, and the self-hosted open-source edition — with its own collector configuration and S3 retention options — lets my team keep every event on servers we control, which is the answer my enterprise customers ask for. Subprocessors are listed by name and purpose (GitHub, Google Cloud Platform, Slack, Zoom) but without their locations, and the contracting entity's jurisdiction and a published data processing agreement are unknown, so the chain is not sovereign end to end. 2 3 4 7 11
The Mobile Team Lead
Servers are documented on Google Cloud Platform with a customer choice of US, Indian or EU data residency, and subprocessors including GitHub, Slack and Zoom are named. We found no public information on the contracting entity's jurisdiction, a published data processing agreement, the location of each subprocessor, or where the Noz AI features process data, so the chain is only partly provable from Hamburg. 2 7
The Site Reliability Engineer
The captured trust page places servers on Google Cloud Platform with a customer-selectable EU residency region alongside US and IN, and names four subprocessors — GitHub, Google Cloud Platform, Slack and Zoom — though without their locations, and a self-hosted edition is documented in the configuration guides. The contracting entity's jurisdiction, a data processing agreement and where the AI teammate processes data are unknown on the captured pages, so I cannot place the chain end to end. 2 4 7
The Data Protection Officer
The trust page states servers on Google Cloud Platform with a choice of US, IN or EU residency and names subprocessors including GitHub, Slack and Zoom, though without their locations; the contracting entity's seat is not stated and we found no public information on a data processing agreement, and the Noz AI teammate inside the cloud names no model or processing location. A self-hosted edition under an active licence, where the ingestion key is optional and events stay in the customer's own stack, is documented across the pages and is the chain I would contract for member data. 1 2 4 7 12
The Skeptic
The trust page states servers on GCP with data residency options in the US, IN or EU, and names subprocessors (GitHub, Google Cloud Platform, Slack, Zoom) — but without their locations, and we found no public information on the contracting entity's jurisdiction, a data processing agreement, or where the Noz AI teammate's model runs. A self-hosted edition exists where the cloud ingestion key is optional, but the captured pages do not state that it keeps every event on your own servers or that it makes no calls home. An EU region choice is something; a proven end-to-end chain it is not. 2 1 7
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
The model is stated as simple usage-based with a 30-day trial and no credit card, retention changes are flagged as affecting the bill with a pricing calculator referenced, and trial users must add a card before changing retention. The captured pages show no plan prices, no per-unit rates, no overage behaviour and no VAT or billing terms, so I cannot compute a monthly cost for forty client sites from what we read. 1 11
The SaaS CTO
The model is stated — simple usage-based pricing, a 30-day free trial with no credit card, and a pricing calculator the docs point to for estimating bills as retention changes — but no price figures were captured on any page: nothing per plan or per unit, no overage rates, no statement of cap versus overage behaviour, and no price for the self-hosted licence. From these pages alone I cannot compute an annual cost. 1 11
The Mobile Team Lead
Usage-based pricing with a 30-day trial that needs no credit card is stated, and retention choices are documented to affect the bill, with a pricing calculator to estimate it. No plan price, per-unit rate, overage behaviour, VAT or billing terms appear on the captured pages, so I cannot compute our annual cost for a known volume of traces and events from them. 1 11
The Site Reliability Engineer
The model is stated as "Simple usage-based pricing" with a 30-day free trial and no credit card required, retention changes are said to affect the cloud bill with a pricing calculator to estimate it, and trials need a payment card before a retention change. We found no plan price, volume limit, overage rate, add-on or VAT figure on the captured pages, so an annual cost for a given trace volume cannot be computed from them. 1 11
The Data Protection Officer
Only the pricing model is public: usage-based pricing, a 30-day free trial without credit card, retention choices that change the bill via a pricing calculator, and an active licence required for self-hosting whose price is not stated. We found no public price figures for any plan, edition or add-on on the captured pages, so an annual cost cannot be computed from them. 1 11 12
The Skeptic
The model is named — usage-based, 30-day trial with no credit card — and a pricing calculator is referenced for retention changes, but not a single figure appears: no plan price, no per-unit rate, no stated behaviour at the quota, no overage rate, no VAT, and no price for the self-hosted licence. The trial even requires adding a payment card before a retention change can be requested. The second-year cost cannot be computed from what was captured. 1 11
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
unverified
Why unverified?Not confirmed on the vendor’s own pages as captured. |
— | 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 SigNoz
Is SigNoz European?
Not determined: the vendor’s pages as captured do not say where SigNoz is based.
Where does SigNoz store data?
Not stated on the vendor’s pages as of 17 Nov 2026.
Does SigNoz have a free plan?
Not stated on the vendor’s pages as of 17 Nov 2026.
What are the best alternatives to SigNoz?
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: SigNoz alternatives.
Where this could be wrong
- Evidence ages. The oldest capture behind this page is from 17 Nov 2026. Vendors change pricing and policies without notice; every fact reflects its source as of the capture date shown in the registry.
- Weak sourcing — Hosting options. Not confirmed on the vendor’s own pages as captured.
- 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.
- 34 product facts could not be confirmed on the vendor’s page as captured and were left out of this page and of the panel’s material. Know more? Tell us
- 8 integrations facts could not be confirmed on the vendor’s page as captured and were left out of this page and of the panel’s material. Know more? Tell us
- 8 pricing facts could not be confirmed on the vendor’s page as captured and were left out of this page and of the panel’s material. Know more? Tell us
- 4 support facts could not be confirmed on the vendor’s page as captured and were left out of this page and of the panel’s material. Know more? Tell us
- 2 hosting facts could not be confirmed on the vendor’s page as captured and were left out of this page and of the panel’s material. Know more? Tell us
- 1 compliance 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 sovereignty dimension could not be confirmed on the vendor’s own pages and is shown as unknown. Know more? Tell us
Sources (13)
The pages every claim on this page was read from — each one checked, dated, and kept verifiable.
- 1 Vendor page signoz.io Checked 17 Nov 2026 Details →
- 2 Security / trust page — found from the homepage trust.signoz.io Checked 17 Nov 2026 Details →
- 3 Code repository (open-source licence) — found from the homepage github.com Checked 17 Nov 2026 Details →
- 4 Error capture, grouping & triage — found from sitemap signoz.io Checked 17 Nov 2026 Details →
- 5 Error capture, grouping & triage — found from sitemap signoz.io Checked 17 Nov 2026 Details →
- 6 APM, tracing & profiling — found from sitemap signoz.io Checked 17 Nov 2026 Details →
- 7 APM, tracing & profiling — found from sitemap signoz.io Checked 17 Nov 2026 Details →
- 8 Alerting, integrations & developer workflow — found from sitemap signoz.io Checked 17 Nov 2026 Details →
- 9 Alerting, integrations & developer workflow — found from sitemap signoz.io Checked 17 Nov 2026 Details →
- 10 Data scrubbing, retention & volume control — found from sitemap signoz.io Checked 17 Nov 2026 Details →
- 11 Data scrubbing, retention & volume control — found from sitemap signoz.io Checked 17 Nov 2026 Details →
- 12 Access control, security & the vendor's reliability — found from sitemap signoz.io Checked 17 Nov 2026 Details →
- 13 Access control, security & the vendor's reliability — found from sitemap signoz.io Checked 17 Nov 2026 Details →