Full-stack deployments without the edge constraints

Cloudflare Pages free tier in 2026 includes 500 build minutes per month, unlimited sites, unlimited bandwidth, unlimited custom domains, and unlimited requests for static assets. For Next.js apps with server-side rendering, you'll also consume Cloudflare Workers — the Workers free tier allows 100,000 requests per day (roughly 3 million per month). There is no managed PostgreSQL or Redis on any Pages plan; you need an external database provider.

Cloudflare Pages free plan includes 500 build minutes per month across all your projects. The Pro plan (part of Workers Paid at $25/month) increases this to 5,000 build minutes per month. Business plan ($85/month) provides 20,000 build minutes per month. There is no per-minute overage charge — you must upgrade your plan to get more minutes. Each build minute counts against deploys for all Pages projects in your account combined.

Yes, but with important limitations. Cloudflare Pages supports Next.js via the @cloudflare/next-on-pages adapter or the OpenNext Cloudflare preset. However, the app must run in Cloudflare's edge runtime (not Node.js), which means no Node.js built-in modules (fs, path, native crypto), no ISR without Cache API workarounds, and limited next/image support. You deploy using wrangler pages deploy .next or the OpenNext CLI. Standard Node.js Next.js deployments — ISR, full image optimization, long-running Server Actions — are not supported on Cloudflare Pages.

Yes. Cloudflare Pages allows unlimited custom domains on the free plan — this is one of the most generous features compared to competitors like Vercel (1 domain on free) or Netlify (1 domain on free). You get both *.pages.dev subdomains and your own custom domains at no extra cost. Your domain's DNS can be managed by Cloudflare or pointed via CNAME if hosted elsewhere.

wrangler pages deploy .next is the Cloudflare CLI command to upload a Next.js app to Cloudflare Pages. Unlike a standard Next.js deployment (which runs a Node.js server), this targets Cloudflare's V8-based edge runtime via Workers. You first run npx @cloudflare/next-on-pages (or the OpenNext Cloudflare build), which transforms your Next.js output into Workers-compatible format. Then wrangler uploads that output to the Cloudflare network. The build command (next build) is the same, but the runtime environment is fundamentally different — no Node.js APIs, edge-runtime only.

Yes, Cloudflare Pages is effectively free for static sites. The free plan includes 500 build minutes per month, unlimited bandwidth, unlimited requests, and unlimited custom domains — all at no cost. There are no per-request charges for static assets. The costs appear when you add Next.js SSR (needs Workers), databases (external provider required), or observability tools (third-party). For a pure static or JAMstack site, the free plan is genuinely competitive.

The main Cloudflare Pages alternatives in 2026 are: Temps (self-hosted full-stack PaaS with managed databases and observability included), Vercel (managed Next.js platform, $20/month Pro), Netlify (JAMstack platform, $19/month Pro), and Render (general-purpose PaaS). Temps is the strongest alternative when you need full Next.js support, managed PostgreSQL, error tracking, and session replay without assembling multiple services. Vercel is the closest match for pure Next.js without Cloudflare's edge constraints.

Choose Cloudflare Pages if: you're deploying static or JAMstack sites, you need global edge delivery across 300+ cities, you want Cloudflare's DDoS protection and WAF, or your app naturally fits the Workers edge runtime. Choose Temps if: you need full Next.js App Router support (ISR, next/image, Node.js APIs without adapters), you want managed PostgreSQL included (Cloudflare has no native Postgres), you need error tracking, session replay, and analytics without paying separately for Sentry ($26/mo), PostHog ($0–50/mo), and LogRocket ($69+/mo), or you want to self-host for data ownership and cost control. Cost comparison for a 5-person team with a full-stack Next.js app: Cloudflare Pages Pro + Workers + Neon + Sentry + PostHog = $75–125+/mo. Temps Cloud = ~$6/mo flat.

Temps uses Pingora, Cloudflare's open-source reverse proxy (written in Rust), as its built-in proxy layer. Pingora is the same technology that processes over a trillion requests per day on Cloudflare's network — Temps ships it as part of the single binary, handling TLS termination, routing, and HTTP/2 without requiring Nginx or Caddy. This is separate from Cloudflare's paid edge network — Temps runs Pingora on your own server, not on Cloudflare's global infrastructure.