TanStack Start in 100 seconds — and the post-Next.js full-stack JS landscape

Fireship”s February 20 video — “TanStack Start in 100 Seconds” — landed in the middle of the most active “alternative to Next.js” discourse the React community has had since the App Router shipped. TanStack Start is the framework that emerged as the most credible Next.js alternative through 2025-2026, and Fireship”s 100-second framing captured what the r/reactjs and r/nextjs communities had been arguing for months: SSR-by-default is the wrong choice for many apps, App Router complexity is real, and there”s now a serious alternative built on TanStack Router that doesn”t force you to make those bets.

The moment of crystallization came earlier than Fireship”s video. The r/nextjs “T3 Chat and Mastra Cloud move off of Nextjs” thread (526 upvotes, December 6 2025) — about Theo”s own T3 Chat migrating to TanStack Start and Mastra Cloud moving to Vite — was the canonical “high-profile projects leaving Next.js for performance” moment. By the time Fireship”s 100-second video shipped, the migration pattern was real and the alternative had a name.

What TanStack Start actually is

From the Fireship 100-second framing and the official docs:

• Built on TanStack Router — file-based routing with type-safe navigation that the React community has been ambivalent about for years (in good and bad ways)
• Vite as the bundler — not webpack, not Turbopack. Fast dev server, predictable production builds.
• SSR + SSG + SPA in one framework — pick the rendering mode per route. Server-only routes work; client-only routes work; mixed apps work.
• Server functions — RPC-style server code call-able from client with end-to-end TypeScript types.
• No vendor lock-in — runs on any Node host, Vercel, Netlify, Cloudflare Workers, Fly, Render, self-hosted.

The architectural pitch: Next.js made you commit to one rendering paradigm per app and one platform (Vercel-flavored). TanStack Start lets you mix paradigms per route and deploy anywhere. For apps where “we need SSR everywhere” was always wrong, the new framework is a better fit.

Why the migration pressure was building

The r/reactjs “Thinking of abandoning SSR/Next.js for Pure React + TanStack Router” thread (218 upvotes, December 23 2025) captured the developer-side frustration. OP:

“I”m hitting a wall with Next.js. Not because of the code, I love it, but because of the infrastructure. I built a project I”m really proud of using the App Router. It works perfectly locally. I deployed to Vercel, and the ”Edge Request”…” [billing exploded]

Top response (450 upvotes):

“SSR is the most over hyped and over recommended thing in FE this decade. If you”re building an app rather than a website it”s straight up a worse option.”

Second response (61 upvotes):

“Afaik neither SSR nor Next.js do anything for scaling. In fact, I”d argue that being locked into vercel is a high risk issue when it comes to scaling.”

These aren”t edge-case complaints — they”re the dominant sentiment in r/reactjs through Q4 2025. The mental model “Next.js is the default React framework” started cracking when the bills came in.

The r/nextjs “Frustrated with Vercel pricing once you scale?” thread (77 upvotes, Jan 26 2026) extended the pressure: Vercel”s Fluid Compute pricing changes through 2025 accelerated the “we need a non-Vercel-locked alternative” conversation. TanStack Start became the answer because it didn”t require a runtime change, just a framework change.

The T3 Chat migration as canonical example

The r/nextjs T3 Chat migration thread (532 upvotes) is the moment the migration became socially visible. Theo (Cursor”s July 2025 vocal critic, Vercel-adjacent for years) moving his own product off Next.js is the kind of signal the community noticed.

The top comments split into recognizable camps:

Pro-migration camp (132 upvotes): “Love how they make it sound like a political stance, when it”s just their inability to choose the right tool for the job in the first place.” — i.e., picking Next.js for everything was the original mistake; migrating to the right tool is correction, not betrayal.

Anti-Theo camp (429 upvotes): “Why should we care what a clickbaiter with silly opinions thinks?” — the personality dimension of the story; Theo”s opinions get amplified disproportionately. Valid critique; doesn”t change the underlying T3 Chat performance numbers that drove the actual migration.

