Caddi
Sign inSign up

Connect Vercel

Vercel is where your sites actually run. Caddi creates a Vercel project per Caddi project, wires env vars per environment, and watches the deploy status. Two ways to connect.

Option 1 — OAuth (recommended)

From Settings → Integrations → Vercel click Connect, choose the team Caddi should deploy to, and approve. The token is scoped to that team and renewed automatically.

bash
caddi vercel connect

# opens https://vercel.com/oauth/authorize?... in your browser

Option 2 — Personal access token (PAT)

If you can’t use OAuth, generate a PAT at vercel.com/account/tokens. Scope it to a single team. Then:

bash
caddi vercel connect --token $VERCEL_TOKEN --team northstar
PATs don’t expire on their own. Rotate yours every 90 days. Caddi will warn you 14 days before a PAT created via OAuth is set to refresh — no action needed for those.

What Caddi does with the token

  • Creates a Vercel project linked to your GitHub repo.
  • Sets env vars per environment (production, preview, development).
  • Reads deploy status and the build log URL.
  • Adds and removes custom domains.
  • That’s it — no source code reads, no team management.

Verify

bash
caddi vercel status

# team:        northstar
# token:       oauth (refreshes 2026-08-12)
# projects:    12 linked
# rate-limit:  ok

Multiple teams

You can connect more than one Vercel team and pick the destination at scaffold time:

bash
caddi init --template astro-marketing --vercel-team meridian-studio

Next

Your first project →