I feel like this isn't really a software question about ngrok vs Docker vs any other proxy / network app, but a question of your business's underlying network architecture decisions made by the business. Presumably some things are on the LAN and not online on purpose...? Or are these just a bunch of legacy systems that just haven't made it online yet?<p>In other words, is IT just concerned about you opening up your LAN to external incoming traffic, or is there some underlying data security concern too?<p>If it's just that IT doesn't want you to be running servers, can you make the webhooks point the other way instead (outgoing from your LAN to the public internet, not the other way around). If you can't do that, you can still write messages to an external queue and have your LAN poll it every few seconds, maybe? Or if your IT allows this (doubtful but maybe worth asking) you can maybe establish a long-lived tunnel via SSH or a Cloudflare Tunnel, etc., that establishes a single connection to a single outside server (which then receives all the public traffic). That is somewhat safer than opening up a port to public traffic directly.<p>But when you say "highly secure", that makes me wonder if some of this data was never meant to leave the LAN (like are there compliance & privacy issues to consider?). You might want to double-check that with them before making any sort of public-interfacing integration, because you'd be risking a lot more than a complaint from IT if you inadvertently exposed all this private stuff to the internet.<p>Otherwise, for webhook testing, can't you just point the payload at some local proxy or recipient? Postman's is pretty easy to use: <a href="https://learning.postman.com/docs/sending-requests/capturing-request-data/capture-with-proxy/" rel="nofollow">https://learning.postman.com/docs/sending-requests/capturing...</a> and there are others. You don't actually have to send the webhook outside the LAN just for development.