<?xml version="1.0" encoding="UTF-8"?>
<rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom" xmlns:dc="http://purl.org/dc/elements/1.1/">
  <channel>
    <title>DEV Community: Zorven App</title>
    <description>The latest articles on DEV Community by Zorven App (@zorven_app_e4b8ac116ca54c).</description>
    <link>https://dev.to/zorven_app_e4b8ac116ca54c</link>
    <image>
      <url>https://media2.dev.to/dynamic/image/width=90,height=90,fit=cover,gravity=auto,format=auto/https:%2F%2Fdev-to-uploads.s3.us-east-2.amazonaws.com%2Fuploads%2Fuser%2Fprofile_image%2F4249034%2F90c21cc8-381e-4814-ae83-c9dc8aaea52e.png</url>
      <title>DEV Community: Zorven App</title>
      <link>https://dev.to/zorven_app_e4b8ac116ca54c</link>
    </image>
    <atom:link rel="self" type="application/rss+xml" href="https://dev.to/feed/zorven_app_e4b8ac116ca54c"/>
    <language>en</language>
    <item>
      <title>Exposing Home Assistant behind CGNAT without port forwarding (2026)</title>
      <dc:creator>Zorven App</dc:creator>
      <pubDate>Tue, 17 Nov 2026 06:37:09 +0000</pubDate>
      <link>https://dev.to/zorven_app_e4b8ac116ca54c/exposing-home-assistant-behind-cgnat-without-port-forwarding-2026-hlf</link>
      <guid>https://dev.to/zorven_app_e4b8ac116ca54c/exposing-home-assistant-behind-cgnat-without-port-forwarding-2026-hlf</guid>
      <description>&lt;p&gt;&lt;em&gt;Disclosure: I work on Zorven, one of the outbound tunnel options mentioned below. Every option here includes its real trade-offs, including when you should skip Zorven and use Tailscale or a plain VPS instead.&lt;/em&gt;&lt;/p&gt;

&lt;p&gt;You set up Home Assistant at home, open &lt;code&gt;http://homeassistant.local:8123&lt;/code&gt;, everything loads on Wi-Fi—then you turn off Wi-Fi on your phone and nothing connects. Adding a port forward for &lt;code&gt;8123&lt;/code&gt; or &lt;code&gt;443&lt;/code&gt; in your router doesn't change anything either.&lt;/p&gt;

&lt;p&gt;In 2026, the usual culprit on residential fiber, 5G home routers, and standard Starlink plans is &lt;strong&gt;CGNAT (Carrier-Grade NAT)&lt;/strong&gt;. Because multiple households share one ISP-level public IPv4 address, unsolicited inbound traffic never reaches your router at all.&lt;/p&gt;

&lt;p&gt;Here is how to confirm CGNAT in 60 seconds, choose the right outbound path for your threat model, and configure Home Assistant's &lt;code&gt;configuration.yaml&lt;/code&gt; so you don't hit &lt;code&gt;400: Bad Request&lt;/code&gt; once traffic starts flowing.&lt;/p&gt;




&lt;h2&gt;
  
  
  Step 1: Confirm whether you are behind CGNAT (and whether IPv6 works)
&lt;/h2&gt;

&lt;p&gt;Check the WAN IP shown on your router's status page against your visible public IPv4 address:&lt;br&gt;
&lt;/p&gt;

&lt;div class="highlight js-code-highlight"&gt;
&lt;pre class="highlight shell"&gt;&lt;code&gt;curl -4 https://ifconfig.me
&lt;/code&gt;&lt;/pre&gt;

&lt;/div&gt;



&lt;p&gt;You are behind CGNAT if:&lt;/p&gt;

&lt;ul&gt;
&lt;li&gt;Your router's WAN IP is in &lt;code&gt;100.64.0.0/10&lt;/code&gt; (&lt;code&gt;100.64.x.x&lt;/code&gt; through &lt;code&gt;100.127.x.x&lt;/code&gt;), OR&lt;/li&gt;
&lt;li&gt;Your router's WAN IP does not match what &lt;code&gt;ifconfig.me&lt;/code&gt; prints.&lt;/li&gt;
&lt;/ul&gt;

&lt;p&gt;Check whether your connection has routable IPv6 as well:&lt;br&gt;
&lt;/p&gt;

&lt;div class="highlight js-code-highlight"&gt;
&lt;pre class="highlight shell"&gt;&lt;code&gt;curl -6 https://ifconfig.me
&lt;/code&gt;&lt;/pre&gt;

&lt;/div&gt;



&lt;p&gt;If your phone network and work Wi-Fi &lt;em&gt;both&lt;/em&gt; have IPv6 and your router exposes an IPv6 firewall rule, native IPv6 is the cleanest path—but many mobile/corporate networks still drop IPv6, which brings us to outbound tunnels.&lt;/p&gt;




&lt;h2&gt;
  
  
  Step 2: Pick the right outbound approach for who needs access
&lt;/h2&gt;

&lt;h3&gt;
  
  
  Option A — Only you and household members need access (Best default: Tailscale)
&lt;/h3&gt;

&lt;p&gt;If you don't need public Google Assistant / Alexa / webhook callbacks and just want the Home Assistant Companion app to work away from home:&lt;/p&gt;

&lt;ol&gt;
&lt;li&gt;Install the Tailscale Home Assistant add-on (or run &lt;code&gt;tailscale up&lt;/code&gt; on your host).&lt;/li&gt;
&lt;li&gt;Install Tailscale on your phone and reach &lt;code&gt;http://&amp;lt;tailscale-node-name&amp;gt;:8123&lt;/code&gt; over WireGuard.&lt;/li&gt;
&lt;li&gt;Zero ports exposed to public internet scanners.&lt;/li&gt;
&lt;/ol&gt;

&lt;p&gt;&lt;strong&gt;When Tailscale isn't enough:&lt;/strong&gt; Tailscale Funnel lets you expose port &lt;code&gt;443&lt;/code&gt;/&lt;code&gt;8443&lt;/code&gt;/&lt;code&gt;10000&lt;/code&gt; publicly without the app, though Funnel bandwidth isn't configurable and its control plane is SaaS-only.&lt;/p&gt;

&lt;h3&gt;
  
  
  Option B — You need a public HTTPS URL (&lt;code&gt;cloudflared&lt;/code&gt; / Cloudflare Tunnel)
&lt;/h3&gt;

&lt;p&gt;For external webhooks (Owntracks, iOS shortcuts, Google Home integration) on a domain managed in Cloudflare DNS:&lt;br&gt;
&lt;/p&gt;

&lt;div class="highlight js-code-highlight"&gt;
&lt;pre class="highlight shell"&gt;&lt;code&gt;cloudflared tunnel login
cloudflared tunnel create ha-home
cloudflared tunnel route dns ha-home ha.yourdomain.com
&lt;/code&gt;&lt;/pre&gt;

&lt;/div&gt;



&lt;p&gt;Create &lt;code&gt;config.yml&lt;/code&gt;:&lt;br&gt;
&lt;/p&gt;

