New On-call in Maple: schedules, escalation and silences.

Traces, logs, errors, replays, uptime, on‑call. One app. Your agent reads it too.

$39/month with 100 GB each of logs, traces and metrics, then $0.30 per GB. No per-host or per-seat fees. Source on GitHub under FSL-1.1, Apache 2.0 after two years.

Start free trial
Health, latency and errors across your system.
  • Self-host it on your own infrastructure

    Every line of Maple's source is on GitHub under FSL-1.1, and each release becomes Apache 2.0 after two years. The self-hosted version runs for one team; alerting and team accounts are on Cloud for now.

    Read the source
  • No proprietary agent

    Maple speaks plain OpenTelemetry. Point an OTLP exporter at it and keep the instrumentation you already wrote. If you leave, there is nothing to rip out.

    See instrumentation
  • Hosted in the US or the EU us eu

    Choose the EU when you sign up and your telemetry is stored and processed in Frankfurt. Same plan and price in both regions.

    About EU hosting
  • $39/month, 14-day free trial

    A card is required to start the trial and nothing is charged until it ends. No per-seat, per-host or per-query fees at any volume.

    See what it costs

Signals

Read the trace.

Every request as a span tree, attributes intact. Click a span and see what it carried.

Distributed Tracing
POST /checkout 8 spans · 203ms
DurationStatus
/checkoutapi-gateway
203ms200
validateTokenauth-service
24.0msOk
createOrderorder-service
111msOk
validateInventory
20.0msOk
reserveItems
16.0msOk
processPaymentpayment-svc
57.0msOk
chargeCard
45.0msOk
sendConfirmationorder-service
30.0msOk

Search the logs.

Structured logs straight from OTLP. Filter by severity, service or any attribute, then jump to the trace.

Log Management
/logs production
TimeLevelMessage
INFOPOST /api/checkout 402
INFOorder canceled order_id=ord_8421 reason=payment_declined
WARNfalling back to authorize-only flow
ERRORcard declined: insufficient_funds
INFOcharging card amount=129.00 currency=EUR
DEBUGevaluate flag fast_checkout=false cohort=A2
INFOreserved 3 items sku=SKU-9081,SKU-1142,SKU-0077
WARNstock low sku=SKU-9081 qty=3
INFOtoken verified user=u_4109 scope=checkout
DEBUGjwks cache hit kid=2026-05
INFOPOST /api/checkout received
INFOGET /api/cart 200
INFOloaded cart user=u_4109 items=3
INFOGET /api/inventory 200
DEBUGreschedule retry_at=12:04:25 job=sync-inventory
INFOPOST /api/feedback 201
16 logs

Replay the session.

Every click, route, console line and failed request. Replay and spans share one session id.

Browser Sessions
A browser session replay showing the recorded page and captured network requests

Incident

From a 3 AM page to the line that caused it.

Four surfaces, one trace id. Every step below opens from the one before it.

  1. alert trace 4f9ac21e…8b7d40f2

    The alert arrives with context.

    Error rate on api-gateway crosses 5%. The alert carries the service, the threshold it broke and the spans that failed. It reaches you in Slack, PagerDuty, email or a webhook.

    An alert rule with its threshold, evaluation window and firing history
  2. trace trace 4f9ac21e…8b7d40f2

    The trace opens on the failing span.

    The failing request opens as a span tree. Three Stripe retries sit at the bottom, red, each timing out at exactly 1.75 seconds.

    A span selected in the waterfall with its full attribute set open alongside
  3. logs trace 4f9ac21e…8b7d40f2

    The logs are already correlated.

    Jump from the failing span to its logs on the trace id. Retry exhaustion, connection pool at 20/20. The confirmation is on the same screen.

    A log detail with linked trace and span IDs, correlated events and full resource attributes
  4. agent trace 4f9ac21e…8b7d40f2

    Or hand it to an agent.

    Point Claude, Cursor or any MCP client at Maple. It lists services, searches traces, reads the source and proposes the fix.

    An MCP client walking the same incident: five tool calls from list_services to propose_fix, ending in a patch

Local

Maple on your laptop, as one binary.

One maple executable runs OTLP ingest, an embedded database, the query API and the dashboard on 127.0.0.1. No account, and your telemetry stays on your machine.

$ brew install Makisuo/tap/maple

or curl -fsSL https://maple.dev/cli/install | sh

local · 127.0.0.1:4318 DEMO
maple start
🍁 maple · local mode
listening on http://127.0.0.1:4318
OTLP/HTTP POST /v1/{traces,logs,metrics}
query POST /local/query
dashboard https://local.maple.dev
· bundled UI: pass --offline
data ~/.maple/data
pid 48213 · stop with maple stop
one binary · one port telemetry stays on 127.0.0.1

Platform

Everything else you'd have bought separately.

Service map

Live request flow between your services. When one fails, you see what it takes down with it.

A focused service neighborhood showing API, database, and cache dependencies with live request flow
Sovereignty

Your data, your instrumentation, your bill.

OpenTelemetry in, no proprietary agent, and the source on GitHub the whole time. You can leave with everything you brought.

Agents

Let an agent run the investigation.

This is the sequence of tool calls an MCP client makes against Maple, from a service list to a proposed patch.

