Best Cloudflare Pages Alternatives for Next.js 2026

Short answer: Temps is the best Cloudflare Pages alternative for Next.js in 2026 if you want to own the stack. It runs a standard Next.js app with next start on the full Node.js runtime, with no Cloudflare adapter, and bundles analytics, error tracking, session replay and uptime monitoring that Cloudflare Pages doesn't include. It is free to self-host on your own server. The full shortlist: Temps, Vercel, Netlify, Render, Railway and Coolify. On Cloudflare itself, server-rendered Next.js no longer runs on Pages: Cloudflare's supported path is Workers, through vinext (its recommended default, in beta) or the OpenNext adapter, and the old @cloudflare/next-on-pages adapter is deprecated. That puts every dynamic request on the Workers limits: 100,000 requests a day and 10 ms of CPU per request on the free plan, 128 MB of memory on every plan, and no built-in error tracking or session replay.

TL;DR: If you want one platform for deployments and observability, Temps is the strongest alternative: free to self-host, no per-seat fees, no bandwidth bills. If you want a managed platform closest to Cloudflare Pages, Vercel and Netlify remain the standard choices.

Pricing and platform capabilities below were re-checked on each vendor's pricing page and docs in October 2026.

What Is the Best Cloudflare Pages Alternative in 2026?

Temps is the best Cloudflare Pages alternative for teams that want to own their infrastructure and cut SaaS sprawl. It is one self-hosted platform that replaces seven SaaS tools: Vercel (git-push deployments), PostHog (analytics and session replay), Sentry (error tracking), Pingdom (uptime monitoring), Datadog (OpenTelemetry traces, metrics and logs), Resend (transactional email) and E2B (AI agent sandboxes). Self-hosting is free under MIT / Apache 2.0, with no per-seat fees and no bandwidth bills; the cost is the server you run it on.

For Next.js specifically: a server-rendered Next.js app on Cloudflare now runs on Workers, not Pages. Cloudflare recommends vinext, a Vite plugin that reimplements the Next.js API surface and is still in beta; the OpenNext adapter (@opennextjs/cloudflare) remains supported for existing apps but doesn't support Node.js middleware. Either way the app runs inside Workers' limits, and new Next.js releases reach Cloudflare only after the adapter catches up. Temps detects Next.js from your next.config file and runs it with next start, so App Router, Server Actions, ISR and middleware behave as they do locally. Vercel remains the best managed choice if you prefer a hosted platform and accept per-seat pricing.

If Cloudflare's global edge network is the reason you use Pages, Vercel and Netlify are the closest managed alternatives, because both serve from a global CDN.

Cloudflare Pages Alternatives at a Glance

Temps vs Vercel vs Netlify: Head-to-Head

Vercel and Netlify match Temps on git-push deploys and preview environments, but neither includes error tracking, session replay or uptime monitoring without a separate subscription. For plan-by-plan detail, see Vercel pricing 2026 and Netlify's hidden costs.

Why Teams Look for Cloudflare Pages Alternatives

Cloudflare Pages is excellent at static hosting and tightly integrated with Workers. These are the limits that push teams elsewhere.

Cloudflare Workers Free Tier: 100K Requests/Day

Static asset requests on Pages are free and unlimited, but every dynamic request runs on Workers, and the free plan allows 100,000 requests a day with 10 ms of CPU per request (the often-quoted 10 million is the monthly allowance on the $5 Workers Paid plan). Memory is 128 MB per isolate on every plan. The full list, and what happens when you hit each limit, is in Cloudflare Pages free tier limits.

No Built-in Observability

Cloudflare includes Web Analytics for pageviews, but no error tracking, session replay or uptime monitoring. A typical add-on stack of Plausible Starter ($9/month), Sentry Team ($26/month) and LogRocket (from $176/month) costs about $211/month before engineering time.

Lock-In Through Workers Bindings

Workers now runs much more Node.js code through the nodejs_compat flag, but the platform services are Cloudflare-specific: KV, R2 bindings, D1 and Durable Objects have no drop-in equivalent elsewhere. An app built around them is easy to start on Cloudflare and costly to move off.

1. Temps — Best All-in-One Self-Hosted Alternative

Temps bundles git-push deployments, web analytics, session replay, error tracking, uptime monitoring, OpenTelemetry traces and logs, transactional email and managed databases in one self-hosted platform. Self-hosting is free under MIT / Apache 2.0, with no per-seat fees and no bandwidth bills; the cost is the server. Temps Cloud, a hosted control plane for your own servers, is coming soon from $29/month.

Why Temps for Cloudflare Pages Migrants?

The workflow is familiar: connect a Git repository, push, and get a preview deployment for each pull request. Traffic goes through Pingora, the open-source Rust proxy framework Cloudflare built, running on your own server rather than Cloudflare's network.

Health-Checked Deployments

