This week we’re coming to you live and direct from Railway HQ[0] with some new features around monitoring and tearing down deployments.

You’ll want to pay special attention to the first item if you’re at all worried about surprise costs and billing. 

We’re also excited to bring you some discoverability updates to the 

Before we get started, we’d also like to call your attention to the 

. We want to hear EVERYTHING that bothers you about Railway. We’ll fix it!

With that said, we have a couple extra items today, so let’s not stand around and dilly-dally any longer. 

[0] We don’t actually have an HQ because we’re 

Email monitors are live in production now

We’ve added configurable monitoring alerts to the 

To start, monitors will send you an email when a threshold is reached. 

These alerting thresholds are configurable above or below specified limits for:

Monitors are very easy to set up. They look like this. 

Don’t know where to start with monitors? Set an alert for Network Egress

Since you can set alerts to trigger above or below thresholds, there are a lot of different use cases. You might set alerts above a threshold on RAM to avoid surprise bills from a memory leak. Or you might set alerts below a certain CPU threshold to detect that your application has crashed. 

If you don’t know where to start, try setting a monitor on Network Egress, which is 

 of unintended cost overruns for most users. (Remember to always use 

We hope you like the direction we’re heading here. It makes us sad every time we read about another victim of some obscure pricing accident when using a hyperscale cloud. We’re trying to do the opposite of what they do and make it extraordinarily easy to control your costs under the belief that if we do right by you we’ll win your business over time.

Set overlap seconds and draining seconds in the service settings panel

Railway supports one deploy per service. This means that when a service is finished deploying, the old service is stopped and deleted. 

But what if you want some extra time to keep both services up? 

And what if you want some extra time to drain requests or close connections? 

 section of the service settings panel that allows you to specify intervals for 

 service variable, specifies the amount of time to keep the previous service up after the new service deploys.

To learn more about this nifty new feature, be sure to 

, which is our revenue sharing program, is growing like a weed. 

If you don’t know “the deal” here it is:

 on all usage cost incurred when people use your template

( To learn more about why it’s 50%, check out our blogpost 

So anyway. We wanted to let you know that we recently introduced a couple of structural improvements to boost the SEO (and thus the discoverability) of your templates so you can make more cash! 

If you’re starting from scratch, all you need to do is use the 

If you’d like to update existing templates, head over to your 

 button on your published template(s). From there you’ll see new guidance for how to add some great descriptive text to your template. 

If you don’t want to make a template yourself, but you’d like to request a template, 

officially updated our data retention policy

This only comes into play after you cancel your plan or after your trial expires. 

We improved the reliability of draining services with volumes and databases

We no longer display skipped deployments on the timeline for metrics graphs (because doing so creates confusion about metrics impact) — but of course skipped deployments are still visible otherwise in the rest of the normal places

We now show a warning toast when you visit a link that specifies an environment that no longer exists (e.g. from a bookmark or old link). This is a much better strategy than falling back to a different environment, which was the previous behavior 🤦

We fixed a display bug related to the staged changes banner

We fixed a display bug when setting low RAM limits in service settings

We fixed a display bug related to canvas centering logic when modifying volumes’

We fixed a bunch more random small display bugs 🐛

https://res.cloudinary.com/railway/image/upload/v1750472418/2025-06-20_wgiu6m.png

Monitoring Beta, Teardowns UI, Template SEO Improvements, New Deletion Rules 

Changelog #0243