We don't provide an export or download of the source snapshot, build context, build manifest, or built image for a deployment, whether it was created with railway up or any other way, and there's no self-serve way to retrieve them.

What you can do without redeploying is read files from the running container itself. The service's Console tab in the dashboard has a Files panel for browsing and downloading files, and scp/sftp against ssh.railway.com (with an SSH key added via railway ssh keys add) can copy a whole directory, for example scp -r [email protected]:/app ./app. This only gives you what ended up in the final image, so with a multi-stage build or bundled output you'll get the build output, not the original source.

A related deployment-safety question: suppose an environment has an existing service A and unrelated pending staged changes for service B. If I run a code-only railway up explicitly targeting service A, can the upload, build, or deployment commit any of the staged environment changes?

Is there a documented, officially supported way to deploy A using its currently applied configuration while leaving the entire pending staged batch untouched?