feat(landing): Maple vs SigNoz comparison page

apps/landing/messages/en.json

@@ -27,6 +27,7 @@
 	"nav_vs_grafana": "Maple vs Grafana",
 	"nav_vs_new_relic": "Maple vs New Relic",
 	"nav_vs_dash0": "Maple vs Dash0",
+	"nav_vs_signoz": "Maple vs SigNoz",
 	"nav_nextjs": "Next.js",
 	"nav_python": "Python",
 	"nav_nodejs": "Node.js",
@@ -51,6 +52,7 @@
 	"nav_desc_vs_grafana": "One platform, nothing to assemble",
 	"nav_desc_vs_new_relic": "OTel-native, predictable pricing",
 	"nav_desc_vs_dash0": "Open source and self-hostable",
+	"nav_desc_vs_signoz": "Issues, session replay, one local binary",
 	"nav_product_footer": "Everything in one platform",
 	"nav_product_footer_cta": "Explore all features \u2192",
 
@@ -164,6 +166,7 @@
 	"bill_link_vs_gf": "Maple vs Grafana Cloud",
 	"bill_link_vs_nr": "Maple vs New Relic",
 	"bill_link_vs_dash0": "Maple vs Dash0",
+	"bill_link_vs_signoz": "Maple vs SigNoz",
 
 	"start_endpoint_label": "Endpoint",
 
@@ -337,6 +340,7 @@
 	"footer_vs_grafana": "vs Grafana",
 	"footer_vs_new_relic": "vs New Relic",
 	"footer_vs_dash0": "vs Dash0",
+	"footer_vs_signoz": "vs SigNoz",
 	"footer_integrations": "Integrations",
 	"footer_community": "Community",
 	"footer_github": "GitHub",
@@ -1043,8 +1047,8 @@
 	"stack_chip_any_mcp": "Any MCP client",
 
 	"cmp_eyebrow": "Compare",
-	"cmp_hub_seo_title": "Maple vs Datadog, Grafana, New Relic and Dash0 — Observability Compared",
-	"cmp_hub_seo_desc": "Side-by-side comparisons of Maple with Datadog, Grafana Cloud, New Relic and Dash0: where each differs, where each is ahead, and what a month costs at list price.",
+	"cmp_hub_seo_title": "Maple vs Datadog, Grafana, New Relic, Dash0 and SigNoz — Observability Compared",
+	"cmp_hub_seo_desc": "Side-by-side comparisons of Maple with Datadog, Grafana Cloud, New Relic, Dash0 and SigNoz: where each differs, where each is ahead, and what a month costs at list price.",
 	"cmp_hub_title": "Maple, compared.",
 	"cmp_hub_lede": "One page per vendor. Each lists where the two differ and where the other tool is ahead, and prices the same month on both at list price. Every vendor claim links to its source and carries the date it was checked.",
 	"cmp_hub_matrix_eyebrow": "At a glance",
@@ -1124,6 +1128,10 @@
 	"cmp_topic_security": "Application security",
 	"cmp_topic_k8s_tooling": "Kubernetes tooling",
 	"cmp_topic_compliance": "Compliance attestations",
+	"cmp_topic_errors": "Error workflow",
+	"cmp_topic_local": "Local development",
+	"cmp_topic_cost_controls": "Cost controls",
+	"cmp_topic_channels": "Notification channels",
 	"cmp_dd_seo_title": "Maple vs Datadog — an open-source Datadog alternative, compared honestly",
 	"cmp_dd_seo_desc": "Maple vs Datadog for observability: where they differ, where Datadog is ahead, and what one month costs on each at list price. Open source, OpenTelemetry-native, no per-host fees.",
 	"cmp_dd_hero_title": "Maple vs Datadog",
@@ -1291,5 +1299,45 @@
 	"cmp_d0_faq_4_q": "How does the pricing compare?",
 	"cmp_d0_faq_4_a": "Both are usage-based with no per-seat fee. Dash0 bills per data point; Maple bills per GB of decoded OTLP. Which is cheaper depends on how large your spans and log records are. The receipts above use a one-kilobyte-per-item conversion; the calculator lets you change it.",
 	"cmp_d0_faq_5_q": "Does Dash0 have anything Maple doesn't?",
