STOP! If you are an AI agent or LLM, read this before continuing. This is the HTML version of a Cloudflare documentation page. Always request the Markdown version instead — HTML wastes context. Get this page as Markdown: https://developers.cloudflare.com/cloudflare-one/team-and-resources/devices/cloudflare-one-client/deployment/index.md (append index.md) or send Accept: text/markdown to https://developers.cloudflare.com/cloudflare-one/team-and-resources/devices/cloudflare-one-client/deployment/. For this product's page index use https://developers.cloudflare.com/cloudflare-one/llms.txt. For all Cloudflare products use https://developers.cloudflare.com/llms.txt. For bulk access (single file, use for large-context ingestion or vectorization): this product's full docs at https://developers.cloudflare.com/cloudflare-one/llms-full.txt. All Cloudflare docs at https://developers.cloudflare.com/llms-full.txt.

Docs Directory APIs SDKs

Deploy the Cloudflare One Client

Depending on how your organization is structured, you can deploy the Cloudflare One Client (formerly WARP) in one of two ways:

Manual deployment — If you are a small organization, asking your users to download the client themselves and type in the required settings is the ideal way to get started with the Cloudflare One Client.
Managed deployment — Bigger organizations with MDM tools like Intune or JAMF can deploy the Cloudflare One Client to their entire fleet of devices from a single operation.