Opyntel
Railway

Railway monitoring across every project, with the latency, error-rate and budget alerts Railway's monitors don't cover

Opyntel’s Railway monitoring reads your Railway projects with one token and puts every service in one table. It alerts on CPU, memory, disk, latency, error rate and spend, by email, Slack or SMS depending on your plan, on rules you scope to a project, environment or service.

See how it works
Built in vs Opyntel

Railway on its own, and Railway with Opyntel

Feature by feature, the biggest gaps first: what Railway gives you, and what you get in one dashboard with Opyntel.

Every service at a glance

On Railway

Railway opens a metrics view per service: you pick a project, then a service, then its Metrics tab. The observability dashboard of a project environment offers CPU, memory, network, disk, logs and project usage widgets, while response times, error rate and status counts sit on each service’s own Metrics tab.

With Opyntel

Opyntel shows the full list of your services in one table, every project and environment together, with down and degraded first. Each public service shows its requests, error rate and p50, p95 and p99 latency in the same row, so you see it all at a glance, Railway plus the other systems you run.

History

On Railway

Railway keeps up to 30 days of CPU, memory, disk and network metrics for each project.

With Opyntel

Opyntel keeps the same metrics for 30 days on the free plan, a year on Pro and unlimited on Enterprise, whatever your Railway plan. You can compare this month with the last quarter without exporting anything.

What monitors watch

On Railway

Railway monitors fire when CPU, RAM, disk usage or network egress crosses a limit you set, above or below it. Monitors need the Pro plan.

With Opyntel

Opyntel watches the same CPU, memory and disk, and adds request status classes, p50, p95 and p99 latency and the 5xx error rate for every public service. Out of the box it alerts when a service goes down or when its error rate or p95 latency passes your threshold.

Alerts when it goes down, and when it recovers

On Railway

On the Pro plan, Railway monitors notify by email and in-app notification, and you can add webhooks.

With Opyntel

Opyntel has default rules on every plan, custom rules per service, project or environment on Pro and up, and sends them by email, Slack or SMS depending on your plan. Every alert notifies when it fires and again when it recovers, and critical ones re-notify hourly while still firing.

The total cost of your app

On Railway

Railway’s workspace Usage page lists usage by project with current and estimated cost for the billing period; a breakdown by service is in the CLI. Usage alerts email you when workspace usage reaches an amount, and hard limits take workloads offline.

With Opyntel

Opyntel shows spend per service and per project on Pro, next to the cost of the other platforms you run, so you see the total cost of your app at a glance. On Enterprise, monthly budget alerts and forecasts warn you before the bill does, without taking anything offline.

Railway dashboard

The Railway dashboard: what it shows and what it misses

The Railway dashboard is built around one project at a time. Opyntel puts every project and service in one dashboard.

What the Railway dashboard shows

  • A project canvas per project, and an observability dashboard scoped to one project environment.
  • Build and deploy logs per deployment, plus a log explorer for one environment.
  • CPU, memory, disk and network graphs per service, with deploys marked on the graph.
  • Workspace usage broken down by project and by resource.

What it does not show or alert on

  • Services from every project and environment in one dashboard.
  • Threshold alerts on Free or Hobby: monitors need the Pro plan.
  • Metrics older than 30 days, or logs older than your plan keeps them (3 days on Free, 7 on Hobby, 30 on Pro).
  • Spend per service across projects, with a budget you can alert on per project.
Railway vs Opyntel

What the console gives you, and what Opyntel adds

Railway has good per-service metrics, a log explorer and Pro monitors. Opyntel builds on them with alerts, history and spend across all your projects.

CapabilityThe Railway consoleWhat Opyntel adds
Service status across projectsThe Railway console

The observability dashboard is scoped to one project environment, so each environment gets its own.

What Opyntel addsEvery service from every project and environment in one table, down and degraded first, filtered by project or environment.
CPU, memory and disk thresholdsThe Railway console

Monitors alert on CPU, RAM, disk usage and network egress by email, in-app notification or webhook. Monitors need the Pro plan.

