Skip to main content
Deployment means taking your app from local development to a live URL that real users can open.
This repo is designed to deploy cleanly on Vercel.

​
What You Need Before Deploying

Before you deploy, make sure:
  • the app already works locally
  • your Supabase project is set up
  • your minimum env vars are known
  • your production domain is decided

​
Build Settings

Use these defaults on Vercel:
  • Install command: pnpm install
  • Build command: pnpm build
  • Start command: pnpm start

​
Minimum Production Env Vars

NEXT_PUBLIC_APP_URL=https://yourdomain.com
NEXT_PUBLIC_SUPABASE_URL=...
NEXT_PUBLIC_SUPABASE_ANON_KEY=...
NEXT_SUPABASE_SERVICE_KEY=...
OPENAI_API_KEY=...
Then add optional env vars only for the features you actually use, such as:
  • storage
  • payments
  • email
  • analytics
  • Sentry
  • Replicate
  • ElevenLabs

​
What To Update After Deployment

Once the app is live, go back and update:
  • Supabase Site URL
  • Supabase Redirect URLs using /auth/confirm
  • payment webhook URLs
  • any provider callback URLs or allowlists

​
Simple Deployment Flow

  1. Push your repo to GitHub
  2. Import the repo into Vercel
  3. Add your production env vars
  4. Deploy
  5. Open the live URL
  6. Update Supabase and payment/webhook settings to use the live domain
  7. Test sign-in and one core feature

​
Verification Checklist

Your deployment is working if:
  • the live landing page opens
  • auth works on the live domain
  • /home loads after sign-in
  • your main enabled feature works in production

​
If You Also Use Mintlify Docs

The docs live in: 
docs/public
If you connect Mintlify to this repo, point the docs root to docs/public.