Evaluate Vercel Flags from another project without sharing SDK keys.

Vercel has launched Project Connections, a feature enabling applications to evaluate flags defined in another Vercel project within the same team without managing SDK keys. Previously, sharing flags between projects required manually copying a server SDK key into an environment variable, which introduced security and maintenance challenges. The new approach allows connected projects to authenticate using their deployment’s identity, streamlining the process and reducing operational overhead.

For local development, developers can use the vercel env pull command to retrieve their project’s OIDC token, facilitating flag evaluation during development. Access to connected projects is managed through the Connections page under the Flags section in the project dashboard or via the vercel flags connections command in the CLI. This centralized management simplifies oversight and reduces the risk of misconfiguration.

Connections grant read-only access to flags across all environments, ensuring that the consumer deployment evaluates the appropriate flag environment—production deployments assess production flags, while others use their respective environments. This alignment ensures consistency between flag evaluation and deployment context, reducing discrepancies in feature rollouts.

To implement Project Connections, developers must use @flags-sdk/vercel 1.6.0 or later, or @vercel/flags-core 1.11.0 or later when using the core library directly. Managing connections from the CLI requires Vercel CLI 63.0.0 or later. The feature is available on all plans, making it accessible to teams regardless of their subscription tier.