A practical comparison of tunr and Cloudflare Tunnel for local development, staging environments, and developer-first workflows .
| Feature | tunr Recommended | Cloudflare Tunnel |
|---|---|---|
| Setup Complexity | 1 command (tunr share -p 3000) | Requires Cloudflare account + DNS |
| Persistent Subdomains | ✓ Yes (tunr.sh managed) | ✕ Must own a domain |
| Custom Domains | ⚠️ Coming soon | ✓ Yes |
| HTTPS / WebSocket | ✓ Full | ✓ Full |
| Bandwidth / Upload Limits | No bandwidth cap · 32 MB per request body | ⚠️ 100 MB max upload |
| Freeze Mode (crash protection) | ✓ Exclusive | ✕ |
| Demo Mode (read-only) | ✓ Exclusive | ✕ |
| Feedback Widget Injection | ✓ Exclusive | ✕ |
| IP Whitelisting | ✓ Yes (CLI-level, HTTP tunnels) | ✓ Via Cloudflare Access |
| Bearer Token Auth | ✓ Yes | ✓ Via Access service tokens |
| Header Modification | ✓ Yes | ✕ |
| QR Code Sharing | ✓ Yes | ✕ |
| Request Inspector / Replay | ✓ Built-in | ✕ |
| Local Dashboard | ✓ Built-in web UI | ✕ |
| Open Source CLI | ✓ Yes | ✓ Yes |
| MCP / AI Integration | ✓ Yes | ✕ |
Competitor features and prices change often; check their current plan pages. tunr's raw TCP/UDP/TLS tunnels are experimental and the relay terminates TLS, so no tunnel is end-to-end encrypted.
Cloudflare Tunnel is a strong choice if you already use Cloudflare for DNS and want to route through their edge network. But for local development, tunr is significantly simpler: one command to start, no account needed, no DNS records.
More importantly, tunr brings vibecoder superpowers that Cloudflare Tunnel simply doesn't have out of the box: freeze mode, demo mode, feedback widgets, QR codes, request inspection, and MCP tools. If you're demoing to clients, debugging webhooks, or working with AI coding agents — tunr is the clear winner.
This page compares tunr's tunnel (tunr share). tunr's main product is now Agent Bridge: approved, read-only, audited access for AI agents to customers' on-prem data. Tunnels & deploy are still part of tunr.