Blog · Cloudflare platform

What the Cloudflare Developer Platform Includes

Cloudflare is more than a CDN. This guide maps Workers, Pages, D1, R2, KV, Queues, and Workers AI for teams deciding where an app should run.

A network, and a place to build

Cloudflare is widely known as the network in front of a website: DNS, TLS, caching, and a global anycast edge that absorbs traffic before it reaches an origin. The Cloudflare Developer Platform is the set of products teams use when they want to build on that network. It covers compute, data, object storage, background work, and AI services that run close to users.

That scope is what people mean by edge computing in a Cloudflare architecture. A CDN configuration speeds up an origin you already operate. Workers and Pages are a serverless place to run the application itself. CF Ready is a community open-source checklist for that second decision. It is not affiliated with Cloudflare, Inc.

Compute with Workers and Pages

Cloudflare Workers is a serverless runtime for JavaScript, TypeScript, and WebAssembly. Handlers run on the edge network, so you deploy code rather than patching a virtual machine. Request routing, small APIs, scheduled tasks, and middleware-style logic fit the model well. There is no long-lived server to SSH into, which is why code that assumes a local disk, a background daemon, or a Node.js-only API needs a review before launch.

Cloudflare Pages hosts static sites and full-stack projects. Pages Functions run on the Workers runtime, so the programming model stays familiar when a site needs server-side behavior. Teams often start on Pages for a front end and add a Worker when they need a dedicated API, a cron trigger, or a route that should live outside the site project. Both are serverless: you ship a build, and the platform runs it.

Data services teams actually wire up

D1 is Cloudflare's serverless SQL database, built on SQLite. It fits relational rows with modest operational overhead: accounts, sessions, and content records. This blog stores its articles in D1. If your current system depends on a large Postgres or MySQL deployment, extensions, or long multi-statement transactions, design for D1 explicitly. Treat it as a product choice, and budget a migration plan for queries that will not move unchanged.

R2 is S3-compatible object storage for uploads, exports, and public assets. KV is a low-latency key-value store for configuration, feature flags, and other small values read at the edge. Durable Objects give you strongly consistent coordination for one entity at a time, such as a chat room, a rate limiter, or a collaborative document. Queues let a Worker hand slower work to a consumer so the user-facing request can finish without doing every step inline.

Where AI fits on the same platform

Workers AI runs model inference on Cloudflare's network, which helps when a feature should stay next to the rest of the app. AI Gateway is a control point for calls to Workers AI or to third-party models, including logging and caching. Vectorize stores embeddings when you need retrieval. These services are optional. Plenty of production sites never call a model, and hosting a site is a separate question from whether your public pages explain themselves to AI crawlers.

Keep the two ideas apart during planning. Platform AI is how your product calls models. AI readiness, in the CF Ready sense, is whether robots.txt, a sitemap, llms.txt, and API descriptions give assistants an accurate map of the site. You can need one, the other, or both.

Judge readiness before the first production deploy

Before a cutover, list the runtime assumptions in the repository. Filesystem writes, child processes, native addons, and in-process background jobs are common blockers on Workers. Committed secrets, a missing sitemap, and thin metadata are quieter problems that still surface on launch day. Edge computing removes a class of server maintenance, and it makes those code-level assumptions your responsibility to find early.

A practical next step is to scan the project with CF Ready. Use the Web Agent at https://ready.orangecloud.vn/app/ or run npx @orangecloud/cf-ready scan from the project root. The scan does not deploy anything. It writes a readiness report so blockers are tickets, not an outage.