They’re exposed through a Cloudflare tunnel — TLS terminated at the edge, so there’s no inbound 80/443 needed and no clash with the box’s existing nginx.
The Cloudflare tunnel is why there’s no nginx-on-80/443 conflict: nothing binds the public ports on the box, the tunnel reaches the localhost ports directly.
Wiring it to the platform
The guardrail group’s custom check and thebackstop-infra MCP server are registered in TrueFoundry against those public HTTPS URLs.
The deploy/ folder
deploy/ has everything needed to reproduce the deployment:
setup.sh— the setup script.ecosystem.config.js— the pm2 process definitions.- the cloudflared and nginx configs.

