IdeaWell

Project ideas from Hacker News discussions.

Cloudflare Quick Tunnels

Original Article

Hacker News Discussion

📝 Discussion Summary (Click to expand)

Four dominant themes in the Hacker News discussion

1. Convenience for quick testing / demos

Many users praised the ability to expose a local service instantly without accounts or complex setup.

  • “handy when prototyping / pocs, etc – I could see that being helpful when testing a new service or change over the internet” – danserfaty
  • “Great for demos and temporary dev environments” – ggg011012
  • “No log in needed, pretty convenient – running cloudflared tunnel --url localhost:XXXX is very easy” – rinconrex

2. Privacy, centralization and trust concerns

A recurring worry was that Cloudflare sees all traffic in cleartext and that the service increases reliance on a single, powerful U.S. company.

  • “Cloudflare sees your plaintext. … you have to trust them not to maliciously alter your traffic” – Tepix
  • “This is yet another traffic generator to drive up Cloudflare’s leverage … a concentration of power issue” – inopinatus
  • “I don’t trust any of these corporates any more” – t_mahmood

3. Comparison with existing tunneling solutions (ngrok, Tailscale, Tor, self‑hosted)

Commenters repeatedly measured Quick Tunnels against ngrok, Tailscale Funnel, Tor onion services, and DIY WireGuard/Tailscale setups.

  • “On what url were those? Or Cloudflare's TOS in general ? … No‑ip gives out free dynamic DNS” – whizzter / ThrowawayTestr
  • “If you already have Tailscale, you don’t need to trust a 3rd party with your cleartext traffic” – Tepix
  • “Tor does the exact same thing, except supported by a global network of volunteers … but you need to install a Tor client” – smalltorch / thenewnewguy

4. Criticism of the marketing / landing page (vibe‑coded, AI‑generated look)

Several users pointed out that the newly launched page looks sloppy, AI‑generated, or “vibe‑coded,” which undermines confidence in the product.

  • “The page is a fine exemplar of marketing deception … Looks like they straight up vibe coded the landing page” – everybodyknows / xeornet
  • “What a sloppy website, did Cloudflare fire a bunch of UI/UX designers?” – cute_boi
  • “AI took all the effort, so I guess nobody sees value in these little pages anymore” – maipen

These four themes capture the bulk of sentiment expressed in the thread.

🚀 Project Ideas

SelfHosted TunnelBox

Summary

  • Open-source self-hosted tunneling server that gives you persistent subdomains and full protocol support (HTTP, TCP, UDP) without relying on third-party providers.
  • Core value proposition: complete control over your tunneling infrastructure, eliminating trust and TOS concerns while providing ngrok-like ease of use.

Details

Key Value
Target Audience Developers, homelab operators, privacy‑conscious users
Core Feature Deploy your own tunnel server on a VPS; get stable subdomains via wildcard DNS; supports HTTP, TCP, UDP, TLS
Tech Stack Go (core), Caddy for TLS, Docker‑Compose for deployment, optional SQLite
Difficulty Medium
Monetization Hobby
#### Notes
- Addresses HN complaints about Cloudflare TOS restrictions and centralization by letting users run their own tunnel infra (see comments from tombert, ZeroCool2u, and mitxela about trust and latency).
- Provides a drop‑in replacement for ngrok/Cloudflare Quick Tunnels that can be self‑hosted, satisfying the desire for open‑source alternatives mentioned in the awesome‑tunneling list.

QuickDNS Tunnel Persister

Summary

  • A lightweight wrapper around cloudflared tunnel --url that registers a persistent subdomain on your own domain using the Cloudflare API, giving you a stable URL for each quick tunnel run.
  • Core value proposition: retain the zero‑account, zero‑setup convenience of Cloudflare Quick Tunnels while solving the random‑subdomain problem that frustrates demo sharing and agent integration.

Details

Key Value
Target Audience Developers who need stable demo URLs, agent builders, CI/CD pipelines
Core Feature On each run, obtains a temporary Cloudflare Quick Tunnel and updates a DNS CNAME (or A) record on your domain to point to the generated trycloudflare.com host, yielding a fixed subdomain like demo.yourdomain.com
Tech Stack Go (or Bash), Cloudflare API v4, optional systemd service
Difficulty Low
Monetization Hobby
#### Notes
- Directly tackles the pain point raised by users who dislike the random trycloudflare.com subdomain (e.g., f_rp_ and commenters wanting persistent URLs for sharing work with clients).
- Enables use of Cloudflare’s infrastructure without sacrificing URL stability, appealing to those who appreciate the service but need a reliable endpoint for demos or agent callbacks.

ShieldTunnel

Summary

  • End‑to‑end encrypted tunneling built on WireGuard where the tunnel only sees encrypted payloads, preventing the tunnel operator (or any intermediary) from inspecting cleartext traffic.
  • Core value proposition: strong confidentiality and integrity for tunneled traffic, addressing concerns about Cloudflare or other providers seeing plaintext and being compelled to modify or log it.

Details

Key Value
Target Audience Privacy‑focused developers, remote workers, anyone handling sensitive data over tunnels
Core Feature Client encrypts traffic with a session key before handing it to WireGuard; server decrypts and forwards to local service; no plaintext ever exposed to the tunnel relay
Tech Stack Go (WireGuard wrapper), Noise Protocol Framework for session keys, optional UI via Electron/Tauri
Difficulty Medium
Monetization Revenue-ready: Subscription $4/mo per active tunnel (includes relay bandwidth)
#### Notes
- Responds to explicit HN worries about Cloudflare seeing cleartext (mitxela, Tepix, ceejayoz) and the desire for a solution like Tailscale that does not require trusting a third party with unencrypted data.
- Provides a self‑hosted or hosted relay option that gives the same ease‑of‑use as Cloudflare Quick Tunnels but with cryptographic guarantees that the relay cannot read or tamper with traffic.

AgentExpose

Summary

  • One‑command tool that creates a temporary HTTPS endpoint for a locally running LLM agent (e.g., Claude Code) and automatically injects the agent’s API key or OAuth token into outgoing requests, while logging all inbound traffic for debugging.
  • Core value proposition: simplifies secure agent‑to‑local‑service communication, eliminating manual token handling and reducing the risk of leaking credentials when exposing dev servers to the internet.

Details

Key Value
Target Audience AI developers, agent builders, teams using LLM‑powered coding assistants
Core Feature Runs a local proxy that authenticates incoming requests via the agent’s token, forwards them to localhost:port, and returns responses; provides a public URL via Cloudflare Quick Tunnel (or self‑hosted alternative) with built‑in token injection and request logging
Tech Stack Node.js (Express), cloudflared CLI, dotenv for token storage, optional Bun for speed
Difficulty Low
Monetization Hobby
#### Notes
- Mirrors the use case highlighted by users wanting to let Claude agents access local MCPs (see dalberto’s mcp‑ferry and comments about remote agents) while avoiding manual port forwarding or insecure exposure.
- Offers a frictionless way to prototype agent integrations locally, addressing the frustration expressed by emadabdulrahim and others about waiting for build/deploy cycles to see changes.

Read Later