One-time setup: run Special → Cloudflare Setup Wizard… with a Cloudflare API token (Zone → DNS → Edit, Account → Cloudflare Tunnel → Edit) and a remotely-managed tunnel. The Cloudflare module in the Control Strip (bottom-left) shows tunnel health at a glance.
Live local traffic uses cloudflared's loopback metrics listener at http://127.0.0.1:20241. If it uses another local port, set cloudflare.metrics_url in Configuration → Cloudflare to the base address (without /metrics). exe verifies that the local connector belongs to the selected tunnel. A machine without a local cloudflared connector can still show the tunnel-wide connection counts; its local counters stay unavailable. A Cloudflare API failure labels cached connection counts as last known rather than reporting them as live.
Then, in a VM's Expose tab, pick a port and an optional subdomain (it defaults to the VM name). exe creates the DNS record, updates the tunnel ingress, and routes the hostname through its reverse proxy to the VM — one click later the service is live at https://<sub>.<your-domain>. Current routes are listed in the Services tab and in Special → Cloudflare Status…, where they can be unpublished.
The CLI can also publish a permanent redirect without a VM:
exe expose example.com -redirect https://exe.example.com exe expose www.example.com -redirect https://exe.example.com
Use your configured domain or one of its full subdomain names. The target must be an HTTP(S) origin, with no path, query, fragment or credentials. exe creates the same DNS and tunnel rules, then answers with 308 Permanent Redirect, preserving each request's path and query string. For example, https://example.com/docs/?from=home becomes https://exe.example.com/docs/?from=home. The method and body survive when the client follows the redirect. exe routes lists these routes as redirect:https://…; exe unexpose <host> removes one.