&lt;div class="highlight js-code-highlight"&gt;
&lt;pre class="highlight yaml"&gt;&lt;code&gt;&lt;span class="na"&gt;tunnel&lt;/span&gt;&lt;span class="p"&gt;:&lt;/span&gt; &lt;span class="s"&gt;ha-home&lt;/span&gt;
&lt;span class="na"&gt;credentials-file&lt;/span&gt;&lt;span class="p"&gt;:&lt;/span&gt; &lt;span class="s"&gt;/root/.cloudflared/&amp;lt;TUNNEL-ID&amp;gt;.json&lt;/span&gt;
&lt;span class="na"&gt;ingress&lt;/span&gt;&lt;span class="p"&gt;:&lt;/span&gt;
  &lt;span class="p"&gt;-&lt;/span&gt; &lt;span class="na"&gt;hostname&lt;/span&gt;&lt;span class="p"&gt;:&lt;/span&gt; &lt;span class="s"&gt;ha.yourdomain.com&lt;/span&gt;
    &lt;span class="na"&gt;service&lt;/span&gt;&lt;span class="p"&gt;:&lt;/span&gt; &lt;span class="s"&gt;http://127.0.0.1:8123&lt;/span&gt;
  &lt;span class="p"&gt;-&lt;/span&gt; &lt;span class="na"&gt;service&lt;/span&gt;&lt;span class="p"&gt;:&lt;/span&gt; &lt;span class="s"&gt;http_status:404&lt;/span&gt;
&lt;/code&gt;&lt;/pre&gt;

&lt;/div&gt;



&lt;p&gt;Start it with &lt;code&gt;cloudflared tunnel run ha-home&lt;/code&gt;. Putting Cloudflare Access in front adds an email-PIN login gate before Home Assistant sees any HTTP traffic.&lt;/p&gt;

&lt;p&gt;&lt;strong&gt;Trade-off:&lt;/strong&gt; Cloudflare terminates TLS at its edge, requires your domain DNS on Cloudflare, and the tunnel control plane cannot be self-hosted.&lt;/p&gt;

&lt;h3&gt;
  
  
  Option C — Full ownership on your own $4–5/mo VPS (WireGuard + Caddy or &lt;code&gt;frp&lt;/code&gt;)
&lt;/h3&gt;

&lt;p&gt;Rent a cheap VPS with a real public IPv4 address, keep a WireGuard tunnel open outbound from home (&lt;code&gt;PersistentKeepalive = 25&lt;/code&gt;), and let &lt;strong&gt;Caddy&lt;/strong&gt; on the VPS terminate HTTPS and reverse-proxy to Home Assistant over the tunnel IP. Zero vendor lock-in, zero SaaS limits—at the cost of maintaining OS updates, firewall rules, and TLS routing yourself.&lt;/p&gt;

&lt;h3&gt;
  
  
  Option D — Open-source, self-hostable tunnel with built-in edge auth (&lt;code&gt;Zorven&lt;/code&gt;)
&lt;/h3&gt;

&lt;p&gt;If you want &lt;code&gt;cloudflared&lt;/code&gt;-style ergonomics without vendor lock-in (either hosted at &lt;code&gt;zorven.app&lt;/code&gt; or self-hosted via Docker Compose on your own VPS, AGPL-3.0):&lt;br&gt;
&lt;/p&gt;

&lt;div class="highlight js-code-highlight"&gt;
&lt;pre class="highlight shell"&gt;&lt;code&gt;&lt;span class="c"&gt;# Install client (Linux / macOS)&lt;/span&gt;
curl -fsSL https://zorven.app/install.sh &lt;span class="o"&gt;|&lt;/span&gt; sudo bash

&lt;span class="c"&gt;# Save token from dashboard and publish port 8123&lt;/span&gt;
zorven authtoken zrv_live_...
zorven http 8123
&lt;/code&gt;&lt;/pre&gt;

&lt;/div&gt;



&lt;p&gt;Typical client output:&lt;br&gt;
&lt;/p&gt;

&lt;div class="highlight js-code-highlight"&gt;
&lt;pre class="highlight plaintext"&gt;&lt;code&gt;Forwarding  https://myhome--user.zorven.app  -&amp;gt;  http://localhost:8123
&lt;/code&gt;&lt;/pre&gt;

&lt;/div&gt;



&lt;p&gt;What fits Home Assistant specifically:&lt;/p&gt;

