Vercel is turning feature flags into a native part of its deployment platform, adding a hosted Vercel Flags product alongside its existing open-source Flags SDK.

The launch is aimed at teams that already ship through Vercel and want to separate deployment from release decisions. Instead of wiring a flag provider entirely outside the hosting stack, teams can now manage Vercel-native flags in the dashboard, use the same interface for connected marketplace providers, and inspect flag behavior through Vercel's development tools.

The developer piece is the Flags SDK, a framework-native library for Next.js and SvelteKit. Vercel's docs describe it as provider-agnostic, type-safe, and optimized for patterns such as static precomputation. That matters because feature flags can otherwise add client-side layout shifts, scattered conditional logic, or hard-to-debug differences between local and production environments.

Vercel is also tying flags into the Vercel Toolbar through Flags Explorer, which lets developers override flag states during development and testing without changing application code. The platform docs also point to observability hooks, including runtime logs and Web Analytics, so teams can connect flag evaluations to application behavior.

The practical shift is not that feature flags are new. LaunchDarkly, Statsig, Split, and other providers already serve the category. Vercel's move is to make flags feel closer to deployment, preview, and framework workflows. For Next.js-heavy teams, that could make gradual rollout and experiment cleanup less of a separate system to maintain.