Cloudflare Workers

Name: Cloudflare Workers
Brand: Cloudflare
Rating: 4.8 (10 reviews)

Leader

At Cloudflare, we have our eyes set on an ambitious goal — to help build a better Internet.

Est 2009|Valuation $112.6B|Raised $3B

LinkedIn 1.2M|Website|Web traffic 91.2M|FTEs 5,483|HQ San Francisco, CA

MarketsWeb Application & API Protection (WAAP)Application Hosting Platforms Cloud Infrastructure Providers (IaaS/PaaS)

Platform CoversFeature Delivery & Experimentation API Management Performance Testing

01Competitive Landscape

Narrative analysis

Cloudflare Workers vs Vercel - Areas where Cloudflare Workers can be advantageous: global edge execution model and CPU-time billing combined with Cloudflare's CDN/security features can be cost-effective for request-munging and caching-heavy workloads. - Areas where Vercel can be advantageous: integration with frameworks (notably Next.js) and developer workflow features such as previews and platform conventions. Cloudflare Workers vs Netlify Edge - Netlify documents that when a cached response is served, edge functions may not be invoked, which affects invocation-based billing differently than architectures that place logic before the cache. This distinction can influence design choices for caching-sensitive workloads. Cloudflare Workers vs Fastly Compute@Edge - Fastly provides edge compute offerings; public pricing for compute can be less transparent and may require sales engagement, which complicates direct self-serve cost comparisons. Sources: - Official vendor pricing and documentation (Cloudflare Workers) - Official vendor pricing information (Vercel) - Official vendor edge usage and billing documentation (Netlify) - Official vendor pricing information (Fastly)

Market perception / analyst coverage

Press coverage at Workers' launch described Cloudflare's expansion into programmable edge compute.
Industry reports and analyst coverage reference Workers among FaaS and edge compute platforms; some reports are licensed and subject to access restrictions.

Sources:

Technology press coverage (launch announcement)
Technology press coverage (product out of beta)
Licensed analyst report (industry research firm)

	Cloudflare Workers	Vercel (Functions / Edge)	Netlify Edge
Starting Price	Workers Paid: Published minimum plan fee plus usage-based charges; Free tier available	Paid plans with team/member pricing; usage add-ons vary	Free tier available; paid plans use credits and team/member pricing
Key Meter	Requests + CPU time (per vendor documentation); platform indicates no separate egress fees for Workers	Requests/invocations + platform usage; bandwidth can be a significant factor	Bandwidth/credits model; edge invocations typically not charged when served from cache per vendor documentation
Common use cases	Edge middleware, globally distributed APIs, Cloudflare-integrated stacks	Next.js-centric teams prioritizing framework integration and deployment workflows	Git-based workflows, Jamstack/static sites with edge personalization
Primary advantages	CPU-time billing for short tasks; integrated CDN/security features	Strong integration with Next.js and project preview workflows	Git-based deployment workflows and explicit caching behavior that can avoid edge invocation costs on cache hits
Primary limitations	Runtime differences from Node; per-invocation limits; reliance on Cloudflare-specific primitives may increase migration effort	Pricing complexity at scale and multiple metered components	Bandwidth and plan constraints; enterprise features may require higher-tier plans

01Competitive Landscape

Narrative analysis

Cloudflare Workers vs Vercel

Areas where Cloudflare Workers can be advantageous: global edge execution model and CPU-time billing combined with Cloudflare's CDN/security features can be cost-effective for request-munging and caching-heavy workloads.
Areas where Vercel can be advantageous: integration with frameworks (notably Next.js) and developer workflow features such as previews and platform conventions.

Cloudflare Workers vs Netlify Edge

Netlify documents that when a cached response is served, edge functions may not be invoked, which affects invocation-based billing differently than architectures that place logic before the cache. This distinction can influence design choices for caching-sensitive workloads.

Cloudflare Workers vs Fastly Compute@Edge

Fastly provides edge compute offerings; public pricing for compute can be less transparent and may require sales engagement, which complicates direct self-serve cost comparisons.

Sources:

Official vendor pricing and documentation (Cloudflare Workers)
Official vendor pricing information (Vercel)
Official vendor edge usage and billing documentation (Netlify)
Official vendor pricing information (Fastly)

Market perception / analyst coverage

Press coverage at Workers' launch described Cloudflare's expansion into programmable edge compute.
Industry reports and analyst coverage reference Workers among FaaS and edge compute platforms; some reports are licensed and subject to access restrictions.

Sources:

Technology press coverage (launch announcement)
Technology press coverage (product out of beta)
Licensed analyst report (industry research firm)

	Cloudflare Workers	Vercel (Functions / Edge)	Netlify Edge
Starting Price	Workers Paid: Published minimum plan fee plus usage-based charges; Free tier available	Paid plans with team/member pricing; usage add-ons vary	Free tier available; paid plans use credits and team/member pricing
Key Meter	Requests + CPU time (per vendor documentation); platform indicates no separate egress fees for Workers	Requests/invocations + platform usage; bandwidth can be a significant factor	Bandwidth/credits model; edge invocations typically not charged when served from cache per vendor documentation
Common use cases	Edge middleware, globally distributed APIs, Cloudflare-integrated stacks	Next.js-centric teams prioritizing framework integration and deployment workflows	Git-based workflows, Jamstack/static sites with edge personalization
Primary advantages	CPU-time billing for short tasks; integrated CDN/security features	Strong integration with Next.js and project preview workflows	Git-based deployment workflows and explicit caching behavior that can avoid edge invocation costs on cache hits
Primary limitations	Runtime differences from Node; per-invocation limits; reliance on Cloudflare-specific primitives may increase migration effort	Pricing complexity at scale and multiple metered components	Bandwidth and plan constraints; enterprise features may require higher-tier plans