&lt;ul&gt;
&lt;li&gt;You can enable visitor authentication (Basic, Google, or GitHub login) or IP allow-lists at the edge before requests ever reach &lt;code&gt;localhost:8123&lt;/code&gt;.&lt;/li&gt;
&lt;li&gt;Hosted plans throttle rather than hard-cutting connections if a monthly allowance is reached, and self-hosting (&lt;code&gt;docker compose up -d&lt;/code&gt; on your own VPS) removes hosted traffic caps completely.&lt;/li&gt;
&lt;/ul&gt;

&lt;p&gt;&lt;strong&gt;When NOT to use Zorven:&lt;/strong&gt;&lt;/p&gt;

&lt;ul&gt;
&lt;li&gt;Only you and your family need access -&amp;gt; use private Tailscale/WireGuard instead.&lt;/li&gt;
&lt;li&gt;You need a battle-tested multi-region CDN network right now -&amp;gt; Zorven's hosted relay currently runs in a single region, whereas Cloudflare has global edge POPs.&lt;/li&gt;
&lt;/ul&gt;




&lt;h2&gt;
  
  
  Step 3: Fix Home Assistant's &lt;code&gt;400: Bad Request&lt;/code&gt; reverse proxy check
&lt;/h2&gt;

&lt;p&gt;Whichever HTTP reverse tunnel you pick (&lt;code&gt;cloudflared&lt;/code&gt;, Caddy over WireGuard, or Zorven), Home Assistant rejects forwarded requests by default until you explicitly declare your local proxy IP trusted.&lt;/p&gt;

&lt;p&gt;Edit &lt;code&gt;/config/configuration.yaml&lt;/code&gt; (or via Studio Code Server add-on):&lt;br&gt;
&lt;/p&gt;

&lt;div class="highlight js-code-highlight"&gt;
&lt;pre class="highlight yaml"&gt;&lt;code&gt;&lt;span class="na"&gt;http&lt;/span&gt;&lt;span class="p"&gt;:&lt;/span&gt;
  &lt;span class="na"&gt;use_x_forwarded_for&lt;/span&gt;&lt;span class="p"&gt;:&lt;/span&gt; &lt;span class="kc"&gt;true&lt;/span&gt;
  &lt;span class="na"&gt;trusted_proxies&lt;/span&gt;&lt;span class="p"&gt;:&lt;/span&gt;
    &lt;span class="p"&gt;-&lt;/span&gt; &lt;span class="mf"&gt;127.0.0.1&lt;/span&gt;
    &lt;span class="p"&gt;-&lt;/span&gt; &lt;span class="s"&gt;::1&lt;/span&gt;
    &lt;span class="c1"&gt;# If running Home Assistant inside Docker bridge networking, also add your bridge/host IP:
&lt;/span&gt;    &lt;span class="c1"&gt;# - 172.30.33.0/24
&lt;/span&gt;&lt;/code&gt;&lt;/pre&gt;

&lt;/div&gt;



&lt;p&gt;Restart Home Assistant (&lt;strong&gt;Developer Tools -&amp;gt; YAML -&amp;gt; Restart&lt;/strong&gt;). If you still see &lt;code&gt;400: Bad Request&lt;/code&gt;, check &lt;strong&gt;Settings -&amp;gt; System -&amp;gt; Logs&lt;/strong&gt; for a line like:&lt;br&gt;
&lt;/p&gt;

&lt;div class="highlight js-code-highlight"&gt;
&lt;pre class="highlight plaintext"&gt;&lt;code&gt;ERROR (MainThread) [homeassistant.components.http.forwarded] A request from a reverse proxy was received from 172.17.0.1, but your HTTP integration is not set-up for reverse proxies
&lt;/code&gt;&lt;/pre&gt;

&lt;/div&gt;



&lt;p&gt;Add that exact logged IP to &lt;code&gt;trusted_proxies&lt;/code&gt; and restart once more.&lt;/p&gt;




&lt;h2&gt;
  
  
  Security checklist before sharing the URL publicly
&lt;/h2&gt;

