Blog
7 min read

Cloudflare Tunnel vs Tailscale: Public Exposure or Private Network?

Cloudflare Tunnel vs Tailscale: one publishes a service to the internet, the other builds a private mesh. Funnel, Serve, Access, free tiers and use cases.

Cloudflare Tunnel is for making a service on your machine reachable by the public internet at your own domain, through Cloudflare's network, without opening ports. Tailscale is for connecting your own devices into a private network so they can reach each other, with nothing exposed publicly. If strangers need to visit it, start with Cloudflare Tunnel. If only you and your team need to reach it, start with Tailscale. Each product has a feature that reaches into the other's territory (Tailscale Funnel, Cloudflare Access and private networking), which is where the confusion comes from.

Plan limits checked against tailscale.com/pricing, Cloudflare's Zero Trust pricing and both companies' docs in November 2026.

The one-minute version

Cloudflare Tunnel Tailscale
Main job Publish a service to the internet Private network between your devices
Who can reach it Anyone, unless you add Cloudflare Access Only devices and users in your tailnet
What the visitor needs A browser The Tailscale app, logged in to your tailnet
Domain Your own domain on Cloudflare, or a random trycloudflare.com URL <device>.<tailnet>.ts.net names
Traffic path Your machine → nearest Cloudflare data centre → visitor Device to device directly over WireGuard, relay only when needed
Protocols HTTP(S) for the public; SSH, RDP and TCP with Cloudflare's client tools Any IP traffic between devices
Public sharing option Built in Tailscale Funnel (beta), ts.net names only
Login in front Cloudflare Access Your tailnet identity is the login
Free plan Tunnel is free; Zero Trust free for up to 50 users Personal plan free for up to 6 users

How each one works

Cloudflare Tunnel runs a small daemon, cloudflared, next to your app. It makes outbound-only connections to Cloudflare's network, so your server needs no public IP and your firewall can block all inbound traffic. When someone visits app.example.com, Cloudflare receives the request and sends it down the tunnel. You get Cloudflare's TLS, CDN and DDoS protection in front for free. The full setup is in our Cloudflare Tunnel guide.

Tailscale installs a client on each device. A coordination server handles keys and discovery, then devices talk to each other directly over WireGuard. When firewalls prevent a direct path, traffic goes through Tailscale's encrypted DERP relays. Every device gets a stable private address and a MagicDNS name, so ssh my-server works from your laptop anywhere. More in what is Tailscale.

The key mental model: Cloudflare sits in the middle of every request and terminates TLS there. Tailscale traffic is end-to-end encrypted between your devices, and Tailscale's servers never see its contents.

Where they overlap

Tailscale Serve and Funnel

  • tailscale serve 3000 shares a local web server with the rest of your tailnet at https://<device>.<tailnet>.ts.net, with a valid TLS certificate. It stays private: only tailnet members (subject to your access rules) can open it.
  • tailscale funnel 3000 makes that same URL public. Tailscale's docs describe it as in beta and available on all plans. It can only listen on ports 443, 8443 and 10000, works only with your ts.net name (not your own domain), and traffic is "subject to non-configurable bandwidth limits". Public DNS points at a Funnel relay, which forwards encrypted TCP to your device. TLS terminates on your machine, so the relay can't read the traffic.

Funnel is ideal for briefly showing someone a dev server or receiving a webhook. It's not built to front a production site on your own domain.

Cloudflare Access and private networking

  • Cloudflare Access puts a login in front of a tunnelled app. Visitors sign in with an email one-time code, Google, GitHub or your SSO before Cloudflare lets the request through. This gives you a private-ish internal tool reachable from any browser, with no client install.
  • Cloudflare's Zero Trust platform can also route private network traffic and non-HTTP protocols like SSH and RDP through a tunnel, with the WARP client or cloudflared on the user's side. This is Cloudflare's answer to a VPN, and it's capable, but it involves more configuration than Tailscale for a small group.

Free tiers and limits

