Vercel Connect now supports Custom Environments
By Steven Van ·
Custom Environments are limited to Pro and Enterprise plans and require a verified domain before triggers can target them.
Vercel Connect can now link a connector to a Custom Environment, letting deployments in that environment request provider tokens and receive forwarded webhooks. Custom Environments appear alongside Production, Preview, and Development when adding or editing a project on a connector in the dashboard, and from the CLI by passing the environment's slug to --environment, which replaces the default environments.
- A deployment in a linked environment can request tokens with getToken as usual; calls from an environment that isn't on the project link fail with a ClientNotEnabledForEnvironmentError.
- Trigger destinations can target a Custom Environment too, but the environment must first be deployed and assigned a verified domain, since Connect forwards webhook events through that domain.
- Project links control which deployments can request tokens, not what a token can do once issued; for provider-level isolation between environments, Vercel recommends creating a separate connector per environment scoped to only what it needs.
Vercel Connect is in beta on all plans. Custom Environments are available on Pro and Enterprise plans.
Vercel
The platform for frontend developers — deploy, preview, and scale web apps and AI agents with zero config.
View Vercel →