Vercel Flags adds Project Connections to evaluate flags from another project without SDK keys
Vercel announced Project Connections for Vercel Flags, which let an application evaluate flags defined in another Vercel project within the same team without managing server SDK keys. Connected projects authenticate with their deployment identity, and for local development, vercel env pull retrieves an OIDC token.
Why it matters
Teams that previously copied server SDK keys into environment variables to share flags across projects can now grant read-only access through connections, which can be revoked without redeploying. Connections are available on all plans and require specific versions of @flags-sdk/vercel (1.6.0 or later) or @vercel/flags-core (1.11.0 or later).
Who should care
Development teams running multiple Vercel projects within one team that share feature flags, and engineers maintaining Vercel Flags integrations.
What you can do
In the consumer application, create an adapter with the source project's ID after granting access via the project's Flags section or the vercel flags connections CLI command (Vercel CLI 63.0.0 or later).