piko

As commented below, Pico is already a well established name for a text editor so I've renamed to Piko: https://github.com/andydunstall/piko

Not sure I follow Pico is a reverse proxy, so the upstream services open outbound-only connections to Pico, then proxy clients send HTTP requests to Pico which are then routed to the upstream services So as long as your browser can access Pico it should work like any other proxy (Theres a getting started guide if that helps: https://github.com/andydunstall/pico/blob/main/docs/getting-...)

The compose file is in the demo folder, you don't need to guess what it's going to do. https://github.com/andydunstall/pico/blob/main/docs/demo/doc... Looks like it's spinning up three replicas of Pico

That demo only uses docker compose: https://github.com/andydunstall/pico/blob/main/docs/demo/doc...

Looks like there is from the instructions in the getting-started guide: https://github.com/andydunstall/pico/blob/main/docs/getting-...

Pico is an open-source alternative to Ngrok. Unlike most other open-source tunnelling solutions, Pico is designed to serve production traffic and be simple to host (particularly on Kubernetes). Upstream services connect to Pico and register endpoints. Pico will then route requests for an endpoint to a registered upstream service via its outbound-only connection. This means you can expose your services without opening a public port. Pico runs as a cluster of nodes in order to be fault tolerant, scale horizontally and support zero downtime deployments. It is also easy to host, such as a Kubernetes Deployment or StatefulSet behind a HTTP load balancer.

Very cool, I've been looking for an open source Ngrok alternative as well though for production traffic rather than development (I couldn't find a good option on awsome-tunneling so have been playing about with a proof of concept at https://github.com/andydunstall/pico)