Frameworks and stack coverage

Choose by signal, framework and runtime, not just language. Package availability, end-to-end evidence and activation on your installation are separate checks. This page records the multistack work as of 6 October 2026; it is not a claim of universal support.

JavaScript and Node

The published 0.13.0 JavaScript package includes optional entries for:

• React and Next.js: /react, /next/server.
• Vue and Nuxt: /vue, /nuxt/client, /nuxt/server.
• Angular: /angular.
• Svelte and SvelteKit: /svelte, /sveltekit/client, /sveltekit/server.
• Express, Fastify and Nest: /express, /fastify, /nest.
• PostgreSQL, MySQL, Drizzle and Prisma PostgreSQL: /database.

Import the adapter explicitly; installing the package does not instrument every framework. Server adapters use Node, not Edge runtimes. Framework errors, logs and native duration measurements do not imply OTLP tracing. Only matching application source maps reconstruct original frames; framework chunks can remain unmapped.

Start with JavaScript, Vue/Nuxt setup, or the Node database setup. The observed Node database tuple used Node 24.21.0, pg 8.23.1, mysql2 3.24.5, Drizzle 0.45.3 and Prisma 7.10.0. Do not infer Prisma compatibility from the base SDK's minimum Node version.

Ruby, Python and Flutter

Ruby covers the native Rails path. Python includes Django query monitoring and FastAPI/Starlette adapters from 0.4.0, alongside Flask, SQLAlchemy and Celery integrations. The separate background-job profile distinguishes queue wait, intentional scheduling delay, attempts and final outcomes; it is not enabled merely by measuring a job's duration.

Dart/Flutter supports public errors, logs and performance measurements from 0.9.3. Logs and measurements have one delivery attempt; the offline queue applies to errors. Dart exceptions are not native iOS or Android crashes.

Additional integrations tested locally

These integrations have real application and backend evidence, but their packages are not published. No registry install command or general runtime guarantee is implied.

• PHP/Laravel, Symfony, WordPress/WooCommerce: explicit request/error profiles using maintained SDKs; framework, query and queue coverage differs by adapter.
• Java/Kotlin with Spring: traces and errors with the maintained OpenTelemetry agent and Sentry integration; observed Spring Boot 3.5.16 and 4.1.1.
• ASP.NET Core: traces and errors on observed .NET 8.0.31 and 10.0.12 framework-dependent builds. An intermittent TCP reset also occurred in SDK-free laboratory repetitions and remains unresolved.
• Go: traces and errors for net/http, Gin, database/sql SQLite and gRPC on Go 1.26.8 and 1.27.1, Darwin arm64. Other databases and platforms are not established by that result.
• Rust/Tokio: errors and explicit operation spans on Rust 1.88.0 and 1.99.0, Darwin arm64; no automatic web framework or SQL instrumentation.
• C/C++: explicit counters, histograms, gauges and native crashes on Linux arm64 with GCC 12.2, C11/C++17. Requires the compatible backend metadata processor and matching symbols; no Windows/macOS runtime claim.
• Elixir/Phoenix: request spans, routed errors, supervised process failures and Ecto SQLite queries, with explicit task context propagation. Observed Elixir 1.19.2 / OTP 28.1.1, Phoenix 1.8.15 and Bandit 1.12.5 on macOS arm64. Local backend checks passed; LiveView, Erlang-only applications and other platforms remain outside this profile.

Use the project's installation catalog for the exact tested combination and its evidence. Do not treat these local candidates as a ready-to-install public SDK.

Product scope

The CloseYourIt roadmap covers web applications, backend services and mobile apps. Swift/iOS, native Android and React Native integrations remain unfinished and unpublished. Flutter covers web and mobile within documented evidence limits. Unity, Unreal and desktop clients remain excluded. Production capacity and rollout checks remain separate gates.

Before enabling a new signal

Read traces, measurements and sessions and OpenTelemetry setup. Check backend identity, private routing, credentials, processors and retention. Use a public key in browsers and distributed apps; server bearer tokens must stay on the server. Finish by reading back an actual stored record in the intended project.