---
title: "Railway Metal Next Phase, Improved Build Error Logs, Migrate Fly apps"
date: 2025-01-17
number: 0221
url: https://railway.com/changelog/2025-01-17-improved-build-error-logs
---

# Railway Metal Next Phase, Improved Build Error Logs, Migrate Fly apps

🎉 Welcome aboard this week’s edition of the Railway Changelog! 🚀

Please make yourself comfortable—our **express train** is about to depart on its **special Friday service**. No delays, no signal failures—just smooth deployments and fresh updates!

Fasten your seatbelts (or grab a snack from the dining car), and let’s roll! 🚂💨

## Railway Metal: The Next Phase Begins

[Image:                 Railway Cage Explorer showing our racks, cables, models and devices ]

You may have [heard](https://railway.com/changelog/2024-09-20-railway-metal-beta#railway-metal-arrives-in-beta) [the](https://railway.com/changelog/2025-09-27-last-chance-nits#railway-metal-reminder) [news](https://railway.com/changelog/2024-10-18-hobby-on-railway-metal#hobby-workloads-on-railway-metal)—we’re building our own physical footprint to transition into a **full cloud provider running physical hardware**, rather than operating as a layer over another cloud.

Now, we’re entering the **next phase**, where we’ll begin migrating more services onto **Railway Metal**. To see what this means for you, check out our [**full documentation**](https://docs.railway.com/railway-metal), and feel free to share your feedback or ask questions in our [**Help Station thread**](https://help.railway.com/feedback/feedback-railway-metal-a41f03a1)**!**

Curious about the details? Our Infra Engineer, Charith, [**wrote a deep dive**](https://blog.railway.com/p/data-center-build-part-one) on how we’re making this happen.

Stay tuned as we continue evolving **Railway Metal. **🚀

## Improved Build Error Logs

[Video:                     Checking build logs to understand why the build failed..]

At Railway, we strive to continuously improve the platform with **QOL (Quality of Life) **updates—small but meaningful changes that make a big difference.

This week, our resident Shakespearean engineer, Jared, took on the noble task of refining build error logs to make them more relatable and easier to understand. Because let’s be honest—no one should feel like a fool when deciphering why a build failed.

Now, you’ll get better, clear, actionable error logs—so you can quickly identify the issue with your failed build and fix it with confidence.

✨ Fewer headaches, faster debugging, and more successful builds. Thanks, Jared! 🎭👏

## Migrate from Flyio with Ease

At Railway, we’re committed to making migrations effortless, ensuring you can transition smoothly while unlocking everything our platform has to offer. 

This week, we shipped a [key differentiators comparison guide](https://docs.railway.com/maturity/compare-to-fly) that highlights what sets us apart from Fly.io, making Railway the superior choice for deploying, managing, and scaling your apps and services.

Now, migrating your apps from Fly.io is easier than ever. Simply select **Deploy from GitHub repo,** and Railway will auto-import your app, automatically setting up all necessary services and environment variables—so you don’t have to.

Ready to make the move? Follow our [Migrate from Fly Guide](https://docs.railway.com/migration/migrate-from-fly) for a step-by-step walkthrough and get started in minutes!