Edge Config renamed to Global Config

Edge Config is now . This rename better reflects that it is a globally replicated data store with ~1ms reads in every region, built for the configuration that applications read at runtime, such as feature flags, redirects, and experimentation settings.Global Config

Global Config stores can now hold up to 1 MB on every plan, and Pro and Enterprise teams can create unlimited stores with more writes per day. The rename also ships with a new server-side SDK, , and a new environment variable.@vercel/global-config

To upgrade, install the new package and update imports:

Pricing is unchanged at $3 per 1,000,000 reads and $1 per 100 writes.

See the for custom setups and the full list of changes.Global Config migration guide

Read more

What changed

What you need to do

New limits

• Global Config is the new name for Edge Config. The store itself is unchanged.Name:

• replaces as a drop-in replacement.Package:@vercel/global-config@vercel/edge-config

• Connecting a Global Config store to a project creates a environment variable instead of .Environment variable:GLOBAL_CONFIGEDGE_CONFIG

• Raised on every plan. Pricing is unchanged.Limits:

• Deployments, connected stores, and the environment variable continue to work.Existing projects: no action required.EDGE_CONFIG

• The new SDK reads by default and falls back to , so it works with stores connected before and after the rename. You can switch packages today without touching your stores.Upgrading proactively is safe.GLOBAL_CONFIGEDGE_CONFIG

• Neither depends on which SDK version your project uses.Creating stores and pushing new config values work without upgrading.

• Connecting a store now creates a environment variable, and the legacy SDK only reads by default. A project still on cannot read a newly connected store.Upgrade before connecting new stores to a project.GLOBAL_CONFIGEDGE_CONFIG@vercel/edge-config