Error Monitoring for Next.js: what 57 makers' products chose
Among 57 makers' products built with Next.js that we know the error monitoring of, Sentry leads: 56 of them (98%). Next come Highlight (1).
Hosted service or self-hosted tracker. Hosted services give you setup in minutes and pricing by event volume; self-hosting keeps error data on your servers for the cost of running and upgrading it.
What makers on Next.js chose
| Option | Next.js products | All makers | Free for | At 10,000 users |
|---|---|---|---|---|
| 56 (98%) | 96% | ~1,000 users | $29/moTeam | |
| HighlightSelf-hosted tracker | 1 (2%) | 1% | — | — |
Live makers' products with a source for both: that they're built with Next.js, and what they use for error monitoring. A product using two options counts in both; not market share. "All makers" is the option's share among every maker's product that made this decision.
Costs are the cheapest plan that fits, from each vendor's pricing page, at the usage our stack planner assumes for a product with that many users. Free for: the users its cheapest plan a business can use stays free for; plans for personal use only, like a non-commercial hobby tier, don't count.
Which to pick, by situation
- You want the widest SDK coverage and tracing next to errors
Sentry 56 here - Your product is a mobile app and crash-free rates per release matter
Sentry 56 here - Your error data must stay on your own servers
Sentry 56 here
Sentry
Hosted service56 Next.js products here (98%), against 96% of all makers' products. Free up to about 1,000 users. About $29 a month at 10,000 users (Team).
llms.txtMCPCLIBest forBroad SDK coverage across languages and frameworks, with performance tracing next to errors.
Trade-offEvent-based billing can jump after a noisy bug; the self-hosted version needs a sizeable server.
“It's simple: if something breaks, Sentry tells us before our users do. Nothing else has saved us more engineering hours, especially with the new Seer AI features.”
- Real-time alerts with full stack traces and user context flag production errors before users report them, which matters most for solo builders without QA. 4 sources
- Issue grouping, release tracking and regression detection, plus links to commits, PRs and issue trackers, turn raw errors into actionable work. 4 sources
- Self-hosting the full suite needs around 16GB of RAM, and some teams gave up on running it themselves. 3 sources
- For simple projects it feels like overkill, with a steep price and an overwhelming dashboard. 3 sources
Status page: 21 incidents in the last 90 days, 13 major (its own page, 2026-10-19).
“Sentry keeps Giselle reliable by catching every error across our entire stack — server, edge, and client. When something goes wrong in a complex AI workflow, we know about it immediately with full context: user info, team data, and detailed traces. The Next.js integration is seamless, and the ability to attach rich context to errors makes debugging production issues so much faster. Thank you for helping us ship with confidence!”
Error MonitoringMaker says so +1 · source ↗“In the Product Department some of the development tools are Retently , User Pilot , New Relic , Sentry and Github .”
Error MonitoringMaker says so · source ↗“As a solopreneur Sentry helps cut down time in understanding when and why something happened that needs quick attention”
Error MonitoringMaker says so · source ↗“Knows exactly when errors happen”
Error MonitoringMaker says so · source ↗“Sentry gives us one place to investigate errors across Marqly’s web app and API. The error context is especially useful when tracing a failed save, sync, or AI Organizer run.”
Error MonitoringMaker says so · source ↗“Helped us track every crash & bug”
Error MonitoringMaker says so · source ↗“Real-time crash reporting with full stack traces made debugging production issues instant instead of guessing from user reports.”
Error MonitoringMaker says so · source ↗“Helps software developers automatically detect, diagnose, and fix crashes or performance issues in real time across web, mobile, and backend systems”
Error MonitoringMaker says so · source ↗“It's simple: if something breaks, Sentry tells us before our users do. Nothing else has saved us more engineering hours, especially with the new Seer AI features.”
Error MonitoringMaker says so · source ↗Also chosen, and not seen yet
Fewer Next.js products here: Highlight (1).
Real options for error monitoring not seen among these Next.js products yet: Rollbar, GlitchTip.
Getting error monitoring right
Install the SDK on both frontend and backend before launch, upload source maps, and tag each release so you can see which deploy introduced an error. Set alerts for new issues only, not every occurrence, or you will start ignoring them. Filter out noise (bots, browser extensions) early to stay inside your event quota.
- Shipping minified frontend code without uploading source maps, so every stack trace points at one unreadable line.
- Alerting on every occurrence instead of new issues, until the channel is muted and real regressions go unseen.
- Sending request bodies and headers with passwords, tokens or personal data into a third-party error tracker.
The rest of the Next.js stack
What makers' Next.js products chose for their other decisions, the most common pick for each:
- Hosting: Vercel 1,078 of 1,312
- Transactional Email: Resend 493 of 830
- Database: Supabase 171 of 382
- Payments: Stripe 288 of 359
- LLM API: OpenAI API 222 of 301
- Authentication: Clerk 176 of 211
- Web Analytics: Google Analytics 105 of 197
- Product Analytics: PostHog 123 of 168
Questions
What do most Next.js apps use for error monitoring?
Among 57 makers' products built with Next.js that we know the error monitoring of, Sentry leads: 56 of them (98%). Next come Highlight (1).
What does error monitoring cost for a Next.js app with 10,000 users?
On our usage model at 10,000 users, Sentry comes to about $29 a month (Team). Prices are from each vendor's pricing page.
Which error monitoring option stays free longest for a Next.js app?
Sentry: on our usage model its cheapest plan stays free up to about 1,000 users.
How this is counted: a product is on Next.js when a live-product source says so (the maker, its website, a customer story or a subprocessor list), and the same for its error monitoring. How evidence is collected.