8 Best Cloudflare Workers & Pages Alternatives (2026)

The closest alternatives to Cloudflare Workers & Pages are AWS Amplify Hosting, Coolify, Deno Deploy and Dokploy, with 4 more below. Each shares a comparison category with it, so every rationale here names both tools' real values. Cloudflare Workers & Pages is 12th of 13 on Exit friction (4) — usually where a switch starts.

Website Docs Source Cloudflare Workers & Pageslogo & brand assets Vercel alternatives

Why do people look for Cloudflare Workers & Pages alternatives?

Most people searching for Cloudflare Workers & Pages alternatives are not shopping — they already run it and something has stopped fitting. That something is usually a specific number rather than a feeling, so this page starts from the fields where Cloudflare Workers & Pages genuinely trails the rosters it appears in, and only then covers the reasons that never show up in a table.

The measured reasons.

Exit friction — 4, 12th of 13. Coolify records 1.
Build minutes incl. — 3,000 min/mo, 3rd of 5. Netlify records 25,000 min/mo.
Image opt billing — metered, 10th of 13. Netlify records included.

Any one of those is enough on its own if you sized your architecture around it. None of them is enough if you didn't — which is why the list is short and specific rather than a general case against Cloudflare Workers & Pages.

The reasons that never make it into a table. A price rise after a funding round. A licence change that turns a self-host into a subscription. A region you now need and they do not have. An acquisition. A support experience that quietly degrades. None of those are fields, and all of them move teams — which is why every entry below links back to Vercel alternatives, where the full field set and its sources live. The ones we catch get logged on the Cloudflare Workers & Pages timeline.

How the shortlist is ordered. Every tool below shares at least one comparison category with Cloudflare Workers & Pages, sorted by how many categories the two overlap in. There is no editorial ranking, no sponsorship and no affiliate link — the order is the overlap count, and the rationale under each is generated from the two tools' own cells, so it names real values rather than adjectives.

1.AWS Amplify Hosting

AWS Amplify Hosting — Managed Next.js and static hosting inside AWS, billed per GB with no spend cap. It meets Cloudflare Workers & Pages in Vercel alternatives. It is ahead on Exit friction (3 against 4), Monorepo support (Yes against Partial) and GA year (2018 against 2017). What you give up: Cron jobs (No, where Cloudflare Workers & Pages records Yes) and Free tier (2, where Cloudflare Workers & Pages records 5). Best for apps whose data already lives in AWS, especially in Sydney. Only worth it when the rest of the stack is already in AWS and the app needs to sit next to your data in ap-southeast-2. Otherwise you are paying Vercel-tier bandwidth prices for worse cold starts, no cron, and CloudWatch as your logging product.

Where AWS Amplify Hosting and Cloudflare Workers & Pages actually differ

Cron jobs: NoCloudflare Workers & Pages: Yes
Free tier: 2Cloudflare Workers & Pages: 5
Pricing clarity: 2Cloudflare Workers & Pages: 4
CLI quality: 2Cloudflare Workers & Pages: 4
Self-hostable: NoCloudflare Workers & Pages: Partial
Price @ 1 TB: $155 /moCloudflare Workers & Pages: $5 /mo

AWS Amplify Hosting profile Compare in Vercel alternatives

2.Coolify

Coolify — Open-source self-hosted PaaS: git push to your own server, with previews and cron. It meets Cloudflare Workers & Pages in Vercel alternatives. It is ahead on Exit friction (1 against 4), Overage behaviour (throttle against bill) and Self-hostable (Yes against Partial). What you give up: WAF & DDoS (No, where Cloudflare Workers & Pages records Yes) and Funding (oss-community, where Cloudflare Workers & Pages records public). Best for teams that already run servers and resent the Vercel invoice. Astonishingly complete for free software — previews, cron, TLS and databases all work — and one of only two rows where a traffic spike degrades instead of billing. What you take on is the pager, the disk-space alerts and the fact that nobody is coming to help at 3am.

Where Coolify and Cloudflare Workers & Pages actually differ

Exit friction: 1Cloudflare Workers & Pages: 4
WAF & DDoS: NoCloudflare Workers & Pages: Yes
Overage behaviour: throttleCloudflare Workers & Pages: bill
Funding: oss-communityCloudflare Workers & Pages: public
CLI quality: 2Cloudflare Workers & Pages: 4
Runtime model: containerCloudflare Workers & Pages: edge-only

