<story><title>Ngrok Alternatives</title><url>https://github.com/anderspitman/awesome-tunneling</url></story><parent_chain></parent_chain><comment><author>moonchrome</author><text>Ngrok was really cool since I never thought about reverse proxying my localhost before l tried it.&lt;p&gt;But for the price of ngrok I&amp;#x27;m paying for a domain and a 2gb ram&amp;#x2F;2 CPU VM on hetzner and using SSH tunnels to nginx reverse proxy.&lt;p&gt;And setting up a shared server for a team with subdomains is just 10 mins of config changes per user - no way they can justify the cost for me.&lt;p&gt;If it was some symbolic price like 20$&amp;#x2F;year then I wouldn&amp;#x27;t bother, otherwise I&amp;#x27;ll take the VM I can load other random dev crap to when I need it.&lt;p&gt;And you&amp;#x27;re using standard web tech to set this up - if you aren&amp;#x27;t familiar with something required to set this up you will be better off learning it in the long run (if you&amp;#x27;re the target audience for ngrok) : VM setup, nginx, reverse proxy, SSH tunneling, let&amp;#x27;s encrypt, domain management&amp;#x2F;DNS - all valuable fundamental skills to acquire on a small project.</text></comment>
<story><title>Ngrok Alternatives</title><url>https://github.com/anderspitman/awesome-tunneling</url></story><parent_chain></parent_chain><comment><author>itsananderson</author><text>I feel like half of Ngrok&amp;#x27;s value prop is being undervalued here. Namely the fact that it captures requests for inspection and replay. That feature is an absolute game-changer for developing things like Webhooks.&lt;p&gt;First, it lets you easily see what the Webhooks payload looks like in real life. Second, it lets you hit your endpoint repeatedly with the same payload (while iterating on your code), without having to trigger the 3rd party event again.</text></comment>