Deploying an application on my own VPS usually ends with the same checklist:

point a domain at the server;

open ports 80 and 443 ;

configure the reverse proxy;

issue an HTTPS certificate;

verify that the firewall is not blocking the request.

None of those steps is unusual. But sometimes I do not want the server to accept public web traffic at all.

Maybe the VPS is behind NAT. Maybe the network does not allow inbound ports. Maybe I want requests to pass through Cloudflare Access before they can reach an internal dashboard. Or maybe I simply do not want the server's public IP to provide a second route around the protection in front of it.

This is the problem behind Cloudflare Tunnel support in Nitrobase.

Nitrobase has only recently launched and is still in Beta . This feature is not an attempt to hide how networking works.…