Pro workspace still blocked by “25 services per day” new account limit
april-jk
PROOP

a month ago

Hi Railway team,

I’m on a Pro workspace, but service creation is still blocked by the “new accounts (25 services per day)” limit.

Workspace details:

  • Workspace name: oneceo- deployment
  • Workspace ID: 828b5f75-22d5-490b-a634-91c188b4f049
  • Workspace plan: PRO
  • Customer state: ACTIVE

Project involved:

  • Project name: oneceo-user-3f290763-8bf-4a3624f
  • Project ID: a2f6cffe-28a7-48c1-81f0-b907fb7f5088

Observed behavior:

  • Railway CLI can access the workspace and project normally.
  • But when creating a new service, Railway returns:
  • You've hit the service creation limit for new accounts (25 services per day).

I reproduced this directly with Railway CLI, not only through my platform integration.

What I need:

  • Please confirm why this Pro workspace/account is still under the new-account service creation restriction.
  • Please remove or raise the service creation limit for this account/workspace so new services can be created normally.

This is blocking first-time deployment in a production workflow.

Thanks.

Solved

5 Replies

Status changed to Awaiting Railway Response Railway about 1 month ago


a month ago

Can you please share your use case for using more than 25 services a day for our records? This is just our standard process whenever we receive a request for a limit increase.


Status changed to Awaiting User Response Railway about 1 month ago


brody

Can you please share your use case for using more than 25 services a day for our records? This is just our standard process whenever we receive a request for a limit increase.

april-jk
PROOP

a month ago

We are an agent platform that provides users with end-to-end website deployment services, enabling users to launch a fully functional online website with just a simple prompt.

We plan to use Railway as our deployment infrastructure. Since the entire deployment process is automatically triggered and executed by AI, deployment failures may occur occasionally, and individual users may also require repeated redeployment multiple times.

This will easily exceed the current daily deployment limit of 25 requests. Notably, we have already hit this 25-times daily cap during our internal testing phase.

Therefore, we kindly request the removal of this usage restriction. If the limit cannot be lifted, we will have no choice but to migrate our services to an alternative platform.


Status changed to Awaiting Railway Response Railway about 1 month ago


a month ago

Thanks for the context. We've raised the service creation limit on your workspace. You should be able to create services without hitting the previous cap now.


Status changed to Awaiting User Response Railway about 1 month ago


brody

Thanks for the context. We've raised the service creation limit on your workspace. You should be able to create services without hitting the previous cap now.

april-jk
PROOP

a month ago

What is the current daily creation limit?


Status changed to Awaiting Railway Response Railway about 1 month ago


a month ago

Apologies, "raised" is the wrong word. I should have said "removed." Now, the only limits would be the standard API rate limits.


Status changed to Awaiting User Response Railway about 1 month ago


Status changed to Solved april-jk about 1 month ago


Welcome!

Sign in to your Railway account to join the conversation.

Loading...