Vercel AI Updates: September 12, 2026

1. Connector Creation Is Now a Restricted Permission on Pro and Enterprise Teams

Vercel added Connector Permissions to Team Settings, letting owners restrict who can create and manage Vercel Connect connectors. Connectors hold the team-managed credentials that applications and agents use to reach external services, so leaving creation open to every team member is effectively leaving credential scope open to every team member. Once enabled, only Owners and members with the Connector Manager extended permission can touch them. Source

2. Tailscale Built Model Access Into the Network Layer With AI Gateway and Sandbox

Vercel published a case study on Aperture by Tailscale, which grants and revokes access to hundreds of models by tailnet network identity rather than by handing out per-user provider API keys. Tailscale evaluated building the routing and execution layers itself and declined: co-founder David Carney notes that provider endpoints are far less uniform than they look, down to basics like whether the response includes cost. Agents raised the stakes further, and the team used Vercel Sandbox for isolated execution as the mitigation for the “lethal trifecta” of private data access, untrusted content, and outbound network reach. Source

3. A Three-Engineer Team Runs 100,000 Media Pitches a Month on the AI SDK and AI Gateway

Featured, a PR co-pilot, migrated 374 Sanity sites off AWS Elastic Beanstalk and now runs its chat agents across 17 models through the AI SDK and AI Gateway, with the Workflow SDK replacing custom long-running job orchestration. The engineering team is three people supporting three brands and more than 100,000 users, which is the actual point of the write-up: each replaced layer was one the team no longer had to operate. Source