Railway CLI

Railway CLI is Railway's official command surface for deploying and operating hosted projects from the shell. It covers project setup, service management, environment configuration, logs, storage, network endpoints, and local development helpers tied to Railway projects.

• Create or link projects and services, deploy the current directory or a template, and redeploy, restart, or scale services without leaving the terminal.
• Inspect project, service, and deployment state; stream build or deploy logs; manage environment variables; and open SSH, database, or local shell sessions with Railway context.
• Manage Railway-specific resources such as environments, domains, buckets, volumes, and project functions, and generate local Docker Compose setups with railway dev.

• High-value inspect and mutate commands expose real --json output, which makes follow-up parsing practical for status checks, deploy flows, logs, variables, and resource management.
• Once credentials and project context are in place, the noun-verb command structure works well for inspect/change/verify loops in CI or local automation.
• Login, project or service selection, confirmation prompts, SSH or shell sessions, and the default dev TUI still introduce interactive edges that agents need to bypass with explicit flags or preset context.

• Many commands assume a linked project, environment, or service; in non-interactive mode you often need to pass explicit names or IDs.
• JSON output is broad but not universal, and some workflows hand off to other tools such as Docker, psql, mongosh, mysql, redis-cli, or an interactive shell.