Next.js monitoring
that actually
explains the errors.

Yes — full support for Next.js 13, 14, and 15, both App Router and Pages Router. The SDK uses the instrumentation.ts hook (stable in Next.js 14.1+) for zero-config setup. Edge Runtime, Middleware, Server Components, Server Actions, and Route Handlers are all covered.

No measurable impact. All event writes are async and non-blocking — your request handlers return immediately and the SDK flushes data in the background. The package is under 3KB gzip. If DeepTracer's ingestion endpoint is unreachable, events are silently dropped — your app never crashes or slows because of monitoring.

The Vercel Log Drain requires zero code changes — it forwards all your app's stdout/stderr logs and function errors to DeepTracer via Vercel's infrastructure. You get error grouping, AI investigations, and retention immediately.

The SDK adds structured telemetry on top: per-request traces with timing, LLM cost tracking (OpenAI, Anthropic), custom events with user context, and richer metadata. Use the drain to start instantly, add the SDK when you want full depth.

Each log line, error occurrence, trace span, or LLM call counts as one event. A typical Next.js app with moderate traffic generates 10K–50K events/month. The free tier covers most side projects. On Pro, the 2M limit per project is enough for a production app serving thousands of daily users.

We never cut off your monitoring. If you exceed 25K events on the free tier, your agent keeps watching and we'll notify you. Overages on Pro are billed at $0.50 per 100K events — most apps never hit this. We'll always warn you before charging overage fees.

Yes — they're complementary. Sentry is great for error grouping and release tracking with a large ecosystem. DeepTracer adds AI investigation (plain-English root cause, not just a stack trace), LLM cost monitoring, and ambient 24/7 health checks that Sentry doesn't do. Many teams run both, at least during evaluation.