&lt;ol&gt;
&lt;li&gt;Keep &lt;code&gt;configuration.yaml&lt;/code&gt; binding Home Assistant strictly to localhost (&lt;code&gt;server_host: 127.0.0.1&lt;/code&gt; if not running add-ons directly on another container bridge).&lt;/li&gt;
&lt;li&gt;Enable &lt;strong&gt;2FA (TOTP)&lt;/strong&gt; on every Home Assistant user account.&lt;/li&gt;
&lt;li&gt;Prefer putting an edge auth layer (Cloudflare Access or Zorven visitor login) in front of Home Assistant if external webhooks aren't hitting &lt;code&gt;/api/webhook/...&lt;/code&gt;.&lt;/li&gt;
&lt;li&gt;Leave &lt;code&gt;/api/webhook/...&lt;/code&gt; excluded from interactive browser login only if you rely on external webhook senders.&lt;/li&gt;
&lt;/ol&gt;

&lt;p&gt;&lt;em&gt;Repos / docs:&lt;/em&gt;&lt;/p&gt;

&lt;ul&gt;
&lt;li&gt;Home Assistant HTTP integration: &lt;code&gt;https://www.home-assistant.io/integrations/http/&lt;/code&gt;
&lt;/li&gt;
&lt;li&gt;Zorven (&lt;code&gt;AGPL-3.0&lt;/code&gt;): &lt;code&gt;https://github.com/tkodcumpeg4/zorven&lt;/code&gt; (&lt;code&gt;https://zorven.app&lt;/code&gt;)&lt;/li&gt;
&lt;/ul&gt;

</description>
      <category>homeassistant</category>
      <category>selfhosted</category>
      <category>networking</category>
      <category>homelab</category>
    </item>
    <item>
      <title>ngrok vs Cloudflare Tunnel vs Tailscale Funnel vs Zorven: an honest comparison (2026)</title>
      <dc:creator>Zorven App</dc:creator>
      <pubDate>Tue, 17 Nov 2026 06:31:12 +0000</pubDate>
      <link>https://dev.to/zorven_app_e4b8ac116ca54c/ngrok-vs-cloudflare-tunnel-vs-tailscale-funnel-vs-zorven-an-honest-comparison-2026-3e8e</link>
      <guid>https://dev.to/zorven_app_e4b8ac116ca54c/ngrok-vs-cloudflare-tunnel-vs-tailscale-funnel-vs-zorven-an-honest-comparison-2026-3e8e</guid>
      <description>&lt;p&gt;&lt;em&gt;Disclosure: I work on Zorven. I kept this comparison conservative: each competitor column reflects documented strengths, and the bottom section lists where you should pick one of the other three instead.&lt;/em&gt;&lt;/p&gt;

&lt;p&gt;All four tools solve the same surface problem: you want traffic from the internet (or another network) to reach a service running on your laptop or home server without opening inbound router ports. Under the hood, they optimize for very different jobs.&lt;/p&gt;

&lt;h2&gt;
  
  
  Quick comparison
&lt;/h2&gt;

