Railway's Frontend Transformation: From Next.js to Vite + TanStack

Railway's frontend has undergone a significant transformation, moving away from Next.js to embrace Vite + TanStack Router. This shift was driven by the need for a faster, more client-focused framework that aligns with Railway's product needs. Next.js, while initially beneficial, became a bottleneck with build times exceeding 10 minutes, largely due to server-first paradigms that didn't suit Railway's client-heavy applications. The migration was executed in just two pull requests, ensuring zero downtime and a seamless transition for millions of users.

The choice of Vite + TanStack was motivated by their explicit, client-first design, which offers type-safe routing, first-class layouts, and a fast development loop. This setup allows for server-side rendering where necessary, while keeping most of the client-side operations pure. The migration involved replacing Next.js-specific components with native alternatives and restructuring the codebase to fit the new framework.

Despite the benefits, the transition required sacrifices, such as giving up built-in image optimization and parts of the Next.js ecosystem. However, the Railway team is confident in the direction of Vite and TanStack, even sponsoring their development. The new setup allows Railway to run its frontend on its own platform, leveraging Fastly for edge optimization and ensuring minimal server load.

This change reflects a broader philosophy at Railway: frontends should be fast, immutable, and cache-friendly, with infrastructure that supports seamless rollouts and previews. The new framework and asset model drastically reduce build times and improve iteration speed, aligning with Railway's vision of near-instant frontend deployments.