Railway integration: connect projects, services and deployments to Polylane
Connect Railway projects, services, volumes and deployments to Polylane via OAuth. Correlate service metrics and deploy alerts in one investigation.
Get started for freeHow to set up Railway
Initial discovery may take a few minutes according to the connection guide. The authorization link is short-lived; retry the flow if consent expires.
- Choose Railway and select Continue to Railway. Sign in with access to the intended workspace.
- Authorize the OAuth application and return to Polylane; discovery starts after authorization.
- For push alerts, copy the webhook URL from the connected account’s Settings. Add it to Railway workspace Notifications and select Deployment.deployed, Deployment.failed, Deployment.crashed and Deployment.oom_killed plus the desired VolumeAlert and Monitor events, including resolved events.
Permissions and access
The exact requested scopes are openid, profile, email, offline_access, workspace:viewer and project:viewer. offline_access allows token refresh; workspace:viewer and project:viewer are the infrastructure reads. The console offers no full-access mode. Webhook notification rules are configured by you in Railway rather than requiring a broader OAuth grant.
Discovery, refresh and the connected view
Projects, non-ephemeral environments, services, deployments, volumes, domains and TCP proxies refresh every 15 minutes. Deployment webhooks request a refresh with a two-minute debounce. Variable names support cross-cloud links; values are never read. Pull-request environments are skipped. Service nodes show metrics and deployment context for investigation.
Disconnect and revoke access
Disconnect Railway in Polylane, then revoke its OAuth authorization in Railway. Remove the notification rule pointing at Polylane if you no longer want alert delivery.
Provider credentials and Polylane’s access mode are separate. Where write-capable tools exist, the connected account’s Settings page offers a Read-only switch. Turning it off permits writes subject to review and confirmation, but cannot add permissions to the provider credential. Agent-connected Kubernetes clusters stay read-only.
In the graph.
Every Railway resource Polylane picks up sits in the graph with its connections, config and history.
Project Environment Service Deployment Volume Domain TCP Proxy Notification Rule Tools for the investigation.
What Polylane can do with Railway while it investigates. Every call is recorded in the transcript.
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
Railway setup and troubleshooting
Docker context deadline exceeded
Common questions.
How does Polylane connect to my Railway workspace?
Choose Railway and select Continue to Railway. Sign in with access to the intended workspace. Authorize the OAuth application and return to Polylane; discovery starts after authorization. For push alerts, copy the webhook URL from the connected account’s Settings. Add it to Railway workspace Notifications and select Deployment.deployed, Deployment.failed, Deployment.crashed and Deployment.oom_killed plus the desired VolumeAlert and Monitor events, including resolved events.
What Railway resources does Polylane sync?
Projects, non-ephemeral environments, services, deployments, volumes, domains and TCP proxies refresh every 15 minutes. Deployment webhooks request a refresh with a two-minute debounce. Variable names support cross-cloud links; values are never read. Pull-request environments are skipped. Service nodes show metrics and deployment context for investigation.