Vercel Made Crystal Clear · chapter 1: What Vercel Actually Is
What happens to a request
2026-09-05
A static asset and an edge cache hit never reach your code. Only when neither is available does a function run, and only when the function needs data does it reach your own origin.
Below: the paragraphs from the book that build this idea, then the diagram itself (Figure 1.2), and a recap. About a minute of reading.
Strip away the framework talk and Vercel, as a product, is a small number of concrete things bundled behind one git push. A global edge network that serves your static files and cached responses from a location near the visitor, rather than from one server on one continent. A build pipeline that installs dependencies, runs your build command, and produces deployable output, triggered automatically on every push, from the CLI, or from the dashboard. Serverless functions for the parts of your app that need to run code per request. A preview deployment for every pull request, with its own real URL, so a reviewer clicks a link instead of pulling a branch and running it locally. Domain and TLS certificate handling, so a custom domain gets a working certificate without you touching a certificate authority directly.
The path a single request takes through that bundle is worth seeing as one picture, because the rest of this book keeps returning to different pieces of it.
Recap
- The idea: A static asset and an edge cache hit never reach your code.
- The picture: Figure 1.2, from chapter 1 ("What Vercel Actually Is") of Vercel Made Crystal Clear.
- Go deeper: the chapter builds this step by step, with recipes and sources at the end.
This diagram is one of many in Vercel Made Crystal Clear.
Every chapter opens with the gist, draws the hard ideas, and ends with recipes and sources.
Get the book
