Connect Vercel — Code.ae docs

Integration · Deploy

Connect Vercel to your project

Generate a Vercel access token so Code.ae can create a Vercel project, link it to your GitHub repo, and trigger deploys when you click Publish.

Before you start

Connect GitHub first — Vercel deploys are wired to a GitHub repo, so the GitHub step has to land before this one. See Connect GitHub if you haven't.

Sign in to Vercel

Open vercel.com/login and sign in. If you don't have an account yet, sign up with the same GitHub account you connected in the previous step — it makes project linking automatic.

Open the Tokens settings

Once signed in, go to vercel.com/account/settings/tokens. You'll see a list of any tokens you've already created (probably empty). Click Create Token.

Configure the token

Fill the dialog like this:

Token name: code.ae (or anything memorable — we use it when you ever want to revoke).
Scope: Full Account if it's your personal account, or pick a specific Team if you're deploying under a Vercel team.
Expiration: 1 year is a good default. No expiration works too — you can always revoke from this same page.

Click Create Token.

Copy the token immediately

One-time view

Vercel shows you the token once. As soon as you close that dialog, the value is gone. Copy it before you click anywhere else. If you do lose it, just delete the token from the list and create a new one — same friction.

Paste into the Connect Vercel dialog

Back in your Code.ae project, click Publish in the workspace top bar. The first time, it opens a Connect Vercel dialog. Paste the token (it starts with vercel_ or similar) and click Connect.

(Optional) Team ID

If you picked a Team scope in step 3, you also need that team's ID so the deploy lands in the right place. Find it under Team Settings → General → Team ID. It looks like team_xxxxxxxx…. Leave the field blank for personal-scope deploys.

Click Publish

Code.ae creates a Vercel project linked to the GitHub repo, kicks off the first deploy, and surfaces the live URL in the Publish dialog when it lands. Subsequent pushes to GitHub auto-redeploy via Vercel's standard git integration — you don't have to click Publish again unless you want a force-deploy.

What we use the token for

Code.ae calls Vercel's REST API on your behalf — creating the project, attaching the GitHub repo, and triggering deployments. That's it. We don't read your other projects, deploy keys, or domains. You can revoke the token any time at vercel.com/account/settings/tokens.

Connect SupabaseWire up a database + auth so your app has somewhere to store user data.Open Connect GitHubSet up the prerequisite for Vercel deploys.Open