👆 would be amazing!

I think going for both volume, and "popular" databases would be the way to go, you don't want to lose pgdump as an example.
We also run other databases such as Chroma vector store, which would be cool to backup as well.

I'd add Redis to the list perhaps but echo the original poster's request.

Additionally, being able to load this data, or a seed data file into PR environments or forked environments would be clutch. Right now I'm hacking this as a custom one-off data loader service that only runs in environments lacking a PRODUCTION environment variable

maybe this could be implemented in a more generic way providing a native backup solution for VOLUMES.

the team has mentioned volume snapshots as the backup method, this would allow taking backups of services that use sqlite databases, along with so much more

Volume snapshots would be awesome

I’d also say a restore feature would be useful. I’d have a lot more confidence with backups and recovery if it was natively baked in to the platform.

Its a no-go that Railway does not provide automatic backups of my Postgres database at least done daily. Render provides daily backups AND point in time recovery. Neon does as well.

This is definitely a shortcoming of Railway... which since you're now saying you help with HIPAA compliance, some pieces are missing... backups, retention, recovery, traceability are all part of that where most good cloud DB providers seem to provide out of the box. Would love this

This really is an uncle in the foot

Hey all!

We now have native backups, it is not limited to databases but works with any service that has an attached volume, check out our docs here -

https://docs.railway.com/reference/backups