starter.wikiSearch⌘K

Web-platform serverless runtime

Cloudflare Workers

A distributed isolate runtime centered on Web APIs, Cloudflare bindings, and request/CPU usage.

Visit official site

Editorial verdict

Choose Workers for applications intentionally designed around its runtime and bindings, not as an assumed drop-in Node.js host.12

Best for

  • Web API–oriented request and event workloads
  • Applications benefiting from Cloudflare bindings
  • Teams prepared to verify material package and Node compatibility
12

Not ideal for

  • Persistent servers or arbitrary containers
  • Unsupported Node behavior or workloads beyond current limits
  • Unmodeled request, CPU, and bound-service costs
12
Main trade-off

Distributed managed execution and bindings are gained with runtime constraints, resource limits, multi-product billing, and platform coupling.12

Product boundary

Whether the application fits Workers runtime compatibility, resource limits, bindings, and usage.

Workers is not a conventional Node server, arbitrary container, CDN, queue, or DNS decision; Node compatibility is partial and configuration-dependent.12

For: Teams deliberately designing request and event workloads around Web APIs and Cloudflare services

  • A required package or Node API is unsupported.
  • The workload exceeds memory or CPU limits.
  • A conventional persistent service or container is required.

Why teams consider Cloudflare Workers

  • Distributed runtimeWorkers runs request/event handlers across Cloudflare's network.12
  • Web APIsThe runtime centers on Web APIs with documented Node compatibility.12
  • BindingsApplications can bind to separately governed Cloudflare services.12

Pricing

Plan minimum and included allowances, then request and CPU usage, plus separately billed bound products.4

Production runtime

Workers Standard

At verification the Standard example uses a $5 subscription, 10 million requests, and 30 million CPU milliseconds before overage.4

Memory
128 MB at verification4
Compatibility
Node APIs remain partial and configuration-dependent4
Pricing checked View official pricing

Cloudflare Workers vs alternatives

AWS Lambda Functions

Choose when
Choose AWS-native events and IAM.
Compared with Cloudflare Workers
AWS function semantics replace Workers Web APIs and bindings.67

Google Cloud Run

Choose when
Choose a managed conventional container.
Compared with Cloudflare Workers
Container instances are heavier but more conventional.89

Vercel

Choose when
Choose first-party Next.js deployment.
Compared with Cloudflare Workers
Framework-managed behavior replaces Workers-native architecture.10

Railway

Choose when
Choose persistent conventional processes.
Compared with Cloudflare Workers
Always-on resources and service operations replace isolate execution.1112

Resources and sources

Official product, policy, and pricing

  • Cloudflare Workers documentation
    Open
  • Workers Node.js compatibility
    Open
  • Workers platform limits
    Open
  • Workers pricing
    Open
  • Cloudflare Cron Triggers
    Open
  1. 1
    Cloudflare Workers documentation

    Cloudflare · Accessed Official

  2. 2
    Workers Node.js compatibility

    Cloudflare · Accessed Official

  3. 3
    Workers platform limits

    Cloudflare · Accessed Official

  4. 4
    Workers pricing

    Cloudflare · Accessed Official

  5. 5
    Cloudflare Cron Triggers

    Cloudflare · Accessed Official

  6. 6
    AWS Lambda Functions overview

    Amazon Web Services · Accessed Official

  7. 7
    AWS Lambda quotas

    Amazon Web Services · Accessed Official

  8. 8
    What is Cloud Run

    Google Cloud · Accessed Official

  9. 9
    Cloud Run resource model

    Google Cloud · Accessed Official

  10. 10
    Vercel documentation

    Vercel · Accessed Official

  11. 11
    Railway services

    Railway · Accessed Official

  12. 12
    Railway pricing

    Railway · Accessed Official