What made Railway switch from Next.js?

Builds hit 10+ minutes, mostly Next.js overhead. Their client-heavy dashboard didn't need server-first patterns—hacks piled up.

How did Railway migrate without downtime?

Two PRs: first stripped Next.js deps, second swapped framework. use their own preview deploys and zero-downtime tools.

For client-driven apps like dashboards, yes—faster builds, type-safe routing, true layouts. Trade ecosystem maturity.

🌐 Frontend & Web

Everyone figured Next.js was frontend endgame. Railway said no—axed it completely, slashed builds to under two minutes, and shipped without a hiccup.

theAIcatchup Apr 08, 2026 3 min read

Railway cut frontend builds from 10+ to under 2 minutes by ditching Next.js for Vite + TanStack Router. 𝕏
Migration done in two PRs with zero downtime, showcasing their own platform's power. 𝕏
Signals shift to client-first stacks for dashboards, predicting more teams will follow. 𝕏

Published by

Ship faster. Build smarter.

#Next.js migration #TanStack Router #Vite #frontend builds

Get the best Developer Tools stories of the week in your inbox — no noise, no spam.

Originally reported by Hacker News