Hi Railway team,

I’m working with internal Python packages that can only be accessed via our company VPN. This makes it impossible to build Docker images on Railway, because pip requests are made from your servers and cannot reach the internal resources.

It would be extremely helpful to have an option similar to:

railway up -s API -d --local-build

...where the build happens locally (with access to internal resources), and the resulting Docker image is then pushed to Railway.

Using a private registry could be a workaround, but it introduces extra maintenance overhead and requires exposing the service to the public network (accessible via api key) - something we’d like to avoid for security reasons.

Thank you for considering this!