# Overview

Maple SDKs are official, opinionated wrappers around OpenTelemetry that auto-detect platform conventions.

Maple SDKs are official, hand-built libraries that wrap OpenTelemetry with sensible defaults for the runtimes and platforms we support. They auto-detect commit SHAs, deployment environments, and runtime metadata so you can ship traces, logs, and metrics with a single `layer()` call.

If your language doesn't have an official SDK yet, see the [Language guides](#language-guides) below — they walk through standard OpenTelemetry setup pointed at Maple's ingest endpoint for Node.js, Next.js, Python, Go, Rust, Java, C#, Kotlin, and Laravel.

## Official SDKs

| SDK                             | Package                 | Platforms                                | Status |
| ------------------------------- | ----------------------- | ---------------------------------------- | ------ |
| [Effect SDK](/docs/sdks/effect) | `@maple-dev/effect-sdk` | Node.js, Bun, Deno, Browsers, Cloudflare | Stable |

<div class="flex flex-wrap gap-2 mt-4 mb-8 not-prose">
    <span class="text-[10px] uppercase tracking-wider px-2 py-1 border border-border text-fg-muted">Node.js</span>
    <span class="text-[10px] uppercase tracking-wider px-2 py-1 border border-border text-fg-muted">Bun</span>
    <span class="text-[10px] uppercase tracking-wider px-2 py-1 border border-border text-fg-muted">Deno</span>
    <span class="text-[10px] uppercase tracking-wider px-2 py-1 border border-border text-fg-muted">Browsers</span>
    <span class="text-[10px] uppercase tracking-wider px-2 py-1 border border-border text-fg-muted">Cloudflare Workers</span>
</div>

## What "official SDK" means

A Maple SDK is more than a thin OTel wrapper. Each SDK:

- **Auto-detects platform metadata** — commit SHA, deployment environment, cloud provider, and runtime are picked up from environment variables (Railway, Vercel, Cloudflare Pages, Render, etc.) so you don't have to wire them up by hand.
- **No-ops safely without an endpoint** — if `MAPLE_ENDPOINT` (or the equivalent) isn't set, the layer becomes a no-op. Local development doesn't need a Maple project.
- **Ships with platform-specific entry points** — server, browser, and serverless runtimes get their own builds with the right exporter and lifecycle wiring.
- **Tracks the Maple ingest API** — when we add new resource attributes or signal types on the backend, the SDK gets updated to match.

## Language guides

Effect is the only language with a dedicated Maple SDK today. For everything else, point the upstream OpenTelemetry SDK at Maple's ingest endpoint -- our guides walk through it end-to-end:

| Language                                         | Approach                                                               |
| ------------------------------------------------ | ---------------------------------------------------------------------- |
| [Node.js](/docs/guides/instrumentation-nodejs)   | `@opentelemetry/sdk-node` + auto-instrumentations                      |
| [Next.js](/docs/guides/instrumentation-nextjs)   | `@vercel/otel` with the App Router / Pages Router instrumentation hook |
| [Python](/docs/guides/instrumentation-python)    | `opentelemetry-sdk` + `opentelemetry-bootstrap` (FastAPI, Django)      |
| [Go](/docs/guides/instrumentation-go)            | `go.opentelemetry.io/otel` + `otelhttp`, `otelgrpc`, `otelsql`         |
| [Rust](/docs/guides/instrumentation-rust)        | `opentelemetry-otlp` bridged to the `tracing` crate                    |
| [Java](/docs/guides/instrumentation-java)        | OpenTelemetry Java agent (zero-code) or manual SDK                     |
| [C# / .NET](/docs/guides/instrumentation-csharp) | `OpenTelemetry.Extensions.Hosting` + ASP.NET Core instrumentation      |
| [Kotlin](/docs/guides/instrumentation-kotlin)    | Java agent, manual SDK, or the Ktor OpenTelemetry plugin               |
| [Laravel](/docs/guides/instrumentation-laravel)  | `keepsuit/laravel-opentelemetry` — Eloquent, queues, HTTP client       |

A dedicated SDK for any of these can come later -- the guide path is identical to what an SDK would do under the hood, so you can switch in place.