&lt;div class="table-wrapper-paragraph"&gt;&lt;table&gt;
&lt;thead&gt;
&lt;tr&gt;
&lt;th&gt;Dimension&lt;/th&gt;
&lt;th&gt;ngrok&lt;/th&gt;
&lt;th&gt;Cloudflare Tunnel (&lt;code&gt;cloudflared&lt;/code&gt;)&lt;/th&gt;
&lt;th&gt;Tailscale / Tailscale Funnel&lt;/th&gt;
&lt;th&gt;Zorven&lt;/th&gt;
&lt;/tr&gt;
&lt;/thead&gt;
&lt;tbody&gt;
&lt;tr&gt;
&lt;td&gt;&lt;strong&gt;Open-source server&lt;/strong&gt;&lt;/td&gt;
&lt;td&gt;No (client agent historically open, server proprietary)&lt;/td&gt;
&lt;td&gt;No (&lt;code&gt;cloudflared&lt;/code&gt; daemon open, edge proprietary)&lt;/td&gt;
&lt;td&gt;Partial (client OSS, coordination server proprietary; community &lt;code&gt;headscale&lt;/code&gt; exists separately)&lt;/td&gt;
&lt;td&gt;&lt;strong&gt;Yes (AGPL-3.0)&lt;/strong&gt;&lt;/td&gt;
&lt;/tr&gt;
&lt;tr&gt;
&lt;td&gt;&lt;strong&gt;Self-hostable control plane&lt;/strong&gt;&lt;/td&gt;
&lt;td&gt;No&lt;/td&gt;
&lt;td&gt;No&lt;/td&gt;
&lt;td&gt;No (official); requires &lt;code&gt;headscale&lt;/code&gt; for self-hosted control plane&lt;/td&gt;
&lt;td&gt;&lt;strong&gt;Yes (Go server + Docker Compose)&lt;/strong&gt;&lt;/td&gt;
&lt;/tr&gt;
&lt;tr&gt;
&lt;td&gt;&lt;strong&gt;One-command HTTP tunnel&lt;/strong&gt;&lt;/td&gt;
&lt;td&gt;&lt;code&gt;ngrok http 3000&lt;/code&gt;&lt;/td&gt;
&lt;td&gt;&lt;code&gt;cloudflared tunnel --url http://localhost:3000&lt;/code&gt;&lt;/td&gt;
&lt;td&gt;&lt;code&gt;tailscale funnel 3000&lt;/code&gt;&lt;/td&gt;
&lt;td&gt;&lt;code&gt;zorven http 3000&lt;/code&gt;&lt;/td&gt;
&lt;/tr&gt;
&lt;tr&gt;
&lt;td&gt;&lt;strong&gt;Raw TCP / UDP tunnels&lt;/strong&gt;&lt;/td&gt;
&lt;td&gt;TCP yes (paid/verified card for some endpoints)&lt;/td&gt;
&lt;td&gt;TCP via Cloudflare Access/Spectrum setups; not aimed at arbitrary UDP&lt;/td&gt;
&lt;td&gt;Private mesh handles TCP/UDP; Funnel HTTPS-only on fixed ports (&lt;code&gt;443&lt;/code&gt;, &lt;code&gt;8443&lt;/code&gt;, &lt;code&gt;10000&lt;/code&gt;)&lt;/td&gt;
&lt;td&gt;&lt;strong&gt;TCP on all plans; advanced UDP (game servers) on Pro and up&lt;/strong&gt;&lt;/td&gt;
&lt;/tr&gt;
&lt;tr&gt;
&lt;td&gt;&lt;strong&gt;Private device-to-device WireGuard mesh&lt;/strong&gt;&lt;/td&gt;
&lt;td&gt;No&lt;/td&gt;
&lt;td&gt;Private WARP/Zero Trust connectors&lt;/td&gt;
&lt;td&gt;&lt;strong&gt;Yes (best-in-class tailnet)&lt;/strong&gt;&lt;/td&gt;
&lt;td&gt;&lt;strong&gt;Yes (Zorven Net, &lt;code&gt;zorven share&lt;/code&gt; / &lt;code&gt;zorven net up&lt;/code&gt;)&lt;/strong&gt;&lt;/td&gt;
&lt;/tr&gt;
&lt;tr&gt;
&lt;td&gt;&lt;strong&gt;Built-in webhook replay / inspector&lt;/strong&gt;&lt;/td&gt;
&lt;td&gt;&lt;strong&gt;Yes (&lt;code&gt;localhost:4040&lt;/code&gt;, very mature)&lt;/strong&gt;&lt;/td&gt;
&lt;td&gt;No built-in webhook replay UI&lt;/td&gt;
&lt;td&gt;No&lt;/td&gt;
&lt;td&gt;&lt;strong&gt;Yes (live request log + replay &amp;amp; diff)&lt;/strong&gt;&lt;/td&gt;
&lt;/tr&gt;
&lt;tr&gt;
&lt;td&gt;&lt;strong&gt;Free tier behavior&lt;/strong&gt;&lt;/td&gt;
&lt;td&gt;Usage/request limits, dev domain, browser interstitial warning unless skipped&lt;/td&gt;
&lt;td&gt;Generous free tunnel (requires Cloudflare-managed domain for stable hostnames; ToS restricts heavy video proxy)&lt;/td&gt;
&lt;td&gt;Generous personal tailnet; Funnel non-configurable bandwidth limits&lt;/td&gt;
&lt;td&gt;Free plan (2 tunnels, 5 GB/mo) &lt;strong&gt;throttles on overage instead of hard cutoffs&lt;/strong&gt; (Free drops to 1 Mbps, Hobby 5 Mbps)&lt;/td&gt;
&lt;/tr&gt;
&lt;tr&gt;
&lt;td&gt;&lt;strong&gt;Global edge POP maturity&lt;/strong&gt;&lt;/td&gt;
&lt;td&gt;Multi-region global POPs&lt;/td&gt;
&lt;td&gt;&lt;strong&gt;Largest global anycast network&lt;/strong&gt;&lt;/td&gt;
&lt;td&gt;Global DERP relay network&lt;/td&gt;
&lt;td&gt;Single-region hosted relay right now (multi-region only if you deploy multiple self-hosted servers)&lt;/td&gt;
&lt;/tr&gt;
&lt;/tbody&gt;
&lt;/table&gt;&lt;/div&gt;




