Overview
Cloudflare Tunnel connects a server, network, or local service to Cloudflare through an outbound-only connection. You install Cloudflare’s lightweight cloudflared daemon on infrastructure you control; it then creates persistent connections to Cloudflare’s global network, so your origin does not need a publicly routable IP or an inbound listener. Cloudflare documents the public-application version as available on all plans, while its Cloudflare One documentation covers private networking and Zero Trust scenarios (public application overview, private-networking overview).
The connection model is useful when you want to keep firewall ingress closed. Cloudflare says traffic can flow to HTTP servers, APIs, SSH servers, remote desktops, and other supported protocols through the tunnel. For public applications, traffic can receive Cloudflare services such as CDN caching, WAF, Bot Management, and DDoS protection (product documentation).
Key Features
- Outbound-only origin connectivity:
cloudflaredinitiates the connection from your environment, so the documented setup does not require opening inbound firewall ports (how it works). - Public hostname routing: You can map a hostname such as
app.example.comto a local service and route HTTP, HTTPS, TCP, SSH, RDP, and other documented protocols (routing documentation). - Private networking and Zero Trust: Cloudflare documents Tunnel as a VPN-replacement and private-network-access component in Cloudflare One, including access to private origins through WARP or
cloudflaredworkflows (Cloudflare One Tunnel). - High availability: Each tunnel maintains four long-lived connections to two Cloudflare data centers, and Cloudflare documents up to 25 active
cloudflaredreplicas per tunnel in its account limits (architecture, limits). - Quick Tunnels: For testing,
cloudflared tunnel --urlcan create a temporarytrycloudflare.comURL without a Cloudflare account or domain (Quick Tunnels). - Platform-scale tunnel capacity: Tunnels for Platforms uses the same daemon, API, and dashboard and supports capacity beyond the default account allowance (Tunnels for Platforms).
Use Cases
Cloudflare Tunnel fits publishing a service running on a private server, protecting an origin while keeping its public IP undisclosed, connecting a remote office or private network to Cloudflare One, and giving authorized users access to internal SSH or RDP services. It can also connect Workers to private databases and APIs through Workers VPC, serve as an origin endpoint for Cloudflare Load Balancing, and provide temporary preview or development URLs through Quick Tunnels (documented use cases, Workers VPC integration). Tunnels for Platforms specifically documents one-tunnel-per-customer SaaS, IoT devices, ephemeral environments, and AI or agent platforms (platform use cases).
Best for
Cloudflare Tunnel is best for teams already using Cloudflare that want a managed edge in front of services hosted behind NAT, firewalls, private networks, or changing infrastructure. It is also a strong fit for developers who need a fast local demo URL, and for organizations that want Cloudflare One policies around private applications. It is less suitable when the requirement is a wholly self-contained tunnel control plane: the documented architecture depends on connections from cloudflared to Cloudflare’s network.
Alternatives
ngrok is a closer alternative for developer-focused public endpoints and local development tunnels, but it is not the same Cloudflare One private-network and edge-security platform. Tailscale is primarily a mesh VPN and identity-based private connectivity product, so it is a better comparison for device-to-device or team-network access than for publishing a public application through Cloudflare’s edge. Hookdeck focuses on receiving, inspecting, replaying, and routing webhooks; it is not a general-purpose origin tunnel or private-network connector.
Pricing
Cloudflare’s public Tunnel documentation says Cloudflare Tunnel is available on all plans (official overview). The account-limits documentation lists 1,000 cloudflared tunnels per account as the default limit (account limits). For deployments above that allowance, Cloudflare’s official Tunnels for Platforms page states that the first 1,000 tunnels remain included and each additional tunnel costs $4.50 per tunnel per month (pricing details). The page also says inactive tunnels count toward the limit. Cloudflare’s Zero Trust pricing page advertises a free plan, but the reviewed page does not provide a Tunnel-specific per-user price or a complete Tunnel-specific free-plan allowance (Zero Trust pricing).
Frequently Asked Questions
1. Does Cloudflare Tunnel require a public IP address?
No. Cloudflare documents an outbound-only model in which cloudflared connects from your infrastructure to Cloudflare, allowing the origin to remain without a publicly routable IP (official explanation).
2. What software runs on my server?
You run cloudflared, Cloudflare’s Tunnel client and daemon. The official repository documents standalone binaries, a Docker image, Debian and RPM packages, Homebrew installation, and building from source (cloudflared repository).
3. Can I use a Quick Tunnel in production?
Cloudflare says Quick Tunnels are for testing and development, not production. They have no uptime guarantee, support up to 200 in-flight requests, do not support Server-Sent Events, and receive a new hostname each time (Quick Tunnel limitations).
4. Is cloudflared open source?
The official cloudflare/cloudflared GitHub repository identifies the project as licensed under Apache-2.0. This confirms the client repository’s license; it does not mean the Cloudflare-hosted edge service can be self-hosted (repository).
5. What are the documented account limits?
Cloudflare lists 1,000 tunnels per account, 50,000 combined CIDR and hostname routes, 25 active cloudflared replicas per tunnel, 1,000 virtual networks per account, and published applications limited by a 1 MB configuration size (Cloudflare One account limits).

