# Flags SDK now supports OpenFeature By Steven Van · 2025-03-21 The adapter lets Next.js and SvelteKit apps load flags from any Node.js OpenFeature provider, though Vercel still recommends native adapters where available. The [Vercel]() Flags SDK now has an [adapter for OpenFeature](), so any Node.js OpenFeature provider can supply flags to it. OpenFeature is an open, vendor-agnostic specification for feature flagging, and the adapter keeps the Flags SDK's integration with Next.js and SvelteKit. The adapter ships as @flags-sdk/openfeature and needs the @openfeature/server-sdk peer dependency. Compatible providers include AB Tasty, Bucket, Cloudbees, Confidence by Spotify, ConfigCat, DevCycle, FeatBit, flagd, Flipt, GO Feature Flag, GrowthBook, Hypertune, Kameleoon, LaunchDarkly, PostHog and Split, plus an environment variables provider. Flags can be declared as boolean, string, number or object values. Each needs a default value, and an identify function that returns the OpenFeature evaluation context. Vercel recommends a native Flags SDK adapter where one exists for your provider. Native adapters are tuned for that provider and can integrate with Global Config and Flags Explorer. The OpenFeature adapter has two caveats: - Some OpenFeature providers may not work on Edge Runtime, which can rule out Routing Middleware and Edge Functions. - Because of limits in the OpenFeature specification, the adapter cannot pass descriptions and available options to Flags Explorer. Descriptions and options declared in code still show. Vercel also offers a template to clone as a starting point. ![Vercel]() Vercel The platform for frontend developers — deploy, preview, and scale web apps and AI agents with zero config. [View Vercel →]() [Original source]() [Read Flags SDK now supports OpenFeature on Creators Toolbox]() --- Canonical source: https://creatorstoolbox.com/blog/vercel-flags-sdk-now-supports-openfeature