cloudflare/cloudflared

Cloudflare Tunnel client

View on GitHub ↗Jump to charts ↓Open shareable report

Summary Information

Updated 11 minutes ago
Added to GitGenius on February 28th, 2026
Created on October 13th, 2017
Open Issues & Pull Requests: 537 (+0)
Number of forks: 1,411
Total Stargazers: 15,411 (+0)
Total Subscribers: 132 (+0)

Repository Insights (GitGenius)

Median issue/PR response: 28.8 days
Mean response time: 279.4 days
90th percentile: 977.1 days
Tracked items: 395

How this project is maintained

Around half of the issues opened in the past year never receive a reply. 100% of open issues come from outside the core team, so the backlog reflects real-world use rather than internal planning. Work labelled "Type: Documentation" is answered fastest, typically in about 3 weeks, while "Needs clarification" waits about 38 months. 66% of tracked open issues have had no activity in three months, so the open count overstates what is actively being worked. Only 4% of issues opened in the past year have been closed.

Charts & Analytics

Fetching additional details & charts...

Issue Activity (beta)

Open issues: 275
New in 7 days: 3
Closed in 7 days: 1
Avg open age: 599 days
Stale 30+ days: 261
Stale 90+ days: 238

Recent activity

Opened in 7 days: 3
Closed in 7 days: 1
Comments in 7 days: 2
Events in 7 days: 9

Top labels

  • Priority: Normal (377)
  • Type: Bug (252)
  • Type: Feature Request (119)
  • Type: Documentation (26)
  • Needs clarification (12)
  • Confirmed (9)
  • Priority: Deferred (8)
  • Area: Packaging (3)

Detailed Description

Cloudflared is a tunneling daemon that proxies traffic from the Cloudflare network to your origins without requiring firewall modifications.

The tool solves the problem of exposing internal services to the internet securely. It sits between the Cloudflare network and your origin servers, allowing Cloudflare to attract client requests and forward them through the daemon to your backend infrastructure. Your origin can remain behind a closed firewall since the daemon initiates outbound connections rather than requiring inbound ports to be opened. The tool also supports Layer 4 TCP traffic proxying for use cases like SSH and RDP access to protected origins, with an alternative being the WARP client for accessing private origins without requiring command-line access tools on the client side.

Cloudflared suits organizations that want to expose internal services while maintaining strict firewall policies and zero-trust network access. It works well for web servers, APIs, and other services that need to be accessible from the Cloudflare edge network. The tool requires adding a website to a Cloudflare account and changing nameservers to Cloudflare before use, though private routing is possible without a website despite this legacy requirement. Installation is straightforward through multiple channels including Homebrew, package managers for Linux distributions, Docker, standalone binaries, or building from source.

The project has a substantial base of adopters reporting real-world use, as evidenced by the fact that almost all open issues are raised by outside users rather than the core team. However, issues and pull requests often wait weeks or longer for a first response. Work in the issue tracker is dominated by normal priority bugs and feature requests from the community.