Vercel is a cloud platform for hosting websites built with modern JavaScript frameworks — primarily Next.js, but also Astro, SvelteKit, Nuxt, Remix, and more. You push code to a Git repository; Vercel builds it, deploys it to a global edge network, and gives you a working URL in under a minute. Think of it as "Heroku for frontend frameworks" — though that undersells the depth of the integration with Next.js specifically.
What Vercel actually does
Vercel does five things, and it does each of them well:
- Build & deploy. Connect a GitHub/GitLab/Bitbucket repo. Every push to your main branch triggers a production deploy; every push to any other branch creates a preview deployment with its own URL.
- Host the static + serverless output. The HTML, CSS, and JS go to a global CDN (300+ edge locations). The serverless functions (API routes, Server Components, middleware) run in regional or edge containers.
- Provide SSL + custom domains. Every deployment gets HTTPS automatically. Pointing your custom domain at Vercel takes 2 minutes.
- Run image optimization, fonts, OG image generation. Next.js features like
next/imageandnext/fontare accelerated by Vercel's infrastructure. Cropping/resizing/format conversion happens on-demand at the edge. - Sell managed services. Postgres, Redis, Blob storage, analytics, KV store — all available as optional add-ons. Most teams use external services (Supabase, Neon) for better pricing.
Who Vercel is for
Vercel makes the most sense for teams building with:
- Next.js — 90% of Vercel's revenue. The framework and platform are built by the same people, so the integration is unmatched. See our deploy guide.
- Modern frontend frameworks — Astro, SvelteKit, Nuxt, Remix, Eleventy. Vercel auto-detects the framework and configures the build correctly.
- Static sites + Jamstack — pre-rendered HTML on a global CDN is the cheapest, fastest way to serve content.
- Solo developers, freelancers, small teams — the free tier covers most personal projects; the Pro tier ($20/seat/month) covers most freelance and small-startup needs.
Vercel is NOT the best fit for: backend-heavy apps with long-running tasks (use Railway, Render, or Fly.io), apps with strict regional data-residency requirements (Vercel runs in US/EU but data-sovereignty controls are limited on lower tiers), and apps with predictable high traffic where self-hosting beats per-request pricing.
How a Vercel deployment works under the hood
When you push to GitHub:
- GitHub webhook fires to Vercel.
- Vercel spins up a build container (Node.js, 30 cores, 60GB RAM by default for paid; smaller for free).
- Runs your project's build command (
next build,npm run build, etc.). - Uploads the output to global edge storage.
- Deploys serverless functions to regional or edge runtimes (depending on your config).
- Aliases the new deployment to your production domain (atomic — no downtime).
The whole process takes 30 seconds to 3 minutes for most projects. Preview deployments work identically — they just get their own URL instead of being aliased to production.
Vercel pricing in 2026
- Hobby (free): Personal projects only. 100GB bandwidth/month, 100 serverless function executions/day, 60s function timeout, no team members.
- Pro ($20/seat/month): Commercial use. 1TB bandwidth, 1M function executions, 60s function timeout, team collaboration, password protection on previews.
- Enterprise (custom): Higher limits, SSO, SLA, dedicated support, on-prem options.
The pricing gotcha: bandwidth + function executions are metered per usage. A surprise viral post can push you past the included limits and add $50-500 to your monthly bill. Set spending alerts in the dashboard.
When to use something else
Vercel is great, but alternatives win in specific scenarios:
- Cloudflare Pages — cheaper at scale (unmetered bandwidth on the free tier), better edge network. Worse Next.js integration.
- Netlify — better form handling, identity features, neutral framework support. Equivalent pricing.
- Railway / Render — better for backend-heavy apps that need persistent processes, databases, queues, cron jobs.
- Self-hosted (Coolify, Dokku, raw Docker) — cheapest at high scale; most maintenance burden.
Getting started with Vercel
The 5-minute version:
- Push a Next.js (or supported framework) project to GitHub.
- Sign up at vercel.com with GitHub.
- Click "Import Project" → select your repo → click Deploy.
- Wait 1-3 minutes. Click the production URL.
- Add custom domain in Settings → Domains (5 more minutes including DNS propagation).
For a complete deploy walkthrough including environment variables, custom domains, and the common gotchas, see our Deploy Next.js to Vercel guide and the Vercel environment variables guide.