SDK Catalog
Choose the right SDK rollout path based on what you are trying to instrument first.
SDK Catalog
Use this page to decide what to instrument first. Do not start by language preference alone. Start by incident value and operational risk.
Choose by intention
I need backend incident visibility first
Best starting SDKs:
Then follow Instrument your first service.
I need frontend to backend correlation
Start with:
I have a multi-stack project (e.g. React + Supabase)
Obtrace auto-detects all stacks. Instrument each one:
- React + Supabase → Browser SDK + Supabase Managed Agent
- Next.js fullstack → Next.js guide (single setup)
- Vite + Cloudflare Workers → Browser SDK + Cloudflare
- Any frontend + Railway → Browser SDK + Railway
I need platform-specific rollout guidance
Start with:
Official SDKs (GA)
| SDK | Primary Runtime | Best first use |
|---|---|---|
| JavaScript Browser | Browser | User-facing telemetry and frontend correlation |
| JavaScript Node/Bun | Node.js / Bun | APIs, workers, edge-compatible JS services |
| Python | CPython | FastAPI, Django, workers, data services |
| Go | Go 1.21+ | Low-latency APIs and high-throughput services |
| Java | JVM 17+ | Spring and enterprise microservices |
| .NET | .NET 8+ | ASP.NET APIs and enterprise backends |
| PHP | PHP 8.2+ | Laravel and traditional web backends |
| Ruby | Ruby 3.2+ | Rails and background jobs |
Platform & Edge SDKs (GA)
| SDK | Runtime | Best first use |
|---|---|---|
| Next.js | Next.js 13+ | Fullstack apps (server + client in one setup) |
| Supabase | Managed Agent (OAuth) | Full Supabase project monitoring (DB, Edge Fn, Auth, Storage, Realtime) |
| Vercel | Vercel Functions | Vercel serverless functions |
| Cloudflare | Cloudflare Workers | Edge compute |
| Railway | Any (Node default) | Railway-hosted services |
Agents
| Agent | Runtime | Best first use |
|---|---|---|
| Database Agent | Docker | Database monitoring (Postgres, MySQL, MongoDB, Redis, etc.) |
| Infrastructure Agent | Docker | Host/container metrics (CPU, memory, disk, network) |
| Kubernetes (Zero) | K8s | Zero-code cluster-wide auto-instrumentation |
| MCP Server | Go / Docker | AI assistant integration (Claude, Cursor) |
Coming Soon (Not Yet Available)
These SDKs are planned but have not been released. No installation instructions are available.
| SDK | Target Runtime | Status |
|---|---|---|
| Kotlin | JVM (Ktor, Spring Boot) | Planned |
| Rust | Rust async | Planned |
| Swift | iOS | Planned |
For Kotlin projects, use the Java SDK which works with any JVM language.
Decision rules
- Start with the service that hurts most when it fails.
- Prefer one production-relevant service over many partial rollouts.
- Add release metadata before expanding.
- Move to runtime and security guidance after basic telemetry is healthy.