# Maple vs SigNoz

SigNoz and Maple are the closest pair on this site: OpenTelemetry in, ClickHouse underneath, one application for traces, logs and metrics, an MCP server, usage pricing with no seats or hosts. The differences are in what happens after the telemetry lands and in how each one is licensed and run. Below: the rows where they diverge, where SigNoz is ahead, and what the same month costs on each.

## Where Maple and SigNoz differ

Every cell is a sentence, not a checkmark. The gutter says who has the edge on that row; rows where both tools do the same thing are collapsed into one line at the end.

### Where they differ

| Topic | Maple | SigNoz | Edge |
| --- | --- | --- | --- |
| Retention | 30 days on every signal at the flat rate. Longer on Enterprise, and your call when you self-host. | 15 days for logs and traces and one month for metrics by default. Longer retention raises the per-GB rate: $0.40 at 30 days, up to $1.40 at one year. [1] | Maple |
| Pricing model | $39 a month with 100 GB per signal included, then $0.30 per GB. Metrics are metered by volume, not by sample. | $49 a month including $49 of usage, then $0.30 per GB of logs and traces and $0.10 per million metric samples. Enterprise from $4,000 a month. [1] | Maple |
| Error workflow | Exceptions become issues with an owner, a state, a severity and comments. A resolved issue that fires again reopens. | An exceptions list grouped by service, type and message, each linked to its trace. No state, owner or severity on a group. [5] | Maple |
| Frontend and mobile | Browser session replay with the trace behind every click. 5,000 sessions a month included. | Browser traces, logs and Web Vitals over OpenTelemetry. No session replay. | Maple |
| Local development | One binary with an embedded ClickHouse. `maple start` on a laptop, no containers, no account. | The Linux install still needs ClickHouse and Postgres beside it; Docker wants 4 GB and five containers. [3] | Maple |
| Source code | FSL-1.1, converting to Apache 2.0 two years after each release. One license, no enterprise directory. | MIT core, plus an `ee/` directory under a commercial license that holds SAML, OIDC and fine-grained RBAC. [2] | Even |
| AI and agents | A hosted MCP server exposing the product's own queries, scoped to the org in the SQL, with opt-in write tools. | A hosted MCP server with fifty-plus tools, agent skills for Claude, Codex and Cursor, and Noz, an AI teammate that is Cloud-only. [7] | Even |

### Where SigNoz is ahead

| Topic | Maple | SigNoz | Edge |
| --- | --- | --- | --- |
| Self-hosting | The repository, a compose file, your Postgres and ClickHouse, one root password. Single-org, no SSO yet. | Docker, Swarm, Helm and Foundry installs with per-platform guides. Multi-user with roles and Google OAuth in the Community edition. [4] | SigNoz |
| PromQL compatibility | No PromQL. Visual builder and SQL, one grammar across signals. | Query Builder v5, ClickHouse SQL and PromQL in dashboards. Prometheus rules carry over. [8] | SigNoz |
| Cost controls | Sampling guidance and volume alerts. No hard ingest cap. | Ingest Guard: daily caps per signal and per team in Cloud that drop data past the limit. [9] | SigNoz |
| Notification channels | Slack, PagerDuty, Discord, Telegram, email and webhooks. | Nine channel types, including Opsgenie, Microsoft Teams, Incident.io, Rootly and Zenduty. [10] | SigNoz |

**Both have:** Distributed tracing · Log management · Metrics and dashboards · Alerting · Error tracking · Kubernetes monitoring · Public API · MCP server for agents · OpenTelemetry ingest

## The same month, billed twice

A reference workload priced on both at list price. Change the sliders underneath for your own numbers.

**Reference workload:** Log volume 100 GB/mo · Trace volume 100 GB/mo · Metric samples / mo 500 M

| Maple | Amount |
| --- | --- |
| Startup plan — 100 GB per signal included | $39 |
| Team seats — No per-seat fees | Free |
| **Total** | **$39** |

| SigNoz | Amount |
| --- | --- |
| Base fee — $49/mo Teams plan base fee | $49 |
| Logs — 100 GB × $0.30 | $30 |
| Traces — 100 GB × $0.30 | $30 |
| Metrics — 500M samples × $0.10/M | $50 |
| Included usage — $49 of usage included in the base fee | −$49 |
| **Total** | **$110** |

$71 less per month on Maple

List prices checked August 2026. Sources at the foot of the page. Maple pricing based on the Startup plan ($39/mo with 100 GB included per signal — logs, traces, metrics — then $0.30/GB, billed per signal), metered on uncompressed (decoded OTLP) bytes. SigNoz modeled on the Teams plan at its default retention (logs and traces $0.30/GB at 15 days, metrics $0.10 per million samples at 1 month) with the $49/mo base fee, from which $49 of usage is subtracted as included; longer retention costs more (up to $1.40/GB at 1 year) and is not included, which favors SigNoz. Maple bills per GB, so the Maple estimate converts metric samples at roughly 0.1 KB per data point (0.1 GB per million samples).