What Opyntel addsReady-made CPU, memory and disk rules, including a forecast of when a disk fills, scoped to a project, environment or service.
Deploy and crash eventsThe Railway console

Each service keeps its deployment history, and project webhooks report deployment status changes.

What Opyntel addsDeploys, restarts and crashes on one activity timeline for all projects, and an alert when a service goes down.
HTTP latency and error rateThe Railway console

Monitors cover CPU, RAM, disk usage and network egress. Latency and error rate are outside that list.

What Opyntel addsRequests, status classes and p50, p95 and p99 latency for your public domains, with error-rate and slow-response alerts.
Spend per projectThe Railway console

Usage limits send an email at a threshold you set and can stop workloads at a hard limit. The observability dashboard can show project usage.

What Opyntel addsDaily spend per project and per service, actual and estimated, with monthly budgets as alert rules.
History lengthThe Railway console

Up to 30 days of metrics per project. Logs are kept 7 days on Hobby and 30 days on Pro.

What Opyntel addsUp to a year of hourly metric history. Opyntel stores metrics, so your logs stay in Railway.
Read-only accessThe Railway console

Account, workspace and project tokens differ in reach, and each acts with the permissions of its scope.

What Opyntel addsOpyntel uses the token only to read, enforced in code, and stores it encrypted.
Railway alerts by plan

Which Railway alerts you get on each plan

What Railway itself alerts on, per plan. The Free column also covers the Trial, which gets Hobby features. Opyntel alerts the same way on every plan.

AlertFree and TrialHobbyProOpyntel
Deploy failedFree and TrialProject webhook to Slack, Discord or any URLHobbyProject webhook to Slack, Discord or any URLProProject webhook to Slack, Discord or any URLOpyntelDeploy failures on one timeline for every project, with an alert by email, Slack or SMS depending on your plan.
CrashFree and TrialProject webhook on a crashed deploymentHobbyProject webhook on a crashed deploymentProProject webhook on a crashed deploymentOpyntelAn alert when a service goes down, on rules scoped to a project, environment or service.
CPUFree and TrialNo monitorsHobbyNo monitorsProMonitor threshold by email, in-app or webhookOpyntelCPU threshold rules on any plan, across every project and environment.
MemoryFree and TrialNo monitorsHobbyNo monitorsProMonitor threshold by email, in-app or webhookOpyntelMemory threshold rules on any plan, across every project and environment.
DiskFree and TrialVolume nearing capacity, by webhookHobbyVolume nearing capacity, by webhookProVolume webhook, plus disk usage monitorsOpyntelDisk threshold rules and a forecast of when a disk fills, on any plan.
SpendFree and TrialOn the Free plan: email at an amount you set, optional hard limit. Not stated for the TrialHobbyEmail at an amount you set, optional hard limitProEmail at an amount you set, optional hard limitOpyntelMonthly budgets per project as alert rules, with daily spend per service.
Certificate expiryFree and TrialNot in Railway's alert listHobbyNot in Railway's alert listProNot in Railway's alert listOpyntelOpt-in certificate checks on your public domains, with an alert before expiry.
Railway cost

What drives a Railway bill, and how Opyntel shows it

Railway bills a plan fee that counts toward usage, then charges for usage beyond it. Opyntel shows daily spend per service across all your projects, actual and estimated, with monthly budgets as alert rules.

Billed on usage
RAM, vCPU, network egress and volume storage are metered by the minute or GB. Hobby includes $5 of usage and Pro $20; anything above is charged on top. Builds are free.
Environments you forgot
Idle services still use memory and CPU, so staging and test environments add up. PR deploys run a copy of the environment for every open pull request.
Memory, egress and volumes
A memory leak raises the bill as RAM grows. Connecting to a database over its public URL counts as egress. Volume storage is billed per GB as it grows.
Setup

How to set up Railway monitoring with Opyntel