&lt;h2&gt;
  
  
  Deep dive by use case
&lt;/h2&gt;

&lt;h3&gt;
  
  
  1. When ngrok is still the fastest choice
&lt;/h3&gt;

&lt;ul&gt;
&lt;li&gt;You just want to inspect a local Stripe/Shopify webhook with a mature local inspector UI at &lt;code&gt;http://127.0.0.1:4040&lt;/code&gt; and don't need self-hosting.&lt;/li&gt;
&lt;li&gt;You rely on low-latency global edge POPs across multiple continents and don't hit the monthly free bandwidth / browser interstitial friction.&lt;/li&gt;
&lt;/ul&gt;

&lt;h3&gt;
  
  
  2. When Cloudflare Tunnel (&lt;code&gt;cloudflared&lt;/code&gt;) wins
&lt;/h3&gt;

&lt;ul&gt;
&lt;li&gt;Your domain DNS is already on Cloudflare, you want Cloudflare Access (Zero Trust SSO/email OTP) in front of self-hosted web apps, and you want massive global anycast DDoS absorption for $0.&lt;/li&gt;
&lt;li&gt;
&lt;strong&gt;Watch out for:&lt;/strong&gt; Cloudflare ends up terminating TLS on their edge, your control plane isn't self-hosted, and heavy non-HTML traffic (e.g., streaming Plex/Jellyfin media libraries) can run afoul of their proxy Terms of Service.&lt;/li&gt;
&lt;/ul&gt;

&lt;h3&gt;
  
  
  3. When Tailscale (and Funnel) wins
&lt;/h3&gt;

&lt;ul&gt;
&lt;li&gt;If access is &lt;strong&gt;only for you, your devices, or your team&lt;/strong&gt;—not random unauthenticated browser visitors—a private tailnet beats any public URL hands down. MagicDNS, mobile clients, ACLs, and direct UDP hole punching are rock-solid.&lt;/li&gt;
&lt;li&gt;Tailscale Funnel is great for quick light sharing on ports &lt;code&gt;443&lt;/code&gt;/&lt;code&gt;8443&lt;/code&gt;/&lt;code&gt;10000&lt;/code&gt;, though it wasn't built as an arbitrary TCP/UDP ingress or a webhook replay debugger.&lt;/li&gt;
&lt;/ul&gt;

