--- title: "Monitoring Beta, Teardowns UI, Template SEO Improvements, New Deletion Rules " date: 2025-06-20 number: 0243 url: https://railway.com/changelog/2025-06-20-monitoring-beta --- # Monitoring Beta, Teardowns UI, Template SEO Improvements, New Deletion Rules Greetings, Passengers! 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 [Templates revenue sharing program](https://railway.com/open-source-kickback), which is [growing like gangbusters](https://x.com/JustJake/status/1922369745480753596). Before we get started, we’d also like to call your attention to the [Q3 2025 nits thread](https://station.railway.com/questions/calling-for-your-2025-q3-nits-33546ea0). 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. Here we go! [0] We don’t actually have an HQ because we’re [globally distributed](https://railway.com/careers#open-positions). ## Monitoring Beta [Video: Email monitors are live in production now] We’ve added configurable monitoring alerts to the [Observability](https://docs.railway.com/guides/observability) panel in the dashboard. To start, monitors will send you an email when a threshold is reached. These alerting thresholds are configurable above or below specified limits for: - CPU - RAM - Disk usage - Network egress Monitors are very easy to set up. They look like this. [Image: 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 [by far the most common cause](https://docs.railway.com/reference/pricing/faqs#why-is-my-resource-usage-higher-than-expected) of unintended cost overruns for most users. (Remember to always use [Private Networking](https://docs.railway.com/guides/private-networking), people!) 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. Enjoy! ## Deployment Teardown Settings [Video: 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? This week we shipped a new `Teardown` section of the service settings panel that allows you to specify intervals for `Overlap` and `Draining`. Overlap, which uses the `RAILWAY_DEPLOYMENT_OVERLAP_SECONDS` service variable, specifies the amount of time to keep the previous service up after the new service deploys. Draining, which uses the `RAILWAY_DEPLOYMENT_DRAINING_SECONDS` service variable, specifies the `SIGTERM` to `SIGKILL` buffer time. To learn more about this nifty new feature, be sure to [read the docs](https://docs.railway.com/guides/deployment-teardown). Onward! ## Template SEO Improvements [Image: Untitled] As we mentioned in the preamble, the [Template Kickback program](https://railway.com/open-source-kickback), which is our revenue sharing program, is growing like a weed. If you don’t know “the deal” here it is: - You [create a template](https://docs.railway.com/guides/create) using the lovely [composer](https://railway.com/compose) - You [publish the template](https://docs.railway.com/guides/publish-and-share) to the marketplace - You get a [50% kickback](https://docs.railway.com/reference/templates#kickback-program) on all usage cost incurred when people use your template … that’s right, 50%! *( To learn more about why it’s 50%, check out our blogpost *[*$1M for Open Source*](https://blog.railway.com/p/1M-open-source-kickbacks)*. )* 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 [Template Composer](https://railway.com/compose) and start building templates. If you’d like to update existing templates, head over to your [Templates](https://railway.com/workspace/templates) page and hit the `Update` 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, [let us know in Central Station](https://station.railway.com/questions/what-templates-do-you-wish-existed-865e6f36)! Ok, that’s it! ## New Deletion Rules We wanted to let you know that we’ve [officially updated our data retention policy](https://docs.railway.com/reference/pricing/plans#how-long-does-railway-keep-my-volume-data-if-i-am-no-longer-on-a-paid-plan). This only comes into play after you cancel your plan or after your trial expires. Here is the new retention policy: - Trial volumes will be deleted **30 days** after trial expiry - Hobby volumes will be deleted **60 days** after cancellation - Pro volumes will be deleted **90 days **after cancellation That’s it! Thanks and have a great weekend 🦚 ## Fixes and Improvements - We improved the reliability of draining services with volumes and databases - We added contributor badges to top [Bounty Hunters](https://railway.com/changelog/2025-05-23-bounty-hunt#bounty-hunters-rejoice-) in [Central Station](https://station.railway.com/bounties)! 🌟 - 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 🐛