Compare

Maple vs New Relic

New Relic is a full-stack platform priced per full-platform user plus data. Maple is an open-source observability platform for traces, logs and metrics that ingests OpenTelemetry directly and charges for data volume.

Maple
maple.dev
New Relic
newrelic.com

Differences

Where Maple and New Relic differ

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.

Where Maple and New Relic differ
Topic Maple New Relic Edge
Where they differ
Per-seat fees Unlimited. Every engineer, on-call responder and manager gets a login. Standard: $10 for the first full-platform user, then $99 each, capped at five. Pro: $349 per user per month on an annual commitment. 1 Maple
Pricing model $39 a month with 100 GB per signal included, then $0.30 per GB. 100 GB free, then $0.40 per GB on Original Data or $0.60 on Data Plus, on top of user fees. 1 Maple
Agents None. OpenTelemetry SDKs and the OpenTelemetry Collector. New Relic agents per language. OTLP is accepted, with some features available only through the agents. 2 Maple
Source code On GitHub under FSL-1.1, converting to Apache 2.0 two years after each release. Proprietary. The agents are open source; the platform is not. Maple
Self-hosting Yes. Run it on your own infrastructure. No. SaaS only. Maple
Retention 30 days on the cloud plan, longer on Enterprise, and your call when you self-host. Eight days for traces and 30 for logs by default. Data Plus adds up to 90 days on most data types. 3 Maple
Query languages Visual builder across every signal, SQL through the API and the MCP server. NRQL, a SQL-like language across all data types, with a mature query builder. Even
AI and agents Built-in diagnostics plus a hosted MCP server, so Claude, Cursor or any agent can query your telemetry. New Relic AI and an MCP server. 4 Even
Where New Relic is ahead
Synthetic monitoring Not available. Alerts evaluate real traffic only. Scripted browser and API checks from managed locations, included in the platform. 1 New Relic
Frontend and mobile Session replay tied to backend traces, web analytics from the browser SDK, and a Swift SDK. Browser RUM with funnels and session traces, plus mobile agents for iOS and Android. 1 New Relic
Integration catalog OpenTelemetry receivers plus a catalog of connected providers: Cloudflare, Prometheus, PlanetScale, WarpStream, Hazel and GitHub. Kubernetes and Docker are agent installs. Hundreds of quickstarts and agents, including legacy runtimes without OpenTelemetry support. 5 New Relic
Application security Not available. Vulnerability management and IAST bundled into the platform. 1 New Relic
Both have
  • Distributed tracing
  • Log management
  • Metrics and dashboards
  • Alerting
  • Error tracking
  • Kubernetes monitoring
  • Public API
  • MCP server for agents
  • Session replay

Price

The same month, billed twice

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

Reference workload Full platform users 10 users · Total data volume 300 GB/mo

Maple

$39 per month

Startup plan 100 GB per signal included $39
Team seats No per-seat fees Free
Total $39

New Relic

$3.6k per month

Full platform users Pro: 10 users × $349/mo (annual) $3,490
Data ingestion 300 GB (100 GB free) $80
Total $3,570

$3.5k less per month on Maple · $42.4k a year

Adjust for your usage

10 users
300 GB/mo
Maple
$39/mo
New Relic
$3.6k/mo
Difference
$3.5k less per month on Maple$42.4k a year · 99% less

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. New Relic is modeled on Standard ($10 for the first user, $99 each after, five at most) and Pro ($349 per user a month on an annual term) above five, with Original Data at $0.40/GB beyond 100 GB free. Data is split evenly across logs, traces and metrics.

Migration

Moving from New Relic

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

  1. 01

    Swap agents for OpenTelemetry

    Replace New Relic's language agents with OpenTelemetry SDKs. Auto-instrumentation covers the same frameworks, and the result is portable to any backend.

  2. 02

    Export to both

    Point the Collector or the SDK exporter at Maple alongside New Relic's OTLP endpoint. Verify traces, logs and alerts in Maple before cutting over.

  3. 03

    Recreate dashboards and alert policies

    NRQL dashboards don't import. Rebuild the ones that matter in Maple's builder and map alert policies to alert rules; the MCP server can draft both.

otel-collector.yaml The change
exporters:  otlp/newrelic:    endpoint: https://otlp.nr-data.net:4317    headers:      api-key: ${env:NEW_RELIC_LICENSE_KEY}  otlphttp/maple:    endpoint: https://ingest.maple.dev    headers:      x-maple-ingest-key: ${env:MAPLE_INGEST_KEY} service:  pipelines:    traces:      exporters: [otlp/newrelic, otlphttp/maple]    logs:      exporters: [otlp/newrelic, otlphttp/maple]    metrics:      exporters: [otlp/newrelic, otlphttp/maple]
Add Maple as a second exporter, run both, then drop the first.
FAQ

Common questions

Is Maple a full replacement for New Relic?
For APM, logs, metrics, dashboards, alerting and error tracking, yes. For browser visibility Maple offers session replay correlated with backend traces rather than full RUM, and it has no Synthetics or vulnerability management. If those products are why you bought New Relic, keep it for them.
How much does the per-user pricing matter?
It is the largest line on the receipts above. New Relic charges per full-platform user, capped at five on Standard and $349 each on Pro. Maple has no per-user line, so the gap grows with every engineer who needs access. The receipts show it on a ten-person team.
Does Maple have a query language like NRQL?
Maple ships a visual query builder that works the same way across traces, logs and metrics, and exposes SQL through the API and the MCP server for questions the builder can't express. There is no proprietary grammar to learn.
Can I run both during migration?
Yes. Configure the OpenTelemetry Collector to export to both New Relic and Maple. Verify in Maple, then remove the New Relic exporter.
Is Maple open source? Can I self-host it?
Yes to both. The source is on GitHub under FSL-1.1, converting to Apache 2.0 two years after each release. Self-host for data residency and unlimited retention, or use the hosted cloud at app.maple.dev.

Sources

Where the New Relic 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. 1 New Relic pricing checked September 2026
  2. 2 New Relic: OpenTelemetry checked August 2026
  3. 3 New Relic: data retention checked September 2026
  4. 4 New Relic AI checked August 2026
  5. 5 New Relic instant observability checked August 2026

Compare

Other comparisons

See the difference on your own traces.

Point one exporter at Maple and run both for a week. The free trial needs a card, with no charge until it ends.