There's no free way to recover this. We can't export the volume for you, give you temporary read-only access, or recover its data another way on your behalf. We also can't extend or pause the 15 October 2026 deletion date for this request.

The CLI file commands work through the service the volume is attached to, so they need that service to have an active deployment. Your Postgres service's latest deployment has been removed, which is why you're getting that error.

To get the service running again, the workspace needs an active paid plan. On the Plans page, "Deploy with Hobby" opens a subscription form, and nothing is charged or activated until you click its separate "Subscribe to Hobby Plan" button. We haven't changed anything on your account and won't start a plan or any charges for you.

We can't confirm whether the database files on the volume are intact, so we can't say what a redeploy would recover.

Please escalate this request for review by a human Railway support representative. Please consider only options that require no paid upgrade and incur no new charges. Do not activate any paid service on my behalf. Thank you.

Thank you for being clear about the no-charge requirement. Nothing on your account has been changed, and no plan or charge will be started for you.

We don't have a no-cost option for this. We can't export the volume, give temporary read-only access, or recover its data another way on your behalf, and we can't hold the volume past its scheduled deletion date.

The Postgres service and its attached volume still exist on the project, but the CLI file commands only work while the service has an active deployment, and getting it running again needs an active paid plan on the workspace. Subscribing is only ever done by you, through the separate "Subscribe to Hobby Plan" button on the subscription form. If you decide not to subscribe, nothing further is charged.