Interactive calculator: https://maple.dev/compare/signoz#calculator

## Moving from SigNoz

Telemetry moves with one exporter change. Dashboards and alert rules don't cross vendors, so plan those as the real work.

1. **Keep the Collector, add an exporter** Both platforms ingest standard OTLP, so SDKs, auto-instrumentation and semantic conventions carry over unchanged. Add Maple next to the SigNoz exporter and ship to both until the alerts you care about fire from Maple.
2. **Move the dashboards and alerts with one prompt** Dashboards and alert rules don't travel over OTLP, but both MCP servers expose them: SigNoz's reads them, Maple's creates them. Connect an agent to both and ask it to port everything. One prompt is usually enough, PromQL panels included.

```yaml
# otel-collector.yaml — Add Maple as a second exporter, run both, then drop the first.
exporters:
  otlp:
    endpoint: ingest.us.signoz.cloud:443
    headers:
      signoz-ingestion-key: ${env:SIGNOZ_INGESTION_KEY}
  otlphttp/maple:
    endpoint: https://ingest.maple.dev
    headers:
      x-maple-ingest-key: ${env:MAPLE_INGEST_KEY}

service:
  pipelines:
    traces:
      exporters: [otlp, otlphttp/maple]
    logs:
      exporters: [otlp, otlphttp/maple]
    metrics:
      exporters: [otlp, otlphttp/maple]
```

## Common questions

### Is SigNoz open source?

The core is MIT. The `ee/` directory is under the SigNoz Enterprise License, which forbids production use without a paid license, and currently holds SAML and OIDC single sign-on and fine-grained RBAC. Maple is under FSL-1.1, source-available for two years per release and Apache 2.0 after, with no enterprise-only directory.

### How is Maple different from SigNoz?

The bones match: OpenTelemetry in, ClickHouse underneath, one app, usage pricing, an MCP server. Maple keeps going after the error is found, with issues that have an owner and a state, browser session replay, agent sessions for AI workloads, and a single-binary local mode. SigNoz is ahead on self-hosting maturity and PromQL.

### Which is cheaper, SigNoz or Maple?

At small volumes they are within ten dollars of each other: $49 against $39. Above that, Maple's 100 GB per signal included and flat 30-day retention make it cheaper for most workloads, because SigNoz's rate rises with retention. SigNoz's per-sample metric pricing can win if your metrics are many and small. The receipts above run both models on the same month.

### Can I self-host both?

Yes. SigNoz has the more polished path today: Docker Compose, Helm, Foundry and platform guides, multi-user with roles in the Community edition. Maple self-hosts from the repository with a compose file, your ClickHouse and a root password, single-org, and runs as one binary with an embedded ClickHouse for local development.

### Does SigNoz have session replay?

No, and their community has said it isn't planned. SigNoz ingests browser traces, logs and Web Vitals over OpenTelemetry. Maple records and replays browser sessions with the trace behind each event, masked in the browser before anything leaves the page.

## Where the SigNoz claims come from

Vendor facts on this page link to the vendor's own pages and carry the month they were last checked. If one is stale, tell us.

1. [SigNoz pricing](https://signoz.io/pricing/) — checked September 2026
2. [SigNoz on GitHub (MIT core, ee/ under the SigNoz Enterprise License)](https://github.com/SigNoz/signoz) — checked September 2026
3. [SigNoz: Docker install](https://signoz.io/docs/install/docker/) — checked September 2026
4. [SigNoz: single sign-on by edition](https://signoz.io/docs/manage/administrator-guide/sso/overview/) — checked September 2026
5. [SigNoz: Exceptions](https://signoz.io/docs/userguide/exceptions/) — checked September 2026
6. [SigNoz: retention periods](https://signoz.io/docs/userguide/retention-period/) — checked September 2026
7. [SigNoz: Noz, MCP server and agent skills](https://signoz.io/docs/ai/overview/) — checked September 2026
8. [SigNoz: querying (Query Builder, ClickHouse SQL, PromQL)](https://signoz.io/docs/querying/overview/) — checked September 2026
9. [SigNoz: ingestion limits (Ingest Guard)](https://signoz.io/docs/cost-control/ingestion-limits/) — checked September 2026
10. [SigNoz: notification channels](https://signoz.io/docs/setup-alerts-notification/) — checked September 2026

## Other comparisons

- [Maple vs Datadog](https://maple.dev/compare/datadog.md)
- [Maple vs Grafana](https://maple.dev/compare/grafana.md)
- [Maple vs New Relic](https://maple.dev/compare/new-relic.md)
- [Maple vs Dash0](https://maple.dev/compare/dash0.md)