Deploying Next.js used to mean Vercel or pain. In 2026, Cloudflare Workers, OpenNext adapters, and mature Docker images mean you have real choices. The right one depends on your traffic shape, your budget, and how much you want to think about infrastructure.
This guide picks the right deployment for your Next.js app, with honest notes on the catches at each tier.
What changed in 2026
The Next.js deployment story finally got competitive.
- OpenNext is mature. The community-built adapter layer makes Next.js run cleanly on Cloudflare, AWS, and standalone Node servers.
- Cloudflare Workers handle full Next.js apps. Server Components, Server Actions, and image optimization all work on Cloudflare's runtime.
- Vercel pricing got predictable. New tiers and bandwidth pricing made costs more transparent than the early "you got DDoS'd, pay us" era.
How we picked
- Real cost at three traffic tiers — hobby, growing, established.
- Cold start performance on edge runtimes.
- Deployment friction including CI setup and rollback.
- Observability — what you can see when things break.
- Vendor lock-in — what costs to leave.
1. Vercel — easiest path
Vercel is the path of least resistance. git push deploys, preview URLs work out of the box, and every feature in Next.js is supported by definition. Image optimization, ISR, edge functions, and Server Actions all work without configuration. For a team that wants to ship product, not configure infrastructure, this is still the right choice.
The trade is predictable cost only up to a point. Bandwidth-heavy apps hit serious bills. The pricing changes in 2025 helped, but Vercel is still the most expensive way to run Next.js at scale.
2. Cloudflare Workers — best edge performance
Cloudflare Workers run Next.js apps via the OpenNext adapter, and the experience in 2026 is genuinely good. Cold starts are sub-50ms globally, the free tier covers small projects entirely, and bandwidth is unmetered. Workers KV, D1, R2, and Durable Objects give you a complete platform without leaving Cloudflare.
The catches: not every Next.js feature works identically — image optimization in particular requires a Cloudflare Images integration, and some npm packages depending on Node-specific APIs need workarounds.
3. Self-host on a VPS — cheapest at scale
For predictable workloads, a $20/month VPS running Next.js in Docker behind Caddy or Nginx is cheaper than any platform. Standalone output mode keeps the image small, and a simple GitHub Actions workflow can deploy in under 30 seconds. Tools like Coolify or Dokploy give you a Heroku-like experience over your own VPS.
The trade is real ops cost. You handle backups, security updates, monitoring, and scaling. For a side project, this is fine. For a production app with no on-call rotation, this is risky.
4. AWS, Railway, Fly, Render — the middle ground
Railway, Fly.io, and Render all run Next.js cleanly with auto-deploys and managed databases. Costs sit between Vercel and self-host. AWS via SST or OpenNext works but is more complex than the alternatives — only worth it if you are already deep in AWS.
Comparison: Next.js deployment in April 2026
| Platform |
Best for |
Free tier |
Pain level |
| Vercel |
Most teams |
Hobby |
None |
| Cloudflare Workers |
Edge performance, low cost |
Generous |
Low |
| Railway / Fly / Render |
Mid-scale |
Limited |
Low |
| Self-hosted VPS |
Cost at scale |
N/A |
Medium |
| AWS (OpenNext / SST) |
Existing AWS shops |
Free tier |
High |
Common mistakes to avoid
Premature self-hosting. A side project does not need a VPS. Use Vercel or Cloudflare's free tier until you have real users.
Ignoring bandwidth pricing. Vercel and AWS charge for bandwidth in ways that surprise people. Estimate your traffic and check the calculator before committing.
Not testing rollback. Every deployment platform handles rollback differently. Practice it before you need it at 3am.
FAQ
Should I use the Pages Router or App Router on Cloudflare?
Both work via OpenNext. App Router with Server Components is the future and is well-supported on Cloudflare in 2026.
What about Edge Runtime vs Node Runtime?
Edge Runtime is faster cold-start but limits which npm packages you can use. Node Runtime is more flexible. Most apps benefit from a mix.
Is the Next.js Standalone build worth using?
Yes, for self-hosted deploys. It produces a much smaller Docker image with only the dependencies you actually use.
Where to go next
For related guides see Best web hosting for developers in 2026, Best monitoring tools for SaaS in 2026, and Cost of running a side project in 2026.