Reads the code behind the trace
The agent pulls the source file behind a span, so the fix it proposes cites your actual code.
Writes back
Claim an issue, set its severity, attach a fix. The agent changes state in Maple as well as reading it.
OAuth, no plugin
Point any MCP client at the endpoint and sign in. Open protocol, nothing to install.
mcp · agent session DEMO
> ask maple
list services that errored in the last 15m
→ list_services { window: "15m", filter: "errors > 0" }
← 3 services
paymentserrors142p992.4s recoserrors38p99840ms shippingerrors6p99320ms
> investigate payments
→ find_errors { service: "payments", window: "15m" }
← 1 issue
stripe.charge declined  ·  142 events  ·  98 users
→ error_detail { issue_id: "iss_8a91" }
← root cause: idempotency key collision
sample trace: trace_9f3c · order 8421
→ propose_fix { issue: "iss_8a91", fix: "scope idempotency_key by user_id" }
← fix attached. opened pr#412.
> 
4 tool calls · 4.2s https://api.maple.dev/mcp
The bill

The bill, line by line.

Each vendor's public list pricing next to Maple's.

Line item Maple Datadog New Relic Grafana Cloud Dash0 SigNoz Axiom Better Stack Honeycomb
Base price $39 / mo None None $19 / mo None $49 / mo, incl. $49 usage $25 / mo None · bundles from $30 $150 / mo (Pro)
Free plan No · 14-day trial 5 hosts, 1-day metrics 100 GB / mo, 1 full user 50 GB logs/traces, 10k series No · 14-day trial No 500 GB / mo, 25 GB stored 3 GB logs, 3 GB traces 20M events / mo
Per-host fee None $15+ / host / mo None None None None None None None
Per-seat fee None None $10 first, then $99–349 / full-platform user / mo $8+ / active-user / mo None None None $29–34 / on-call responder / mo None
Ingest pricing $0.30 / GB per signal $0.10 / GB + $1.70 / M indexed $0.40 / GB $0.55 / GB $0.60 / M spans or logs · $0.20 / M metric points $0.30 / GB · $0.10 / M samples $0.12 / GB + $0.20 / GB-hr $0.10 / GB + $0.05 / GB-mo stored (EU) $3.00 / M events (spans, logs)
Default retention 30d logs/traces · 90d metrics 15d indexed logs 30d logs · 8d traces 30d logs/traces · 13mo metrics 30d spans/logs · 13mo metrics 15d logs/traces · 1mo metrics Configurable · from $0.03 / GB stored 30d in bundles · billed per GB-mo stored 60d events and metrics
OpenTelemetry support Native Yes Yes Yes Native Native Native Native Native
License FSL-1.1 → Apache 2.0 Proprietary Proprietary AGPL components Proprietary MIT + commercial ee/ Proprietary Proprietary Proprietary
Self-host option One team, no alerting No No OSS components No Supported No No Enterprise, own AWS account

Competitor cells summarize public list prices, checked September 2026 (base prices and free plans, November 2026). Check each vendor's pricing page for current numbers. Maple's rate is the published per-GB rate, billed per signal. Use the calculator to project your monthly cost.

Pricing

One plan, billed by the gigabyte.

100 GB each of logs, traces and metrics included, then a flat rate. Nothing metered by host, seat or query.

Startup 14-day trial
$39 /month

Every feature is included.

$0
per host
$0
per seat
$0
per query
Start 14-day free trial

Free for 14 days · Cancel anytime · Card required to start

Hosted in the US or the EU (Frankfurt) at the same price. EU hosting

Included every month
Logs
100 GB
then $0.30 / GB
Traces
100 GB
then $0.30 / GB
Metrics
100 GB
then $0.30 / GB
Browser Sessions
5,000
then $0.002 / session
Product Events
1M
then $5.00 / 1M events
AI usage
$10
then billed per model, by tokens used

30 days of traces and logs, 90 of metrics · Private support channel · Unlimited dashboards · Advanced alerting · MCP server · AI error triaging · Full API access · Six-year audit log

Estimate your bill →
Enterprise

Higher volume, custom retention, priority support, SSO (SAML/OIDC) with SCIM, and your own cloud account.

Works with every language OpenTelemetry supports

FAQ

Common questions

What is Maple?
Maple is an observability platform for traces, logs, metrics, errors, session replay, uptime checks and on-call, built on OpenTelemetry and backed by ClickHouse. You collect, query and visualize telemetry from your systems in one app, or let an AI agent do it for you over MCP.
Is Maple open source?
Maple is source available. The code is on GitHub under the Functional Source License (FSL-1.1): you can read every line, fork it and self-host it, but not offer it as a competing commercial service. Each release becomes Apache 2.0 two years after publication.
Is Maple OpenTelemetry-native?
Yes. Maple is built on OpenTelemetry, the open, vendor-neutral standard for telemetry, so there are no proprietary agents. If you already emit OpenTelemetry data, you can point it at Maple without re-instrumenting your code.
How is Maple priced?
The Startup plan is $39/month with 100 GB each of logs, traces and metrics included, then a flat $0.30 per GB. No per-host or per-seat fees. Enterprise plans add custom volume and retention.
Does Maple work with AI agents?
Yes. Maple runs an MCP (Model Context Protocol) server, so compatible AI agents can list services, search traces, find errors and propose fixes directly against your telemetry.
Can I self-host Maple?
Yes. Run the Maple container on your own server with a persistent volume. It bundles ingest, the dashboard and its own storage, for one team and without alerting. Maple Cloud is there for teams that need alerting, team accounts, or would rather not operate it.
Where is my data stored?
Maple Cloud runs in two regions: the United States and the European Union (Frankfurt, Germany). You choose one when you create your organization, and all of its telemetry is stored and processed there. The region cannot be changed later. Pricing is the same in both. To keep the data inside your own network, self-host Maple.

Try it on your own traces.

14-day free trial, card required, no charge until it ends. Or self-host, or run maple start locally with no account at all.