Vercel

What it enables in Codexa

• Deploy a project to your own Vercel account from the Deploy panel, as an alternative to Codexa static hosting.
• View deployment history and roll back by re-pointing the alias to a previous deployment.

• test
• deploy

Setup

Fields on the workspace connection form. Password-type fields are encrypted before storage and never shown again.

1. Open Settings → Integrations in your workspace (requires the admin or owner role).
2. Choose the provider, give the connection a name, and fill in the fields listed above. Secret fields are encrypted before they are stored and are never sent back to the browser.
3. Click Test connection. Codexa makes a single read-only request to the provider to confirm the credentials work.
4. Save. The connection is now available to projects in this workspace.
5. In a project, open Deploy, choose Vercel as the target and start a deployment. Build output comes from the sandbox build step.

Required permissions and scopes

• A Vercel access token (Account settings → Tokens). Add the team ID if the project should live in a team scope.
• The token needs permission to create projects and deployments in that scope.

Limitations

• The adapter is implemented against the public Vercel API but has only been exercised with a real token in limited environments; treat the first deployment as a smoke test.
• Environment variables and custom domains on Vercel are managed in the Vercel dashboard, not from Codexa.
• Serverless functions are not deployed; only the static build output is uploaded.