Quick answer
Railway documents paid volume resize as Pro self-serve up to 1 TB. The standard Pro volume size is lower and can be expanded on paid plans.
Verified Aug 22, 2026Official source
Current limits
| Constraint | Current value | Scope | Verified source |
|---|---|---|---|
| paid volume resizeThe standard Pro volume size is lower and can be expanded on paid plans. | Pro self-serve up to 1 TB | Pro | RailwayAug 22, 2026 |
Why does this limit matter?
Capacity planning should distinguish the default plan allocation from the maximum self-serve resize.
This value is scoped to Pro; a different plan, runtime, model, endpoint, region, or account can produce a different effective constraint.
What should you check?
- Confirm plan, current size, resize eligibility, backups, and expected growth before expansion.
- 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
- A volume attaches to a specific service and deployment topology affects availability.
- 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