This is a pretty huge problem for marketing teams in general with site sprawl (and docs, too) so I like how this was solved.

With nd, developers shouldn’t need to know how to build or deploy a service; they just need to know what service they want to interact with, and nd helps whether go, webpack, bazel, or docker builds that service. Likewise, deploying a service automatically checks if it was built, and if not, nd will build it for them (or warn them if it's production-bound and they want a CI build instead).

Curious: why do you see ngrok as just for testing and dev when thousands of users use ngrok in production?

Full disclosure I work there.

Why route all traffic through a tunnel for a production setup? On-premise solutions will use static IPs from their ISPs.

Full disclosure - I work at https://pinggy.io

Would the internal endpoints solve this for you? https://ngrok.com/docs/network-edge/internal-endpoints/

Happy to help with a solution. Sam at ngrok.com is my email

Cool, dropped an email.

Nice job team!

great job ngrok