Vercel Connect goes GA, replacing stored provider secrets

Vercel Connect went generally available on every plan, including v0, per Vercel Connect's GA changelog. Leaked provider secrets in environment variables are a common way into a breach, and Connect closes that specific hole.

The feature changes how a deployment reaches outside services. Instead of storing a provider's API key in a project's environment variables, the deployment authenticates with the Vercel OIDC identity it already holds. It calls getToken() for a credential scoped to that one task. Vercel refreshes and expires the token itself, so no static secret sits in the project.

The list of covered services is long. Vercel counts more than 100 integrations, with managed connectors for Slack, GitHub, Linear, Salesforce, Snowflake and Microsoft. It also supports generic OAuth, API keys and MCP servers.

Any team with a provider secret already sitting in a Vercel project's environment variables has a migration to schedule.

Going GA doesn't retire the old path. Projects that keep static secrets in place get none of the protection, and the changelog sets no deadline for moving off them.