Hi Railway Team,

I wanted to ask about the design decision behind not allowing storage buckets to be public. Currently, we cannot directly access or view bucket contents without generating signed URLs.

This approach adds extra overhead, as every file request requires generating a presigned URL from the backend, which can slow down performance and increase backend resource usage.

Could you please clarify the reasoning behind this limitation? Additionally, are there any plans to support controlled public access (for example, optional public buckets or simpler access methods) to improve performance and reduce dependency on backend services?

Thank you.