&lt;h3&gt;
  
  
  4. Where Zorven fits (&lt;code&gt;https://zorven.app&lt;/code&gt;)
&lt;/h3&gt;

&lt;p&gt;Zorven tries to combine the pieces developers usually duct-tape together from ngrok + Tailscale + a Caddy reverse proxy—without locking the control plane inside a SaaS:&lt;br&gt;
&lt;/p&gt;

&lt;div class="highlight js-code-highlight"&gt;
&lt;pre class="highlight shell"&gt;&lt;code&gt;&lt;span class="c"&gt;# Quick temporary URL that cleans itself up after 30m:&lt;/span&gt;
zorven ephemeral 3000 --ttl 30m

&lt;span class="c"&gt;# Clean scripting output for CI / wrappers:&lt;/span&gt;
zorven http 3000 --print-url

&lt;span class="c"&gt;# Share a local Postgres port privately with one teammate (end-to-end encrypted):&lt;/span&gt;
zorven share 5432 --to colleague@company.com --name db
&lt;/code&gt;&lt;/pre&gt;

&lt;/div&gt;



&lt;p&gt;Where it stands out today:&lt;/p&gt;

&lt;ul&gt;
&lt;li&gt;
&lt;strong&gt;AGPL-3.0 open source and self-hostable:&lt;/strong&gt; Deploy the whole server (&lt;code&gt;server/&lt;/code&gt; Go binary + Nuxt dashboard + Postgres via &lt;code&gt;deploy/docker-compose.yml&lt;/code&gt;) on a $5 VPS under your own domain.&lt;/li&gt;
&lt;li&gt;
&lt;strong&gt;Flat per-plan hosted pricing ($0 Free / $5 Hobby / $12 Pro / $29 Team):&lt;/strong&gt; Not per-user or per-seat—useful if an agency, studio, or field installer manages multiple customer sites.&lt;/li&gt;
&lt;li&gt;
&lt;strong&gt;Extras in one binary:&lt;/strong&gt; Request inspector with replay, visitor login gates (Basic / Google / GitHub), UDP/TCP ports + SNI passthrough, browser terminal/screen share (&lt;code&gt;--enable-terminal&lt;/code&gt; / &lt;code&gt;--enable-screen&lt;/code&gt;, off by default), and built-in MCP server (&lt;code&gt;zorven mcp&lt;/code&gt;).&lt;/li&gt;
&lt;/ul&gt;




&lt;h2&gt;
  
  
  When NOT to pick Zorven
&lt;/h2&gt;

&lt;ol&gt;
&lt;li&gt;
&lt;strong&gt;You need a battle-tested multi-region edge today.&lt;/strong&gt; Cloudflare and ngrok have years of global multi-POP reliability; Zorven is young (~v0.x, 8 GitHub stars) and its hosted service runs in one region right now.&lt;/li&gt;
&lt;li&gt;
&lt;strong&gt;You strictly need a private mesh for personal devices.&lt;/strong&gt; Tailscale's native OS apps and onboarding polish are much more mature if you never expose public URLs.&lt;/li&gt;
&lt;li&gt;
&lt;strong&gt;You don't want AGPL-3.0 for proprietary redistribution.&lt;/strong&gt; Zorven is AGPL-3.0 open source; check license compatibility before embedding the server into commercial proprietary appliances.&lt;/li&gt;
&lt;/ol&gt;




&lt;p&gt;&lt;em&gt;Links:&lt;/em&gt;&lt;/p&gt;

&lt;ul&gt;
&lt;li&gt;Zorven repository: &lt;code&gt;https://github.com/tkodcumpeg4/zorven&lt;/code&gt;
&lt;/li&gt;
&lt;li&gt;Hosted site: &lt;code&gt;https://zorven.app&lt;/code&gt;
&lt;/li&gt;
&lt;/ul&gt;

</description>
      <category>devtools</category>
      <category>selfhosted</category>
      <category>networking</category>
      <category>opensource</category>
    </item>
  </channel>
</rss>
