# SigNoz — Error Tracking & APM

SigNoz by SigNoz Inc. holds a panel rating of 2.5/5 from 6 AI judges (category median 2.5/5), as of 2026-11-18. Provenance: provenance unknown; sovereignty: not determined.

- Vendor: SigNoz Inc. (https://signoz.io)
- Category: [Error Tracking & APM](https://whats-best.ai/software/error-tracking.md)
- Provenance (editorial classification): provenance unknown
- Canonical page: https://whats-best.ai/software/error-tracking/signoz
- Alternatives: https://whats-best.ai/software/error-tracking/signoz/alternatives ([markdown](https://whats-best.ai/software/error-tracking/signoz/alternatives.md))
- Data as of: 2026-11-21 · evaluated 2026-11-18 · oldest source captured 2026-11-17

**AI-generated.** Every score, rationale and verdict here is written by a panel of AI judges from public evidence — an analysis, not a hands-on test. Every fact quotes the vendor page it was read from. No score can be bought. How scores are made: https://whats-best.ai/methodology

## 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

## 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

## Scores by judge and criterion

Scores out of 5, each judge scoring independently against the published rubric (v1). "n/r" = not rated: the vendor publishes no price, or the judge found no public information on that criterion.

| Criterion | The Agency Tech Lead | The SaaS CTO | The Mobile Team Lead | The Site Reliability Engineer | The Data Protection Officer | The Skeptic |
| --- | --- | --- | --- | --- | --- | --- |
| Error capture, grouping & triage | 2/5 | 2/5 | 2/5 | 2/5 | 2/5 | 2/5 |
| APM, tracing & profiling | 3/5 | 3/5 | 3/5 | 2.5/5 | 3/5 | 3/5 |
| Alerting, integrations & developer workflow | 2/5 | 2/5 | 2/5 | 2/5 | 2/5 | 2/5 |
| Data scrubbing, retention & volume control | 3/5 | 2.5/5 | 2.5/5 | 2.5/5 | 2.5/5 | 2/5 |
| Access control, security & the vendor's reliability | 3/5 | 3/5 | 3/5 | 3/5 | 3/5 | 3/5 |
| European sovereignty | 2.5/5 | 3/5 | 2/5 | 2/5 | 3/5 | 2/5 |
| Pricing transparency | 1.5/5 | 1/5 | 1.5/5 | 1/5 | 1/5 | 1/5 |
| **Weighted verdict** | **2.5/5** | **2.5/5** | **2/5** | **2.5/5** | **2.5/5** | **2/5** |

### The judges

- **The Agency Tech Lead** (v1.0): 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.
- **The SaaS CTO** (v1.0): CTO of a B2B SaaS company in Berlin with thirty-five engineers, twelve services in Go, Python and TypeScript on Kubernetes and a React frontend. Wants one trace from the click in the browser to the slow database call three services down, OpenTelemetry so the instrumentation is not locked to one vendor, errors routed to the team that owns the service, releases linked to the commits that broke them, and an EU region because the enterprise customers ask where their data goes.
- **The Mobile Team Lead** (v1.0): Leads the six-person app team of a fashion retailer in Hamburg, with an iOS and an Android app and a Flutter rewrite under way, released every two weeks. Wants native crashes symbolicated without a manual upload, crash-free users per release so a bad version is stopped in the store rollout, the device, OS and the last screens before the crash, logs from a customer's phone when support asks, and alerts when a new release crashes more than the last.
- **The Site Reliability Engineer** (v1.0): Site reliability engineer on the on-call rota of a payments platform in Amsterdam, woken at night when checkout latency climbs. Wants alerts on error rates and latency percentiles, not on every single exception, routed to PagerDuty with the trace attached, spike protection so an incident does not also blow the quota, SSO and audit logs for the auditors, and a vendor whose own status page and SLA say what happens when the monitoring is the thing that is down.
- **The Data Protection Officer** (v1.0): Data protection officer of a statutory health insurer whose member portal and app are built by an in-house team and two agencies. Knows that a stack trace or a request body can carry a member number, a diagnosis code or an IBAN. Reads the subprocessor list, asks where events are stored and for how long, wants scrubbing on the server and not only in the SDK, asks which AI model explains the errors and where, and needs a DPA before the first SDK goes into production.
- **The Skeptic** (v1.0): Has seen a "free tier" that ran out on the first busy Monday, an overage bill larger than the plan after one deploy looped on an exception, "EU hosting" with the support desk and the AI assistant in the US, and an SDK that slowed the app it was meant to watch. Asks what happens at the quota, how long events are really kept, whether the instrumentation works with another vendor after leaving, what the self-hosted edition leaves out — and what the second year costs.

## European sovereignty — proven facts

Built only from facts on the vendor's own pages; a dimension we could not prove is left open, never scored as zero. Headline: not determined.

| Dimension | Finding | Points | Source |
|---|---|---|---|
| Legal entity | Not determined | — | — |
| Hosting location | Not determined | — | — |
| Hosting options | Not determined | — | — |
| Open source | Not determined | — | — |
| Data processing agreement | Not determined | — | — |
| Transfer impact assessment | Not determined | — | — |

## Key facts

Each fact is the vendor's own statement, cited to the source page it was read from ([S*n*] → Sources).

**Compliance**
- HIPAA: yes · HIPAA [S1]
- HIPAA: yes [S2]
- HIPAA: yes [S13]
- Penetration test: 2025 · yes [S2]
- Policies published: Code of Conduct, Secure Development Policy, Business Continuity and Disaster Recovery Plan, Human Resource Security Policy [S2]
- Regular audits: yes [S13]
- Security email: security@signoz.io [S2]
- SOC 2: yes · SOC 2 Type II [S1]
- SOC 2 type1: yes [S2]
- SOC 2 type2: yes [S2]
- SOC 2 type2: security · availability · processing integrity · confidentiality · privacy · yes [S13]
- Transparent operations: Clear, transparent processes for data handling [S13]

**Data**
- Classification policy: yes [S2]
- Deletion upon leaving: yes [S2]
- Retention procedures: yes [S2]

**Hosting**
- Auth ingestion key: signoz-ingestion-key · yes · Optional for the self-hosted version [S7]
- Cloud ingestion endpoint: 443 · OTLP/HTTP · https://ingest.<INGESTION_REGION>.signoz.cloud:443/v1/traces [S7]
- Provider: GCP · US · IN · EU [S2]

**Integrations**
- API reference exists: SigNoz provides a versioned API documentation page where users select a version to view API documentation [S8]
- Opentelemetry: OpenTelemetry-based instrumentation [S1]
- Traces API: Traces API available for programmatic search and aggregation [S6]

**Pricing**
- Retention affects pricing: Retention changes affect cloud pricing; pricing calculator available [S11]
- Trial: 30 · no [S1]
- Usage based: usage-based [S1]

**Product**
- Admin only role assignment: signoz-admin [S12]
- Aggregation functions: Rate · Rate Sum · Rate Avg · Rate Max · Rate Min · P05 · P10 · P25 · P50 · P75 · P90 · P95 · P99 · Count · Count Distinct · Sum · Avg · Min · Max [S6]
- Alerts dashboards: yes [S7]
- Android support: OpenTelemetry Android agent · Android · Java · Kotlin · traces · logs · metrics [S5]
- Anti malware: yes [S2]
- API key management: yes [S13]
- Chart thresholds: good · needs improvement · critical · yes [S7]
- Clickhouse sql dashboards only: dashboards_only · yes [S6]
- Cloud retention logs options: 15 · 30 · 90 · 180 · 1 [S11]
- Cloud retention metrics options: 1 · 3 · 6 · 13 [S11]
- Cloud retention traces options: 15 · 30 · 90 · 180 · 1 [S11]
- Custom role name rules: 50 · lowercase letters and hyphens · no [S12]
- Custom roles update delete: yes [S12]
- Custom span processor: custom SpanProcessor implementation attaching attributes to exported spans [S7]
- Cybersecurity insurance: yes [S2]
- Data encryption: yes [S2]
- Default retention: 15 · 30 [S11]
- Demo application: Demo React application · yes [S7]
- Disaster recovery: yes [S2]
- Employee background checks: yes [S2]
- Exceptions alerts: alerts on new exception types or increased frequency [S4]
- Exceptions browse: list shows exception type, count, first seen and last seen times [S4]
- Exceptions cloud grouping restriction: cloud · no [S4]
- Exceptions collector version: 0.120.0 · 0.144.3 [S4]
- Exceptions detail identifiers: spanID · traceID · serviceName · groupID [S4]
- Exceptions event name rule: span event named exception or ending in .exception counts [S4]
- Exceptions filters: deployment environment · service · host · Kubernetes cluster · namespace · deployment · pod [S4]
- Exceptions grouping: service · exception type · exception message [S4]
- Exceptions identifiers: span ID · trace ID [S4]
- Exceptions log based convention: log-based .exception records do not reach Exceptions view unless SDK routes them onto spans [S4]
- Exceptions selfhost grouping option: low_cardinal_exception_grouping · self-hosted only [S4]
- Exceptions semconv opt in: OTEL_SEMCONV_EXCEPTION_SIGNAL_OPT_IN=logs diverts exceptions to logs; logs/dup emits both [S4]
- Exceptions sorting: Last Seen · First Seen · Count · Exception Type · Application [S4]
- Exceptions source: exception span events from traces [S4]
- Exceptions stacktrace: yes [S4]
- Exceptions stored attributes: exception.type · exception.message · exception.stacktrace · exception.escaped [S4]
- Exceptions trace link: exceptions link to flame graph / waterfall of full trace [S4]
- Filter operators: = · != · IN · LIKE · EXISTS · AND · OR [S6]
- Fine grained access control beta: yes [S12]
- Flutter data: events [S5]
- Flutter support: iOS · Android · Flutter · yes [S5]
- Formulas limit: 10 [S6]
- Group by: Group By supported in Time Series and Table views, by one or more attributes [S6]
- Having clause: yes [S6]
- Infinite retention aws s3: Infinite retention using AWS S3 documented [S11]
- Infrastructure security controls: Unique production database authentication enforced, encryption key access restricted, unique account authentication enforced [S2]
- Ios support: OpenTelemetry Swift SDK · iOS · Swift UI [S5]
- Managed roles: 4 · SigNoz-Admin · SigNoz-Editor · SigNoz-Viewer · SigNoz-Anonymous [S12]
- Managed roles immutable: no [S12]
- Missing key handling: Queries against keys missing from metadata still run against stored span data with a warning [S6]
- Mobile data types: traces · logs · performance data [S5]
- Mobile otel instrumentation: yes · OpenTelemetry SDK instrumentation [S5]
- Mobile visibility: app behavior · API call latency · errors · crashes [S5]
- Noz AI: Noz AI teammate inside SigNoz Cloud [S1]
- Out of box dashboard: importable out-of-the-box dashboard for web vitals · yes [S7]
- Penetration testing: yes [S2]
- Pii scrubbing: before sending to SigNoz · OpenTelemetry Collector transform processor · yes [S10]
- Pii scrubbing: yes [S13]
- Pii types documented: email · SSN · credit_card [S10]
- Platform description: SigNoz Cloud is an OpenTelemetry-native platform for traces, metrics, and logs [S1]
- Platforms: Web [S1]
- Prerequisites: yes [S12]
- Query builder: Query builder, PromQL, and ClickHouse SQL [S1]
- Query builder availability: trace_explorer · dashboards [S6]
- Related guide resource attributes: related guide exists for removing resource attributes from logs [S10]
- Retention applies new data only: Retention changes apply only to newly ingested data; existing data keeps previous settings [S11]
- Retention permanent deletion: Data past TTL is permanently deleted and not recoverable [S11]
- Retention trial payment card: yes [S11]
- Role delete preconditions: yes [S12]
- Role name immutable: no [S12]
- Role relation scopes: all · only_selected · none [S12]
- Rum enrichment: RUM-like insights · yes · browser type · user ID · page URL [S7]
- Self hosted cors required: yes [S7]
- SSO SAML: yes [S13]
- Swiftui data: events [S5]
- Trace based alerts: yes [S6]
- Trace details views: flamegraph · waterfall [S6]
- Trace matching operators: Has Direct Child => · Has Descendant -> · AND && · OR \|\| · NOT [S6]
- Traces explorer view: each trace contains the 5 web vitals as child spans · Traces Explorer [S7]
- Transaction groups modes: interactive · json [S12]
- Transform processor regex: replace_pattern statements with regular expressions in OTel Collector transform processor [S10]
- Web vitals metrics captured: LCP · INP · CLS · TTFB · FCP [S7]
- Web vitals traces: web vitals monitoring via OpenTelemetry traces [S7]

**Subprocessors**
- Github: GitHub · Version Control Provider [S2]
- Google cloud platform: Google Cloud Platform · Infrastructure Hosting [S2]
- Slack: Slack · Collaboration Services [S2]
- Zoom: Zoom · Video Conferencing Services [S2]

**Support**
- Exceptions channels: SigNoz Community Slack · in-product chat support (Cloud) [S4]
- Pii doc channels: community_slack · in_product_chat_for_cloud [S10]
- Status page: yes [S2]
- Trust center: yes [S1]

## Questions

### 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)](https://whats-best.ai/software/error-tracking/sentry), [Datadog APM & Error Tracking (3.5/5)](https://whats-best.ai/software/error-tracking/datadog) and [Dynatrace (3/5)](https://whats-best.ai/software/error-tracking/dynatrace) 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](https://whats-best.ai/software/error-tracking/tideways) (EU-Made). Ratings are the AI panel’s opinion, formed from public evidence: [how scores are made](https://whats-best.ai/methodology#ordering). The full list, with European products first: [SigNoz alternatives](https://whats-best.ai/software/error-tracking/signoz/alternatives).

## What this page leaves out

- 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.
- 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.
- 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.
- 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.
- 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.
- 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.
- 1 sovereignty dimension could not be confirmed on the vendor’s own pages and is shown as unknown.

## Sources

- [S1] Vendor page: https://signoz.io (checked 2026-11-17)
- [S2] Security / trust page — found from the homepage: https://trust.signoz.io/ (checked 2026-11-17)
- [S3] Code repository (open-source licence) — found from the homepage: https://github.com/SigNoz (checked 2026-11-17)
- [S4] Error capture, grouping & triage — found from sitemap: https://signoz.io/docs/userguide/exceptions/ (checked 2026-11-17)
- [S5] Error capture, grouping & triage — found from sitemap: https://signoz.io/docs/mobile-monitoring/ (checked 2026-11-17)
- [S6] APM, tracing & profiling — found from sitemap: https://signoz.io/docs/apm-and-distributed-tracing/querying-traces/ (checked 2026-11-17)
- [S7] APM, tracing & profiling — found from sitemap: https://signoz.io/docs/frontend-monitoring/web-vitals-with-traces/ (checked 2026-11-17)
- [S8] Alerting, integrations & developer workflow — found from sitemap: https://signoz.io/api-reference/ (checked 2026-11-17)
- [S9] Alerting, integrations & developer workflow — found from sitemap: https://signoz.io/docs/alerts-management/reference/ (checked 2026-11-17)
- [S10] Data scrubbing, retention & volume control — found from sitemap: https://signoz.io/docs/logs-management/guides/pii-scrubbing/ (checked 2026-11-17)
- [S11] Data scrubbing, retention & volume control — found from sitemap: https://signoz.io/docs/userguide/retention-period/ (checked 2026-11-17)
- [S12] Access control, security & the vendor's reliability — found from sitemap: https://signoz.io/docs/manage/administrator-guide/iam/roles/ (checked 2026-11-17)
- [S13] Access control, security & the vendor's reliability — found from sitemap: https://signoz.io/faqs/how-signoz-ensures-data-security-and-privacy/ (checked 2026-11-17)

---

Cite as: whats-best.ai, "SigNoz — Error Tracking & APM", AI panel analysis, as of 2026-11-21. https://whats-best.ai/software/error-tracking/signoz

Corrections: https://whats-best.ai/correct/1994?target=page
