Migrating from Edge Config to Global Config
Edge Config is now Global Config. This rename better reflects that it is a globally replicated data store for the configuration that applications read at runtime, such as feature flags, redirects, and experimentation settings.
The store itself is unchanged. This page lists everything that changed with the rename, and what to do if you use the REST API, connection strings, or a custom environment variable setup.
| Area | Before | Now |
|---|---|---|
| Domain | https://edge-config.vercel.com | https://global-config.vercel.com |
| REST API | api.vercel.com/v1/edge-config | api.vercel.com/v1/global-config |
| SDK package | @vercel/edge-config | @vercel/global-config |
| Default environment variable | EDGE_CONFIG | GLOBAL_CONFIG |
| CLI command | vercel edge-config | vercel global-config |
| Dashboard | Storage tab shows Edge Config | Storage tab shows Global Config, everything else is unchanged |
| Documentation | /docs/edge-config | /docs/global-config, old URLs redirect |
| Limits | Plan-based caps | Raised on every plan, see new limits |
The old connection string, API path, package, vercel edge-config CLI command, and EDGE_CONFIG environment variable all continue to work. There is no timeline for when they'll be removed.
- Existing projects: no action required. Deployments, connected stores, and the
EDGE_CONFIGenvironment variable continue to work. - Upgrading proactively is safe. The new SDK reads
GLOBAL_CONFIGby default and falls back toEDGE_CONFIG, so it works with stores connected before and after the rename. You can switch packages today without touching your stores. - Creating stores and pushing new config values work without upgrading. Neither depends on which SDK version your project uses.
- Upgrade before connecting new stores to a project. Connecting a store now creates a
GLOBAL_CONFIGenvironment variable, and the legacy SDK only readsEDGE_CONFIGby default. A project still on@vercel/edge-configcannot read a newly connected store.
Use @vercel/global-config as a drop-in replacement for @vercel/edge-config:
pnpm i @vercel/global-configyarn add @vercel/global-confignpm i @vercel/global-configbun add @vercel/global-configThen update your imports:
- import { get } from '@vercel/edge-config';
+ import { get } from '@vercel/global-config';If you store connection strings under custom environment variable names and read them with createClient, both packages continue to work with your existing setup.
- REST API: New integrations should use
api.vercel.com/v1/global-config. Requests toapi.vercel.com/v1/edge-configcontinue to work. - Connection strings: Stores connected to a project from now on receive connection strings that use
global-config.vercel.com. Existingedge-config.vercel.comconnection strings remain valid.
Limits are raised on every plan:
| Limit | Hobby | Pro | Enterprise |
|---|---|---|---|
| Stores | 1 (unchanged) | Unlimited (was 3) | Unlimited (was 10) |
| Writes | 250 per month (unchanged) | 100 per hour (was 480 per day) | 100 per hour (was 480 per day) |
| Store size | 1 MB (was 8 KB) | 1 MB (was 64 KB) | 1 MB (was 512 KB) |
The hourly write limit allows up to 2,400 writes per day. The per-project connection limit is unchanged: 1 on Hobby, and 3 on Pro and Enterprise.
Pricing is unchanged, see Limits and Pricing for details.
Was this helpful?