DevOps
Monitor Railway with MrCron
MrCron tracks Railway service deploy state, crashed services, and build duration trends every 5 minutes so you can watch your infrastructure without leaving the dashboard.
How MrCron monitors Railway
- Service deploy state per Railway project (SUCCESS, FAILED, DEPLOYING).
- Crashed service count across the project.
- Build duration trend for the last 24 hours.
- Workspace-wide roll-up: connect one API token, auto-link every Railway service.
- Per-project override: attach a specific Railway project to a specific MrCron project.
- Alert rules that fire on crashed services via any notification channel.
What you will see
Service deploy state, crashed services, build duration trends.
Auth flow: API Key. Credentials are stored encrypted at rest with AES-256-GCM and never returned to your browser.
Start monitoring Railway
Sign in, create a project, and connect Railway in under a minute. First check ships in the free tier.
Frequently asked questions
- What Railway credentials does MrCron need?
- A Railway API token from your account settings. MrCron stores it encrypted at rest and only decrypts it inside the sync worker.
- How does auto-linking work for Railway?
- After you connect a Railway account at /integrations/railway, MrCron lists every service across every project. You choose auto-link, manual link, or ignore per Railway project.
- Does MrCron read Railway service logs?
- No. MrCron reads deployment metadata (state, duration, timestamp). Service logs remain in the Railway UI.
- What triggers a crashed-service alert?
- The next sync sees a service report a crash state. Configure an alert rule to route the count spike to any channel.