Railway. Projects, services, deployments, and volumes.
Connect your Railway workspace to give agents visibility into your projects, environments, services, and deployments. Agents can track deploy status, watch service resource usage, and correlate Railway activity with the rest of your infrastructure.
Join the waitlistWhat Polylane does with Railway.
Your whole workspace in one graph
Projects, environments, services, deployments, volumes, domains, and TCP proxies, with their edges and history. Template databases next to the services that use them.
Deploys watched as they land
Railway webhooks alert on failed and crashed deployments the moment they happen, resolve the alert on the next success, and can trigger an agent to investigate every deploy.
Metrics and logs read on a cadence
Agents comb each service's CPU, memory, and disk against how that service normally behaves, and pull deploy and runtime logs mid-investigation. No thresholds to tune.
Your secrets stay yours
Polylane syncs variable names for cross-cloud linking and never reads variable values. Tokens are encrypted before they're stored, and the agent never sees them.
How it works.
Connect
OAuth with read scopes only. Click connect, approve in Railway, and syncing starts.
Sync
Projects, services, deployments, and volumes land in the graph, and every sync after records what changed.
Agents take the watch
Deploy failures get investigated as they land, resource usage is judged against each service's normal, and fixes arrive for your review.
In the graph.
The Railway resource types Polylane syncs, with their edges, config, and history.
Project Environment Service Deployment Volume Domain TCP Proxy Notification Rule The tools agents get.
What an agent can do with Railway mid-investigation. Every call lands in the thread transcript, cited.
railwayApi Run a curated Railway GraphQL operation (reads, restarts, redeploys, scaling)
railwayGetLogs Get runtime logs for a Railway service or deployment
railwayListDeployments List recent Railway deployments for a project
railwayQueryMetrics Query CPU, memory, network, and disk metrics for Railway services
Questions.
Is Polylane an AI SRE for Railway?
It's what most people mean by the term: agents that keep your Railway resources in one context graph, watch them, investigate issues and fix what they can, with a human approving anything that changes production. We call it self-operating software rather than an AI SRE: the point is that your software looks after itself, not that a bot joins the on-call rotation.
Can Polylane change anything in Railway?
Only if you let it. Connected read-only, agents investigate and explain, and changes only ever land as pull requests for you to review. With write access, every write pauses for your approval first, with the method, path and reason on screen. Rollbacks are off by default: you enable them per automation and can turn them off at any time.