Artificial intelligence news.
Straight from the original announcements.

Vercel sets deadlines for Marketplace vendors to drop static credentials

October 22, 2026By the AI News Bites Editorial TeamSource: Vercel
Vercel sets deadlines for Marketplace vendors to drop static credentials
Image: Vercel

Vercel wants to retire long-lived static credentials such as API keys and database passwords, and it is using its Marketplace to force the issue. According to the company, vendors without OIDC support will get a "Not secure" label by November 30, 2026 and face delisting by January 2027.

Key points
  • Vercel will label Marketplace vendors using long-lived secrets without OIDC support "Not secure" by November 30, 2026.
  • Vendors that do not offer secure auth will be delisted by January 2027.
  • Vercel's survey of more than 1,000 SaaS vendors found only 8.4% supported secure authentication methods.
  • Vercel released OIDC UI, a shadcn/ui registry with trust-policy forms and token verification code for providers.
  • Vercel Connect lets applications and agents request provider tokens at runtime without storing long-lived secrets.

Why Vercel is targeting static credentials

Vercel compares the current state of machine-to-machine authentication to HTTPS in 2010. Some vendors and enterprises lead the way, but long-lived static credentials remain the default for many SaaS vendors and infrastructure providers, the company says.

The risk, according to Vercel, grows as agents take on more work. They are given access to systems, tools and data through credentials that can grant permissions far beyond the task at hand. Those credentials can leak into a code repository or chat, be stolen when a service or dependency is compromised, or be exposed when prompt injection leads an agent to reveal them. Until the credential expires or is revoked, an attacker can use it with the permissions it carries.

Rotation is also costly. Vercel says it has previously spent "thousands of engineering hours" on multiple, very painful key rotations, and that it never wants to repeat that.

OIDC as the alternative, and why adoption lags

With OIDC, an application authenticates without storing a long-lived provider key. A trusted issuer provides a signed, short-lived token identifying the application, and the receiving service verifies it before granting access. A stolen token stops working when it expires, and applications can fetch fresh credentials programmatically.

Vercel says it has prioritized OIDC so applications can reach Blob, AI Gateway and Sandbox without storing long-lived keys. Its OIDC federation has been generally available since 2024, letting applications on Vercel exchange Vercel-issued identity tokens for temporary AWS, Google Cloud and Azure credentials under configured trust policies.

The wider web has not followed. Vercel surveyed more than 1,000 SaaS vendors and found that only 8.4% supported secure authentication methods. Even where a secure option exists, developers often pick a static key because it is simpler. The company names three barriers:

  • Tooling and setup that make secure authentication more complicated than a static key.
  • Added latency from fetching or exchanging tokens on the request path.
  • Weak incentives for vendors to offer and prioritize secure authentication.

New tools: Vercel Connect and OIDC UI

On Vercel, code retrieves an OIDC token with a function call, and a custom audience names the service meant to receive it. With Vercel Connect, applications and agents use their deployment identity to request provider tokens at runtime, without keeping long-lived provider secrets in environment variables. Vercel is also extending OIDC support across its API and CLI, so deployment workflows no longer need long-lived Vercel tokens.

OIDC UI is a shadcn/ui component registry that includes a trust-policy configurator and a server-side token verifier. It ships provider forms for Vercel, GitHub, GitLab, Google, Bitbucket, AWS, Azure and custom OIDC issuers. A provider can let customers set trust for a particular Vercel project's production environment and verify incoming tokens against that policy, without building the interface and verification code from scratch.

On performance, Vercel notes that a static key in an environment variable needs no network request, while token exchange can add latency. Vercel Functions receive a platform-issued token in the request header, which the SDK reads without another fetch. The platform reuses unexpired tokens, and Vercel Connect caches provider tokens in process and refreshes them near expiry. Custom-audience and provider exchanges still require network calls.

Marketplace deadlines and what they mean

The Vercel Marketplace offers third-party databases, content management systems, observability tools and more. Vercel wants all of these vendors to support short-lived, identity-based authentication, either by accepting OIDC tokens directly or by exchanging them for temporary credentials. It is also working to have integrations configure that authentication automatically when a developer connects a service.

The company points to Chrome's path with HTTPS, which put a "Not secure" label on plain HTTP and then set deadlines. Vercel is now doing the same. By November 30, 2026, vendors that lack OIDC auth from Vercel to their services and use long-lived secrets will get a "Not secure" message on their listing. By January 2027, vendors that do not offer secure auth will be delisted. Vercel says the Vercel API and its own native integrations are held to the same bar.

For Marketplace vendors, the message is a concrete timeline to add OIDC support. For developers, the aim is to connect services without storing long-lived keys, though the benefit depends on vendors meeting the deadlines.

Related news

Vercel Adds Parallel Decisions to AI Gateway for Free
For developersNovember 13, 2026

Vercel Adds Parallel Decisions to AI Gateway for Free

Vercel has made Parallel Decisions Fast from Parallel available through AI Gateway, with free access through November 23, 2026. The model searches the live web and…

Vercel Security Review can scan GitHub repositories without projects
Safety and ethicsNovember 13, 2026

Vercel Security Review can scan GitHub repositories without projects

Vercel Security Review can now scan code changes in GitHub repositories that are not linked to a Vercel project. The change allows teams to review covered repositories…

Vercel Adds Kimi K3.1 Pro to Token Pass for Pro Teams
Products and toolsNovember 12, 2026

Vercel Adds Kimi K3.1 Pro to Token Pass for Pro Teams

Vercel has added Moonshot AI's Kimi K3.1 Pro to Token Pass, its Early Access subscription for Pro teams using coding agents through AI Gateway. The model supports…