How Cloudflare Quick Tunnels works: outbound-only reverse tunneling with zero inbound ports
xiaohu · x · 2026-09-21
A detailed breakdown of how Cloudflare Quick Tunnels works:
- Built on the cloudflared daemon with an outbound-only reverse tunnel architecture;
- cloudflared initiates an encrypted outbound connection to the nearest Cloudflare node, so no inbound ports are needed (restricted networks must allow port 7844);
- Incoming requests hit Cloudflare's edge for TLS, DDoS protection and routing, then travel back through the tunnel to the local cloudflared and on to the localhost port;
- The tunnel ends with the process, so the public URL is for testing/temporary use;
- Use cases: mobile previews, webhook callbacks, browser tests, and giving local coding agents a public endpoint.
More from coding & agent
- claude-ops turns Claude Code into a business OS with 57 skills, 21 agents — tom_doerr · 2026-09-21
- Inside OpenAI's agentic software factory: Codex takes over, IDEs and pull requests fade — AxSaucedo · 2026-09-21
- Developer Gives AI Agent a Phone, Turns It Into a Personal Concierge — ethanniser · 2026-09-21
- Benchmarks show coding agents edit code they shouldn't in 35-65% of cases; prompt framing is the lever — RunAI_Coder · 2026-09-21
- Using a second LLM as a watchdog to catch coding agents faking success — Ascend-910 · 2026-09-21
- OpenAI opens Agents API to public beta: Codex harness in a single API call — emmanuelvivier · 2026-09-21