Implementations
Pick the shortest path to production.
All official PHP, TypeScript, Python, Ruby, Go, Java and .NET integrations share the same telemetry contract. Choose a framework adapter for automatic request tracking, or start from a language core when building a custom adapter.
PHP framework
Laravel
Laravel 11–13 · Queue transportPHP framework
Symfony
Symfony 6.4–8.x · MessengerPHP framework
Nette
Nette 3.2–3.3 · Native DIPHP framework
Slim
Slim 4.15+ · PSR-15 middlewarePHP framework
CakePHP
CakePHP 4.5–5.x · PSR-15 middlewarePHP framework
FlightPHP
FlightPHP 3.10+ · Native middlewareLanguage foundation
PHP Core
PHP 8.2+ · Custom adaptersTypeScript framework
Express
Express 4–5 · Async batchingTypeScript framework
Fastify
Fastify 4–5 · Native hooksTypeScript framework
NestJS
NestJS 10–11 · Global interceptorTypeScript framework
Nuxt
Nuxt 3–4 · Nitro server routesLanguage foundation
Node.js Core
Node.js 20+ · Custom adaptersPython framework
FastAPI
FastAPI 0.100+ · Native ASGI middlewarePython framework
Django + DRF
Django 4.2–6 · Sync and async middlewarePython framework
Flask
Flask 2.3–3.x · Native lifecycle hooksLanguage foundation
Python Core
Python 3.9+ · No dependenciesRuby framework
Ruby on Rails
Rails 7.1–8.x · Automatic RailtieLanguage foundation
Ruby Core
Ruby 3.1+ · Rack middlewareGo framework
Gin
Gin 1.12 · Native middlewareGo framework
Fiber
Fiber v2 · Native middlewareLanguage foundation
Go Core
Go 1.23+ · Concurrent deliveryJava framework
Spring Boot
Boot 3.5–4.x · MVC auto-configuration.NET framework
ASP.NET Core
.NET 8–10 · Endpoint middlewareArchitecture
One pipeline, native integrations.
Framework packages understand native routes, requests, dependency injection and lifecycle hooks. The language cores handle the stable event shape, privacy filtering, retry, buffering and backpressure.
Your application
→ framework SDK
→ privacy-safe event
→ Apirelio ingestion
→ customer integration analyticsFramework native
Use middleware, interceptors and lifecycle hooks instead of custom instrumentation around every controller.
Customer aware
Resolvers attach a stable B2B customer and consuming application to normalized endpoint metrics.
Fail-safe
Telemetry failures never change the observed API response or hide its original exception.