Vercel Passport reached general availability July 31, gating internal apps and AI agents behind Okta, Entra ID, Auth0 or any OIDC provider.
Vercel Passport, a layer that gates internal apps and AI agents behind a company’s own identity provider, reached general availability on July 31, 2026, six weeks after it entered public beta (Vercel changelog, July 31, 2026).
What changed #
Passport puts every internal app and agent deployed on Vercel behind an organization’s existing identity provider by default — Okta, Microsoft Entra ID, Auth0 or any other OpenID Connect-compatible service. A visitor opening a protected deployment is redirected to that provider; once authenticated, Vercel sets a session cookie and forwards a signed identity token to the application’s own server code, so app logic can build on who the visitor actually is instead of trusting an unauthenticated request (Vercel docs, Restrict access to deployments with Passport).
That token arrives in an x-vercel-oidc-passport-token
request header as a Vercel-signed JWT, and its external_sub
claim is the reliable user identifier. Vercel strips any client-supplied value for that header before injecting its own verified token, closing off the obvious spoofing path (Vercel Knowledge Base, The Complete Guide to Vercel Passport). It’s an Enterprise-plan feature, priced flat rather than per seat. Vercel’s pitch is putting the whole company behind it at no incremental cost (Vercel, Passport).
The build-up #
Passport isn’t new; it shipped in public beta on June 17, 2026, at Vercel’s Ship conference in London, alongside eve, an open-source framework for building AI agents (Vercel changelog, Vercel Passport is now in Public Beta; The Register, June 19, 2026). The Register’s framing at the time was blunt: Passport is Vercel’s answer to “shadow AI,” the pattern of engineers standing up internal agents and tools that never touch the corporate SSO umbrella IT already manages. Vercel paired it with Connect, a companion feature that issues agents short-lived credentials for systems like Slack, GitHub, Snowflake and Salesforce instead of static API keys, so a compromised agent has a smaller and shorter-lived blast radius (The Register, June 19, 2026).
Our take #
Teams are shipping internal agents faster than IT can inventory them, and an agent with its own URL and no login is a bigger liability than a forgotten internal dashboard, because it can also take actions on someone’s behalf. Gating that behind the IdP a company already audits is a sound default, and tying the identity token to app code with a verified header is the right shape for it.
Who gets to buy it is the catch. Passport is Enterprise-only. The flat per-org pricing removes one bad incentive, since nobody pays more for onboarding another team, but it also means the mid-market and startup teams most likely to have agents sprawling ungoverned across a Vercel account are the ones priced out of the fix. Governance tooling that only ships to the tier that can already afford a dedicated platform team solves the problem for the accounts least likely to have it.
Key Takeaways #
- Vercel Passport reached general availability July 31, 2026, gating internal apps and AI agents behind a customer’s own identity provider (Okta, Entra ID, Auth0 or any OIDC provider).
- A verified identity JWT reaches app code via the
x-vercel-oidc-passport-token
header; Vercel strips client-supplied values for that header to prevent spoofing. - It shipped in beta June 17, 2026, alongside the open-source eve agent framework, explicitly positioned against “shadow AI” — ungoverned internal agents and tools.
- Companion feature Connect gives agents short-lived credentials for third-party systems instead of static API keys.
- Passport is Enterprise-plan only, with flat rather than per-seat pricing.