March 2025 Summaries

We've built a system for operationalizing hardware at scale, starting with building a CSV of identifiers for equipment in a rack, pushing this data to an internal control plane called MetalCP. This data is used by Temporal workers to implement a Host Import workflow that matches devices to their representations in our internal DCIM tool (Railyard), connects to the datacenter's management network, scrapes BMC data, creates static DHCP leases for the BMC and management NICs on the host using discovered MAC addresses from the scrape, updates a DB with server details, generates stable interface and drive names, flags faults in hardware, and configures Ansible. Additionally, we use Pixiecore to automate PXE booting, leveraging Redfish APIs to obtain near-real-time images of server screens (Claude) for state monitoring during OS installation. The dataplane network uses FRR with BGP unnumbered to achieve uniform routing setups on switches and servers, making expansion plug-and-play. Our tooling is proving an entire software vertical in itself, including MetalCP as our in-house RANCID/Oxidized replacement.

We're giving away $1,000,000 in cash to open source developers and maintainers who publish a template in our library and get other developers to start using it. For every $1 someone spends deploying their code on Railway's cloud, the developer receives $0.50 in cash. The program has already paid out $66,500 in cash and secured around $199K in revenue for the company. To participate, developers need to rack up $100 in earned credits before they can withdraw those credits to cash. This is a limited-time offer, with the million dollars set to run out once it's gone. The program benefits both open source maintainers and Railway by providing a way for users to deploy their code quickly and efficiently while also generating revenue for the developers.

Railway has announced the introduction of an SSH capability for its instances, a feature that has been highly requested by its users. The announcement follows a previous surprise feature reveal during a Launch Week, when Infrastructure Engineer Miguel introduced what is now known as the Serverless feature. With the latest addition, users can now SSH into their Railway instances using the command-line interface (CLI). To utilize this new feature, users need to download the latest version of the Railway CLI, log in to their account, link to their project, and then SSH into the service. This development marks a significant enhancement in Railway's offerings, emphasizing user feedback and providing more flexibility for managing Railway instances.

Railway introduces Central Station, an evolved platform that extends beyond traditional support to become the core of its community, integrating feedback, news, and a public feature roadmap. This transformation stems from the need to accommodate a rapidly growing user base nearing one million and to streamline feedback collection, which previously suffered from disjointed channels. Central Station facilitates a collaborative environment where user interactions are valued, enabling users to suggest features, engage with them, and track their development progress. This approach allows Railway to prioritize features based on their potential revenue impact, user importance, and contribution to ongoing sales engagements. By involving users in the development process, Central Station fosters a stronger connection between the company and its community, enhancing product development and user satisfaction. As Railway continues to innovate and respond to user needs, it emphasizes the importance of the journey over the destination, inviting users to actively participate in shaping the platform's future.

The complexity of frontend development has significantly increased, with developers now engaging in server-side rendering, client-side rendering, and extensive API calls, leading to performance challenges due to fragmented infrastructures. Railway addresses these issues by enabling developers to deploy their UI, API, and databases on the same infrastructure, eliminating cross-cloud delays and enhancing speed by keeping compute close to users. The platform offers multi-region compute, built-in anycast routing, and automatic geosteering to optimize performance and reduce latency. Additionally, Railway provides affordable egress costs, caching efficiencies, serverless modes, and pre-built templates for major frontend frameworks, ensuring seamless, fast deployment without the need for extensive server management. The platform aims to empower developers to focus on creating responsive user experiences rather than dealing with infrastructural complexities.

Railway has introduced a new feature called Railway Functions, designed to streamline and significantly accelerate the deployment process for developers. This innovation allows code to be deployed within 45 seconds, eliminating the need for package managers, GitHub repositories, infrastructure as code (IaC), or container builds, thus simplifying the deployment workflow to just the code itself. Powered by the Bun runtime, Railway Functions offer native code execution in containers, leveraging infra-less compute similar to Railway Services. The process involves parsing source code, analyzing dependencies, installing them with the fast-performing Bun installer, and executing TypeScript/JavaScript without prior transpiling. This rapid deployment capability, which can be achieved in as little as one second, enhances productivity by allowing developers to experiment, iterate, and ship projects more efficiently. Currently supporting TypeScript, Railway plans to extend support to additional languages in the future, providing developers with tools like REST API, JSX landing pages, and cron utilities to facilitate diverse use cases.

Railway has introduced Railpack, an upgrade to its previous Nixpacks system, designed to overcome limitations encountered by a significant portion of its users and to support its scaling objectives. Railpack offers granular versioning, reducing image sizes up to 77%, and improved caching by interfacing with BuildKit for more efficient builds. The transition from Nixpacks was driven by issues such as commit-based package versioning, which often led to large, inefficient builds and unexpected errors when package versions updated. Railpack addresses these challenges by using a custom BuildKit configuration, allowing for precise control over image construction and dependency management. It supports Node, Python, Go, Php, and Static HTML deployments, and integrates tightly with the Railway UI. Currently in beta and open source, Railpack promises to enhance deployment processes with support for static sites like Vite and Angular, optimized caching, and the capacity to incorporate the latest language versions without requiring a Railpack release.

Railway announced the launch of Railway V3, branded as "Railway Metal," which promises to be faster and more cost-effective than major cloud providers by operating its own data centers. This new iteration is positioned as being almost 50% cheaper than leading cloud providers, offering significant savings on egress, storage, and additional features, with a "pay only for what you use" model. During testing, Railway Metal demonstrated substantial performance improvements, with up to 6x faster multicore benchmarks and a 50x better price-performance ratio in database and stateful workloads. The company emphasizes its commitment to reducing complexity and costs for users, advocating for simplicity over the multitude of tools and configurations typical in cloud services. Railway aims to provide a streamlined experience, allowing users to deploy and scale code with minimal hassle and less infrastructure management, encapsulated in the concept of "infraless."