Volume backups support manual and scheduled (daily/weekly/monthly) creation with full restore capability, and on Pro, automatic backups are also created before image auto-updates. We don't publicly document the specific storage backend or redundancy details (e.g. whether backups land on S3, R2, or what parity scheme is used), so we can't share those specifics here. The backups reference covers what's available from a feature standpoint.

Can those specifics be shared?

We don't disclose the specifics of our backup storage infrastructure publicly. The backups reference covers everything we document about the feature, including creation, scheduling, restore, and size limits.

Can I have a member of the community or moderator reply?

As the bot mentioned, the specifics of Railway's infrastructure won't be disclosed publicly.

So I can assume that backups and volumes could be lost/deleted at any time then? We need some sort of assurance that your backup solution is thorough enough for enterprise workloads.

Backups and volumes won't be lost or deleted at any time.

How is this assured? Unfortunately, you can't just say "we do backups" to clients. They want technical explanations on how their data is secured against data loss.