Railway monitoring in four steps: from Railway to one dashboard with everything else you run.

  1. Create a Railway account or workspace token
    On the tokens page of your Railway account settings, create a token with no workspace for your whole account, or pick a workspace to scope it to that workspace. A project token sees one environment only, so use one of these.
    Create a Railway API token
  2. Sign in to Opyntel
    Open your Opyntel dashboard and add a source. Accounts start from the waitlist, so join it to get yours.
  3. Paste the token in your dashboard
    Add Railway as a source, paste the token and pick the workspace to watch. Opyntel sends only read queries with it.
  4. See Railway in one dashboard
    Railway monitoring lands next to the other platforms you run: every service and server sits in one dashboard, down and degraded first, with default alert rules on from the start.

Don’t see your platform? From your Opyntel account you can request an integration with more platforms. Until then, and tell us which one you run on.

Dashboard

All your Railway services in one dashboard

All projects and environments in one table.

Opyntel

Services from every Railway project land in one table, down and degraded first, with CPU, RAM and the last deploy. Open any service for its status history, traffic, events and usage charts.

Services

Down and degraded first

Example data
Services
6
Down or degraded
2
Monthly spend (estimated)
$27.40
Last sync
40 s ago
ServiceStatusProjectSourceCPURAMLast deploy
workerdownshopRailway——2 h ago
apidegradedshopRailway0.61 vCPU412 MB18 min ago
webdeployingshopRailway0.05 vCPU180 MBjust now
postgresokshopRailway0.22 vCPU1.1 GB6 d ago
docsokblogRailway0.02 vCPU96 MB4 d ago
cronstoppedtoolsRailway——3 d ago
FAQ

Railway questions, answered

Plans, tokens, spend and how fresh the numbers are.

The $5 Hobby fee includes $5 of usage, and anything you use beyond it is charged on top. Running services use memory and CPU even with no traffic, and PR environments run copies of your services. Railway explains this in Understanding your bill. Opyntel shows daily spend per service so you can see which one is growing.

Railway can do this itself: paste a Slack webhook URL into the project's Webhooks tab and crashes and failed deploys post to the channel (Railway guide). You set it up once per project. Opyntel sends crash and down alerts for every project from one set of rules.

Railway's monitors are opt-in and need the Pro plan, so the graph can show high memory without anything being sent (Railway monitors). Opyntel's memory rules are on from the start, on any plan.

Railway's own monitors need the Pro plan. Opyntel's alert rules run on the metrics it reads through the Railway API with your token, so they work separately from Railway's monitors.

An account or workspace token, which covers every project it can reach; a project token covers one environment only, so it is not enough. Opyntel only reads with the token, which is enforced in code, and keeps it encrypted.

Keep them if they work for you. Opyntel adds alerts Railway's monitors don't have, such as latency, error rate and spend, across every project, by email, Slack or SMS depending on your plan. Logs stay in Railway, because Opyntel collects metrics, not logs.

Opyntel reads cost data per project and per service from Railway each hour, marks each day as actual or estimated, and shows totals in USD. Your Railway invoice is the amount you pay.

Service states, metrics, deploys and HTTP traffic refresh as often as every five minutes and costs every hour. Alert rules are checked every 30 seconds.

Requests, status classes and latency for services on public domains. Traffic on private networking between your services is not included.

Open the service and pick Deploy Logs, or HTTP Logs for its requests; the Log Explorer in a project’s Observability tab searches across services. In a terminal, railway logs streams the linked service. Opyntel’s Railway monitoring shows every service’s status, errors and latency in one dashboard, next to your other platforms.

It ran out of memory, often in a spike the graph misses. How to confirm and fix exit code 137 on Railway.

No. Railway charts 5xx responses, but its monitors cover CPU, memory, disk and egress only. Railway 5xx errors and how to get alerted.

Its process exits and the restart policy brings it back, up to 10 times by default. Why a Railway service keeps restarting.

Not on its own. Railway charts P50 to P99 per service, but its monitors cover CPU, RAM, disk and egress. How to alert on P95 latency on Railway.

The alerts your platform doesn’t send.

One dashboard for everything you run, with the alerts your platforms leave out. Read-only, nothing to install in your apps.

See how it works