Coolify profile Compare in Vercel alternatives

3.Deno Deploy

Deno Deploy — Web-standard JavaScript at the edge, with built-in OpenTelemetry and a global KV. It meets Cloudflare Workers & Pages in Vercel alternatives. It is ahead on Exit friction (2 against 4), Observability (included-full against included-basic) and GA year (2021 against 2017). What you give up: Next.js parity (basic, where Cloudflare Workers & Pages records most) and Self-hostable (No, where Cloudflare Workers & Pages records Partial). Best for web-standard TypeScript services and APIs. The best out-of-the-box observability story on this page and a genuinely pleasant runtime if you write web-standard JavaScript. It is also the smallest platform here, with a pricing model that has been rebuilt more than once: fine for services, risky as the foundation of a business.

Where Deno Deploy and Cloudflare Workers & Pages actually differ

Exit friction: 2Cloudflare Workers & Pages: 4
Next.js parity: basicCloudflare Workers & Pages: most
Self-hostable: NoCloudflare Workers & Pages: Partial
WAF & DDoS: PartialCloudflare Workers & Pages: Yes
Pricing clarity: 3Cloudflare Workers & Pages: 4
Observability: included-fullCloudflare Workers & Pages: included-basic

Deno Deploy profile Compare in Vercel alternatives

4.Dokploy

Dokploy — Open-source self-hosted PaaS on Docker Swarm, with multi-node clustering built in. It meets Cloudflare Workers & Pages in Vercel alternatives. It is ahead on Exit friction (1 against 4), Overage behaviour (throttle against bill) and GA year (2024 against 2017). What you give up: WAF & DDoS (No, where Cloudflare Workers & Pages records Yes) and Funding (oss-community, where Cloudflare Workers & Pages records public). Best for self-hosters who need more than one node from day one. Coolify's architecture argument in reverse: Docker Swarm underneath means multi-node clustering and rolling deploys across several boxes with no extra tooling. Younger, smaller ecosystem, fewer templates — pick it over Coolify specifically when you expect to outgrow one server.

Where Dokploy and Cloudflare Workers & Pages actually differ

Exit friction: 1Cloudflare Workers & Pages: 4
WAF & DDoS: NoCloudflare Workers & Pages: Yes
Overage behaviour: throttleCloudflare Workers & Pages: bill
Funding: oss-communityCloudflare Workers & Pages: public
CLI quality: 2Cloudflare Workers & Pages: 4
Runtime model: containerCloudflare Workers & Pages: edge-only

Dokploy profile Compare in Vercel alternatives

5.Fly.io

Fly.io — Firecracker microVMs in 35+ regions including Sydney, driven from the CLI. It meets Cloudflare Workers & Pages in Vercel alternatives. It is ahead on Exit friction (2 against 4), Monorepo support (Yes against Partial) and CLI quality (5 against 4). What you give up: Free tier (2, where Cloudflare Workers & Pages records 5) and Self-hostable (No, where Cloudflare Workers & Pages records Partial). Best for australian or multi-region apps that need compute near users. The right answer for Australian teams who want containers: the only host in this roster with real Sydney compute and cheap egress in the same product. The cost is that cron, previews and observability are patterns you assemble rather than features you switch on.

Where Fly.io and Cloudflare Workers & Pages actually differ

Exit friction: 2Cloudflare Workers & Pages: 4
Free tier: 2Cloudflare Workers & Pages: 5
Self-hostable: NoCloudflare Workers & Pages: Partial
Runtime model: containerCloudflare Workers & Pages: edge-only
Preview deploys: PartialCloudflare Workers & Pages: Yes
Cron jobs: PartialCloudflare Workers & Pages: Yes

Fly.io profile Compare in Vercel alternatives

6.Hetzner + Coolify

Hetzner + Coolify — The DIY baseline: a €4 CX22 running Coolify, with 20 TB of traffic included. It meets Cloudflare Workers & Pages in Vercel alternatives. It is ahead on Exit friction (1 against 4), Self-hostable (Yes against Partial) and Monorepo support (Yes against Partial). What you give up: Sydney region (No, where Cloudflare Workers & Pages records Yes) and Free tier (1, where Cloudflare Workers & Pages records 5). Best for benchmarking whether a managed host is worth its markup. The number every managed host is implicitly arguing against: about $5 a month with 20 TB of traffic included and an overage rate of €1/TB. Nothing scales automatically, there is no Australian region and the pager is yours — but you should know what the floor costs before agreeing to sit above it. Note that we carry Hetzner + Coolify as the do-it-yourself baseline in that roster — the "what if we just ran this ourselves" reference point. The honest answer is usually that it is cheaper and considerably more work.