The “it”s about tooling, not framework” camp — recurring in adjacent threads. The argument: Next.js + Vercel is a stack choice; if you”re unhappy with the stack, the framework swap matters less than people think. Counter: framework swaps unlock platform options (Cloudflare Workers, Fly.io) that Next.js makes harder.

The Reddit “TanStack vs everything” decision matrix

The r/reactjs “Tanstack vs React Router vs Next” thread (71 upvotes, Jan 30 2026) captured the framework-shopping moment many React devs were in by early 2026:

• TanStack Start — for users who want full-stack JS with Vite-speed builds, multi-platform deploy, type-safe routing
• React Router (now Remix-merged) — for users who want SSR with simpler mental model than Next.js App Router
• Next.js — still the default for users who specifically want Vercel”s ecosystem and don”t mind the platform lock-in

The mature read from late January 2026: the React framework landscape has fragmented in a healthy way. Next.js is no longer the only credible default; the alternatives are mature enough that “pick the right tool for the workload” is now a real decision rather than “use Next.js because that”s what the React community does.”

Creator POV vs Reddit dissent

Fireship”s POV in the 100-second video is descriptive and brief — here”s what TanStack Start is, here”s who”s using it, here”s why it matters. He doesn”t pile on Next.js; he doesn”t evangelize TanStack. Standard Fireship pattern.

Theo”s broader 2025-2026 POV on the platform side (“Vercel Finally Caught Up” but with persistent pricing concerns) frames the architectural context: the framework decision is downstream of the platform decision. TanStack Start exists because the platform layer needed an alternative; the framework choice followed.

The Reddit dissent splits productively:

The pro-TanStack camp — vocal in r/reactjs and r/nextjs threads. Valued: type-safe routing, Vite speed, no SSR commitment, platform flexibility.

The “Next.js still works” camp — accurate for many users. Most production Next.js apps don”t hit Vercel pricing pain or App Router complexity at scales where switching matters.

The “React itself is the problem” camp — present and growing. Some users in the same threads argue Solid.js, Svelte, or Vue handle the trade-offs better than any React framework. Different debate; legitimate position.

The “just use plain Vite + React” camp — minimalist response. For SPAs that don”t need SSR, plain Vite + React Router + your-own-backend is a real option that requires less framework opinion than TanStack Start.

What this means for working engineers in late February 2026

Three practical positions:

1. If you”re starting a new React app today and don”t specifically need SSR, evaluate TanStack Start. Type-safe routing alone is a meaningful productivity gain; multi-platform deploy unlocks cost options Next.js makes harder.

2. If you”re on Next.js and it works, don”t migrate reactively. The T3 Chat migration is high-profile but driven by specific performance and platform constraints. Most Next.js apps don”t have those constraints.

3. If you”re Vercel-fatigued, the framework swap is real leverage. Moving off Next.js to TanStack Start (or Vite + React Router) is the path that unlocks Cloudflare Workers, Fly.io, or self-hosted deploys without fighting the framework.

The honest critique

What TanStack Start doesn”t solve:

• It doesn”t eliminate the “which framework” anxiety. Frameworks come and go; in 18 months we”ll be having this discussion about the next thing.
• The ecosystem is smaller than Next.js. Fewer tutorials, fewer Stack Overflow answers, fewer hire-able developers who know it. Real cost.
• Tanner Linsley”s “one person owns this” risk. TanStack”s broader ecosystem (Query, Router, Table, Start) is largely his vision. If priorities shift, downstream users feel it.
• SSR still matters for some workloads. SEO-critical content, social media link previews, certain compliance needs. TanStack Start supports SSR per-route; doesn”t make those needs go away.

For most working engineers reading this in late February 2026: the post-Next.js landscape is now a real choice, not a forced default. TanStack Start is the most credible alternative for the “I love React, I”m tired of Next.js + Vercel” cohort. Whether it”s the right answer for your specific app is workload-driven, not trend-driven.

For broader platform context, see our Vercel runtime shifts piece and the Cloudflare Vinext analysis for the parallel Cloudflare-side reimplementation of Next.js.