Hello Railway Support Team,

We are using Railway Hobby with an existing PostgreSQL service and Web service in the same staging environment.

Before performing a one-time forward-only database migration, we need to obtain a recoverable backup and independently verify restoration without changing the original database.

Our blockers are:

1. Volume backup creation is restricted to Pro.
2. We cannot independently verify the SSH gateway's host identity using a Railway-published host key or CA.
3. The Dashboard SQL editor adds LIMIT to queries and cannot reliably execute our multi-statement transactional migration.
4. The Web service's masked DATABASE_URL does not reveal whether it references the intended PostgreSQL service.

Could you recommend a supported Hobby-plan workflow for:

• Secure, encrypted PostgreSQL logical backup without exposing credentials.
• Independent restoration and verification without modifying the source database.
• A single transactional schema migration after backup recovery is verified.
• Confirming the Web-to-PostgreSQL reference without revealing secrets.

We prefer no public database exposure, no additional paid services, and no changes to production.

No credentials, private keys, database URLs, or customer data are included.

Thank you.