Vercel launch readiness
VercelVercel Preview to Production Checklist
For an AI-built app on Vercel + Supabase, VibeRaven reads the repo, not your Vercel project. It lists env vars the code reads that .env.example does not list, a direct database connection that skips the Supabase pooler, a service role key in client code, and Supabase tables without RLS. It is advice, not a gate, and a repository check, not a live database or security test.
A variable works in the preview and is undefined in production? Five checks for Vercel env vars that fail in production.
Why it matters
The working demo is not the launch.
A preview deployment can pass while production still has different environment variables, domains, callback URLs, webhook endpoints, cache behavior, region choices, or rollback assumptions. The launch pass needs to compare what the repo expects with what production must provide.
What breaks first after promoting a preview to production?
A function that crashed with a 500: Vercel "This Serverless Function has crashed": what FUNCTION_INVOCATION_FAILED means and how to fix it. One that ran out of time with a 504: Why does my Vercel function time out with FUNCTION_INVOCATION_TIMEOUT?. A single-page app whose deep links return 404: Why does my Vite or React app 404 on refresh on Vercel?.
A secret that reached the browser: Are NEXT_PUBLIC_ environment variables exposed to the browser?, and how the Secret type differs: What are sensitive environment variables on Vercel?. Supabase variables from the integration: Which env vars does the Supabase Vercel integration add?. Every Vercel question in one list: Vercel for AI-built apps: the deploy, env var and function questions.
A build that fails on the Node.js version since 2026-10-01: Node.js Version "20.x" is discontinued and must be upgraded on Vercel: the fix. Sign-up emails that stop once real users sign up: Supabase "email rate limit exceeded": why sign-up emails stop, and the fix.
Sign-ins that land on localhost:3000 after the deploy: why Supabase login redirects to localhost. Confirmation emails that never arrive: why Supabase confirmation emails do not arrive. File uploads that fail for signed-in users with a row-level security error: the Supabase Storage upload policy fix.
Checklist
Check Vercel before promoting production
- 01List the env vars required by local, preview, and production and confirm which ones differ.
- 02Verify production domains, redirects, callback URLs, webhook URLs, and canonical URLs.
- 03Check build commands, lockfiles, ignored files, monorepo settings, and runtime assumptions.
- 04Review cache headers, function regions, API routes, and data-fetching behavior for production traffic.
- 05Confirm monitoring, logs, error reporting, and rollback steps before inviting users.
- 06Create one focused coding-agent prompt for the deployment gap that repo evidence can improve.
Analytics after deploy
Verify one analytics action on the production URL
This is a manual verification step, not a live analytics check performed by VibeRaven.
Follow one event through the deployed app
Perform one permitted test action on the actual production URL and check the intended receiving project. If it never arrives, use the deployed-event diagnostic before treating an empty dashboard as zero use. Repeat for the environment you are promoting; a preview result does not establish production collection.
Related
Related guides
Browse all launch guides · Read resources · How to make and check your next change
FAQ
FAQ for builders before launch
Does Vercel have its own production checklist?
Yes. Vercel publishes a production checklist for launch, grouped into operational excellence, security, reliability, performance and cost optimization. Use it for the Vercel project itself. This page covers what changes between a working preview and production in an AI-built app: env vars, domains, callback URLs and webhook endpoints that differ by environment.
Why does a Vercel preview work but production fails?
Preview and production can differ in environment variables, branch settings, domains, callback URLs, webhook endpoints, build settings and runtime behavior. VibeRaven only lists the env var names the code expects.
Does VibeRaven replace the Vercel dashboard checklist?
No. It reads repo files; the Vercel dashboard and vercel env ls show what is actually configured.
What should I ask my coding agent after this scan?
Ask it to fix one deployment gap, such as missing env validation, route redirects, or production callback documentation, with clear verification steps.