Deployment status in project context
See current Railway activity beside the project plan so a failed or delayed deployment can become visible work instead of remaining an isolated infrastructure event.
What you can do
Connect Railway to see deployment status directly on your project records. Choose which object types should track deployments and Kato adds the Railway Project field for you — then monitor build and deploy status across environments without leaving Kato.
One place for related resources
Move between services, environments, domains, variables, and logs from a connected record rather than rediscovering the correct Railway project during every review.
OAuth-based project access
Authorize Railway through its supported connection flow and link only the project relevant to the Kato record being configured.
Inside Kato
Relio / APIExample workspace
relio-api
RailwayProduction2 hours ago
Ready
Latest deployment
32sAdd invoice sync retries
a91c3e7main
What changed
Retry failed invoice syncs
Add service health checks
Previous deploymentc4f82abReady
Previous production release
Yesterday
Connect Railway
Connect Railway with Login with Railway (OAuth). Choose which object types should track deployments and Kato adds a Railway Project field to each one automatically. Set that field on a record to your Railway project name, and incoming Railway webhooks log deployment activity (building, succeeded, failed) on every matching record. Personal API tokens remain available as an advanced fallback.
- 01In Kato, go to Settings > Integrations, open Railway, and click Connect.
- 02Authorize Kato on Railway and select the workspaces or projects to share.
- 03Choose which object types should track Railway deployments — the Railway Project field is added automatically.
- 04Set the Railway Project field on a record to your Railway project name, and add a project webhook in Railway pointing at your Kato API's /railway/webhooks URL.
Made for your workflow
Release monitoring
Review recent deployments before a launch call and create a Kato follow-up when a service or environment needs engineering attention.
Environment discovery
Help teammates identify the relevant service, environment, and public domain from the project record without relying on undocumented tribal knowledge.
Incident coordination
Inspect available logs and deployment context while coordinating tasks, owners, and client communication in the broader Kato project workflow.
Common questions
Does Kato replace the Railway dashboard?
No. Railway remains the control plane for infrastructure. Kato presents connected operational context and coordinates the project work that results from it.
What can a linked project show?
The integration supports views of Railway projects, services, environments, deployments, domains, environment variables, and logs according to the authorized connection.
How is a Railway project selected?
After authorizing Railway, open the relevant Kato project record and link the Railway project that represents the same product, client deployment, or initiative.
Last updated Jul 13, 2026