Got creation limit for new account
haiika
HOBBYOP

7 days ago

Hello, I encountered an error while deploying:

"You've hit the service creation limit for new accounts (25 services per day). Contact us at station.railway.com to raise this."

I had previously used your AI Agent to describe the architecture, but subsequently experienced multiple deployment failures. Please help me resolve this issue.

Thank you,

Haika

Awaiting User Response

3 Replies

Railway
BOT

7 days ago

That limit is real and applies to your account: it caps service creation at 25 services per rolling 24-hour window. As the services you created earlier age out of that window, you will be able to create new ones again.


Status changed to Awaiting User Response Railway • 7 days ago


Railway

That limit is real and applies to your account: it caps service creation at 25 services per rolling 24-hour window. As the services you created earlier age out of that window, you will be able to create new ones again.

haiika
HOBBYOP

7 days ago

Hi,

I'm deploying a production SaaS platform to Railway and hit the 25 service/day creation limit.

I need to deploy 7 services:

PostgreSQL 18 (with n8n database)

Redis 7

Laravel app (h-web)

Queue worker (h-worker)

Scheduler (h-scheduler)

n8n 2.38.7 (workflow automation)

WAHA (WhatsApp integration)

Plus 6 persistent volumes for databases and storage.

Could you increase my service creation limit so I can complete this initial deployment? I'm ready to go live and have everything staged and tested.

Thanks


Status changed to Awaiting Railway Response Railway • 7 days ago


Railway
BOT

7 days ago

The 25-per-day cap counts every service created in the last 24 hours, including the ones created during your earlier deployment attempts. It resets on a rolling basis, so as those earlier creations age past 24 hours you will have room again, and your 7 services fit well within 25 once they do.


Status changed to Awaiting User Response Railway • 7 days ago


Welcome!

Sign in to your Railway account to join the conversation.

Loading...