Sentry launch readiness
SentryDo AI-Built Apps Need Sentry Before Launch?
Most AI-built apps need error monitoring before real users arrive; Sentry is one common choice. VibeRaven does not decide this for you: it only notes when the repo has no Sentry or PostHog reference. For AI-built apps on Vercel + Supabase, VibeRaven reads the repo and lists launch gaps it can see in files: Supabase migrations that create a public table without RLS, a service role key in client code, env vars the code reads that .env.example does not list, and Stripe webhooks without signature checks. It is advice, not a gate, and a repository check, not a live database or security test.
Why it matters
The working demo is not the launch.
Builders ask whether Sentry is required because agents mention it constantly while the repo may have zero instrumentation, wrong env vars, or no alerts on paid-user paths. The real question is whether you can see production failures, not whether a DSN exists in a tutorial.
Checklist
Decide if Sentry is needed before launch
- 01List launch-critical paths: signup, auth, checkout, webhooks, and core API routes.
- 02Check whether any client or server error reporting exists in the repo today.
- 03Verify you can distinguish preview from production failures with environments and releases.
- 04Confirm someone will be notified when a paid-user path breaks, not only when you check logs.
- 05Plan source maps and PII filtering so captured errors are actionable in production.
- 06If gaps remain, add Sentry or equivalent monitoring before inviting users, not after the first outage.
Related
Related guides
Browse all launch guides · Read resources · How to make and check your next change
FAQ
FAQ for builders before launch
Do AI-built apps need Sentry before launch?
They need a way to see production errors on launch-critical paths. Sentry is a common default. VibeRaven only notes when the repo has no monitoring reference.
Is Sentry required for every vibe-coded MVP?
Not always on day one for a private beta, but a public launch without error monitoring is risky.
What if my app already has console.log debugging?
Console logs do not replace alerts, release context or server-side capture. VibeRaven does not check logging; it only notes a missing Sentry or PostHog reference.