Railway · Rate Limits

Railway App Rate Limits

Railway enforces per-plan rate limits on the GraphQL Public API (https://backboard.railway.com/graphql/v2), expressed as requests per hour (RPH) and, on paid plans, requests per second (RPS). Limits scale with the workspace plan: Free/Trial, Hobby, Pro, and Enterprise. Every response carries X-RateLimit-* headers so clients can track remaining quota, and throttled requests return HTTP 429 with a Retry-After header.

Railway App Rate Limits is the machine-readable rate-limit profile for Railway on the APIs.io network, conforming to the API Commons Rate Limits specification.

It captures 6 rate-limit definitions, measuring requests.

The profile also includes 3 backoff/retry policies defined and response codes documented for throttled.

Tagged areas include Deployment, PaaS, Cloud, GraphQL, and Rate Limiting.

6 Limits Throttle: 429
DeploymentPaaSCloudGraphQLRate LimitingQuotasThrottling

Limits

Free / Trial Requests Per Hour account
requests · hour
100
Applies to the Trial tier before a paid plan is attached.
Hobby Requests Per Hour workspace
requests · hour
1000
Hobby plan hourly ceiling on GraphQL Public API calls.
Hobby Requests Per Second workspace
requests · second
10
Hobby plan burst ceiling.
Pro Requests Per Hour workspace
requests · hour
10000
Pro plan hourly ceiling on GraphQL Public API calls.
Pro Requests Per Second workspace
requests · second
50
Pro plan burst ceiling.
Enterprise workspace
requests · hour
custom
Negotiated custom rate limits.

Policies

Tiered Limits
Rate limits increase as workspaces move from Trial to Hobby to Pro to Enterprise.
Header-Based Tracking
Clients should read X-RateLimit-Remaining and X-RateLimit-Reset to pace requests.
Backoff Strategy
On HTTP 429, honor the Retry-After header and apply exponential backoff with jitter.

Sources