For years, Next.js has been the undisputed king of React frameworks. But if you’ve been working with the App Router and React Server Components, you’ve probably encountered the infamous “use client” directive more times than you’d like to admit. What if I told you there’s a new framework that takes a fundamentally different approach—one that stays true to React’s client-side roots while still delivering enterprise-grade server features?

Enter TanStack Start, the framework that’s making developers reconsider their Next.js dependency.

The Next.js Golden Era (And What Changed)

Remember when Next.js was simple? The Pages Router was intuitive, file-based routing was magical, and getServerSideProps just made sense. Then came the App Router and React Server Components, bringing with them a new paradigm that divided the React community.

Don’t get me wrong—Server Components are powerful. But they introduced a cognitive load that many developers weren’t prepared for:

Constantly deciding between server and client components
Wrestling with the “use client” directive
Debugging mysterious hydration mismatches
Dealing with the complexity of data fetching patterns

For many teams, what was supposed to simplify full-stack development ended up complicating it.

TanStack Start: Client-First, 100% Server Capable

TanStack Start, currently in Release Candidate status and approaching its v1.0 launch, takes a refreshingly different approach. Built on top of the battle-tested TanStack Router and powered by Vite, it proudly declares its philosophy: “CLIENT-SIDE FIRST, 100% SERVER CAPABLE.”

This isn’t about rejecting server-side rendering—it’s about maintaining React’s original vision while adding server capabilities that feel natural, not bolted-on.

Core Features That Set It Apart

1. Type-Safe Everything

TanStack Start leverages TypeScript end-to-end with a level of type safety that makes tRPC jealous:

Fully type-safe routing with automatic URL parameter inference
Type-safe server functions that feel like calling local functions
Autocomplete across your entire data flow
Compile-time route validation

2. Server Functions Without the Ceremony

Instead of creating separate API routes or worrying about Server Components, TanStack Start introduces server functions that work more like RPC calls:

// Define a server function
import { createServerFn } from '@tanstack/start'

export const getUser = createServerFn('GET', async (userId: string) => {
  // This runs on the server
  const user = await db.users.findUnique({ where: { id: userId } })
  return user
})

// Call it from the client like a normal function
const userData = await getUser('123')

No need for tRPC, GraphQL, or separate API layers. Just functions.

3. Full-Document SSR with Streaming

TanStack Start supports proper server-side rendering with streaming out of the box:

Initial page load is fully server-rendered
Streaming lets you send HTML as it’s generated
Seamless hydration without the headaches
Progressive enhancement by default

4. Built on Vite

Unlike Next.js’s custom webpack configuration, TanStack Start builds on Vite, giving you:

Blazing fast dev server with instant hot module replacement
Simplified build configuration
Access to Vite’s massive plugin ecosystem
Near-instant server startup

Deploy Anywhere (Really)

Here’s where TanStack Start truly shines for South African developers dealing with various hosting requirements. While Next.js is increasingly tied to Vercel’s infrastructure for optimal performance, TanStack Start runs anywhere JavaScript can run:

Serverless platforms: AWS Lambda, CloudFlare Workers, Netlify Functions
Edge networks: CloudFlare, Deno Deploy
Traditional servers: VPS, containers, Kubernetes
Local development: Node.js, Bun, Deno

This deployment flexibility means you’re not locked into any particular provider—crucial for teams with existing infrastructure or specific compliance requirements.

Does It Support React Server Components?

Here’s the honest answer: Not yet, but it’s coming. The TanStack team is actively developing RSC support, which will be added in future releases. However, the team’s philosophy is worth noting—they’re building RSC support as an optional enhancement rather than forcing it as the default paradigm.

This means:

You can use TanStack Start productively today without RSC
Server functions already solve most use cases people want RSC for
When RSC arrives, it’ll be opt-in, not mandatory

What Developers Are Saying

The developer community’s response to TanStack Start has been enthusiastic:

@webdevcody: “TanStack Start solves the ‘use client’ dilemma that’s been frustrating Next.js developers.”

@melvynxdev: “It’s like Remix and Next had a baby that actually cares about TypeScript.”

@shayanAzd: “Finally, a framework that eliminates the need for tRPC or GraphQL with proper server functions.”

When Should You Choose TanStack Start Over Next.js?

TanStack Start isn’t trying to replace Next.js for everyone—it’s offering a genuine alternative for specific use cases:

Choose TanStack Start if:

You prefer a client-first mental model
You want maximum deployment flexibility
TypeScript type safety is non-negotiable
You’re building complex SPAs with server features
You love Vite’s developer experience
You want to avoid vendor lock-in

Stick with Next.js if:

You’re building primarily content-heavy sites
You need React Server Components today
You’re already invested in Vercel’s ecosystem
Your team is comfortable with the App Router
You need the largest community and ecosystem

Getting Started for South African Developers

The learning curve for TanStack Start is surprisingly gentle, especially if you’re already familiar with React and TypeScript:

# Create a new TanStack Start app
npm create @tanstack/start@latest

# Start the dev server
npm run dev

The official documentation at tanstack.com/start is comprehensive, with examples for deployment to various platforms.

The Road Ahead

TanStack Start is currently in Release Candidate status, which means the team is polishing features and gathering feedback before the official v1.0 release. The core features are stable and production-ready—companies are already using it to ship real applications.

Upcoming features on the roadmap include:

React Server Components support (opt-in)
Enhanced edge runtime support
Additional deployment adapters
Performance optimizations

Final Thoughts

Next.js isn’t going anywhere, and for many projects, it remains the best choice. But TanStack Start represents something important: a reminder that there’s more than one way to build modern web applications, and that the React ecosystem benefits from diverse approaches.

For developers frustrated with the complexity of Server Components, longing for better type safety, or simply wanting deployment flexibility, TanStack Start offers a compelling alternative that respects React’s client-first heritage while delivering the server features modern apps demand.

The framework landscape is richer when we have choices. TanStack Start is proof that sometimes the best innovation comes from staying true to first principles while thoughtfully adding new capabilities.

Ready to try it? Head over to tanstack.com/start and see if the client-first approach resonates with your development philosophy. The South African tech community is all about pragmatic solutions—and TanStack Start might just be the pragmatic choice you’ve been looking for.

Have you tried TanStack Start? Are you considering alternatives to Next.js for your next project? Share your thoughts with us at hello@webrack.co.za.

TanStack Start in 2026: The Client-First Alternative to Next.js You've Been Waiting For