a month ago
Hello Railway Support Team,
I would like clarification regarding billing for services that are not actively running.
Our requirement is to keep certain services completely offline when they are not in use and only start them when required. We would like to understand:
- If a service is stopped or taken offline, will compute charges stop immediately?
- Are there any charges that continue while the service is offline (e.g., storage, volumes, databases, networking, or plan fees)?
- Is there a way to completely pause a service so that no usage-based charges are incurred until it is restarted?
- What is the recommended approach for environments that are used only occasionally and should not generate costs while inactive?
- Are there any auto-sleep, scale-to-zero, or hibernation options available for this use case?
Please provide guidance on the best way to minimize costs while retaining the ability to restart services when needed.
Thank you for your assistance.
1 Replies
a month ago
Stopping a service halts compute (CPU/memory) charges immediately since billing is per-minute, but volumes and buckets continue to bill for storage even while stopped since the data is still stored. Your Pro plan subscription fee also continues regardless of service state. To avoid storage charges entirely, you would need to delete the volume or bucket. For services that receive traffic intermittently, enabling Serverless in the service settings automatically stops a service after 10 minutes of no outbound traffic and wakes it on the next inbound request, so you only pay for compute while it is actually running.
Status changed to Awaiting User Response Railway • 26 days ago
19 days ago
This thread has been marked as solved automatically due to a lack of recent activity. Please re-open this thread or create a new one if you require further assistance. Thank you!
Status changed to Solved Railway • 19 days ago