Where Hetzner + Coolify and Cloudflare Workers & Pages actually differ

Exit friction: 1Cloudflare Workers & Pages: 4
Sydney region: NoCloudflare Workers & Pages: Yes
Free tier: 1Cloudflare Workers & Pages: 5
CLI quality: 2Cloudflare Workers & Pages: 4
Runtime model: containerCloudflare Workers & Pages: edge-only
Funding: bootstrappedCloudflare Workers & Pages: public

Hetzner + Coolify profile Compare in Vercel alternatives

7.Netlify

Netlify — The original Jamstack host: strong build pipeline, punishing bandwidth overage. It meets Cloudflare Workers & Pages in Vercel alternatives. It is ahead on Build minutes incl. (25,000 min/mo against 3,000 min/mo), Image opt billing (included against metered) and Exit friction (3 against 4). What you give up: Bandwidth price ($550 /TB, where Cloudflare Workers & Pages records $0 /TB) and Self-hostable (No, where Cloudflare Workers & Pages records Partial). Best for content sites with steady, forecastable traffic. A very good build pipeline attached to the worst egress pricing in the category. If your traffic is predictable and modest it is a fine Vercel substitute; if it is spiky, the $55-per-100 GB overage is a documented hazard rather than a theoretical one.

Where Netlify and Cloudflare Workers & Pages actually differ

Bandwidth price: $550 /TBCloudflare Workers & Pages: $0 /TB
Build minutes incl.: 25,000 min/moCloudflare Workers & Pages: 3,000 min/mo
Image opt billing: includedCloudflare Workers & Pages: metered
Self-hostable: NoCloudflare Workers & Pages: Partial
Free tier: 3Cloudflare Workers & Pages: 5
Sydney region: PartialCloudflare Workers & Pages: Yes

Netlify profile Compare in Vercel alternatives

8.Northflank

Northflank — Container platform with bring-your-own-cloud, GPUs and a sandbox-shaped API. It meets Cloudflare Workers & Pages in Vercel alternatives. It is ahead on Exit friction (2 against 4), Monorepo support (Yes against Partial) and Image opt billing (byo against metered). What you give up: Runtime model (container, where Cloudflare Workers & Pages records edge-only) and Free tier (3, where Cloudflare Workers & Pages records 5). Best for teams that need workloads inside their own cloud account for compliance. The most capable platform on this page that nobody shortlists. Preview environments and jobs beat Railway's, and bring-your-own-cloud is the only route to Sydney compute under a managed control plane. Its published pricing is the least legible thing about it.

Where Northflank and Cloudflare Workers & Pages actually differ

Exit friction: 2Cloudflare Workers & Pages: 4
Runtime model: containerCloudflare Workers & Pages: edge-only
Free tier: 3Cloudflare Workers & Pages: 5
Sydney region: PartialCloudflare Workers & Pages: Yes
WAF & DDoS: PartialCloudflare Workers & Pages: Yes
Price @ 1 TB: $120 /moCloudflare Workers & Pages: $5 /mo

Northflank profile Compare in Vercel alternatives

How this list was built

There is no editorial ranking on this page and no sponsorship behind it. The order is mechanical: every tool that shares a comparison category with Cloudflare Workers & Pages, sorted by how many categories the two overlap in. A tool that meets Cloudflare Workers & Pages in three rosters sits above one that meets it in a single roster, because more overlap means the comparison is more like-for-like.

The rationale under each entry is composed from the two tools' own cells. Where they differ on a field we score, the sentence names both values and the unit. Where they don't differ, it says so instead of manufacturing a distinction — which is why some entries are short.

Values, sources and verification dates all live on the category tables: Vercel alternatives. If a figure here disagrees with a vendor's current pricing page, the vendor is right and we are stale.

Still deciding whether to move at all? The Cloudflare Workers & Pages profile has the when-to-use and when-not-to-use blocks, and the Cloudflare Workers & Pages timeline has the dated changes that usually trigger a migration.