Compare
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.
Differences
The marker beside each row shows which tool is ahead on it. Rows where both do the same thing are grouped into one line at the end.
| Topic | Maple | SigNoz | Edge |
|---|---|---|---|
| Where they differ | |||
| 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 and per-sample rates; the calculator on SigNoz's pricing page quotes them. 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 of memory. 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, with write tools for alert rules, dashboards and issues. | 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 |
| Cost controls | Overage caps per signal and usage alerts in the billing settings. At a cap the ingest gateway rejects that signal until the billing cycle resets. | Ingest Guard: daily caps per signal and per team in Cloud that drop data past the limit. 9 | Even |
| Where SigNoz is ahead | |||
| 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 |
| Notification channels | Slack, PagerDuty, Discord, Telegram, email and webhooks. | Nine channel types, including Opsgenie, Microsoft Teams, Incident.io, Rootly and Zenduty. 10 | SigNoz |
Price
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
$39 per month
| Startup plan 100 GB per signal included | $39 |
|---|---|
| Team seats No per-seat fees | Free |
| Total | $39 |
$110 per month
| 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 · $852 a year
Adjust for your usage
List prices checked September 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 is modeled on the Teams plan at default retention: logs and traces $0.30/GB at 15 days, metrics $0.10 per million samples at one month, and the $49 base fee with $49 of usage included. Longer retention raises both rates and is not modeled, which favors SigNoz. The Maple estimate converts metric samples at 0.1 KB per data point.
Migration
Telemetry moves with one exporter change. Dashboards and alert rules don't cross vendors, so plan those as the real work.
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.
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.
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]Sources
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.
Compare
Open-source, no per-host billing
→ 02One platform, nothing to assemble
→ 03OTel-native, no per-user fees
→ 04Open source and self-hostable
→ 05Issues, session replay, self-hosting
→ 06Source code, self-hosting, local mode
→ 07Session replay, self-hosting, price per GB
→
Point one exporter at Maple and run both for a week. The free trial needs a card, with no charge until it ends.