Vercel projects△
—Connect an account to loadMULTI-ACCOUNT INFRASTRUCTURE
Infrastructure overview
A single view of your Vercel projects, deployments, and Supabase projects.
Server-encrypted accounts
Recent deployments↗
—Live status, latest 20 per accountSupabase projects◉
—Connect an account to loadConnected accounts⌘
0No sample or inferred accountsVercel projects
Projects reported by connected accounts
| Project | Account | Framework | Last updated | Open |
|---|
△No Vercel projects loadedConnect a Vercel account to fetch its live project inventory.
Supabase projects
Project status from the Management API
| Project | Account | Region | Status |
|---|
◉No Supabase projects loadedConnect a Supabase account to fetch its live project inventory.
Recent deployments
Latest deployment activity across connected Vercel accounts
↗No deployment dataConnect a Vercel account to see live deployment status.
| Project | Account | Framework | Updated | Manage |
|---|
△No Vercel projects loadedAdd an account with permission to list its projects.
Recent deployments
Latest 20 available deployments per connected account
↗No deployments loadedDeployment history appears after a Vercel account is connected.
| Project | Account | Region | Status | Created | Manage |
|---|
◉No Supabase projects loadedAdd a Supabase account with project-list read access or a project-scoped database_read token.
⌘No accounts connectedAdd one or more Vercel or Supabase accounts to populate this dashboard with live data.
Connection and token storage
Personal dashboard, not a shared SaaS workspace
01
Create a scoped token
Use a short-expiry Vercel token for the account/team and project controls needed. For Supabase database access, use a project-scoped PAT with the database_read permission.
02
Connect without a vault password
After verification, the token is encrypted on the server with AES-256-GCM. The master key stays in the server environment; a per-user key is derived and each ciphertext is bound to that user and account.
03
Isolated access on demand
Supabase Row Level Security restricts each record to its owner. The proxy decrypts a token only in server memory for an allowlisted provider request; it never returns the credential.