Cloudflare Zero Trust

Architecture Summary

Internet / WARP Clients

Cloudflare Edge (Atlanta)

homelab tunnel (89c486fb...)

pi4a + pi4b (redundant connectors)

192.168.50.0/24 (pfSense LAN)

What routes traffic where:

When you add a new self-hosted service:

  1. Add proxy host in NPM pointing to the service — it’s immediately live at newservice.mykk.us via the wildcard, no other changes needed
  2. If you want a mykk.foo URL instead, add a published application route in the tunnel and a ZT Access application to protect it

When you add a new internal service that needs direct access:

Nothing — CIDR routing already covers all of 192.168.50.x

When you add a new device that needs remote access:

Install Cloudflare One Client → enroll in techguywithabeard org → device gets full tunnel access automatically

Things that live in the Cloudflare dashboard: