SigNoz and HyperDX are both open source observability platforms built on ClickHouse for columnar telemetry storage and OpenTelemetry for instrumentation. Both position themselves as cost-effective alternatives to Datadog and New Relic. But they diverge sharply on architecture philosophy, deployment complexity, session replay support, and pricing transparency.
According to the CNCF Annual Survey 2024, 38% of organizations now use OpenTelemetry in production, and open source observability adoption continues to accelerate as teams seek vendor-neutral instrumentation and predictable costs. Both SigNoz and HyperDX benefit from this shift, but their positioning differs: SigNoz focuses on APM and unified logs-metrics-traces, while HyperDX emphasizes production debugging with session replay and error tracking alongside telemetry.
This guide compares both platforms on deployment model, feature depth, query experience, community maturity, pricing transparency, and ease of migration. CubeAPM is included as a third option for teams evaluating managed on-premises observability with OpenTelemetry compatibility.
Quick Comparison: SigNoz vs HyperDX vs CubeAPM
| Feature | SigNoz | HyperDX | CubeAPM |
|---|---|---|---|
| License | MIT | MIT | Proprietary (managed on-prem) |
| Best for | OTel-native APM and unified telemetry | Production debugging with session replay | Self-hosted managed observability |
| Deployment | Self-hosted or SigNoz Cloud | Self-hosted or managed | Managed on-prem (vendor-operated) |
| Storage | ClickHouse | ClickHouse | On-prem |
| Query language | ClickQL (SQL-like) | SQL + Lucene-style | SQL |
| Session replay | No | Yes | Yes (RUM) |
| OTel support | Native from day one | Native | Native |
| Pricing (cloud) | $0.30/GB beyond free tier | Custom pricing | $0.15/GB flat |
| GitHub stars | 27,521 (as of April 2026) | 9,633 (as of April 2026) | N/A (proprietary) |
| Community maturity | 5 years, 2,264 forks | 3 years, smaller contributor base | N/A |
| Retention | 15 days default self-hosted | Configurable | Unlimited |
Pricing based on publicly available information as of April 2026. Enterprise discounts and custom contracts are not reflected here.
SigNoz Overview
SigNoz is an open source observability platform built natively on OpenTelemetry from its first commit. It provides APM, distributed tracing, logs, and infrastructure monitoring in one unified interface. The platform uses ClickHouse as its storage backend and ships with a single Helm chart for Kubernetes deployment or Docker Compose for local setups.
SigNoz targets teams that want a Datadog-like experience without SaaS vendor lock-in. It offers both a self-hosted version under the MIT license and SigNoz Cloud, a managed option with consumption-based pricing starting at $0.30/GB beyond a 50 GB monthly free tier.
Pros:
- Native OpenTelemetry support with no proprietary agent
- Unified logs, metrics, and traces in one platform
- Strong community adoption: 27,521 GitHub stars and active Slack channels
- Self-hosted option eliminates data egress fees
- Clean UI modeled after commercial APM tools
Cons:
- Self-hosted deployment requires ClickHouse expertise at scale
- Default retention is 15 days for self-hosted setups without additional configuration
- No session replay or frontend error tracking built in
- Query performance degrades with default sampling disabled
Pricing:
- Self-hosted: free under MIT license (infrastructure costs apply)
- SigNoz Cloud: $0.30/GB beyond 50 GB/month free tier
- Enterprise: custom pricing with dedicated support and longer retention
Verify current rates at [SigNoz pricing page](https://signoz.io/pricing/).
HyperDX Overview
HyperDX (formerly ClickStack) is an open source observability platform focused on production debugging. It combines traditional telemetry (logs, traces, metrics) with session replay and frontend error tracking to help teams reproduce bugs and understand user context around backend failures.
HyperDX uses ClickHouse for storage and OpenTelemetry for instrumentation. Its UI emphasizes Lucene-style log search with SQL fallback for power users. The platform is less mature than SigNoz in terms of community size but offers unique session replay capabilities that SigNoz lacks entirely.
Pros:
- Session replay integrated with backend telemetry
- Strong frontend debugging with error tracking
- ClickHouse-native SQL query support
- Self-hosted deployment keeps telemetry data internal
- Apache 2.0 license
Cons:
- Smaller community: 9,633 GitHub stars vs SigNoz’s 27,521
- UI relies heavily on Lucene-style search, which may not fit all workflows
- Less documentation and fewer integrations compared to SigNoz
- Deployment complexity similar to SigNoz: requires ClickHouse management
Pricing:
- Self-hosted: free under Apache 2.0 license (infrastructure costs apply)
- Managed HyperDX: custom pricing, contact required
Verify current rates at [HyperDX contact page](https://hyperdx.io/contact).
Feature Comparison: SigNoz vs HyperDX
Distributed Tracing
SigNoz: Built-in distributed tracing with OpenTelemetry SDKs. Traces are stored in ClickHouse with default 15-day retention. Users can drill from service graphs into individual spans and correlate traces with logs using trace IDs.
HyperDX: Distributed tracing supported via OpenTelemetry. Traces are queryable via SQL. HyperDX’s unique feature is linking traces to session replay, allowing teams to see what the user was doing when a backend trace showed high latency.
Winner: HyperDX edges ahead for teams that need session context. SigNoz wins for teams focused purely on backend APM without frontend replay needs.
Logs
SigNoz: Unified log ingestion via OpenTelemetry Collector, Fluentd, or Logstash. Logs are indexed in ClickHouse and searchable via ClickQL. Correlation with traces is automatic when trace IDs are present in log fields.
HyperDX: Logs are ingested via OpenTelemetry or Fluentd. Search is Lucene-style by default with SQL fallback. HyperDX emphasizes fast free-text search over structured queries.
Winner: Tie. SigNoz offers better SQL-first querying. HyperDX offers faster keyword search for teams used to ELK-style workflows.
Metrics
SigNoz: Prometheus-compatible metrics via OpenTelemetry or Prometheus remote write. Metrics are stored in ClickHouse and queryable via ClickQL. Dashboards support PromQL-like queries.
HyperDX: Metrics ingested via OpenTelemetry. SQL-based querying for metrics correlation with logs and traces.
Winner: SigNoz. More mature Prometheus integration and better dashboard templating.
Session Replay and Error Tracking
SigNoz: Not supported. SigNoz focuses on backend observability and does not include session replay or frontend error tracking.
HyperDX: Session replay and error tracking are core features. Teams can replay user sessions frame-by-frame and correlate them with backend traces and logs to understand full context around failures.
Winner: HyperDX. This is its standout differentiator.
Infrastructure Monitoring
SigNoz: Supports infrastructure metrics via OpenTelemetry Collector or Prometheus. Dashboards for CPU, memory, disk, and network are included.
HyperDX: Infrastructure metrics supported via OpenTelemetry. Less emphasis on infra-specific dashboards compared to SigNoz.
Winner: SigNoz. Better out-of-the-box infra monitoring dashboards.
Alerting
SigNoz: Alert rules can be created on metrics, logs, or traces. Alerts route to Slack, PagerDuty, email, or webhooks. Anomaly detection is not built in.
HyperDX: Alerts supported via SQL queries on logs, metrics, and traces. Routing to standard channels. No anomaly detection.
Winner: Tie. Both offer functional alerting without advanced AI-based anomaly detection.
Deployment Model Comparison
Self-Hosted Deployment
SigNoz: Single Helm chart for Kubernetes or Docker Compose for local setups. Requires ClickHouse, Kafka (optional for scale), and OpenTelemetry Collector. Default setup uses 1 ClickHouse instance with 800 MB RAM even if ZooKeeper is disabled. A Reddit user documented the challenge of tuning resource consumption for smaller deployments.
HyperDX: Helm chart or Docker Compose. Requires ClickHouse and OpenTelemetry Collector. Similar resource requirements to SigNoz but less documented in community discussions.
Winner: Tie. Both require ClickHouse expertise and similar resource footprints.
Managed Options
SigNoz Cloud: Consumption-based pricing starting at $0.30/GB beyond a 50 GB free tier. SigNoz manages infrastructure, upgrades, and scaling.
HyperDX Managed: Custom pricing. Contact required for details.
Winner: SigNoz. Transparent pricing and established managed offering.
Pricing Comparison: SigNoz vs HyperDX vs CubeAPM
Self-Hosted Cost Estimate
Assumptions: 30 TB/month ingestion, 100 hosts, 30-day retention.
| Component | SigNoz | HyperDX | CubeAPM |
|---|---|---|---|
| ClickHouse storage | ~$600/month (S3) | ~$600/month (S3) | Included in $0.15/GB |
| Compute (Kubernetes) | ~$1,200/month | ~$1,200/month | Managed by vendor |
| Data ingestion | Free (OSS) | Free (OSS) | $4,500/month |
| Ops burden | High (DIY) | High (DIY) | Managed by CubeAPM |
| Total | ~$1,800/month + ops time | ~$1,800/month + ops time | $4,500/month managed |
This estimate models a production-ready setup with high availability. A smaller or simpler deployment may cost significantly less.
Managed Cloud Cost Estimate
Assumptions: 30 TB/month ingestion.
| Platform | Cost |
|---|---|
| SigNoz Cloud | $8,850/month ($0.30/GB × 29,500 GB beyond free tier) |
| HyperDX Managed | Custom pricing (contact required) |
| CubeAPM | $4,500/month ($0.15/GB × 30,000 GB) |
Pricing based on publicly available information as of April 2026. Enterprise discounts and negotiated rates are not reflected here.
Query Experience: ClickQL vs Lucene vs SQL
SigNoz: Uses ClickQL, a SQL-like language for querying logs, traces, and metrics. Teams familiar with SQL can query telemetry without learning PromQL or LogQL. Example:
SELECT service_name, COUNT(*) as errors
FROM traces
WHERE status_code = 'ERROR'
GROUP BY service_nameHyperDX: Default UI is Lucene-style search (similar to Elastic). SQL fallback is available for power users. Example Lucene query:
service:checkout AND error:trueCubeAPM: SQL-first querying across all telemetry types. No proprietary query language.
Winner: Tie. SigNoz and CubeAPM suit teams that prefer SQL. HyperDX suits teams used to Elastic-style keyword search.
Community Maturity and Ecosystem
SigNoz:
- 27,521 GitHub stars, 2,264 forks
- Active Slack community with daily activity
- 5 years of development history
- Regular release cadence
- Strong documentation and tutorials
HyperDX:
- 9,633 GitHub stars, smaller contributor base
- 3 years of development history
- Less documentation compared to SigNoz
- Smaller community but responsive maintainers
Winner: SigNoz. Larger community, more contributors, and more production deployments documented publicly.
Who Should Choose SigNoz
SigNoz is the better choice for teams that:
- Want unified APM, logs, and metrics in one open source platform
- Prefer SQL-based querying over Lucene-style search
- Need mature community support and extensive documentation
- Plan to self-host and have ClickHouse expertise in-house
- Do not require session replay or frontend error tracking
- Want a managed cloud option with transparent per-GB pricing
Who Should Choose HyperDX
HyperDX is the better choice for teams that:
- Need session replay integrated with backend telemetry
- Focus on production debugging and frontend error tracking
- Prefer Lucene-style log search over SQL
- Want ClickHouse-native observability with less APM overhead
- Are comfortable with a smaller, less mature community
- Can manage ClickHouse infrastructure themselves
Who Should Choose CubeAPM
CubeAPM fits teams that:
- Want managed on-premises deployment without DIY ops burden
- Need full data residency and compliance inside their own VPC
- Prefer predictable $0.15/GB flat pricing with unlimited retention
- Want session replay (RUM), APM, logs, and infra in one platform
- Need vendor-managed upgrades and support without SaaS data egress
Migration: Moving from SigNoz or HyperDX to Another Platform
Migrating from SigNoz
- Export historical telemetry from ClickHouse via SQL queries or ClickHouse backup tools
- Switch OpenTelemetry Collector endpoints to new platform
- Reconfigure dashboards and alerts in the new platform
- Validate trace and log correlation before decommissioning SigNoz
- Timeline: 1–2 weeks for production migration
Migrating from HyperDX
- Export telemetry data from ClickHouse
- Reconfigure OpenTelemetry SDKs to send to new backend
- Recreate session replay configurations if the new platform supports RUM
- Rebuild Lucene-style queries as SQL or the new platform’s query language
- Timeline: 1–2 weeks for production migration
Migrating to CubeAPM
CubeAPM supports OpenTelemetry natively, making migration from SigNoz or HyperDX straightforward. Teams can run both platforms in parallel during migration and switch endpoints incrementally.
Comparing SigNoz, HyperDX, and CubeAPM Together
| Feature | SigNoz | HyperDX | CubeAPM |
|---|---|---|---|
| Deployment model | Self-hosted or cloud | Self-hosted or managed | Managed on-prem |
| Session replay | No | Yes | Yes (RUM) |
| Query language | ClickQL (SQL-like) | Lucene + SQL | SQL |
| Community maturity | 5 years, 27k stars | 3 years, 9k stars | N/A (proprietary) |
| Pricing (cloud) | $0.30/GB | Custom | $0.15/GB |
| Ops burden (self-hosted) | High (ClickHouse management) | High (ClickHouse management) | None (vendor-managed) |
| Best for | OTel-native APM | Production debugging | Managed on-prem observability |
Verdict: SigNoz vs HyperDX
Choose SigNoz if:
- You want a mature open source APM platform with strong community support
- You need unified logs, metrics, and traces with SQL-based querying
- You plan to self-host and have ClickHouse expertise or want a managed cloud option
- Session replay is not a requirement
Choose HyperDX if:
- You need session replay and frontend error tracking alongside backend telemetry
- You prefer Lucene-style log search over SQL
- You are willing to work with a smaller, less mature community
- Production debugging is your primary use case
Choose CubeAPM if:
- You want managed on-premises deployment without DIY ClickHouse operations
- You need full data residency and predictable $0.15/GB pricing
- You want session replay, APM, logs, and infra in one vendor-managed platform
Disclaimer: The information in this article reflects the latest details available at the time of publication and may change as technologies and products evolve. Features, pricing, and plan limits can change over time. Always verify the latest information directly with the vendor before making purchasing or deployment decisions.
Frequently Asked Questions
What is the main difference between SigNoz and HyperDX?
SigNoz focuses on unified APM with logs, metrics, and traces using SQL-based querying. HyperDX emphasizes production debugging with session replay and error tracking alongside telemetry. Both use ClickHouse and OpenTelemetry but serve different primary use cases.
Which platform has better community support?
SigNoz has stronger community support with 27,521 GitHub stars, 2,264 forks, and 5 years of development history. HyperDX has 9,633 stars and a smaller but responsive community. SigNoz offers more documentation and integrations.
Can I self-host both SigNoz and HyperDX?
Yes. Both platforms are open source and support self-hosted deployment via Kubernetes Helm charts or Docker Compose. Both require ClickHouse expertise to manage at scale. Infrastructure costs and operational burden are similar for both.
Does HyperDX support distributed tracing like SigNoz?
Yes. HyperDX supports distributed tracing via OpenTelemetry. Its unique feature is linking traces to session replay so teams can see user context around backend failures. SigNoz offers distributed tracing without session replay integration.
How does CubeAPM compare to SigNoz and HyperDX on pricing?
CubeAPM charges $0.15/GB with unlimited retention and vendor-managed infrastructure. SigNoz Cloud charges $0.30/GB beyond a free tier. HyperDX offers custom pricing. Self-hosted SigNoz and HyperDX are free but require ClickHouse infrastructure costs and operations.
Which platform is easier to deploy?
SigNoz and HyperDX have similar deployment complexity requiring ClickHouse and Kubernetes expertise. CubeAPM is managed by the vendor and deploys inside your VPC without requiring you to manage ClickHouse, reducing operational burden significantly.
Can I migrate from SigNoz to HyperDX or vice versa?
Yes. Both use OpenTelemetry for instrumentation so switching involves reconfiguring OpenTelemetry Collector endpoints and exporting historical data from ClickHouse. Dashboards and alerts must be recreated. Migration typically takes one to two weeks for production workloads.