Cloudflare:

  • Tunnels themselves don't cost anything. You need a domain whose DNS is on Cloudflare for a named tunnel.
  • The Zero Trust free plan, which includes Access, covers up to 50 users. Beyond that, Cloudflare lists pay-as-you-go at $7 per user per month, billed annually.
  • Quick tunnels (cloudflared tunnel --url http://localhost:8080) need no account. Cloudflare's docs say each supports up to 200 in-flight requests (extra requests get a 429) and does not support Server-Sent Events. See protected quick tunnels.
  • Cloudflare's terms restrict using its network mainly to serve large video or other heavy non-web content on self-serve plans. A media server is the classic thing that runs into this.

Tailscale:

  • The free Personal plan includes up to 6 users and unlimited user devices, with 50 tagged resources (servers and other non-user devices) to start.
  • Paid plans are Standard at $8 per user per month and Premium at $18 per user per month.
  • Funnel has unpublished bandwidth limits, as noted above.

Latency and traffic path

With Cloudflare Tunnel, every request goes visitor → Cloudflare edge near them → Cloudflare edge near your server → down the tunnel → your app. For public websites this is usually fine and sometimes faster than direct thanks to caching. For you, sitting next to your home server, it adds a round trip through Cloudflare that you wouldn't have on a LAN.

With Tailscale, a direct connection is just WireGuard between two devices, about as fast as the underlying network. If NAT traversal fails and traffic falls back to a DERP relay, you'll notice slower speeds; tailscale status and tailscale ping <device> show whether a connection is direct or relayed.

Neither should be used to judge raw speed without testing your own setup. Results depend on where your devices and the nearest data centres are.

Typical use cases

Home lab

  • Services only you and family use (Home Assistant, NAS, Jellyfin, Proxmox): Tailscale. Nothing is exposed, and the apps on your phone just work. Media streaming also stays clear of Cloudflare's content terms.
  • One service you want public (a blog, a status page, a small web app on a home server): Cloudflare Tunnel on your own domain.
  • Plenty of home labs run both: Tailscale for admin access, Cloudflare Tunnel for the one or two public sites.

Sharing a dev server

  • Quick demo to a client, or a webhook from Stripe or GitHub: a Cloudflare quick tunnel or tailscale funnel both work in a single command. Quick tunnels give a random URL with no account. Funnel gives a stable ts.net URL tied to your machine. (Test webhooks locally)
  • Teammate needs to see your branch: tailscale serve if they're on your tailnet, otherwise a tunnel with Access.

SSH to a server

  • Tailscale is the simpler choice. Install it on the server, close port 22 to the internet, and ssh user@server over the tailnet. Tailscale SSH can even replace key management with tailnet identity. (SSH hardening)
  • Cloudflare can do it too, via a tunnel plus Access with cloudflared on the client or a browser-rendered terminal, which is handy if users can't install a VPN client. It's more setup for one or two people.

Production app

  • A real public app is usually best served directly from a server with a public IP behind a reverse proxy, optionally proxied through Cloudflare. A tunnel is useful when the server can't accept inbound connections (home network, corporate firewall, CGNAT).
  • Tailscale's role in production is the back office: private access to databases, admin panels and SSH, and connecting servers across clouds.

Which should you pick?

  • "I want people on the internet to visit this": Cloudflare Tunnel.
  • "I want to reach my own stuff from anywhere": Tailscale.
  • "I want an internal tool reachable from any browser, behind a login, no client install": Cloudflare Tunnel plus Access.
  • "I want to show a teammate or client something running on my laptop for an hour": either; use whichever you already have installed.
  • "I want to stop exposing SSH": Tailscale.

Using both is normal and they don't conflict.


EasySpawn gives every environment a live HTTPS URL on its own server, so sharing a work-in-progress app doesn't need a tunnel from your laptop. See how it works or join the waitlist.

Related: Cloudflare Tunnel Explained: Put a Local App Online Without Opening Ports · What Is Tailscale? A Private Network for Your Devices and Servers · Cloudflare Protected Quick Tunnels: Share Localhost Only With the Emails You Choose · How to Test Webhooks Locally: Stripe CLI, Tunnels, and Replays

Keep reading