
# SigNoz Self-Hosted

OpenTelemetry-based application observability platform for traces, metrics and logs.

Canonical page: https://launchinyourcloud.com/directory/signoz/
Catalog revision: 170de95bb7d832897d269051ad4500713acf96a62f3d01bc1d4e649679a56fde




Named clouds have provider-specific evidence. Missing clouds do not establish incompatibility. Preserve edition, account boundary, operating responsibilities and publisher disclosures. Source review dates record human checks, not rebuilds.


1 listing.


## SigNoz Self-Hosted

OpenTelemetry-based application observability platform for traces, metrics and logs.

- Listing: https://launchinyourcloud.com/directory/signoz/
- Publisher listing: No
- Entry kind: product
- Documented cloud IDs: aws, azure, gcp
- Operating model: Customer-operated
- Infrastructure IDs: servers
- License: MIT Expat for core code; ee/ enterprise code has its own separate license.
- Licensing model: open-source
- Installation: Use the supported Foundry workflow to generate and run the Docker Compose stack; the older bundled install script/deploy files are deprecated.
- Architecture: Customer-operated observability services, OpenTelemetry collection and persistent analytical storage
- Operations: Customer manages collectors, storage capacity, retention, authentication, backups, alert API and operator migrations, and platform upgrades.
- Product website: https://signoz.io/
- Source review: 2026-11-16; cloud review: 2026-11-12; licensing review: 2026-11-10; infrastructure review: 2026-11-16

### Scope and qualifications

The reviewed guide is explicitly for self-hosted Community without a license. Commercial features require their stated terms. Instrumentation can capture sensitive payloads, so configure capture and retention according to the data being monitored. SigNoz v0.150.0 automatically migrates stored alert rules to v2alpha1 but removes the v1 rule APIs and GET /api/v2/rules. Update API scripts, move Terraform configurations from signoz_alert to signoz_rule, use SigNoz Operator v0.0.5 or newer, and back up the metastore before upgrading. The release also begins dual-ingesting log bodies into native JSON storage; plan additional collector, ClickHouse, and log-disk capacity before rollout.

MIT Expat for core code; ee/ enterprise code has its own separate license. This classification covers the reviewed upstream edition; external services and dependencies retain their own terms.

Customer-operated observability services, OpenTelemetry collection and persistent analytical storage. This is a customer-operated server/container deployment; portability does not establish named cloud-provider support. From v0.150.0, log bodies are dual-ingested during migration. The vendor recommends 25% OpenTelemetry Collector CPU and memory headroom, 15% ClickHouse CPU headroom, and log-disk growth approximately equal to the existing body column.


### Category fit

- observability: Application observability over OpenTelemetry traces, metrics and logs; applications must be instrumented and collection configured.

### Deployment boundaries


- aws: Customer cloud account; Customer-operated; control plane: not-assessed. Source: https://signoz.io/docs/install/kubernetes/aws/ (checked 2026-11-12). 

- azure: Customer cloud account; Customer-operated; control plane: not-assessed. Source: https://signoz.io/docs/install/kubernetes/aks/ (checked 2026-11-12). 

- gcp: Customer cloud account; Customer-operated; control plane: not-assessed. Source: https://signoz.io/docs/install/kubernetes/gcp/ (checked 2026-11-12). 


### Cloud deployment evidence

- SigNoz self-hosting on Amazon EKS (aws): https://signoz.io/docs/install/kubernetes/aws/
  Official self-hosting instructions install SigNoz and its storage components on Amazon EKS; this is not the vendor-hosted SigNoz Cloud service.
  Source type: vendor-documentation; reviewed: 2026-11-12; vendor support: not-assessed.

- SigNoz self-hosting on Azure Kubernetes Service (azure): https://signoz.io/docs/install/kubernetes/aks/
  Official self-hosting instructions install SigNoz and its storage components on Azure Kubernetes Service; this is not the vendor-hosted SigNoz Cloud service.
  Source type: vendor-documentation; reviewed: 2026-11-12; vendor support: not-assessed.

