Skip to content

Deploy to Vercel

AI Web Launcher is built for Vercel. The whole flow takes a few minutes.

1

Push to a Git provider

Push your repo to GitHub, GitLab, or Bitbucket.

Terminal
$
gitadd .
$
gitcommit -m "Initial commit"
$
gitpush origin main
2

Import the project

Go to vercel.com/new, select your repository, and click Import. Vercel auto-detects Next.js — no build settings to change. The default build command is next build, and the postbuild script runs next-sitemap automatically.

3

Set environment variables

In the Vercel import screen (or Project → Settings → Environment Variables), add only the keys you use. Everything is optional; the build is green with none of them.

.env
NEXT_PUBLIC_SUPABASE_URL=...
NEXT_PUBLIC_SUPABASE_ANON_KEY=...
SUPABASE_SERVICE_ROLE_KEY=...
RESEND_API_KEY=...
NEXT_PUBLIC_GA_ID=...
NEXT_PUBLIC_DOMAIN=your-domain.com
Public vs server keys
NEXT_PUBLIC_* variables are exposed to the browser. Never put a Stripe secret or Supabase service-role key behind a NEXT_PUBLIC_ prefix.
4

Deploy

Click Deploy. Vercel builds and ships. You get a *.vercel.app URL immediately.

5

Add a custom domain

Project → Settings → Domains → Add. Enter your-domain.com, then point your DNS at Vercel (an A record to Vercel's IP, or a CNAME for the www subdomain). Vercel provisions SSL automatically.

Set NEXT_PUBLIC_DOMAIN to your naked domain to enable the built-in www → apex redirect in next.config.js.

Sitemap & robots

next-sitemap runs after every build (the postbuild script) and writes public/sitemap.xml and public/robots.txt. Update next-sitemap.config.js with your production domain so the generated URLs are correct.

Re-verify the build locally first
Run pnpm build before pushing. A clean local build is the fastest way to catch issues before Vercel does.

Step 9 of the workflow — then re-run it

Deploy is the last step of the idea → deployed workflow. The part most templates miss: the chain ships in the box. ai_rules/ — the prompts, generators, and memory bank — travels with the repo, so your next site starts at Step 1 again on the same rails. One purchase covers unlimited sites, including paid client work; you just cannot resell the boilerplate itself as a competing template.