Vercel Integration

KuaDashboard provides a full Vercel management panel accessible from the Vercel provider tab. Manage your projects, deployments, domains, environment variables, and serverless functions without leaving the dashboard.

Authentication

Vercel credentials can be configured in two ways:

Method	Description
API Token	Generate a token at vercel.com/account/tokens and store it with the Env Manager (key icon)
OAuth (Electron only)	Click Connect with Vercel in the Add Connection dialog to authorize via browser — no copy-pasting required

Using an API Token

1. Open the Env Manager (key icon in the toolbar)
2. Click Add Connection and select Vercel as the provider
3. Enter your VERCEL_API_TOKEN
4. Optionally add a VERCEL_TEAM_ID if your token belongs to a Vercel team account (format: team_XXXXXXXXXXXX)
5. Give the profile a name and save

Using OAuth (Electron app only)

1. Click Add Connection and select Vercel
2. Click Connect with Vercel — your default browser opens the Vercel authorization page
3. Authorize KuaDashboard — Vercel redirects to the HTTPS callback page (https://lnavarrocarter.github.io/kuadashboard/vercel-callback), which automatically hands the authorization code back to the app via the kua:// deep-link
4. The profile is saved automatically and selected as active

Note: OAuth requires VERCEL_OAUTH_CLIENT_ID and VERCEL_OAUTH_CLIENT_SECRET to be set in the app environment. These are bundled in the official release.

---

Projects

The Projects tab shows all Vercel projects accessible with the active profile.

Column	Description
Name	Project name — click to navigate to its deployments
Framework	Detected framework (Next.js, Vite, etc.)
Last Deploy	State of the most recent deployment (READY, ERROR, BUILDING, etc.)
URL	Production URL of the latest deployment
Repo	Linked Git repository
Updated	Last activity timestamp

Actions per project:

• Deployments — switch to the Deployments tab scoped to this project
• Domains — switch to the Domains tab scoped to this project
• Env Vars — switch to the Env Vars tab scoped to this project

---

Deployments

Lists all deployments for the selected project. Use the target filter to narrow by environment:

• All — all deployments
• Production — only target: production
• Preview — only target: preview

Column	Description
Deployment	Deployment UID
State	READY / ERROR / BUILDING / QUEUED / CANCELED
Target	production or preview
URL	Deployment URL
Creator	Email/username of the person who triggered it
Created	Creation timestamp

Actions per deployment:

• Logs — open the real-time build log panel (SSE streaming)
• Functions — view the serverless/edge functions in this deployment
• Redeploy — trigger a new deployment from the same source
• Promote — promote a preview deployment to production (hidden for production deployments)
• Cancel — cancel a deployment that is BUILDING or QUEUED

Build Logs

Click Logs on any deployment to open the log panel. Logs stream in real time via Server-Sent Events. The panel supports:

• Auto-scroll — keep the view pinned to the latest line
• Clear — wipe the current log buffer
• Line coloring by event type: stdout (white), stderr (red), command (yellow), deployment state (blue)

Runtime log intelligence in KUA Applications

The build-log stream above is separate from runtime logs. In Signals → Logs, select a Vercel project and choose Cache for log intelligence to estimate up to two API requests per sync (latest production deployment lookup plus its runtime-log request) before confirming. KUA reads only runtime logs from the latest production deployment, respects Vercel rate limits and Retry-After, and marks a response partial if its bounded 2 MiB/5,000-event read is reached. Events enter the same encrypted local cache, sanitizer and analyzer as other providers, and observed evidence is linked to the project in the KUA Application.

---

Domains

Lists all custom domains configured for the selected project.

Column	Description
Domain	Full domain name
Apex	Root domain
Branch	Git branch this domain is mapped to (if any)
Redirect	Target URL if the domain is a redirect
Verified	Whether the DNS records have been verified by Vercel

---

Environment Variables

Lists all environment variable keys for the selected project. Values are intentionally never displayed or transmitted — this is a security measure to prevent accidental exposure of secrets.

Column	Description
Key	Variable name
Type	plain, secret, or sensitive
Target	Environments the variable applies to (production / preview / development)

---

Functions

Lists the serverless and edge functions included in a selected deployment.

Column	Description
Function	File path within the deployment
Type	lambda (Node.js serverless) or edge
Mode	Execution mode reported by Vercel

Select a deployment from the Deployments tab first — the Functions tab shows the functions of the currently selected deployment.

---

Overview

Overview is the first entry of the sidebar and the view Vercel opens on. It summarizes the account or team of the active profile from one scan:

• Health: healthy, needs attention (paused projects, unverified domains or data that could not be read) or production failing (a project whose last production deploy failed).
• Projects (paused, with Git), Production (healthy, failed, building, without production), Recent failure rate (last 10 deployments per project) and Domains (not verified).
• Projects by last deployment: framework, Node.js, production state, last deploy, recent failures and domains of each project; the name sets it as the active project. Env vars are counted by type.

The scan is shared with the Advisor and cached 15 minutes; Scan again forces a new one.

Advisor

The Advisor, inside the Overview, checks every project of the account or team against good practices. It needs the Pro or Team plan; on Free it shows how many findings there are.

Category	Checks
Security	Credentials in Plain env vars · production secrets shared with every preview · production secrets that are not Sensitive · previews without Deployment Protection · Git Fork Protection off
Infrastructure	Last production deploy failed · unverified domains · paused projects · projects without a production deployment
Architecture	Projects that deploy straight to production, without previews
Development	End-of-life Node.js · half or more of the recent deployments failed · projects not connected to Git

• What it reads: the projects (up to 100), their last 10 deployments, their domains and the name, type and target of their env vars. Env var values are dropped as they arrive and never stored. A variable counts as a credential by its name (password, secret, token, API key…).
• Cost: free Vercel API reads, about 3 per project. The scan is cached 15 minutes; Scan again forces a new one.
• Decisions and history: accept a risk or silence a check that does not apply, see the posture over time and schedule the analysis, as in the AWS and GCP Advisors. A profile added with a bare token (local:<token>) is stored under a hash of the token and cannot be scheduled.
• AI agents: the MCP tool vercel_advisor returns the same findings (see AI agents).

---

Switching Profiles and Projects

The header works like Cluster → Namespace in Kubernetes: pick a profile, then a project.

• Profile — switches between Vercel accounts or team profiles. Changing it clears the current project and loads that profile's project list. The selection is persisted across sessions.
• Project — the active project for the project-scoped views: Deployments, Domains, Env Vars and Cron. Choosing a project reloads the view you are on; views that do not depend on a project (Projects, Aliases, Webhooks, Edge Config, Activity) are not reloaded. Choose — Project — to clear it.
• The project list is available from any Vercel tab, you do not need to open Projects first.
• KUA remembers the last project used with each profile and selects it again when you come back to that profile. If the project no longer exists, the selection is cleared.
• Clicking a row in the Projects table is a shortcut for the same selection: the header and the table always show the same project.