Vercel & The Ecosystem

Vercel makes Next.js, but doesn't own it

Vercel created and maintains Next.js, and runs a hosting platform optimized for it. The two are tightly aligned but Next.js is open source and self-hostable everywhere Node runs.

What Vercel adds on top of `next start`

Zero-config deploys — git push on a connected repo ships to production.
Preview deployments per PR with a unique URL.
Edge runtime for low-latency middleware/proxy work in 30+ regions.
ISR distributed across the edge cache (sub-second invalidation).
Image CDN — no sharp install, served from the edge.
Analytics & Speed Insights for real-user Core Web Vitals.

The self-hosting reality

Self-hosting works, and the docs are honest about what it costs: image optimization needs sharp installed, ISR cache lives in one region by default, no preview URLs, and you operate the SSL/process manager yourself.

Why "Vercel-only" myths are wrong

Server Actions, RSC, streaming, ISR, image/font optimization, Server Actions caching — all run on a vanilla Node server. The Vercel-only features are the platform layer (preview URLs, distributed cache, edge functions), not the framework features.

Code

Connect a repo and deploy·bash

npm i -g vercel
cd my-nextjs-app
vercel              # interactive: link to org, set project name
# Subsequent pushes to main → auto-deploys to production

Self-host the same app·bash

npm run build
NODE_ENV=production npm run start
# Behind nginx / caddy + a process manager (PM2, systemd, launchd).
# All Next.js features available.

Vercel makes Next.js, but doesn't own it

What Vercel adds on top of `next start`

The self-hosting reality

Why "Vercel-only" myths are wrong

Code

External links

Exercise

Progress

Comments 0

Vercel makes Next.js, but doesn't own it

What Vercel adds on top of next start

The self-hosting reality

Why "Vercel-only" myths are wrong

Code

External links

Exercise

Progress

What Vercel adds on top of `next start`