Resuming only staging is not possible through a plan change. Once a paid subscription becomes active, we automatically redeploy the deployments that were stopped when the trial ended, across all projects and environments in the workspace, and checkout has no option to skip that or to exclude production. Existing attached volumes are mounted again for those redeployed services. Subscribing does not replace or detach them.

There is no read-only HTTPS export for the volumes while services are stopped. Volume file access (the CLI volume file commands and SFTP) works through the attached service and needs an active deployment, so a volume with no running deployment cannot be listed or downloaded.

For retention, volume data on Free or Trial workspaces is deleted 30 days after the trial credits expire, and a warning comes first. That puts your deadline 30 days after the date your credits ran out. See data retention.

Hobby costs $5/month, charged upfront, and includes $5 of usage. If usage stays under $5 you pay $5, and if it goes over you pay $5 plus the extra usage. There is no other mandatory charge. Any leftover trial credit on an expired trial does not carry over. More detail is in understanding your bill.

The automated reply says a paid upgrade resumes all paused deployments and suspended volumes cannot be exported. Could a human confirm whether Railway support can preserve or export existing suspended volume data without resuming any production service? If not, is there a supported way to guarantee production remains stopped before subscription activation without deleting or detaching existing data? Please also clarify how we can obtain the exact credit-expiry and volume-retention timestamps. This is a request for technical advice only: do not change the account, activate a plan, modify settings, deploy, restart or delete anything.

We can't preserve or export volume data separately while the workspace is stopped. We don't reactivate individual services, run exports on your behalf, or give read-only access to stopped volumes. Volume file access (the CLI volume file commands and SFTP) goes through the attached service and needs an active deployment.

We also can't guarantee production stays stopped through a paid subscription. When a subscription becomes active, the deployments that were stopped are redeployed automatically across all projects and environments in the workspace. Checkout has no option to skip that or to choose environments. Any attached volumes are mounted again for those redeployed services, and pre-deploy commands and start commands run as they would on a normal deploy.

We don't show an exact credit-expiry or deletion timestamp in the dashboard. The policy is that volume data on Trial or Free workspaces is deleted 30 days after the trial credits expire, and a warning email is sent before that happens. Use the date your credits ran out to work out the deadline. See data retention.