Before Temps switches traffic to a new deployment, it probes the app every 5 seconds and needs 2 consecutive successful responses. If the app isn't healthy within the startup timeout (5 minutes), the deployment fails and the previous one keeps serving, so a broken build never takes over. Temps doesn't roll back on its own after a deployment has gone live; to go back, you redeploy a previous deployment from the dashboard or CLI. See rollbacks.

What You Replace

Hosting comes on top in both columns: Workers Paid or a managed platform on one side, your server on the other.

Getting Started with Temps

# On your server: install Temps (installs Docker if needed)
curl -fsSL https://temps.sh/deploy.sh | bash

# From your project: deploy with the CLI
bunx @temps-sdk/cli deploy --project my-app -e production

The Next.js deployment guide covers environment variables, health checks and custom domains.

Migrating a Next.js App from Cloudflare to Temps

Moving a Next.js app off Cloudflare is mostly deletion:

1. Remove the Cloudflare adapter. On Workers, remove vinext or @opennextjs/cloudflare and its Wrangler configuration. On a legacy Pages project, remove @cloudflare/next-on-pages and any export const runtime = "edge" lines you added only to satisfy it.
2. Restore Node.js code you worked around. Route handlers rewritten to avoid Node.js APIs, native modules or long execution can go back to plain Node.js, since Temps runs next start on the full runtime.
3. Connect the repository and push. Temps detects Next.js from your next.config file and builds it with your package manager's build script. Push to a branch for a preview, merge to deploy to production.
4. Re-point DNS. Point the domain at your server once the deployment is healthy. Temps provisions a Let's Encrypt certificate for it automatically.
5. Set up observability once. Analytics, error tracking and session replay run on the same platform, instead of three SDKs for three vendors.

The real migration cost is Cloudflare bindings. Swap KV for managed Redis, R2 for S3-compatible storage, D1 for managed Postgres, and replace Durable Objects with a database-backed pattern; standard Next.js code moves without changes.

Limitations

Temps runs on servers you provision, so it is not a global edge network. If you need Cloudflare's PoPs for static asset latency, keep Cloudflare in front of Temps as a CDN, or stay on Pages. Temps has no edge functions.

Temps is also newer than Cloudflare Pages, Vercel or Netlify, and its community is smaller. That is also why it ships deployment and observability together, which the older platforms were not built for. If the largest ecosystem matters most today, weigh that; if you want deployment plus analytics, error tracking and session replay in one platform from day one, that is what Temps is for.

For the feature-by-feature breakdown, see Temps vs Cloudflare Pages.

2. Vercel — Best Managed Cloudflare Pages Alternative

Vercel is the closest managed alternative to Cloudflare Pages for Next.js and React. It is built by the Next.js team, runs functions on Fluid compute, and serves from a global CDN, with the best Next.js developer experience available.

Limitations: Pro is a $20/month platform fee that includes one deploying seat, plus $20 for each extra deploying seat, and CDN traffic past the included 1 TB and 1M requests costs a Flat Rate CDN tier ($20 to $300/month, the default for Pro teams created since 8 September 2026) or from $0.15/GB on demand for older teams. Error tracking and session replay need separate subscriptions. See Vercel pricing 2026 for worked bills.

3. Netlify — Best for Static Sites and Jamstack

Netlify pioneered git-push deployment and remains a standard for static and Jamstack workflows, with Edge Functions, form handling and a large plugin ecosystem. Since April 2026, credit-based Pro is $20/month per team with unlimited members.

Limitations: Usage draws on credits: the Free plan's 300 credits a month is about 15 GB of bandwidth, and bandwidth costs 20 credits per GB. Synchronous functions time out after 60 seconds on every plan. Edge Functions run on Deno, not Node.js. Observability needs separate subscriptions. More in Netlify's hidden costs.

4. Render — Best Managed Full-Stack Alternative

Render runs static sites, web services, background workers and cron jobs from one dashboard, without per-seat fees: the Pro workspace plan is $25/month plus compute, with unlimited seats.

Limitations: No built-in analytics, error tracking or session replay. Free web services spin down after 15 minutes without traffic, so the next request waits for the service to start again, up to about a minute. Only moving the service to a paid instance (from $7/month) removes that.

5. Railway — Best for Rapid Prototyping

Railway is one of the fastest ways to get a new project running: connect a GitHub repository and it detects the runtime and deploys. It has a permanent Free plan with $1 of usage credit a month, a one-time $5 trial credit, Hobby at $5/month and Pro at $20/month per workspace with unlimited seats.

Limitations: Usage beyond the plan credit is metered, so bills move with traffic. No built-in observability. See Railway pricing 2026.

6. Coolify — Best Open-Source Self-Hosted Alternative

Coolify is open source (Apache 2.0) and self-hosted, with 280+ one-click templates and a web UI for managing several servers. It is free to self-host; Coolify Cloud starts at $5/month for two servers.

Limitations: Coolify added opt-in traffic analytics in v4.4 (October 2026), but it has no built-in error tracking, session replay or uptime checks, so those remain separate subscriptions.

