Railway's production frontend including dashboard, canvas, and railway.com has migrated from Next.js to Vite plus TanStack Router and Start. Builds that exceeded 10 minutes with six minutes spent in Next.js page optimization now finish under two minutes. The application is overwhelmingly client-side with real-time websockets and stateful interfaces according to the primary source.

Railway remained on the Pages Router and built custom abstractions for layouts because first-class support was absent. The App Router's server-first patterns did not align with their client-driven architecture. TanStack Start supplied file-system route generation with inferred type-safe params, composable pathless layouts, instant HMR, and selective SSR limited to marketing pages per the Railway post and TanStack documentation.

The change required two PRs and zero downtime: the first eliminated next/image, next/head, and next/router dependencies using native browser APIs; the second replaced the framework after extracting components from 200 routes. Vite documentation states its esbuild and native ESM approach delivers faster cold starts and builds than webpack-based toolchains used by Next.js. Similar client-first migrations appear in teams moving away from monolithic frameworks once iteration tax becomes unsustainable as cited in Vite comparisons.