Railway Deployment Management

Manage existing Railway deployments: list, view logs, redeploy, or remove.

Important: “Remove deployment” (railway down) stops the current deployment but keeps the service. To delete a service entirely, use the railway-environment skill with isDeleted: true.

When to Use

• User says “remove deploy”, “take down service”, “stop deployment”, “railway down”
• User wants to “redeploy”, “restart the service”, “restart deployment”
• User asks to “list deployments”, “show deployment history”, “deployment status”
• User asks to “see logs”, “show logs”, “check errors”, “debug issues”

List Deployments

1railway deployment list --limit 10 --json

Shows deployment IDs, statuses, and metadata. Use to find specific deployment IDs for logs or debugging.

Specify Service

1railway deployment list --service backend --limit 10 --json

View Logs

Deploy Logs

1railway logs --lines 100 --json

In non-interactive mode, streaming is auto-disabled and CLI fetches logs then exits.

Build Logs

1railway logs --build --lines 100 --json

For debugging build failures or viewing build output.

Logs for Failed/In-Progress Deployments

By default railway logs shows the last successful deployment. Use --latest for current:

1railway logs --latest --lines 100 --json

Filter Logs

1# Errors only
2railway logs --lines 50 --filter "@level:error" --json
3
4# Text search
5railway logs --lines 50 --filter "connection refused" --json
6
7# Combined
8railway logs --lines 50 --filter "@level:error AND timeout" --json

Time-Based Filtering

1# Logs from last hour
2railway logs --since 1h --lines 100 --json
3
4# Logs between 30 and 10 minutes ago
5railway logs --since 30m --until 10m --lines 100 --json
6
7# Logs from specific timestamp
8railway logs --since 2024-01-15T10:00:00Z --lines 100 --json

Formats: relative (30s, 5m, 2h, 1d, 1w) or ISO 8601 timestamps.

Logs from Specific Deployment

Deploy logs:

1railway logs <deployment-id> --lines 100 --json

Build logs:

1railway logs --build <deployment-id> --lines 100 --json

Get deployment ID from railway deployment list.

Note: The deployment ID is a positional argument, NOT --deployment <id>. The --deployment flag is a boolean that selects deploy logs (vs --build for build logs).

Redeploy

Redeploy the most recent deployment:

1railway redeploy --service <name> -y

The -y flag skips confirmation. Useful when:

• Config changed via railway-environment skill
• Need to restart without new code
• Previous deploy succeeded but service misbehaving

Restart Container Only

Restart without rebuilding (picks up external resource changes):

1railway restart --service <name> -y

Use when external resources (S3 files, config maps) changed but code didn’t.

Remove Deployment

Takes down the current deployment. The service remains but has no running deployment.

1# Remove deployment for linked service
2railway down -y
3
4# Remove deployment for specific service
5railway down --service web -y
6railway down --service api -y

This is what users mean when they say “remove deploy”, “take down”, or “stop the deployment”.

Note: This does NOT delete the service. To delete a service entirely, use the railway-environment skill with isDeleted: true.

CLI Options

deployment list

logs

redeploy

restart

down

Presenting Logs

When showing logs:

• Include timestamps
• Highlight errors and warnings
• For build failures: show error and suggest fixes
• For runtime crashes: show stack trace context
• Summarize patterns (e.g., “15 timeout errors in last 100 logs”)

Composability

• Push new code: Use railway-deploy skill
• Check service status: Use railway-status skill
• Fix config issues: Use railway-environment skill
• Create new service: Use railway-new skill

Error Handling

No Service Linked

No service linked. Run `railway service` to select one.

No Deployments Found

No deployments found. Deploy first with `railway up`.

No Logs Found

Deployment may be too old (log retention limits) or service hasn’t produced output.