Between year-end shipping sprints and Black Friday load tests, it’s peak alert fatigue season. This week we’re shipping better webhooks so you only get pinged when it matters, smarter service settings that catch misconfigurations before they bite you, and 

 with the Railway team for folks running larger workloads.

Whether you’re tuning alerts, hardening production, or evaluating Railway for your infra, this one’s for you.

Now let’s get into what shipped this week 🚄

Configuring webhook alerts for critical service events

Webhooks on Railway just got a lot more powerful. You can now subscribe to a richer set of events, including CPU and memory threshold alerts, so your external tooling can react to performance issues in real time instead of waiting for a human to notice graphs spiking.

We also revamped the UI to make it easier to pick the events that matter. In a single click, you can subscribe to a curated set of critical events such as VolumeAlert Triggered, Monitor Triggered, Deployment Crashed, and Deployment OOM Killed, instead of hunting through a long checklist. This makes it straightforward to wire up “only wake me up when things are really broken” alert policies.

Finally, you can choose whether or not to receive webhooks from PR environments. They’re disabled by default, so your staging and preview workflows don’t accidentally spam your alert channels, but you can enable them when you want full parity between preview and production.

As always, we’d love to hear how you’re using the new webhooks and what events you’d like to see next over 

The Service Settings panel picked up a whole wave of quality-of-life improvements this week, aimed at catching configuration issues before they reach your build or deploy.

 let you run short-lived tasks on a schedule by starting your service according to a crontab expression, running your task, then exiting once you’re done (for example, a daily backup or periodic job). We now validate cron schedules directly in the UI, so invalid expressions (including certain special characters, expressions, and hashes that caused build failures) are caught before they ever hit your pipeline.

We also tightened up how Docker images are handled in Service Settings. Docker image names are required to be lowercase, but previously we didn’t enforce that, which led to confusing failed deploys. From now on, Railway will transparently lowercase image names while preserving the case of image tags and hashes, since those are case-sensitive. This reduces a whole class of subtle “why did my image deploy fail?” errors.

Docker image names is uses the correct casing

Domains and ports also received a big usability pass. The Generate Domain button is now disabled until you enter a valid port, with dynamic validation feedback so it’s clear what’s wrong and how to fix it. These improvements extend across the lifecycle of managing domains—adding domains, editing existing domains, and as a little bonus, the same validation behavior is applied to the TCP Proxy. The goal: fewer “what state is this actually in?” moments when wiring up network access.

On top of that, we shipped several smaller polish changes that should make daily usage smoother:

Copy DNS record name easily: We added a copy button to the name field in the DNS records modal, so you can grab hostnames without carefully selecting text by hand.

Template composer state behaves correctly between templates: Previously, when switching templates (for example: Edit a template → Create a new template, or Edit template A → Edit template B), the canvas configuration from the previously opened template could leak into the new one. We now clear the state when templateId changes, so every template opens with the correct canvas configuration.

Safer diffs for project shared variables: When using the project shared variables raw editor, we now pass the existing decrypted variables into the editor, so the diff correctly represents what’s actually stored. This prevents sealed variables from being inadvertently overwritten with empty strings when applying changes.

 for implementing all of these changes. If you have any feedback, 

Open Office Hours with the Railway Team

Sit down with the Railway team to tune your infra

Cloud bills creeping up, deploys slowing down, and every “quick change” turning into a yak shave? For a limited time, we’re opening up Office Hours with the Railway team for companies running larger workloads who want to move faster 

If your org is spending $5,000/month or more on infrastructure, you can grab time directly with our customer and solutions folks. In a session, we will:

Map your workload: walk through your current architecture, pain points, and constraints

Match you with the right setup: show how to get started on Railway, often with one of 1

Pressure-test the value: explore where Railway can realistically help you ship 10x faster or cut infra costs by up to 65%, based on what we have already seen with similar teams

Plan the path forward: if Railway looks like a fit, outline next steps for onboarding, migration, and change management so you do not have to figure it out alone

If you are the person bringing Railway to your workplace, this is also your chance to benefit personally. When your company adopts Railway because you championed it, you can get paid for bringing Railway to work through 

We are keeping this offer tight with limited slots and limited time, so if you have been meaning to rethink your infra, this is a good excuse to get it on the calendar.

cal.com/team/railway/railway-office-hours

We shipped notifications for important SSO-related events, so workspace admins can quickly understand what changed in their authentication setup. You can now receive notifications when SSO is Connected, Disconnected, or Updated, as well as when a SAML certificate requires renewal and when a SAML certificate is renewed. You can learn more in the 

We shipped a new upgrade flow for payment methods that supports 3DS cards and removes the old $1 temporary verification charge. The previous flow could be confusing, especially when customers saw a $1 authorization that later disappeared. This new flow reduces friction when adding or updating cards and makes billing behavior more transparent

https://res.cloudinary.com/railway/image/upload/v1763153996/2025-11-14_jxt4yl.png

Better Webhooks, Better Service Settings, Office Hours

Changelog #0264