I dont understand replicas pricing
markwitt1
PROOP

a month ago

I set up a Railway service and set the replicas to 50. In 99% of cases most of them will be idle, and only use idle memory.

Does anything speak against doing that? how is railway able to reserve 50 big instances for me?

Are there any strings attached regarding pricing?

Solved

1 Replies

Railway
BOT

a month ago

Railway bills purely on actual resource consumption (CPU and memory metered by the minute), not on reserved capacity, so nothing is "reserved" for you and there is no flat fee per replica. With 50 replicas you pay for whatever CPU and memory all 50 instances actually consume, summed together, so even idle replicas accrue cost for their baseline idle memory footprint multiplied across all 50. Resource rates are $10/GB/month for RAM and $20/vCPU/month for CPU, detailed in our pricing docs, and each replica can independently use up to your plan's per-service limits as described in the scaling docs.

[{"text": "Railway bills on actual resource consumption metered by the minute, not reserved capacity, with no flat per-replica fee", "sourceToolCallIds": ["searchDocs"]}, {"text": "You pay for the summed CPU and memory all replicas actually consume", "sourceToolCallIds": ["searchDocs"]}, {"text": "RAM is $10/GB/month and CPU is $20/vCPU/month", "sourceToolCallIds": ["searchDocs"]}, {"text": "Each replica can independently use up to the plan's per-service resource limits", "sourceToolCallIds": ["searchDocs"]}]


Status changed to Awaiting User Response Railway 29 days ago


Railway
BOT

22 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 22 days ago


Welcome!

Sign in to your Railway account to join the conversation.

Loading...