Vercel Deploy
Vercel turns git push into a live URL. No servers, no Docker, no YAML. Push code, get a website. Let's simulate the full pipeline.
The Deploy Pipeline
Click "Deploy" to watch code go from your machine to a live global CDN (Content Delivery Network — servers around the world that serve your site from the closest location to each visitor).
This is a simulation — the pipeline below shows what happens when you deploy to Vercel, but runs entirely in your browser. In production, this process is triggered automatically when you git push to your repo.
Environment Variables
Secrets go in Vercel's environment variables — never in your code. Configure them here.
Public vs. Secret — the critical difference:
Variables starting with NEXT_PUBLIC_ are exposed to the browser. Anyone can see them in your page source. This is fine for your Supabase URL and anon key (they're designed to be public — RLS protects your data).
Variables without that prefix are secret — they only exist on the server. API keys, service role keys, and Stripe secret keys must NEVER start with NEXT_PUBLIC_. If you accidentally expose a secret key, revoke it immediately in that service's dashboard.
This lesson is for Pro members
Unlock all 300+ lessons across 30 courses with Academy Pro. Founding members get 90% off — forever.
Already a member? Sign in to access your lessons.