Cloudflare: plan deployment by product type

Match edge code, static sites, stateful services, and storage to the right Wrangler workflow.

Skills

Use this workflow only when the user asks to host or deploy on Cloudflare. Select Workers, Pages, Durable Objects, Workflows, containers, or a data product based on the requirement, then open its focused reference instead of forcing every feature into a Worker. Before deployment, inspect the repository configuration, target environment, and `npx wrangler whoami` result. If unauthenticated, explain local OAuth or CI-token options; never read or print the token. A deploy command publishes to an external account, and creating D1, KV, or R2 resources persists infrastructure, so stay within the task’s authorization. Verify the deployment output and URL; a local build is not proof of production success.

Permissions

Prerequisites

The user asks to deploy, host, or configure a service on Cloudflare; identify the product and target account first.
Before publishing, check authentication with `npx wrangler whoami` and confirm the target environment.

Permissions

May inspect the project and use Wrangler; deploying, creating resources, or changing account configuration affects an external Cloudflare account.
OAuth login and CI-token setup change authentication state; never expose secrets or publish without authorization.

Limitations

Select among Workers, Pages, Durable Objects, Workflows, and storage by use case, then read the matching official reference. A generated scaffold does not prove a deployment succeeded.