Operate Railway infrastructure: sign up for or sign in to a Railway account, create projects, provision services and databases, manage object storage buckets,…
Use Railway Railway resource model Railway organizes infrastructure in a hierarchy: Workspace is the billing and team scope. A user belongs to one or more workspaces. Project is a collection of services under one workspace. It maps to one deployable unit of work. Environment is an isolated configuration plane inside a project (for example, production, staging). Each environment has its own variables, config, and deployment history. Service is a single deployable unit inside a project. It can be an app from a repo, a Docker image, or a managed database. Bucket is an S3-compatible object storage resource inside a project. Buckets are created at the project level and deployed to environments. Each bucket has credentials (endpoint, access key, secret key) for S3-compatible access. Deployment is a point-in-time release of a service in an environment. It has build logs, runtime logs, and a status lifecycle. Most CLI commands operate on the linked project/environment/service context. Use railway status --json to see the context, and --project, --environment, --service flags to override. Tool routing Railway has three agent-facing operation paths. Choose the path that matches the job:
don't have the plugin yet? install it then click "run inline in claude" again.