Vercel remains the path of least resistance for Next.js, yet plenty of teams host outside Vercel for predictable bandwidth billing, AWS/Cloudflare network colocation, or strict enterprise vendor lists. This very monorepo runs its public Next.js 16 site on Netlify, its Go RAG backend on Railway, and edge services alongside Cloudflare.
1. Next.js Non-Vercel Hosting Matrix (2026)
| Platform | Runtime Model | ISR / revalidateTag Support | Cold Starts & Ops | Best Workload Fit |
|---|---|---|---|---|
Netlify (@netlify/plugin-nextjs) | Serverless functions + Edge CDN + Durable Cache | Native revalidateTag & revalidatePath (swr / expire) | Low ops; occasional cold start on uncached SSR | Content-heavy SEO sites, marketing + CMS frontends |
Cloudflare Workers (OpenNext / vinext) | V8 isolates on global Cloudflare network + R2/KV cache | Supported via OpenNext R2/Durable Object cache adapters | Near-zero isolate cold start; watch Node native C++ addons | Global low-TTFB edge apps without native binaries (sharp via Images binding) |
Railway / Fly.io (output: 'standalone') | Long-lived Node.js container(s) | In-memory/filesystem by default; add Redis cache handler for multi-replica | 0ms cold start; supports WebSockets & long streams | Full-stack SaaS, Payload CMS admin, heavy SSR + AI streaming |
2. Netlify: Durable Cache + Webhook Revalidation
On Netlify, static and ISR App Router pages work best when you set export const revalidate = false on CMS-backed routes and purge explicitly from an authenticated /api/revalidate route handler whenever Payload CMS publishes or deletes a document. Splitting background refreshes (revalidateTag(tag, 'max')) from hard unpublishes (revalidateTag(tag, { expire: 0 })) gives instant CDN hits without serving deleted URLs.
3. Cloudflare Workers: OpenNext vs vinext
Cloudflare now offers two viable paths: OpenNext for Cloudflare (@opennextjs/cloudflare), which adapts standard next build artifacts to Workers, and vinext, which re-implements the Next.js routing/RSC surface on Vite for lighter Worker bundles. Before committing, audit every server dependency for Node native C++ bindings.
4. Railway: Why Containers Still Beat Serverless for CMS & AI Backends
Whenever a Next.js app embeds Payload CMS, runs long-lived SSE streams, or talks to PostgreSQL over persistent connection pools without cold starts, output: 'standalone' on Railway (or ECS/Fly.io) removes serverless timeout ceilings and per-invocation billing surprises.
Pick the host from the workload, not the logo. A marketing site that revalidates on CMS publish belongs on Netlify. A globally read edge app without native addons belongs on Workers. A Payload admin, WebSocket, or long SSE stream belongs in a Railway container.
Frequently Asked Questions
Does Next.js revalidateTag work properly outside Vercel?
Yes. Netlify's Next.js runtime wires revalidateTag and revalidatePath into Netlify's Durable Cache out of the box. On Cloudflare Workers (OpenNext), configure the incremental cache with R2/KV, and on multi-container Railway/ECS deployments attach a shared Redis cacheHandler in next.config.ts.
Can Payload CMS run on Cloudflare Workers?
Payload CMS relies heavily on Node.js APIs, sharp image processing, and Postgres connection pools, making long-lived Node containers (Railway, Fly.io, AWS ECS, Render) far cleaner and more reliable than V8 Worker isolates for the CMS service.
Which Next.js host has the most predictable bandwidth pricing?
Cloudflare Workers/Pages (zero egress fees on R2/CDN) and Railway/container setups behind Cloudflare CDN provide the most predictable bandwidth economics when serving media-heavy or high-traffic routes.