At Vercel, feature flags are how we ship. From new features to model updates in v0, and even infrastructure changes like a production database migration where a flag was the cutover. The v0 team alone runs hundreds at any given moment.

Merging code sends a build to production, but the feature flags control whether users can see what changed. Flags let you ship on your own schedule, release to segments when you're ready, and roll back immediately by toggling a flag, without touching source files or redeploying.

Vercel Flags is platform-native: server-side by default, zero impact on page performance, and directly integrated with the frameworks you already use.

Vercel Flags lets you create feature flags, define targeting rules by user attributes, segments, or environment, run progressive rollouts, and flip kill switches if something breaks in production.

From your code, you read flags through Flags SDK, an open-source, provider-agnostic library we maintain with first-class adapters for Next.js and SvelteKit. If you are using another framework, you can consume Vercel Flags using the built-in OpenFeature provider.

The Vercel Flags dashboard sits alongside your project and deployments, where you can create and manage flags.

But what makes Vercel Flags different from other flag services is the framework integration.

Other flag providers give you a generic SDK to wire through your framework yourself, and a separate dashboard to manage flags in. Vercel Flags is built into the Vercel platform, so you manage flags in the same dashboard as your deployments, and your code reads them through the framework-native Flags SDK.

At Vercel, feature flags are how we ship. From new features to model updates in v0, and even infrastructure changes like a production database migration where a flag was the cutover. The v0 team alone runs hundreds at any given moment.

Merging code sends a build to production, but the feature flags control whether users can see what changed. Flags let you ship on your own schedule, release to segments when you're ready, and roll back immediately by toggling a flag, without touching source files or redeploying.

Vercel Flags is platform-native: server-side by default, zero impact on page performance, and directly integrated with the frameworks you already use.

Vercel Flags lets you create feature flags, define targeting rules by user attributes, segments, or environment, run progressive rollouts, and flip kill switches if something breaks in production.

From your code, you read flags through Flags SDK, an open-source, provider-agnostic library we maintain with first-class adapters for Next.js and SvelteKit. If you are using another framework, you can consume Vercel Flags using the built-in OpenFeature provider.

The Vercel Flags dashboard sits alongside your project and deployments, where you can create and manage flags.

But what makes Vercel Flags different from other flag services is the framework integration.

Other flag providers give you a generic SDK to wire through your framework yourself, and a separate dashboard to manage flags in. Vercel Flags is built into the Vercel platform, so you manage flags in the same dashboard as your deployments, and your code reads them through the framework-native Flags SDK.