SigNoz Self-Hosted

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

6 sources checked by an editor on · Product website ↗

Deployment terms: BYOC · control plane · data plane · private offer

· Open requirements shortlist · Estimate operating costs

Compare this listing with another →

What lands where

  1. Supplied by

    Vendor or project

    Use the supported Foundry workflow to generate and run the Docker Compose stack; the older bundled install script/deploy files are deprecated.

  2. Operated by

    Your team

    Customer manages collectors, storage capacity, retention, authentication, backups, alert API and operator migrations, and platform upgrades.

Deployment boundaries by provider

Application operations and account ownership are separate from infrastructure operations. Confirm external services, telemetry, support access and backup destinations for the chosen path.

Install methodUse the supported Foundry workflow to generate and run the Docker Compose stack; the older bundled install script/deploy files are deprecated.
InfrastructureServers / containers
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.
Licensing modelOpen Source / Open Core
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.
LicenseMIT Expat for core code; ee/ enterprise code has its own separate license.

Buyer diligence

Answers apply to the reviewed edition and deployment. Expand a row for qualifications and sources.

How to read these facts

Not researched means no field-specific review is recorded. Not confirmed means sources were checked but did not establish an answer. Availability, eligibility and edition-dependent findings retain the scope given in their evidence. A vendor’s hosted-service certification does not automatically cover your deployment. Evidence coverage is not a feature score.

5 of 12 fields researched (42%) · 5 documented · 0 unresolved. Evidence coverage is not a feature score.

Single sign-on
Edition-dependentEvidence and scope for Single sign-on

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.

Self-hosted SigNoz edition-specific protocols · Source ↗ · Reviewed 2026-11-14

Edition-dependent · Editor reviewed.

Deployment artifact / IaC
DocumentedEvidence and scope for Deployment artifact / IaC

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.

Upstream self-hosted deployment; not a provider support or production-readiness certification · Source ↗ · Reviewed 2026-11-14

Documented · Editor reviewed.

Minimum footprint / sizing
DocumentedEvidence and scope for Minimum footprint / sizing

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.

Current supported Docker installation requirements; application, storage and collector roles require workload sizing · Source ↗ · Reviewed 2026-11-20

Documented · Editor reviewed.

License pricing
DocumentedEvidence and scope for License pricing

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.

Published Community/Enterprise source boundary; not a hosted usage-price quote · Source ↗ · Reviewed 2026-11-20

Documented · Editor reviewed.

Release snapshot / cadence
DocumentedEvidence and scope for Release snapshot / cadence

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.

Upstream SigNoz/signoz release record; commercial editions and deployment packages may differ · Source ↗ · Reviewed 2026-11-14

Documented · Editor reviewed.

Show all fields (7 not researched)
Marketplace delivery
Not researched Supply a public source.
Cloud commitment eligibility
Not researched Supply a public source.
SCIM provisioning
Not researched Supply a public source.
Compliance attestations
Not researched Supply a public source.
Security controls
Not researched Supply a public source.
Air-gapped operation
Not researched Supply a public source.
Operating cost estimate
Not researched Supply a public source.

Scope & considerations

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.

Community & maintenance

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

Category fit

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

Compare within Observability

  • AVEVA PI System (BYOL)Commercial industrial data collection, historian and visualization system with an AWS architecture.
    • AWS
    Customer-operated · Commercial Only
  • Cloud Carbon FootprintOpen-source cloud-usage, energy and carbon-estimation application.
    • Google Cloud
    Customer-operated · Open Source / Open Core
  • Coroot Community EditionSelf-hosted application observability with service maps, logs, metrics, traces and continuous profiling.
    • AWS
    • Azure
    • Google Cloud
    • Oracle Cloud
    Customer-operated · Open Source / Open Core
  • Datadog BYOC LogsDatadog log processing, indexing and storage in the customer's cloud, with search through Datadog Log Explorer.
    • AWS
    • Azure
    • Google Cloud
    Customer-operated · vendor control plane · Commercial Only
  • Elastic Cloud EnterpriseCommercial self-managed orchestration platform for Elastic Stack deployments across customer cloud hosts.
    • AWS
    • Azure
    • Google Cloud
    Customer-operated · Commercial Only
  • Elastic Cloud on KubernetesElastic's Kubernetes operator for deploying and operating Elasticsearch, Kibana and related Elastic Stack resources in customer clusters.
    • AWS
    • Azure
    • Google Cloud
    Customer-operated · Source Available
  • Grafana OSS Self-HostedSelf-hosted dashboards, visualization and alerting for operational data.
    • AWS
    Customer-operated · Open Source / Open Core
  • Langfuse Self-HostedSelf-hosted LLM observability, evaluations and prompt-management platform.
    • AWS
    • Azure
    • Google Cloud
    • Railway
    • Render
    Customer-operated · Open Source / Open Core

Showing 8 of 20 other listings in Observability. These products address related workflows; read their category-fit notes before comparing scope. See all of Observability →

Installation outline

  1. Choose the documented deployment option and a dedicated cloud environment. Follow the launch methodology.
  2. Review the vendor's installation documentation, required permissions and outbound data flows.
  3. Deploy to a non-production environment; configure identity, networking and monitoring.
  4. Test backup recovery and upgrades before promoting to production.

Watch this listing with RSS

Evidence trail

Every claim on this page traces to the sources below. They document the deployment option; they do not constitute a security certification.

  1. Deployment sourcesChecked
  2. Cloud deployment evidenceChecked

    The linked sources describe each deployment path, edition and support scope. Community templates and partner statements are identified in the notes.

    • SigNoz self-hosting on Amazon EKS ↗ · AWS

      Vendor / upstream documentation · Reviewed 2026-11-12. Vendor support commitment: not assessed; confirm the selected release and contract.

      Official self-hosting instructions install SigNoz and its storage components on Amazon EKS; this is not the vendor-hosted SigNoz Cloud service.

    • SigNoz self-hosting on Azure Kubernetes Service ↗ · Azure

      Vendor / upstream documentation · Reviewed 2026-11-12. Vendor support commitment: not assessed; confirm the selected release and contract.

      Official self-hosting instructions install SigNoz and its storage components on Azure Kubernetes Service; this is not the vendor-hosted SigNoz Cloud service.

    • SigNoz self-hosting on Google Kubernetes Engine ↗ · Google Cloud

      Vendor / upstream documentation · Reviewed 2026-11-12. Vendor support commitment: not assessed; confirm the selected release and contract.

      Official self-hosting instructions install SigNoz and its storage components on Google Kubernetes Engine; this is not the vendor-hosted SigNoz Cloud service.

  3. Infrastructure evidenceChecked
  4. Licensing evidenceChecked
  5. Community & maintenance evidenceChecked

Suggest a correction · Back to directory