Hello! I've been recently working with a self-hosted Netbird instance (outside Railway, ofc) and created railbird to access our services hosted in Railway as long as we're connected in our Netbird instance.

The main purpose was to enable site-to-site connectivity for use cases such as kong clustering since public TCP proxies is not a good idea (and most probably won't work).

While experimenting, I accidentally found that it is possible to set the railbird deployment as a working exit node. By accident, I mean I've set the railbird deployment as an exit node, forgot about it, and then had a call while my device was connected to our Netbird mesh. Seeing the egress go up after the call made me think that the exit node functionality is working.

I'm asking if it is okay to use Railway as a Netbird exit node because we have an existing issue with the ISPs in our office; traffic to github.com and ghcr.io during business hours is severely degraded. For context, a single go mod tidy in our CI pipeline takes about an hour and that should take no more than 1 minute under normal conditions. A single 10mb asset download from github takes 20mins <:angreee:1044158679664037888> .

I'm just asking to know if this could be a viable option. Based on the pricing, 1TB egress for around $50 sounds pretty reasonable given that some VPNs charge around $10 per seat.

If it breaks ToS, we'll just not use the exit node functionality.

Happy to hear a response from the team <:yeeee:993361534308851782>