Vercel is a deployment platform built for frontend and serverless projects. It solves a straightforward problem: getting code from your machine to a site accessible anywhere in the world, without touching a server. This lesson gives you the conceptual foundations before you deploy your first project.
What Vercel is (and what it is not)
Vercel is a deployment and hosting platform specialized in web applications. You connect a Git repository, and Vercel handles the rest: building the project, publishing it, and distributing it globally.
What Vercel is not:
- Not a VPS (Virtual Private Server): you manage no operating system, no background services.
- Not a general-purpose cloud like AWS, GCP, or Azure: Vercel does not offer native managed databases, virtual machines, or broad object storage.
- Not simple static hosting: Vercel also runs server-side code via its functions.
In practice, Vercel replaces the classic combination of "server + Docker + nginx + CI/CD pipeline" for the vast majority of modern frontend projects.
The deploy-on-push model
The core behavior of Vercel rests on one simple rule: every Git push triggers an automatic deployment.
Here is what concretely happens:
- You connect your GitHub, GitLab, or Bitbucket repository to a Vercel project.
- On every commit or pull request, Vercel starts a Build: framework detection, dependency installation, and compilation.
- The result is a Deployment: an immutable version of your site, accessible via a unique URL generated automatically.
- If the push targets your main branch (usually
main), the deployment becomes Production and is served on your domain. - If it is another branch or a pull request, the deployment is a Preview: an isolated URL, perfect for testing before merging.
Every deployment is independent and kept. You can roll back to any past version in seconds from the dashboard.
The key building blocks of the platform
Vercel is made up of several building blocks that work together:
- Builds: the compilation phase. Vercel detects your framework automatically and knows how to build the project without manual configuration in most cases.
- Preview Deployments: every branch or pull request gets its own preview URL, accessible to your team before any production release.
- Edge Network / CDN: once deployed, your site is distributed across a global network of servers. Visitors receive files from the server geographically closest to them.
- Serverless Functions: backend code (API routes, server logic) that runs on demand, with no permanent server to manage. They stop when no one calls them and restart in a few milliseconds.
- Edge Functions: similar to Serverless Functions, but they run as close as possible to the user on the Edge network, with even shorter cold-start times. Ideal for redirects, geolocation, or lightweight personalization.
What this changes in practice
Before Vercel (or a similar platform), deploying a frontend project often meant: configuring a server, installing a reverse proxy (nginx or Apache), writing a CI/CD pipeline, managing SSL certificates, and keeping all of it up to date over time.
With Vercel:
- The SSL certificate is automatic and renewed without any action on your part.
- The CI/CD pipeline is built in (a push is all it takes).
- Scalability is handled by the platform: if your site suddenly receives 10,000 visitors, you do nothing extra.
- Rollback is instant: one click puts a previous deployment back in production.
The next lesson walks you through connecting your first Git project and triggering your first deployment.