Vercel Sets 2027 Deadline for Marketplace Vendors to Replace Static API Keys

Oct 23, 2026 574 views
Glitches and screens

Vercel is putting dates on a shift away from API keys that can remain valid indefinitely. Its Marketplace vendors must support stronger authentication by January 2027 or face delisting, giving software providers a clear deadline to adopt OpenID Connect (OIDC) or another short-lived, identity-based approach.

The practical case is familiar to security teams: a stolen secret can give an attacker persistent access. Recent credential theft, including a npm worm that scraped tokens from CI pipelines, illustrates how exposed build credentials can spread risk beyond a single system. Vercel CEO Guillermo Rauch summed up the company’s position on X: it’s “time to kill ‘static credentials.’” Even if an intrusion succeeds, he argued, stolen credentials should act more like “self-destructing keys,” limiting the time available to use them.

In an October 22 announcement, Vercel CTO Malte Ubl said a survey of more than 1,000 SaaS vendors found that just 8.4% supported authentication methods Vercel considers secure. The company is advocating OIDC and temporary tokens tied to an identity, which can expire instead of remaining usable until someone manually revokes them.

Vercel’s timeline starts on November 30, 2026. Marketplace listings for vendors that depend on long-lived secrets without OIDC support will then carry a “Not secure” warning. By January 2027, vendors that still lack secure authentication will be removed from the Marketplace. Vercel says its own API and native integrations are subject to the same standard.

The announcement leaves some details open. Vercel did not publish its survey methodology or name the companies surveyed, and it hasn’t said how many current Marketplace partners will need to change their systems. For vendors, the deadline is clear; the scale of the work is not.

Vercel is still updating its deployment workflow

The company’s own migration is underway. Vercel’s GitHub Actions deployment guide still instructs customers to store a VERCEL_TOKEN secret for deployments.

That requirement drew attention on October 23, when Yordis Prieto, a senior software engineer at Fanatics, asked Vercel to remove it. He said the workflow still required “a long-lived access token” in his CI pipeline and criticized the dashboard option for creating tokens that don’t expire.

Vercel had said the day before that it was extending OIDC support across its API and CLI. In a reply to Prieto on October 23, Ubl said the rollout was in progress. He added that the new system would offer more precise control over the actions a credential can perform, but didn’t give a completion date.

Vercel already supports GitHub OIDC for one part of the workflow. On September 25, it added OIDC authentication to its Container Registry, allowing customers to push images without keeping long-lived registry credentials. Application deployments through the documented GitHub Actions guide still use VERCEL_TOKEN, pending the broader rollout.

Temporary credentials matter for agents, too

As AI agents gain access to external services, their credentials become another point of exposure. One way to reduce the risk of persistent access is to issue short-lived, just-in-time credentials that expire after use or a limited period, instead of leaving an agent with an enduring key.

Vercel’s Connect service lets applications and agents use their deployment identity to request credentials from supported providers at runtime. For supported OAuth services, Connect manages token exchange and renewal, so applications don’t need to keep those provider credentials in their environments.

On October 15, Vercel added enterprise-managed authorization to Connect in public beta. Administrators can manage access to supported services through identity providers such as Okta.

Central storage doesn’t shorten a static key’s life

Connect also supports services that rely on static API keys. Its documentation explains how to store a key centrally and retrieve it when an application needs it. That changes where the key lives and how software obtains it; the key itself can still remain valid indefinitely.

The next test is Vercel’s deployment rollout

For teams planning their authentication changes, Vercel’s tools are at different stages. Container image publishing already supports GitHub OIDC, and Connect can obtain credentials for supported services. The documented GitHub Actions deployment path still requires VERCEL_TOKEN, while Vercel says OIDC deployment support is being rolled out with finer controls over permitted actions. That rollout will show how quickly the company can bring its everyday developer workflows in line with the standard it has set for Marketplace vendors.


Correction, October 25, 2026: An earlier version of this article described a documented GitHub Actions workflow for Vercel customers as Vercel’s own workflow and characterized its token requirement as a “double standard.” Vercel’s October 22 announcement said it was extending OIDC support to deployments and holding its own API and native integrations to the same authentication standard as Marketplace vendors. CTO Malte Ubl said on October 23 that OIDC authentication for deployments was in rollout. We have revised the headline and article to clarify this context and added his response.

The post Vercel sets a deadline for vendors to move beyond long-lived keys appeared first on The New Stack.

Source: Amanda Caswell · thenewstack.io

Comments

Sign in to comment.
No comments yet. Be the first to comment.

Related Articles

Vercel sets a deadline for vendors to move beyond long-li...