Skip to content
Hobby Plan - Minimum CPU/RAM Limits per Service Replica
Anonymous
OP

12 days ago

Hi Railway Team,

I'm currently using the Hobby plan and preparing a temporary verification service. Before creating or deploying anything, I'd like to confirm the resource configuration limits.

Could you please clarify:

  1. Does the Hobby plan support setting a service replica limit of 0.5 vCPU and 0.5 GB RAM?
  2. If not, what are the exact minimum configurable CPU and RAM values?
  3. Are these minimum limits available when creating a new service, or only after deployment?
  4. Does Railway provide a hard spending cap for an individual service, or are spending controls only available at the workspace level?

This is a small, temporary technical verification. No service has been created or deployed yet.

I'm looking to confirm the supported settings and billing boundaries before proceeding.

Thank you!

Solved

1 Reply

Railway
BOT

12 days ago

Yes, 0.5 vCPU and 0.5 GB RAM per replica is supported on Hobby. That is also the lowest value you can set on any plan. You set it in the service's Settings > Deploy > Replica Limits. These limits cap what a replica can use, but billing is based on actual usage. Setting them too low can make the service crash.

You can create an empty service with no source, set its configuration, and apply it before connecting a repo or image. Applying settings to a service that has no source does not start a deployment.

Spending caps work at the workspace level, not per service. On the Workspace Usage page you can set a custom email alert and a hard limit for Compute Usage. The minimum hard limit is $10. When usage reaches it, every workload in the workspace is taken offline. See Cost Control for details.


Status changed to Awaiting User Response Railway • 12 days ago


Railway
BOT

5 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 • 5 days ago


Welcome!

Sign in to your Railway account to join the conversation.

Loading...