Edge Config renamed to Global Config
Edge Config has been renamed to Global Config to better reflect its globally replicated nature with ~1ms reads across regions. All existing projects continue to work, though users should upgrade the @vercel/global-config SDK and update environment variable references from EDGE_CONFIG to GLOBAL_CONFIG. Storage limits have increased to 1 MB on all plans.
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
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-configConnecting a Global Config store to a project creates a environment variable instead of .Environment variable:
GLOBAL_CONFIGEDGE_CONFIGRaised on every plan. Pricing is unchanged.Limits:
Deployments, connected stores, and the environment variable continue to work.Existing projects: no action required.
EDGE_CONFIGThe 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_CONFIGNeither 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
Limit | Hobby | Pro | Enterprise |
|---|---|---|---|
Stores | 1 (unchanged) | Unlimited (was 3) | Unlimited (was 10) |
Writes | 250/month (unchanged) | 100/hour (was 480/day) | 100/hour (was 480/day) |
Store size | 1 MB (was 8 KB) | 1 MB (was 64 KB) | 1 MB (was 512 KB) |
Source: original entry ↗
More from Vercel
Follow Vercel to get its new changes in your feed and email digest.
OpenAI Decisions API now available on AI Gateway
OpenAI's Decisions API is now accessible through Vercel's AI Gateway with an OpenAI-compatible endpoint, enabling decision models to answer typed questions and return probabilities, choices, and scores for routing, triage, and guardrails use cases. Support is available across the OpenAI SDK, AI SDK, HTTP API, and CLI with the latest versions.
Timestamp attributes now supported in Vercel Flags
Vercel Flags now supports timestamp attributes for entities, allowing you to create time-based targeting rules. Use this feature to run limited-time campaigns, show content between specific dates, or target users based on registration date.
Glyph Cluster now available in stealth on AI Gateway
Glyph Cluster, a reasoning model for coding and long-context analysis, is now available as a stealth model on Vercel's AI Gateway for Pro and Enterprise plan teams with purchased AI Gateway credits at no cost during the stealth period. The model supports function calling, streams responses, and can be accessed via AI SDK, OpenAI-compatible APIs, and coding agents.