TanStack Teams Up with Vercel: How Next.js’s Home Is Embracing a Rival

TanStack announced an official partnership with Vercel, positioning Vercel as the primary hosting platform for TanStack Start and promising tighter integration for deployment, runtime, and support.

What TanStack Start Targets

If you already use TanStack Query or TanStack Router, Start is a natural next step. It expands the router into a full‑stack framework, adding complete documentation for SSR, streaming rendering, Server Functions, middleware, and both front‑end and back‑end builds.

The difference from Next.js is clear: Next.js App Router centers React Server Components and server‑side rendering, while TanStack Start relies on a route‑tree organization where URL parameters, search state, loader data, and server functions retain type inference along the tree. This type‑safe routing shines in admin panels, search pages, and complex business systems where a lot of state lives in the URL.

TanStack Start is still in RC. The team says the feature set is complete and the API is stabilising, but bugs and ecosystem maturity still need work before it can be used blindly in production.

Deploying to Vercel – How Simple Is It?

First, add Nitro to the project: pnpm i nitro Then register Nitro in vite.config.ts:

import { tanstackStart } from '@tanstack/react-start/plugin/vite'
import { defineConfig } from 'vite'
import viteReact from '@vitejs/plugin-react'
import { nitro } from 'nitro/vite'

export default defineConfig({
  plugins: [tanstackStart(), nitro(), viteReact()],
})

With those changes Vercel automatically recognises TanStack Start and Nitro, so you usually don’t need to specify a build command or output directory. The project can be imported from a Git repository or run directly with the vercel CLI. After linking the repo, pushes to a preview branch create preview deployments, while pushes to the main branch trigger production deployments.

TanStack Start’s server code is compiled by Nitro into Vercel Functions and runs on Vercel’s Fluid compute, scaling automatically with traffic and shutting down idle instances.

The workflow is short, but two common friction points remain compared with the familiar Next.js experience:

Framework detection in monorepos or migrated projects. If Vercel does not auto‑select TanStack Start, you must manually set the framework in the project settings or add a vercel.json file:

{
  "framework": "tanstack-start"
}

Environment variables. Variables prefixed with VITE_ are exposed to the browser, so secret credentials and API keys must stay under ordinary names and be accessed on the server via process.env.

These are engineering details that can be documented, but developers will be watching the partnership for faster version compatibility, stable framework detection, and who will handle production‑grade issues.

Why Vercel Is Opening the Door to a Next.js Competitor

Vercel wants Next.js to stay dominant, yet a cloud platform that only supports its own framework would be limited by framework boundaries. The Vercel site already lists Nuxt, SvelteKit, FastAPI, and Nitro; TanStack Start now joins that list, giving developers the same Git‑preview, Functions, logging, and rollback experience while expanding Vercel’s workload portfolio.

Vercel’s June announcement about TanStack Start was blunt: applications don’t need to be rewritten as Next.js; they can keep their router‑first architecture and still deploy on the same infrastructure.

This arrangement benefits both sides. A team might use Next.js for a content site and TanStack Start for a complex post‑login app; keeping both projects on Vercel means the platform, not the framework, becomes the primary value driver.

Will the Partnership Lock TanStack to Vercel?

There is no sign of lock‑in. TanStack Start still builds on Vite or Rsbuild, with Nitro handling the adaptation to various runtimes. Official docs list Cloudflare Workers, Netlify, Railway, Node.js, and Docker as supported targets, so moving off Vercel only changes the deployment plugin and platform services, not the core routing or Server Functions.

Vercel is now a Gold Partner of TanStack, meaning both parties will invest resources to improve support, but TanStack Start’s emphasis on portability remains unchanged.

Developers should be patient: TanStack Start is still in RC, so tutorial count, third‑party integrations, live case studies, and troubleshooting resources lag behind Next.js. For content‑heavy sites that rely on mature RSC, image optimisation, and ISR, Next.js remains easier. For applications with complex state, heavy URL usage, and strict type‑safe routing, TanStack Start can play to its strengths.