Cloudflare Workers Freemium

Serverless runtime for building and shipping AI backends at the edge

Cloudflare Workers is a serverless platform that runs your code in V8 isolates across 300+ data centers. The free tier allows 100,000 requests per day; the paid plan is $5 per month with 10 million requests included.

What is Cloudflare Workers?

Workers is Cloudflare’s compute product, launched in 2017. You write a JavaScript or TypeScript module, deploy with wrangler deploy, and it runs within milliseconds of most users. No containers, no cold starts measured in seconds — a Worker boots in about 5 ms.

For AI work, Workers matters because of the bindings: Workers AI runs hosted models (Llama, Mistral, Whisper) with no separate API key, Vectorize stores embeddings, D1 is SQLite, R2 is object storage with no egress fee, and Queues handles background jobs.

Product Features

  • V8 isolates — 128 MB memory per invocation, 30 seconds CPU time on paid plans, no container images to build.
  • Workers AI — pay-per-token inference on Cloudflare GPUs; 10,000 Neurons per day free.
  • Vectorize — vector database for RAG, indexes up to 5 million vectors per index.
  • D1 and R2 — SQLite at the edge and S3-compatible storage with zero egress charges.
  • Durable Objects — stateful coordination for chat rooms, rate limits, agent sessions.
  • Cron triggers and Queues — scheduled jobs and async pipelines without a server.

Product Highlights

Latency is the headline. A request from Tokyo to a Worker in Tokyo never crosses an ocean. That changes how you design an AI app: stream tokens from the edge, cache embeddings next to the user, and skip the region-pinning headache.

Pricing is unusual in a good way. Free plan: 100,000 requests a day, 10,000 Neurons a day for Workers AI, 5 GB on R2. Paid: $5 per month for 10 million requests, then $0.30 per million. R2 charges $0.015 per GB-month and nothing for egress.

The catch is the runtime. It is not Node.js. No native modules, no arbitrary binaries, no long-running process. Anything CPU-heavy (video transcoding, large model fine-tuning) belongs on a GPU host elsewhere.

Who should use it (and who should not)

Good fit: teams shipping an API or chatbot front door where p95 latency and cost per request matter. Bad fit: teams with a Laravel or Django monolith, or workloads needing 10+ minutes of CPU — that is Containers or a plain VM.

Use Cases

  • A RAG chatbot that embeds queries in Vectorize and streams answers from Workers AI.
  • Webhook receivers for Stripe or Slack that must respond in under 100 ms.
  • Image resizing and moderation on upload before hitting R2.
  • Per-key rate limiting with Durable Objects in front of an expensive model endpoint.
  • Geo-routing requests to the nearest inference provider.

Quick Summary

  • Workers is serverless JavaScript on Cloudflare’s edge network.
  • Free: 100,000 requests per day and 10,000 AI Neurons per day.
  • Paid: $5 per month for 10 million requests, then $0.30 per million.
  • It is not Node.js; native modules and long CPU jobs are off the table.
  • Best fit is latency-sensitive AI APIs and webhook endpoints.