Monitoring

Error and performance monitoring — catch what users hit in production.

Sentry captures errors, performance issues, and user feedback from your live site. Drop it into an exported InBuild project and you'll know when something breaks before users tell you. Especially valuable once you're handling form submissions, integrations, or auth.

What you get

Automatic error capture on the client and server (Next.js integration is best-in-class)

Performance monitoring — slow page loads, slow API routes, Core Web Vitals

Session replay — watch what the user did before the error

Source maps for readable stack traces

Generous free tier: 5k errors/month, 10k transactions

FAQ

How do I add Sentry to an exported InBuild site?

`npx @sentry/wizard@latest -i nextjs` — Sentry's wizard auto-configures `sentry.client.config.ts`, `sentry.server.config.ts`, source-map upload, and adds the DSN to your env. Total setup is under five minutes.

Will Sentry slow down my site?

The client-side SDK is around 30KB gzipped (lazy-loaded by default). Performance impact is negligible for what you get — first-class visibility into production errors.

Sentry vs PostHog?

Different problems. Sentry catches errors and performance regressions. PostHog measures user behavior. Most production sites run both.