This is a question the Railway community is better placed to answer than support: people who have already worked this out on their own projects and can tell you what actually worked.

So we'd like to open your thread as a community bounty. Railway pays a bounty to the community member who answers it, and threads like this usually get picked up quickly.

Opening it makes this entire thread public, including everything already posted. Nothing becomes public until you decide. Use the buttons below.

• Open to the community - Before you click, take a moment to edit or remove anything you'd rather not share. The thread becomes publicly visible right away.
• Keep it private and close the thread - Nothing becomes public and the thread closes.

I'm using sandboxes heavily in production, and I can say that while they work well - they are not "great".

A few issues I noticed have been:

• sandboxes created from the SDK regularly do not show up when calling list, they are only accessible via the sandbox id. this means its possible to launch a sandbox and never know it exists, and therefore never have it shutdown unless you launched it with an idle timeout.
• Railway keep changing the base OS image without any notice or changelog, it went from Debian 13 to Ubuntu 26.04 and my entire workflow broke (package versions completely different).
• Further on the above, you are at the mercy of whatever Railway do to the base image as you cannot choose what distro to launch with (centos, debian, ubuntu, etc), only a checkpoint you created earlier.
• The base image ship with LOTS of stuff you don't want, in an effort to be "helpful" and increases risk surface pretty wide. you will spend a lot of time removing and uninstalling all of this to get an environment you are safe in.