---
title: "Railway Metal EU Region, Serverless, AWS Marketplace"
date: 2025-02-14
number: 0225
url: https://railway.com/changelog/2025-02-14-railway-metal-amsterdam
---

# Railway Metal EU Region, Serverless, AWS Marketplace

🎉 **Welcome to this week’s Edition of Railway Changelog!** 🚀 🗓️

Before we get started, I hope you’re having a fantastic day full of love, gifts and joy, whether you’re celebrating Valentine’s Day or just enjoying a regular Friday!

On Tuesday, our founder and CEO, [Jake](https://x.com/JustJake), published a blogpost called [How We Work (Volume IV)](https://blog.railway.com/p/how-we-work-volume-iv). Be sure to give it a read if you’re curious about the nitty-gritty of how we get work done while maintaining a fully remote culture across the globe!

Now, let’s dive in and see what we shipped this week! 🚂✨

## Railway Metal live in EU West Region

[Video:                               Relocating an existing service to Railway Metal EU West Region]

[Two weeks ago](https://railway.com/changelog/2025-01-31-customers-page), we mentioned that AMS Metal Region is coming! 

We’re stoked to announce that Railway Metal is now live in Amsterdam for the `eu-west` region. 

Hobby users can now deploy or relocate their stateless services across Europe. Note that volumes are not available at this time.

This expansion marks a crucial milestone in in our mission to provide developers across the globe with fast, cost-effective and reliable infrastructure on metal. 

With the addition of the Amsterdam region, we're not just expanding our geographical footprint, we're delivering on our promise to bring Railway's renowned deployment experience closer to European users. Teams across Europe can now enjoy significantly reduced latency, enhanced performance, and improved reliability for their apps and services!

## App Sleeping is now “Serverless”

We have renamed the **“App Sleeping”** feature to **“Serverless”. **When enabled, your service runs only when triggered by events like incoming traffic, making requests to other services, or even open database connections.

This on-demand execution model significantly reduces costs and aligns with core serverless computing principles. While the functionality remains the same, the new name better communicates its value proposition to developers who are already familiar with the “serverless” architecture and computing model. 

Whether you're running a small side project, a medium-sized service or managing a large-scale app, the **Serverless** feature gives you the flexibility to instantly optimize your resource usage and scale to zero without any additional configuration. 

Be sure to[ read the docs to learn more about this feature](https://docs.railway.com/reference/app-sleeping).

## Railway is live on AWS Marketplace

[Image:                                                                     Railway on AWS Marketplace]

We just listed Railway as a SaaS on [AWS Marketplace](https://aws.amazon.com/marketplace/pp/prodview-cnib4vbrfgs5a). This move makes it easier for organizations and teams to find our offerings in the AWS marketplace and partner network. It also represents a significant milestone in our enterprise strategy. 

As stated in the pricing section, organizations can better control their cloud spending by locking into a 12 month contract while enjoying fast deploys, great UX and consistent reliability on our platform- and at certain spend tiers, deploy into AWS hardware.

For enterprise customers, this integration brings several key advantages. You can now peer into AWS, or, provision and manage Railway through your existing AWS account. Companies can benefit from consolidated billing and the ability to apply your AWS Enterprise Discount Program (EDP) credits. This makes the procurement process easier and eliminates the complexity of managing multiple vendor relationships, thus making it simple and effective for teams to adopt and scale with Railway.

## Fixes & Improvements

- We improved the help station sidebar to become collapsible.
- We improved Railway Functions to now have 3 default examples in the Source code editor
  - A REST API
  - A Landing page with JSX
  - A cron job
- We fixed a bug with subscription migration.
- We fixed an empty state copy on the metrics page.
- We added an edit link to the Source code of a Railway function from the active deployment tab.
- Dockerfile builds are much more likely to utilize the layer cache.