Vercel's Edge Network lets you store content close to your customers and compute in regions close to your data, reducing latency and improving end-user performance.
Our Edge Network is both a Content Delivery Network (CDN) and a globally distributed platform for running compute in regions around the globe.
If you're deploying an app on Vercel, you already use our Edge Network. These docs will teach you how to optimize your apps and deployment configuration to get the best performance for your use case.
Vercel's Edge Network is built on a robust global infrastructure designed for optimal performance and reliability:
- Points of Presence (PoPs): Our network includes over 100 PoPs distributed worldwide. These PoPs act as the first point of contact for incoming requests and route requests to the nearest Edge region.
- Edge Regions: Behind these PoPs, we maintain 18 compute-capable regions where your code runs close to your data.
- Private Network: Traffic flows through private, low-latency connections from PoPs to the nearest Edge region, ensuring fast and efficient data transfer.
This architecture balances the widespread geographical distribution benefits with the efficiency of concentrated caching and computing resources. By maintaining fewer, dense regions, we increase cache hit probabilities while ensuring low-latency access through our extensive PoP network.
- Redirects: Redirects tell the client to make a new request to a different URL. They are useful for enforcing HTTPS, redirecting users, and directing traffic.
- Rewrites: Rewrites change the URL the server uses to fetch the requested resource internally, allowing for dynamic content and improved routing.
- Headers: Headers can modify the request and response headers, improving security, performance, and functionality.
- Caching: Caching stores responses at the edge, reducing latency and improving performance
- Streaming: Streaming enhances your user's perception of your app's speed and performance.
- HTTPS / SSL: Vercel serves every deployment over an HTTPS connection by automatically provisioning SSL certificates.
- Compression: Compression reduces data transfer and improves performance, supporting both gzip and brotli compression.
Vercel's Edge Network pricing is divided into three resources:
- Fast Data Transfer: Data transfer between the Vercel Edge Network and the user's device.
- Fast Origin Transfer: Data transfer between the Edge Network and Vercel Functions.
- Edge Requests: Requests made to the Edge Network.
All resources are billed based on usage with each plan having an included allotment. Those on the Pro plan are billed according to additional allotments.
The pricing for each resource is based on the region from which requests to your site come. Use the dropdown to select your preferred region and see the pricing for each resource.
The table below shows the metrics for the Networking section of the Usage dashboard.
To view information on managing each resource, select the resource link in the Metric column. To jump straight to guidance on optimization, select the corresponding resource link in the Optimize column.
See the manage and optimize networking usage section for more information on how to optimize your usage.
The Edge Network supports the following protocols (negotiated with ALPN):
Vercel supports 35 frontend frameworks. These frameworks provide a local development environment used to test your app before deploying to Vercel.
Through framework-defined infrastructure, Vercel then transforms your framework build outputs into globally managed infrastructure for production.
If you are using Vercel Functions or other compute on Vercel without a framework, you can use the Vercel CLI to test your code locally with vercel dev.
While sometimes necessary, proceed with caution when you place another CDN in front of Vercel:
- Vercel's Edge Network is designed to deploy new releases of your site without downtime by purging the Edge Network cache globally and replacing the current deployment.
- If you use an additional CDN in front of Vercel, it can cause issues because Vercel has no control over the other provider, leading to the serving of stale content or returning 404 errors.
- To avoid these problems while still using another CDN, we recommend you either configure a short cache time or disable the cache entirely. Visit the documentation for your preferred CDN to learn how to do either option or learn more about using a proxy in front of Vercel.
Was this helpful?