A faster home for configuration data

Vercel has announced the general availability of Edge Config, a globally distributed data store built specifically for fast, low-latency reads. By replicating data across every Vercel region at write time, the service pushes configuration changes out to the edge before a request ever arrives. Once data is in place, reads happen immediately from a Vercel Function or Routing Middleware, with most lookups completing in 5 ms or less and 99% of reads finishing in under 15 ms.

The design makes Edge Config particularly well-suited to workloads that need fresh configuration without the overhead of a separate service or redeploy. Common use cases include A/B testing, feature flags, complex and dynamic redirects, and request-blocking rules that need to update in real time.

For developers already using the service through the earlier limited availability release, note that the product was renamed to Global Config in July 2026. The same API ships as @vercel/global-config, while projects built against @vercel/edge-config continue to work unchanged. For new projects, Vercel recommends using Functions on the Node.js runtime with Fluid compute, and Routing Middleware for request-time routing decisions.

Experimentation without the extra round trip

Edge Config also changes how experimentation platforms deliver data to the edge. When integrated tools like Statsig, HappyKit, or Split push an update, that change lands in Edge Config's distributed store immediately. A returning user's browser triggers no additional network request to fetch flag or experiment config — the data is already present in the local region, which cuts both serverless cold-start time and overall latency.

Two partner integrations arrive alongside the GA release:

  • Statsig, the experimentation and feature management platform, lets Vercel users run its server SDK at the edge to pull configurations and bucket users into feature experiences. Statig's own engineers describe the result as the ability to read up-to-date configs with ultra-low latency, with config updates pushed to the edge on change.
  • HappyKit, a feature flagging service for Next.js applications, works directly with Edge Config so flags can be toggled without a redeploy. Evaluation happens in milliseconds, and HappyKit reports serving over a billion feature flags across hundreds of projects since its launch.

Vercel says it is actively working with other partners in the space to build out more first-party integrations.

Getting started

Edge Config is now generally available. Developers can start with a partner integration, the Edge Config SDK, or one of the deployable examples. The documentation covers setup and usage, and feedback can be left in the Vercel Community.