Vercel

DeepTracer is built for Vercel. If your app is already using the SDK, deploying to Vercel requires nothing extra — no config files, no build plugins, no environment-specific code.

Environment Variables

Set these in your Vercel project settings under Settings > Environment Variables:

Variable	Value	Required
`DEEPTRACER_KEY`	Your API key (starts with `dt_`)	Yes
`DEEPTRACER_ENDPOINT`	`https://ingest.deeptracer.dev`	Yes
`NEXT_PUBLIC_DEEPTRACER_KEY`	Same API key	For browser monitoring
`NEXT_PUBLIC_DEEPTRACER_ENDPOINT`	`https://ingest.deeptracer.dev`	For browser monitoring

DeepTracer uses a single API key per project — the same key works for both server and browser. No public/secret split needed.

What works automatically

When you deploy to Vercel with the SDK installed, you get several things for free:

waitUntil auto-wired — logs and errors are sent after the response, so your serverless functions stay fast. No data is lost when the function shuts down.
Release detection — DeepTracer reads VERCEL_GIT_COMMIT_SHA automatically. Every error and log is tagged with the git commit that caused it.
Source maps — when you use withDeepTracer() in your next.config.ts, source maps are uploaded during next build on Vercel. Stack traces show your original source code, not minified output.

next.config.ts

import { withDeepTracer } from "@deeptracer/nextjs/config"

export default withDeepTracer({
  // your existing Next.js config
})

Log Drains

Vercel can forward all server-side logs to DeepTracer automatically — even without the SDK. This is useful as a safety net alongside the SDK, or as a standalone zero-code option.

Add the log drain

In your Vercel dashboard, go to Project Settings > Log Drains and add:

Endpoint: https://ingest.deeptracer.dev/ingest/drain
Headers: Authorization: Bearer dt_your_api_key_here
Sources: Select all (Build, Edge, Serverless, Static)

Verify it works

Deploy your app. Logs start flowing immediately — check your DeepTracer dashboard within a few seconds.

SDK + Log Drains = full coverage. The SDK gives you structured logging, browser errors, traces, and AI/LLM monitoring. Log drains catch everything else — build output, edge function logs, and anything written to console.log. Use both for the best results.

What's next?

Next.js Quickstart — Set up the SDK if you haven't already
Source Maps — See original source in stack traces
Vercel Log Drain (zero code) — Use log drains without the SDK
Set up alerts — Get Slack notifications when something breaks