Railway
Railway is a cloud application deployment platform (PaaS) that builds, deploys, and scales services, databases, and cron jobs from a Git repository or Docker image. Its programmatic surface is a GraphQL-first Public API served at https://backboard.railway.com/graphql/v2 - the same API that powers the Railway dashboard. There is no REST API; all queries and mutations are issued as GraphQL POST requests, and real-time build, deployment, and environment log streams are delivered as GraphQL subscriptions over a WebSocket endpoint at wss://backboard.railway.com/graphql/v2.
Limited machine-readable signal and partial portal coverage — documentation a human can read, but little a machine or agent can consume without scraping.
API Evangelist profiles Railway the way a machine reads it — 22 machine-readable artifacts across 13 APIs, pulled from the provider's own public surface and indexed so a developer, an analyst, or an AI agent can evaluate it against every other provider on the network.
Every provider in the network is reduced to the same set of machine-readable artifacts — OpenAPI contracts, event specifications, GraphQL schemas, runnable collections, pricing and rate-limit signals, security posture, OAuth scopes, and the agent surfaces (MCP servers and skills) that let software drive the API on its own. We profile them because the interface is the part of a company you can actually inspect: it is a truer signal of what a provider does than any marketing page. From those artifacts we compute the Kin Score — Railway scores 41.1/100 (thin), with a separate agent-readiness read of 13/100 (human only). The full breakdown is below, followed by every artifact we hold — each card links through to its machine-readable definition on apis.io.
Kin Score
This is the API Evangelist rating — a single, repeatable read computed from the artifacts on this page. Green fill is points earned; the red track is points possible, so every bar shows earned-versus-possible at a glance.
Kin Score
How this is scored →scored 2026-07-27 · rubric v0.5
How we profile Railway
Each block below is one kind of artifact we hold for Railway. For each we say what it is and why it earns a place in the profile, then list every one we've indexed — capped at two rows, scroll within the panel for the rest.
APIs 13
Each API is captured as its own OpenAPI definition — every operation, parameter, and response. This is the single most useful machine-readable description of what an API does, and it's what lets us score, lint, mock, and generate against it without asking the provider for anything.
Individual APIs this provider publishes, each with its own machine-readable definition.
Railway Projects API
GraphQL operations for creating, reading, updating, and deleting Railway projects - the top-level container for services and environments. Queries include project and projects; ...
Railway Services API
GraphQL operations for managing services and their per-environment service instances. Queries include service and serviceInstance; mutations include serviceCreate, serviceUpdate...
Railway Deployments API
GraphQL operations for triggering and managing deployments. Queries include deployment and deployments; mutations include serviceInstanceDeployV2, serviceInstanceRedeploy, deplo...
Railway Environments API
GraphQL operations for isolated project environments (for example production and staging). Queries include environment and environments; mutations include environmentCreate, env...
Railway Variables API
GraphQL operations for service and environment configuration variables. Queries include variables; mutations include variableUpsert, variableDelete, and variableCollectionUpsert...
Railway Volumes API
GraphQL operations for persistent volumes attached to services. Queries include volume; mutations include volumeCreate, volumeUpdate, volumeDelete, and volumeInstanceUpdate for ...
Railway Plugins API
GraphQL operations for legacy plugins (managed database add-ons such as Postgres, MySQL, Redis, and MongoDB). Queries include plugin; mutations include pluginCreate, pluginUpdat...
Railway Custom Domains API
GraphQL operations for attaching custom and Railway-provided domains to a service. Queries include customDomain and domains; mutations include customDomainCreate, customDomainDe...
Railway TCP Proxies API
GraphQL operations for exposing a service over raw TCP. Queries include tcpProxies; mutations include tcpProxyCreate and tcpProxyDelete.
Railway Usage and Metrics API
GraphQL operations for reading resource consumption and cost. Queries include usage, estimatedUsage, and metrics for per-service vCPU, memory, network egress, and disk utilization.
Railway Teams and Workspaces API
GraphQL operations for the authenticated account, its workspaces, teams, and members. Queries include me, workspace, and workspaces; mutations include workspaceUpdate and teamMe...
Railway Webhooks API
GraphQL operations for project webhooks that notify external URLs of deployment status changes. Queries include projectWebhooks; mutations include webhookCreate, webhookUpdate, ...
Railway Logs API
GraphQL log surface for builds, deployments, environments, and HTTP traffic. Available both as point-in-time queries (buildLogs, deploymentLogs, environmentLogs, httpLogs) and a...
Scroll within the panel for all 13 ·
Open Collections 1
Open, tool-agnostic collections carry the same runnable value as Postman without locking you to one client — the portable, forkable form of the same exercise.
Open, tool-agnostic API collections (OpenAPI-derived and Bruno).
Railway GraphQL Public API
OPEN COLLECTIONGraphQL 1
Where a provider ships GraphQL, the schema is the contract. We profile it alongside the REST surface so the whole interface is legible in one place.
GraphQL schemas published by this provider.
Railway GraphQL Public API
Railway is a cloud application deployment platform (PaaS). Its entire programmatic surface is a **GraphQL API** - there is no REST API. The Public API is the same API that power...
GRAPHQLPricing Plans 1
Pricing is part of the interface. Machine-readable plans tell you what a tier costs and includes before you commit — one of the six things the Kin Score reads for commercial clarity.
Published pricing tiers and plan structures.
Rate Limits 1
Rate limits are the difference between a demo that works and a production integration that doesn't fall over. Publishing them is an operational-transparency signal — and a hard requirement for any agent that plans its own throughput.
Documented rate limits and quota policies.
Railway App Rate Limits
RATE LIMITSFinOps 1
Cost, billing, and metering signals let a buyer model the financial operations of an API before it's live. We profile them for the same reason we profile pricing: the money is part of the contract.
Cost, billing, and metering signals for API financial operations.
Railway App Finops
FINOPSEvent Specifications 1
Not every API is request/response. AsyncAPI describes the event-driven and streaming side — the webhooks and channels — so the asynchronous half of the interface is documented the same way the synchronous half is.
AsyncAPI definitions for this provider's event-driven and streaming APIs.
Railway GraphQL Subscriptions (WebSocket)
AsyncAPI 2.6 description of Railway's **real-time log streaming** surface. Unlike many providers in this catalog, Railway **does** publish a documented public WebSocket transpor...
ASYNCAPISpectral Rules 1
Governance rulesets we run against this provider's specs — the automated checks behind parts of the score. Profiling them makes the quality bar explicit and re-runnable, not a matter of opinion.
Railway API Rules
SPECTRALSecurity Posture 2
Authentication, domain security, vulnerability disclosure, and trust-center signals — the evidence that a provider takes security seriously enough to document it. We profile it because you can't govern what you can't see.
Authentication, domain security, vulnerability disclosure, and trust-center signals.
Resources
Every other property we hold for Railway — documentation, portals, status pages, policies, and corporate surface — grouped by the job it does, following the integrator's arc from getting started to running in production.
Documentation 1
Reference material describing how the API behaves
Build 1
SDKs, sample code, and the tooling you integrate with
Access & Security 2
Authentication, authorization, and security posture
Operate 1
Status, limits, changes, and where to get help
Commercial 2
Pricing, plans, and the legal terms of use
Company 3
The organization behind the API
← All providers · Data indexed from github.com/api-evangelist/railway-app · machine-readable index on apis.io