Summary: Vercel Enterprise Apps and Agents makes governance the default for internal software: Passport places deployments behind the customer IdP from creation, Connect issues task-scoped short-lived credentials, Enterprise Managed Users ties account lifecycle to the directory, and BYOC keeps AWS workloads in the customer account. Passport and Connect are in Beta; Managed Users and AWS BYOC are in Private Beta. The bundle shifts security from per-project configuration to inherited platform controls.
When AI-assisted building of internal tools spreads across a company, shipping stops being the hard part. What follows an agent into use is a set of four questions, which Vercel distilled from a year of internal experience: which people are permitted to run each agent? What keeps an internal agent from becoming external? What data and systems may an agent reach? Which models run underneath, and at what cost? Across the past year, Vercel employees put hundreds of agents and internal apps into service on eve and the Agent Stack — reaching production proved easy; governing what shipped did not. Enterprise Apps and Agents is where those lessons turn into product: ownership, access, and security arrive as defaults builders inherit rather than projects stacked in a platform team’s queue.
| Platform component | Security approach |
|---|---|
| Vercel Passport | By default, places every internal app and agent behind your identity provider |
| Vercel Connect | Issues agents short-lived credentials limited in scope, covering Slack, GitHub, Snowflake, Salesforce, and Linear |
| Enterprise Managed Users | Puts the whole lifecycle of every Vercel and v0 user under the control of your existing directory |
| Bring your own cloud on AWS | Operates apps and agents within your own AWS account (Private Beta) |
Passport: Private from the Moment a Deployment Exists
Most companies meet agents first as internal tools, and staying “internal” has historically meant configuring each project by hand — a single missed private flag on a single deployment was enough to leave sensitive systems and data exposed. Passport turns the starting assumption around: a deployment is private from the instant it comes into being, entry always requires employee identity, every visit leaves an auditable trace, and policy is written centrally by admins. Wire an IdP in once — Okta, Microsoft Entra, Auth0, or any provider speaking OpenID Connect — and Passport carries the configuration to every deployment on its own. The feature is in Beta at present.
Connect: Per-Task Tokens in Place of Standing Keys
Passport settles who may open an agent; the agent itself still has to reach data and systems — the very duality that makes agents valuable and hazardous at once. The inherited pattern: long-lived credentials parked in environment variables, pre-authorized for the full range of what the agent might someday do. Vercel Connect gathers OAuth, OIDC, and secret injection under one product and retires the static key: agents hold no secrets and instead obtain short-lived credentials at the moment of work — a token is issued per task and dies when the task does. The supported list today covers Slack, GitHub, Snowflake, Salesforce, and Linear, together with anything reachable over OAuth or an API. The feature is in Beta at present.
Enterprise Managed Users: Reining In Account Sprawl
With builders everywhere, account sprawl fails quietly: seats nobody remembers opening, permissions that outlive a team change or an exit, and no unified record of who did what. Underneath Managed Users sit SAML SSO and Directory Sync — when the directory gains a person, the seat is there; when the directory drops them, access ends that instant. Group-based access, deployment protection, and MFA reach across the whole org, and every action funnels into one audit trail; your existing Okta setup or other SAML/OIDC directory can now govern v0 too. The feature is in Private Beta at present. Shipping with it is v0’s connection to Snowflake: anyone can assemble data apps straight on the warehouse, access continues to pass through your IdP, and the data never leaves the internal boundary.
BYOC on AWS: Your Workloads, Your Account
At enterprise scale the perimeter question stretches beyond private deployments — the workloads themselves have to sit on infrastructure the security team owns and audits. Bring your own cloud (BYOC) places your compute, build artifacts, and data within your own AWS account and VPC, with Vercel running only the control plane above them; reaching private backends works the way it does for anything else in the account, and source code never departs your CI. Engineers hold on to the Vercel development experience, while the security team keeps its network controls, audit evidence, and account. The feature is in Private Beta on AWS at present.
For Platform Teams: Turn the Safe Route into the Default One
In Vercel’s own telling, the old order had its logic: ideas died in security review because breach risk made a poor trade against innovation gain. Once the controls live in the platform, three shifts follow: prototyping turns secure at scale (anyone can experiment on v0’s governed rails, and experimenting is no longer a security carve-out); domain experts assemble their own tools (the person nearest the problem solves it on the spot rather than filing a ticket and waiting a quarter); and the road to production runs straight (a proven prototype ships on the very platform where it was prototyped — nothing rebuilt, nothing banned). For evaluators, the status breakdown matters: Passport and Connect sit in Beta, while Managed Users and BYOC sit in Private Beta — the governance blueprint is complete, but availability has to be confirmed component by component.