DISCLAIMER: This page is for information only. It is not legal, financial or procurement advice and does not replace your own due diligence. Licenses, ownership, features and certifications can change: confirm what your decision rests on with the official sources.
🩺 Vitals
- 🟢 Last active: 2026-11-11
- 📦 Latest release: v0.149.0 (2026-11-04)
- 🐞 Open issues: 1617
- 🌟 Stars: 32.6k
What do these metrics mean?
- Last active: when code was last pushed, as of our last check. The dot is green when that was recent, grey otherwise. A long gap can mean a tool is finished and stable, not only unmaintained.
- Latest release: the most recent stable version the maintainers published as a release on the forge. Some healthy projects publish only tags, or publish their versions elsewhere.
- Open issues: unresolved reports and requests. A high number is normal for a popular project and is not a warning on its own.
- Stars: how many people bookmarked the project on its forge. A rough popularity signal, not a measure of quality.
🏗️ Profile
- Official: signoz.io
- Source: github.com/SigNoz/signoz
- License: MIT (core; paid edition under its own terms)
- Deployment: Docker Container | Kubernetes (K8s) | Native System (Binary/Linux)
- Jurisdiction: United States 🇺🇸 (SigNoz, Inc.)
- Compliance (SaaS): SigNoz Cloud security and compliance page
- Compliance (Self-Hosted): Self-Hosted (User Managed)
- Complexity: High (4/5) - Five services on one node by default: the SigNoz server, an OpenTelemetry collector, ClickHouse with ClickHouse Keeper, and PostgreSQL; production sizing spreads ClickHouse over shards
- Maintenance: High (4/5) - Weekly releases carry breaking changes, and some are required upgrade stops for schema migrations; ClickHouse storage is sized to the retention you keep
- User Management: Moderate (3/5) - Three built-in roles, Google Workspace sign-in and TLS in its own server in the free build; SAML, other OpenID Connect providers and custom roles need a paid license, and there is no audit log
What the scores mean: Reading the Scores
1. The Executive Summary
What is it? SigNoz is an observability platform built on OpenTelemetry that brings logs, metrics, traces, alerts and dashboards into one place, stored in ClickHouse. It serves engineering teams that monitor their own applications and infrastructure. The paid edition adds anomaly-detection alerts.
The Strategic Verdict:
- 🔴 For teams that must keep personal data in-house: Caution. By default the install sends usage data, users' email addresses included, to a US analytics provider until the operator switches it off (Jurisdiction, The Compliance Shift).
- 🟢 For engineering teams leaving a bill that grows with hosts and data: Strong Buy. The MIT core carries no license fee, so the cost follows the servers you run (Cost of Ownership).
2. Cost of Ownership
| Cost Component | SigNoz (Self-Hosted) |
|---|---|
| Pricing Model | No license fee for the core; paid edition for some features |
| Adoption | Manual migration (agents replaced with OpenTelemetry; dashboards recreated) |
| Operations | Distributed cluster, grows with telemetry volume; plus your team's time to run it (Maintenance, in the Profile) |
| Support | From the vendor: SigNoz Cloud, a managed service, and paid support for self-hosted installs (enterprise support); elsewhere, a paid service provider |
| Exit | Direct database access (ClickHouse SQL) |
What each row covers: Total Cost of Ownership
3. Risk Assessment
- Jurisdiction: SigNoz, Inc., the project's vendor, is registered in the United States, under US law. The vendor runs SigNoz Cloud, a hosted service where your data can live; its hosts include a party domiciled in or controlled from the US. Data in SigNoz Cloud is within reach of the US CLOUD Act wherever it is stored, since its operator is based in the US. A self-hosted install sends usage data to Twilio Inc. in the United States unless the operator switches it off. US law can compel the recipient to hand over that usage data.
- The Compliance Shift: The usage reports include users' email addresses by default. Self-hosting moves the security and compliance duties of running the software to the operator (the operator's compliance checklist). Any audit of SigNoz Cloud (such as SOC 2 or ISO 27001) covers the vendor's own systems, never your install.
- License Risk: SigNoz is under MIT, an OSI-approved permissive license (what it allows and requires). MIT lets anyone, the vendor included, release modified versions under other terms, closed ones too. The default install image also carries enterprise-licensed code, allowed in production only with a subscription; an MIT-only image is published apart.
4. Market Landscape
🏢 Proprietary Incumbents
- Datadog: Datadog is a cloud platform for monitoring infrastructure, applications and logs.
Data held by: Datadog, Inc., United States 🇺🇸, subject to the US CLOUD Act for the data it holds, wherever it is stored.
Why teams leave: It may raise its prices at renewal, and its bill grows with hosts and log volume.
Exit: Log archives to the customer's own storage (JSON), partial export (metrics and traces in bulk)
With SigNoz: No license fee per host or per gigabyte; the cost is the servers you run (Cost of Ownership). - New Relic: New Relic is a cloud observability platform for monitoring software systems.
Data held by: New Relic, Inc., United States 🇺🇸, subject to the US CLOUD Act for the data it holds, wherever it is stored.
Why teams leave: Its automated user provisioning comes only on its higher editions.
Exit: Historical data export through the NerdGraph API (gzipped JSON), bulk export only in a higher tier, partial export (metric timeslice data)
🤝 Open-Source Alternatives
- Grafana: AGPL-3.0 dashboarding and observability platform: self-hostable unified metrics, logs, and traces. A sovereign alternative to Datadog with no per-host ingestion cost.