Hi Railway team and community,

I have a question about how Railway calculates project storage limits and billing for Database volumes vs Storage Buckets.

Situation:

- I have a Railway project with PostgreSQL database

- I exported records from database to Railway Storage Bucket

- After exporting and deleting data from database, my project total volume hasn't changed

Question:

1. Do Railway Database storage and Storage Bucket storage count towards the same project storage quota?

2. Are they billed the same way (same price per GB)?

3. Or are Database and Storage Bucket separate storage pools with separate limits/billing?

What I observed:

- Exported database data to Storage Bucket successfully

- Deleted data from database

- Project total volume remained unchanged

Expected clarification:

- If they share the same quota: Moving data from DB to Bucket shouldn't change total volume (makes sense)

- If they're separate: I'd expect to see some change, or at least understand how each is counted

Thanks for clarifying how project storage is calculated and billed!