Railway Service Management

Check status, update properties, and advanced service creation.

When to Use

• User asks about service status, health, or deployments
• User asks “is my service deployed?”
• User wants to rename a service or change service icon
• User wants to link a different service
• User wants to deploy a Docker image as a new service (advanced)

Note: For creating services with local code (the common case), prefer the railway-new skill which handles project setup, scaffolding, and service creation together.

For GitHub repo sources: Use railway-new skill to create empty service, then railway-environment skill to configure source.repo via staged changes API.

Create Service

Create a new service via GraphQL API. There is no CLI command for this.

Get Context

1railway status --json

Extract:

• project.id - for creating the service
• environment.id - for staging the instance config

Create Service Mutation

1mutation serviceCreate($input: ServiceCreateInput!) {
2  serviceCreate(input: $input) {
3    id
4    name
5  }
6}

ServiceCreateInput Fields

Example: Create empty service

1bash <<'SCRIPT'
2${CLAUDE_PLUGIN_ROOT}/skills/lib/railway-api.sh \
3  'mutation createService($input: ServiceCreateInput!) {
4    serviceCreate(input: $input) { id name }
5  }' \
6  '{"input": {"projectId": "PROJECT_ID"}}'
7SCRIPT

Example: Create service with image

1bash <<'SCRIPT'
2${CLAUDE_PLUGIN_ROOT}/skills/lib/railway-api.sh \
3  'mutation createService($input: ServiceCreateInput!) {
4    serviceCreate(input: $input) { id name }
5  }' \
6  '{"input": {"projectId": "PROJECT_ID", "name": "my-service", "source": {"image": "nginx:latest"}}}'
7SCRIPT

Connecting a GitHub Repo

Do NOT use serviceCreate with source.repo - use staged changes API instead.

Flow:

1. Create empty service: serviceCreate(input: {projectId: "...", name: "my-service"})
2. Use railway-environment skill to configure source via staged changes API
3. Apply to trigger deployment

After Creating: Configure Instance

Use railway-environment skill to configure the service instance:

 1{
 2  "services": {
 3    "<serviceId>": {
 4      "isCreated": true,
 5      "source": { "image": "nginx:latest" },
 6      "variables": {
 7        "PORT": { "value": "8080" }
 8      }
 9    }
10  }
11}

Critical: Always include isCreated: true for new service instances.

Then use railway-environment skill to apply and deploy.

Check Service Status

1railway service status --json

Returns current deployment status for the linked service.

Deployment History

1railway deployment list --json --limit 5

Present Status

Show:

• Service: name and current status
• Latest Deployment: status (SUCCESS, FAILED, DEPLOYING, CRASHED, etc.)
• Deployed At: when the current deployment went live
• Recent Deployments: last 3-5 with status and timestamps

Deployment Statuses

Update Service

Update service name or icon via GraphQL API.

Get Service ID

1railway status --json

Extract service.id from the response.

Update Name

1bash <<'SCRIPT'
2${CLAUDE_PLUGIN_ROOT}/skills/lib/railway-api.sh \
3  'mutation updateService($id: String!, $input: ServiceUpdateInput!) {
4    serviceUpdate(id: $id, input: $input) { id name }
5  }' \
6  '{"id": "SERVICE_ID", "input": {"name": "new-name"}}'
7SCRIPT

Update Icon

Icons can be image URLs or animated GIFs.

Railway Devicons: Query https://devicons.railway.app/{query} for common developer icons (e.g., github, postgres, redis, nodejs). Browse all at https://devicons.railway.app

1bash <<'SCRIPT'
2${CLAUDE_PLUGIN_ROOT}/skills/lib/railway-api.sh \
3  'mutation updateService($id: String!, $input: ServiceUpdateInput!) {
4    serviceUpdate(id: $id, input: $input) { id icon }
5  }' \
6  '{"id": "SERVICE_ID", "input": {"icon": "https://devicons.railway.app/github"}}'
7SCRIPT

ServiceUpdateInput Fields

Link Service

Switch the linked service for the current directory:

1railway service link

Or specify directly:

1railway service link <service-name>

Composability

• Create service with local code: Use railway-new skill (handles scaffolding + creation)
• Configure service: Use railway-environment skill (variables, commands, image, etc.)
• Delete service: Use railway-environment skill with isDeleted: true
• Apply changes: Use railway-environment skill
• View logs: Use railway-deployment skill
• Deploy local code: Use railway-deploy skill

Error Handling

No Service Linked

No service linked. Run `railway service link` to link a service.

No Deployments

Service exists but has no deployments yet. Deploy with `railway up`.

Service Not Found

Service "foo" not found. Check available services with `railway status`.

Project Not Found

User may not be in a linked project. Check railway status.

Permission Denied

User needs at least DEVELOPER role to create services.

Invalid Image

Docker image must be accessible (public or with registry credentials).