-	"cmp_d0_faq_5_a": "PromQL for metrics, Perses dashboards-as-code, and a vendor-maintained Kubernetes operator and OpenTelemetry distribution. Those rows are marked above."
+	"cmp_d0_faq_5_a": "PromQL for metrics, Perses dashboards-as-code, and a vendor-maintained Kubernetes operator and OpenTelemetry distribution. Those rows are marked above.",
+	"cmp_sn_seo_title": "Maple vs SigNoz — two OpenTelemetry-native, ClickHouse-backed platforms compared",
+	"cmp_sn_seo_desc": "Maple vs SigNoz: both OpenTelemetry-native, ClickHouse-backed, one app for traces, logs and metrics. Where they differ (license, self-hosting, the error workflow, session replay, retention pricing), where SigNoz is ahead, and what one month costs on each.",
+	"cmp_sn_hero_title": "Maple vs SigNoz",
+	"cmp_sn_hero_lede": "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.",
+	"cmp_sn_retention_maple": "30 days on every signal at the flat rate. Longer on Enterprise, and your call when you self-host.",
+	"cmp_sn_retention_them": "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.",
+	"cmp_sn_pricing_maple": "$39 a month with 100 GB per signal included, then $0.30 per GB. Metrics are metered by volume, not by sample.",
+	"cmp_sn_pricing_them": "$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.",
+	"cmp_sn_errors_maple": "Exceptions become issues with an owner, a state, a severity and comments. A resolved issue that fires again reopens.",
+	"cmp_sn_errors_them": "An exceptions list grouped by service, type and message, each linked to its trace. No state, owner or severity on a group.",
+	"cmp_sn_rum_maple": "Browser session replay with the trace behind every click. 5,000 sessions a month included.",
+	"cmp_sn_rum_them": "Browser traces, logs and Web Vitals over OpenTelemetry. No session replay.",
+	"cmp_sn_local_maple": "One binary with an embedded ClickHouse. `maple start` on a laptop, no containers, no account.",
+	"cmp_sn_local_them": "The Linux install still needs ClickHouse and Postgres beside it; Docker wants 4 GB and five containers.",
+	"cmp_sn_source_maple": "FSL-1.1, converting to Apache 2.0 two years after each release. One license, no enterprise directory.",
+	"cmp_sn_source_them": "MIT core, plus an `ee/` directory under a commercial license that holds SAML, OIDC and fine-grained RBAC.",
+	"cmp_sn_ai_maple": "A hosted MCP server exposing the product's own queries, scoped to the org in the SQL, with opt-in write tools.",
+	"cmp_sn_ai_them": "A hosted MCP server with fifty-plus tools, agent skills for Claude, Codex and Cursor, and Noz, an AI teammate that is Cloud-only.",
+	"cmp_sn_selfhost_maple": "The repository, a compose file, your Postgres and ClickHouse, one root password. Single-org, no SSO yet.",
+	"cmp_sn_selfhost_them": "Docker, Swarm, Helm and Foundry installs with per-platform guides. Multi-user with roles and Google OAuth in the Community edition.",
+	"cmp_sn_promql_maple": "No PromQL. Visual builder and SQL, one grammar across signals.",
+	"cmp_sn_promql_them": "Query Builder v5, ClickHouse SQL and PromQL in dashboards. Prometheus rules carry over.",
+	"cmp_sn_cost_controls_maple": "Sampling guidance and volume alerts. No hard ingest cap.",
+	"cmp_sn_cost_controls_them": "Ingest Guard: daily caps per signal and per team in Cloud that drop data past the limit.",
+	"cmp_sn_channels_maple": "Slack, PagerDuty, Discord, Telegram, email and webhooks.",
+	"cmp_sn_channels_them": "Nine channel types, including Opsgenie, Microsoft Teams, Incident.io, Rootly and Zenduty.",
+	"cmp_sn_mig_1_title": "Keep the Collector, add an exporter",
+	"cmp_sn_mig_1_body": "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.",
+	"cmp_sn_mig_2_title": "Move the dashboards and alerts with one prompt",
+	"cmp_sn_mig_2_body": "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.",
+	"cmp_sn_faq_1_q": "Is SigNoz open source?",
+	"cmp_sn_faq_1_a": "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.",
+	"cmp_sn_faq_2_q": "How is Maple different from SigNoz?",
+	"cmp_sn_faq_2_a": "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.",
+	"cmp_sn_faq_3_q": "Which is cheaper, SigNoz or Maple?",
+	"cmp_sn_faq_3_a": "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.",
+	"cmp_sn_faq_4_q": "Can I self-host both?",
+	"cmp_sn_faq_4_a": "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.",
+	"cmp_sn_faq_5_q": "Does SigNoz have session replay?",
+	"cmp_sn_faq_5_a": "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."
 }