Quick answer
Railway documents persistent volume capacity as Free/Trial: 0.5 GB; Hobby: 5 GB; Pro: 50 GB. Paid plans can resize, and Pro offers a self-serve path up to 1 TB.
Verified Aug 22, 2026Official source
Current limits
| Constraint | Current value | Scope | Verified source |
|---|---|---|---|
| persistent volume capacityPaid plans can resize, and Pro offers a self-serve path up to 1 TB. | Free/Trial: 0.5 GB; Hobby: 5 GB; Pro: 50 GB | Plan dependent | RailwayAug 22, 2026 |
Why does this limit matter?
A deployment can have ample compute while its attached persistent volume becomes the first capacity constraint.
This value is scoped to Plan dependent; a different plan, runtime, model, endpoint, region, or account can produce a different effective constraint.
What should you check?
- Open the service volume settings and compare used bytes with the plan's current maximum.
- Confirm the exact plan, model, runtime, endpoint, region, and account that serve the failing workload.
- Record the observed value, response headers or configuration, timestamp, and source without logging secrets.
Important caveats
- Volume capacity is distinct from ephemeral deployment filesystem space.
- Treat the official source and live account configuration as authoritative if they differ from this verified snapshot.
HyperObserve reports the documented platform constraint. Your application, SDK, gateway, provider, region, or account can impose a lower effective limit.
Related