Feature flags, targeting rules, rollouts. All from Vercel.
Vercel Flags, a feature flag provider built into the Vercel platform, is now generally available. Create flags, define targeting rules, run progressive rollouts, and run A/B tests, all from the Vercel Dashboard without adding another service to your stack.
nice, having flags native in the Vercel dashboard is a big quality-of-life win. does it support server-side evaluation inside edge functions without an extra round-trip, or is everything going through an API call?
About Vercel Flags on Product Hunt
“Feature flags, targeting rules, rollouts. All from Vercel.”
Vercel Flags launched on Product Hunt on April 18th, 2026 and earned 169 upvotes and 4 comments, placing #5 on the daily leaderboard. Vercel Flags, a feature flag provider built into the Vercel platform, is now generally available. Create flags, define targeting rules, run progressive rollouts, and run A/B tests, all from the Vercel Dashboard without adding another service to your stack.
On the analytics side, Vercel Flags competes within Software Engineering and Developer Tools — topics that collectively have 553.4k followers on Product Hunt. The dashboard above tracks how Vercel Flags performed against the three products that launched closest to it on the same day.
Who hunted Vercel Flags?
Vercel Flags was hunted by fmerian. A “hunter” on Product Hunt is the community member who submits a product to the platform — uploading the images, the link, and tagging the makers behind it. Hunters typically write the first comment explaining why a product is worth attention, and their followers are notified the moment they post. Around 79% of featured launches on Product Hunt are self-hunted by their makers, but a well-known hunter still acts as a signal of quality to the rest of the community. See the full all-time top hunters leaderboard to discover who is shaping the Product Hunt ecosystem.
fmerian
nice, having flags native in the Vercel dashboard is a big quality-of-life win. does it support server-side evaluation inside edge functions without an extra round-trip, or is everything going through an API call?