Deployment
What this layer solves
Deployment puts your built app on the internet: build pipeline, HTTPS, scaling basics. For static and serverless Next apps, a platform beats renting a raw VM for most solo/small teams.
Options
| Host | Best for | Tradeoffs |
|---|---|---|
| Vercel | Next.js, zero-config Git deploys, edge network | Vendor lock-in patterns; fair-use limits on free tier |
| Netlify | Static + serverless, great DX | Slightly different defaults than Vercel for some Next features |
| Cloudflare Pages / Workers | Edge, pricing, global | More DIY for full Next parity |
| Fly.io / Railway / Render | Containers, long-running servers | More ops surface area |
NK Wiki default: Vercel — same company as Next.js; connect GitHub, get preview URLs per branch.
Outline: shipping
- Push repo to GitHub (or GitLab/Bitbucket supported by host).
- Import project on Vercel — select framework Next.js.
- Set environment variables in the dashboard (match local names).
- Attach custom domain — DNS
CNAMEorAper Vercel’s UI for your registrar. - Turn on preview deployments for every PR — catch breaks early.
Official links
When to pick an alternative
- Fly.io if you need WebSockets, background workers, or non-HTTP long processes.
- Cloudflare if edge latency and bandwidth pricing dominate.
Last reviewed: April 2026.
Last updated on