Obzly
Compare / SigNoz

Obzly vs SigNoz

SigNoz is an OpenTelemetry-native observability tool that stores every signal in ClickHouse. Its Community edition is MIT-licensed, and SAML, OIDC and fine-grained roles come with Enterprise or SigNoz Cloud. Obzly covers the same three signals with Parquet in object storage, so there is no ClickHouse to run.

Checked 27 October 2026 against SigNoz's own docs and pricing. Sources

Which to choose

Choose Obzly if

  • you'd rather not run ClickHouse and ZooKeeper: Obzly keeps data as Parquet in object storage;
  • you send Prometheus remote write, or want a PromQL API that Grafana can query;
  • you want synthetic checks for HTTP, TLS, TCP, DNS and ICMP from probes you host;
  • you want OIDC with any provider, SCIM and an audit log without a paid license;
  • you need one login across regions, with each region's data staying put.

Choose SigNoz if

  • you already run ClickHouse, or want it as your store, with replicated or sharded clusters;
  • you want ready-made APM and an exceptions view: latency, error rate, Apdex, trace funnels and stack traces;
  • you need frontend or mobile monitoring (iOS, Android, Flutter), which Obzly doesn't have;
  • you want native alert channels such as Opsgenie, incident.io and Rootly, plus alerts as code and a Terraform provider;
  • you want a managed service with BYOC, SOC 2 Type II and HIPAA, and data centres in the US, EU and India.

What you run

To self-host SigNoz you run SigNoz, ClickHouse, ZooKeeper, Collector, Postgres, with clickhouse disks. Obzly is one image in a few roles, plus Postgres, Valkey and object storage.SigNoz, self-hostedSigNozUI, API server, ruler, Alertmanager and OpAMP in one binaryClickHouselogstracesmetricsreplicasZooKeeperor Keeperfor clustersCollectorOTLP 4317OTLP 4318JaegerZipkinPostgresmetadataor SQLiteClickHouse disks · optional S3/GCS cold tierObzlyone imageSERVICE_MODE = all, or one role per deployment:apiworkerbrokerquerierlogs, metrics and traces in one storeplus control-plane for many SitesPostgresValkeyObject storage
SigNoz stores every signal in ClickHouse on local disks, and the Helm chart can move older data to S3 or GCS. A distributed ClickHouse cluster needs ZooKeeper or ClickHouse Keeper. Obzly writes Parquet to object storage, so it needs neither.

Feature by feature

CapabilityObzlyCommunity (self-hosted)Enterprise / SigNoz CloudSource
LicenseApache 2.0, every featureMIT (Expat)Proprietary ee/ code, licensed per user seatLicenseee/ license
What you runOne image in up to five roles, Postgres, ValkeyClickHouse, ZooKeeper or Keeper, Postgres, SigNoz, collectorSame with support, or BYOC, or nothing on CloudArchitectureDistributed ClickHouseDocker install
StorageZSTD Parquet on S3, GCS, Azure Blob or MinIOClickHouse on disks; optional S3/GCS cold tierSameArchitectureHelm values
OTLP inLogs, metrics and traces, gRPC and HTTPLogs, metrics and traces, gRPC and HTTPSame; Cloud takes both on port 443Docker installCloud ingestion
Query languagesSearch bar and SQL for logs, PromQL, Jaeger API for tracesQuery Builder; ClickHouse SQL and PromQL in dashboards onlySameQuery BuilderClickHouse queriesPromQL
PrometheusRemote-write ingest and a PromQL APIPromQL in dashboards; no remote write, Collector scrapesSameRemote writePrometheus metrics
DashboardsOwn dashboards; imports Grafana layouts, not SigNozOwn dashboards; Grafana ones are rebuilt by handSameFrom GrafanaImport
AlertingWebhook, Slack, PagerDuty, emailSlack, PagerDuty, Opsgenie, Teams, email and moreSame, plus anomaly-detection alertsChannelsPricing
Synthetic checksHTTP, TLS, TCP, DNS, ICMP from your probes; no browserNot supported; Collector httpcheck for HTTP and TLS expiryNot supportedFAQ
Infrastructure inventoryClusters to containers, plus AWS and Azure resourcesHosts and Kubernetes objects; AWS, Azure, GCP servicesAdds one-click AWS integrationsInfrastructurePricing
RUM and profilingNeitherFrontend and mobile monitoring, no replay; no profilingSameFrontendSession replayProfiling
SSOOIDC with any provider; no SAMLGoogle Workspace onlySAML 2.0 and OIDCSSOPricing
SCIMIncludedNot supportedNot supportedSSO
RBAC and audit logPer-project roles, teams, audit log with CSV exportAdmin, Editor and Viewer roles; no audit logFine-grained RBAC in beta; audit log coming soonRolesPricing
MCP serverBuilt in at /mcp, read-onlyOfficial server you run yourselfHosted server on SigNoz CloudMCP server
Many regionsControl plane in front of many SitesNot supportedNot supportedMulti-cluster
PriceFree; you run the infrastructureFree; you run the infrastructureTeams from $49/month incl. usage; Enterprise from $4,000/monthPricing

Moving from SigNoz

  1. Send to both. Add an OTLP exporter for Obzly to the Collector that feeds SigNoz. Collector guide
  2. Bring Prometheus metrics. Keep scraping with the Collector, or send Prometheus remote write to Obzly directly. PromQL and Grafana
  3. Rebuild the dashboards you use. Obzly doesn't import SigNoz dashboards. PromQL panels carry over once metric and label names are checked; Query Builder and ClickHouse SQL panels need rewriting.
  4. Move alert rules. Recreate them as PromQL, log search or trace latency rules, and connect Slack, PagerDuty, email or a webhook. Alerts
  5. Replace httpcheck. Move HTTP and TLS checks from the Collector to Obzly synthetics, which run from your probe groups and need a control plane. Synthetics
  6. Switch off ClickHouse once Obzly has your full retention.

Sources

Every SigNoz fact on this page comes from its vendor's own pages, read on 27 October 2026. Plan names and prices change; check the linked page before you decide.

Spotted something out of date? Open an issue.