[cachestash]

I honestly don't see the use of this. Why would anyone want to expose a development environment to the internet, especially in the age of devops and reproducible environments. 98% of all my development happens over 127.0.0.1 now. I have zero need to expose a service when I can replicate multi sites on a lan with the lightweight environment given to me with containers and vms.

[kelnos]

One of the original popular use cases for services like this was if you're developing against a third-party service that wants to send you webhooks.

But it's also useful if you want to run something locally and show it to a friend or co-worker. The co-worker bit is especially useful now with people working from home.

Regardless, this space is pretty crowded, so I'm not sure what a new offering could do to differentiate. I'm skeptical of their "6x faster than ngrok" claim, and even if it is true, I don't think this is a use case where that metric really matters all that much.

(Full disclosure: the founder of ngrok is a friend of mine, so I'm certainly biased here.)

[jedieaston]

If you are working on someone and want to show a friend, or if you want to open a project on another device that isn’t necessarily on the same network. And you don’t have to pay for a droplet or setup a PaaS if you’re in the middle of the nitty gritty of development.