Skip to content
Last updated on June 6, 2023
2 min read

Edge Config Limits and pricing

Learn about the Edge Configs limits and pricing based on account plans.

An Edge Config is a global data store that enables experimentation with feature flags, A/B testing, critical redirects, and IP blocking. It enables you to read data at the edge without querying an external database or hitting upstream servers. To keep Edge Configs optimized for frequent, high-speed reads and infrequent writes, the following account-level constraints exist:

Hobby
Pro
Enterprise
Reads
50,000 reads / month
1,000,000 reads / month
Custom
Writes
250 writes / month
1000 writes / month
Custom
Maximum store size
8 KB
64 KB
512 KB
Maximum number of Edge Config stores
1
3
10
Data item key name
Limited to 256 characters
Limited to 256 characters
Limited to 256 characters
Write propagation
Up to 10 seconds globally
Up to 10 seconds globally
Up to 10 seconds globally

Edge Configs accessed from local development environments cannot benefit from Vercel's optimizations. As a result, they can be well over 100 milliseconds slower than production.

Troubleshooting

If reading from your Edge Config seems slower than expected, ensure that the following are true:

  • You've set the connection string as an environment variable
  • You are using the SDK to read from your Edge Config
  • You see the Edge Config icon on the row for the connected environment variable on the Environment Variables page of your project settings
  • You are testing on your Vercel deployment, as the optimizations happen only when you deploy to Vercel

    Edge Config icon with connected environment variable

  • You are testing your Vercel deployment. The optimizations happen only when you deploy to Vercel

Security

If you are developing locally or self-hosting, your Edge Config is loaded via the public internet network. In this case, you may wonder if it's safe to have the token as a parameter in the connection string.

  • It is safe to have the token as a parameter in the connection string, because the SDK parses the passed string, then sends the token via an Authorization header instead