Cloudflare One, Zero Trust, WARP and Cloudflare WAN: what the names mean in 2026

Who this is for: engineers and buyers who meet old and new names in the same project and need to know whether they are looking at one product or several. This is a naming reference, not a design guide, and it is reviewed quarterly and whenever Cloudflare renames another product.

What is the difference between Cloudflare One and Zero Trust?#

Cloudflare One is the platform; Zero Trust is the model it implements. Cloudflare’s glossary defines Cloudflare One as its SASE platform, which includes Zero Trust and network services. The Cloudflare One documentation describes Zero Trust as a model built on least privilege, where every request is authenticated and authorized based on identity and context before access is granted.

The two terms overlap in practice: the glossary still carries a “Cloudflare Zero Trust” entry, and many buyers search for it. On this site, “Cloudflare Zero Trust” appears in headlines and “Cloudflare One” where the whole platform is meant. The products under Cloudflare One include Access, Cloudflare Tunnel, the Secure Web Gateway, the Cloudflare One Client, remote browser isolation, CASB, data loss prevention, email security, Cloudflare Mesh, and Cloudflare WAN.

The Cloudflare One name map#

The Cloudflare One name map lists each old name, its current name, what the product does, and where the old name still appears.

Not renamed: Access, Gateway (also called the Secure Web Gateway), Cloudflare Tunnel, and cloudflared. Magic Transit keeps its name; its product page is still titled Cloudflare Magic Transit.

What changed, and when?#

Three changes carry the dates. On February 17, 2026, the changelog post “Cloudflare One Product Name Updates” listed the seven Magic-family renames in the table. On April 14, 2026, the post “Introducing Cloudflare Mesh” announced that WARP Connector is now Cloudflare Mesh, that existing connectors are now called mesh nodes, and that the node limit rose from 10 to 50 per account. The client rename has no dated announcement: Cloudflare’s release notes switched from “WARP client” to “Cloudflare One Client” between March 10 and April 2, 2026.

What did not change?#

For the February renames, Cloudflare stated that no action is required and that functionality, existing configurations, and billing remain the same. For Mesh, Cloudflare says existing deployments continue to work and no migration is required; it does not mention billing. For the client rename, no equivalent statement was found, so this article does not claim one.

The documentation still uses WARP names inside the product. The Cloudflare One Client page keeps the WARP daemon and describes warp-cli as the command-line interface for managing the client; the graphical interface is now called the Cloudflare One Client GUI. Scripts and runbooks that call warp-cli are not obsolete because of the new name.

How do you read an older guide?#

Translate the names first, then check the steps. Four checks:

1. Look up every product name in the table. If a guide says “Magic WAN”, read “Cloudflare WAN” and check the current page, not the old URL.
2. If a guide uses “WARP Connector”, read “Mesh node” and follow the current Mesh documentation, remembering that Mesh is in beta.
3. Keep command names and file paths as written until the current documentation changes them.
4. Check the guide’s date against February 17, 2026, March to April 2026 for the client, and April 14, 2026. Anything older uses the old names.

Mesh and Tunnel remain different tools. Cloudflare’s Mesh page says to use Mesh for bidirectional private IP connectivity and stable, long-lived connections, and Tunnel to publish specific applications, hostnames, or IP routes through an outbound-only connector.