A single SDK instruments your entire Next.js app — React components, server actions, API routes, and edge middleware. npx @sentry/wizard -i nextjs and you're done.
Debug the hard parts of Next.js.
From edge middleware to client components, server action, and production-only failures, see what’s actually happening in your app.
Run this command to sign up for and install Sentry.
Copied!Click to Copy
npx @sentry/wizard@latest -i nextjsGet all the context of every error, full-stack
One install covers client, server, and edge
Debug with complete context
Sentry groups errors and surfaces everything in one place. Each issue includes stack traces, logs, breadcrumbs, and session replays.
Trace requests across every boundary
Follow a request from the browser through server components, edge middleware, and back. See every route path, redirect chain, and console log.
Prevent Next.js regressions before and after deploy
Compare releases across every runtime
See error rates and performance before and after every deploy. Pinpoint exactly which release introduced a regression so you can roll back and fix it faster.
Use logs to catch issues before they escalate
Capture structured application logs from your Next.js code and automatically import platform logs and distributed traces via Vercel drains to inspect unexpected behavior in real time.
See agent behavior before it becomes a problem
Monitor AI agents, LLM tool calls, and MCP servers to catch latency spikes, token blowups, failed tool calls, and noisy third-party APIs—all in one place.
Fix what’s broken faster – from local dev to Vercel production
Stop Next.js bugs before they make it to production
Seer code review catches breaking changes in your PR before they hit your users.
Catch issues instantly and get automatic root cause analysis
Automatically connect errors with runtime context (browser, Node.js, edge), performance data, and recent changes to generate RCAs and solutions.
Let agents handle the fixes for you
Seer generates PRs with fixes for you, or, delegate to Cursor Cloud Agents to implement solutions in your application code.
Sentry has changed how we monitor and respond to errors at Vercel by increasing code visibility and reducing resolution times. I’m thrilled for the new SDK to make error monitoring even easier for the Next.js ecosystem.
Read MoreVercel testimonialFAQs
When debugging, logs, traces, and errors work better together. Logs provide the granular context—like retries, API failures, and internal state—that spans and errors can miss. But in most tools today, logs live in a separate system, forcing you to switch between tools to piece together the full picture.
With logs in Sentry, everything is in one place. You can see logs right alongside your errors and traces—no more context switching, just faster debugging.
Yes. Send logs and traces without code changes to Sentry from platforms where you can't use the Sentry SDKs. Set up log drains to forward logs from your deployments directly to Sentry without code changes. Log drains are available for Vercel, Cloudflare, Heroku, Supabase, and Shopify Hydrogen.
You can get started for free. Pricing depends on the number of monthly events, transactions, and attachments that you send Sentry. For more details, visit our pricing page.
Sentry doesn’t impact a web site’s performance.
If you look at the configuration options for when you initialize Sentry in your code, you’ll see there’s nothing regarding minimizing its impact on your app’s performance. This is because our team of SDK engineers already developed Sentry with this in mind.
Sentry is a listener/handler for errors that asynchronously sends out the error/event to Sentry.io. This is non-blocking. The error/event only goes out if this is an error.
Global handlers have almost no impact as well, as they are native APIs provided by the browsers.
Of course we have more content
Fix It
Get started with the only application monitoring platform that empowers developers to fix application problems without compromising on velocity.