- SigNoz self-hosting on Google Kubernetes Engine (gcp): https://signoz.io/docs/install/kubernetes/gcp/
  Official self-hosting instructions install SigNoz and its storage components on Google Kubernetes Engine; this is not the vendor-hosted SigNoz Cloud service.
  Source type: vendor-documentation; reviewed: 2026-11-12; vendor support: not-assessed.


### Community and maintenance

The active release stream records recent maintenance and multiple named contributors and first-time contributions across releases.

Reviewed 2026-11-10.

- Maintenance and community contributor credits: https://github.com/SigNoz/signoz/releases

- Public upstream project: https://github.com/SigNoz/signoz

### Sources

- Official installation and runtime: https://signoz.io/docs/install/docker/

- Upstream project and capabilities: https://github.com/SigNoz/signoz

- Current upstream license: https://raw.githubusercontent.com/SigNoz/signoz/develop/LICENSE

- SigNoz v0.150.0 breaking changes: https://github.com/SigNoz/signoz/releases/tag/v0.150.0

- SigNoz v0.150.0 alert-rule upgrade guide: https://signoz.io/docs/operate/migration/upgrade-0-150/

- SigNoz JSON log migration capacity guidance: https://signoz.io/guides/json-logs-migration/

### Licensing sources

- https://raw.githubusercontent.com/SigNoz/signoz/develop/LICENSE

### Infrastructure sources

- https://signoz.io/docs/install/docker/

- https://signoz.io/docs/operate/migration/upgrade-0-150/

- https://signoz.io/guides/json-logs-migration/


### Buyer diligence


Research coverage: 5/12 fields (42%); 5 documented, 0 unresolved. Coverage is not a feature score.

Unrecorded fields are not researched, not a statement that the feature is unavailable. Sources checked — unresolved means the cited material did not establish an answer. Hosted-service certifications do not automatically cover customer installations.


- Marketplace delivery: Not researched.

- Cloud commitment eligibility: Not researched.

- Single sign-on: Edition-dependent. SAML and OIDC require Enterprise Self-Hosted. Google Workspace OAuth2 is also documented for Community Edition. Login-time account creation is distinct from automated deprovisioning. Scope: Self-hosted SigNoz edition-specific protocols. Source: https://signoz.io/docs/manage/administrator-guide/sso/overview/ (reviewed 2026-11-14).

- SCIM provisioning: Not researched.

- Compliance attestations: Not researched.

- Security controls: Not researched.

- Air-gapped operation: Not researched.

- Deployment artifact / IaC: Documented. The supported Docker workflow uses Foundry to generate/manage the Compose deployment. The older install.sh and bundled deploy files are deprecated from v0.130.0; do not use them as the current installation artifact. Scope: Upstream self-hosted deployment; not a provider support or production-readiness certification. Source: https://signoz.io/docs/install/docker/ (reviewed 2026-11-14).

- Minimum footprint / sizing: Documented. The supported Foundry/Docker installation requires at least 4 GB allocated to Docker for its local stack. Production ingestion rate, ClickHouse/Keeper topology, retention and replicas can raise capacity substantially; this is an installation baseline, not a 1 TB HA telemetry sizing guarantee. Scope: Current supported Docker installation requirements; application, storage and collector roles require workload sizing. Source: https://signoz.io/docs/install/docker/ (reviewed 2026-11-20).

- License pricing: Documented. The v0.150.0 licence applies MIT terms to the core and explicitly excludes ee/ and cmd/enterprise/, which have separate Enterprise terms. Community source rights do not grant paid SAML/OIDC features or commercial support. Self-hosted licence, ingestion/storage infrastructure and SigNoz Cloud charges are separate. Scope: Published Community/Enterprise source boundary; not a hosted usage-price quote. Source: https://github.com/SigNoz/signoz/blob/v0.150.0/LICENSE (reviewed 2026-11-20).

- Operating cost estimate: Not researched.

- Release snapshot / cadence: Documented. The publisher-designated GitHub release checked was v0.150.0, published 2026-11-13. This is a release snapshot, not a promised cadence, support designation or approval to substitute it into a provider package. Scope: Upstream SigNoz/signoz release record; commercial editions and deployment packages may differ. Source: https://github.com/SigNoz/signoz/releases/tag/v0.150.0 (reviewed 2026-11-14).