Cloudflare Pages vs Alternatives: Key Differences

Static Sites vs Full-Stack Apps

Cloudflare Pages is built for static and Jamstack sites. For full-stack apps with long-running processes, persistent database connections or background workers, Temps, Render or Railway fit better, because Workers limits CPU time and memory per request.

Free Tier Reality Check

• Cloudflare Pages: static hosting is free with unlimited static requests; dynamic requests use the Workers free plan (100K requests/day, 10 ms CPU). Details in Cloudflare Pages free tier limits.
• Vercel: Hobby includes 100 GB of Fast Data Transfer, 1M CDN requests, 1M function invocations and 4 Active CPU-hours a month, with 100 deployments a day and one build at a time. Non-commercial use only.
• Netlify: the Free plan is 300 credits a month (about 15 GB of bandwidth, or 20 production deploys), hard-capped.
• Render: free web services spin down after 15 minutes of inactivity; free Postgres expires after 30 days.
• Railway: Free plan with $1 of usage credit a month, plus a one-time $5 trial.
• Fly.io: new organisations have no free allowance, only a trial (2 machine-hours or 7 days).
• Temps: free software; you pay for the server, for example a Hetzner CX23 at €5.49/month excluding VAT (verified 2026-10-07).

Edge Network vs Single-Region Hosting

Cloudflare Pages serves static assets from Cloudflare's global network. Self-hosted alternatives (Temps, Coolify, Dokploy) run on the servers you choose and need a CDN in front to match that. If global static asset performance is your main requirement, Cloudflare's network is a genuine advantage.

Frequently Asked Questions

What are good Cloudflare Pages alternatives for Next.js?

The strongest Cloudflare Pages alternatives for Next.js in 2026 are Temps, Vercel, Netlify and Railway. Temps is the self-hosted option that bundles deployment with analytics, error tracking, session replay and uptime monitoring; it runs a standard Next.js build with next start, so App Router, Server Actions, ISR and middleware work as they do locally, with no Cloudflare adapter. Vercel is the best managed choice, built by the Next.js team, but charges $20 per deploying seat on Pro plus usage and observability subscriptions. Netlify and Railway also run Next.js well, without per-seat fees on their team plans, but neither bundles observability.

How does Next.js run on Cloudflare in 2026?

Server-rendered Next.js runs on Cloudflare Workers, not Pages. Cloudflare recommends vinext, a Vite plugin that reimplements the Next.js API (currently in beta), and keeps the OpenNext adapter (@opennextjs/cloudflare) supported for existing apps; OpenNext doesn't support Node.js middleware yet. The @cloudflare/next-on-pages adapter, which was Edge-runtime only, is deprecated. Pages remains an option for static Next.js exports.

What is the Cloudflare Workers free tier limit?

The Workers free plan allows 100,000 requests a day with 10 ms of CPU time per request. Workers Paid is $5/month and includes 10 million requests, then $0.30 per additional million. See Cloudflare Pages free tier limits for the full table.

Does Fly.io have a free tier in 2026?

No. New Fly.io organisations get no free allowance, only a trial of 2 machine-hours or 7 days, whichever comes first. After that, Fly.io is pay as you go; the smallest always-on machine costs about $2.19/month.

Can I self-host a Cloudflare Pages alternative?

Yes. Temps and Coolify are the main self-hosted options. Temps includes analytics, error tracking, session replay, uptime monitoring and managed databases. Coolify focuses on deployment with a large one-click template catalogue and added opt-in traffic analytics in v4.4. Both are free to self-host; you pay for the server.

Is Temps a drop-in replacement for Cloudflare Pages?

Temps replaces Cloudflare Pages' deployment workflow (git push, preview, production) but not its edge network. If you rely on Cloudflare's CDN for static asset performance, keep Cloudflare in front of Temps. If what you need is deployments plus observability without vendor lock-in, Temps replaces it directly.

How does Temps pricing compare to Cloudflare Pages?

For teams that need error tracking and session replay, the comparison is the hosting cost plus about $211/month for Plausible, Sentry Team and LogRocket on the Cloudflare side, against the server cost on the Temps side.

Which Cloudflare Pages Alternative Should You Choose?

• Choose Temps if you want git-push deployments plus analytics, error tracking, session replay and uptime monitoring in one self-hosted platform, without per-seat fees.
• Choose Vercel if you build Next.js apps and want the best managed experience on a global network, and accept per-seat pricing and separate observability costs.
• Choose Netlify if you build static or Jamstack sites and want its plugin and form-handling ecosystem.
• Choose Render if you need managed full-stack hosting without per-seat fees and don't need edge performance.
• Choose Coolify if you want open-source self-hosted deployments and will run observability separately.
• Stay on Cloudflare Pages if global static asset performance is your main requirement and your dynamic code fits within Workers' limits.

For a wider list that starts from Vercel instead, see 10 Vercel alternatives for Next.js.