TanStack
Start

Full-stack framework

TanStackStart

RC

The full-stack framework for Router-first apps.

Start takes TanStack Router's typed route tree, URL state, loaders, and prefetching, then adds the server pieces: full-document SSR, streaming, server functions, server routes, and build output for the runtime you choose.

Total DownloadsWeekly DownloadsGitHub Stars

The fastest-growing full-stack framework in the JavaScript ecosystem.

Read the docs

Built on Router

Routes, search, loaders, links

Client-authored, server-powered

SSR, streaming, server functions

Portable output

Cloudflare, Railway, Netlify ready

Built in publicPartner-backedSponsor-supported
Router + server

Start keeps Router as the application contract.

Then it runs the server work Router shouldn't own: SSR, streaming, server functions, server routes, and deployable output.

GET /projects/tanstack?tab=activity

server first

export const Route = createFileRoute('/_app/projects/$id')({

validateSearch: projectSearchSchema,

loader: ({ context, params }) =>

context.queryClient.ensureQueryData(projectQuery(params.id)),

})

const getProject = createServerFn({ method: 'GET' })

.handler(({ data }) => db.project.find(data.id))

Request trace

streaming
1

Match route

routes/_app.projects.$id.tsx

Router narrows params, search, context, loader deps, and links before React starts rendering.

2

Run loader

loader({ context, params })

Start can do the preload on the server, dehydrate Query, and reuse the same contract during client navigation.

3

Call server function

createServerFn({ method: "GET" })

Database, auth, and environment work stay behind an explicit, validated server boundary.

4

Stream document

SSR + route data + pending UI

The HTML shell, head tags, loader data, and useful pending states can leave as one streaming response.

5

Ship runtime output

runtime adapter for the host

The same app model builds for the deployment target instead of changing how routes are authored.

Route contract

params.id, search.tab, loaderData

Server boundary

db, auth, env, files, mutations

Deploy output

Node, Workers, Netlify, Railway

Application builder

Turn an app idea into a Start-ready implementation plan.

Pick a starting shape, describe the product, and let the builder assemble the TanStack libraries and partner integrations that fit the job. The output is a practical agent prompt, not a generic starter checklist.

Describe the app you want to build

Ideas
Prompt
TanStack Libraries
Partner Integrations

Why Start

Most of the framework is the route tree.

If all you need is a SPA router, use Router. Start is for the moment the same app also needs SSR, streaming, server-only work, server routes, middleware, and deployable server output.

Built on TanStack Router

Routes, params, search schemas, loaders, pending states, links, and navigation all come from TanStack Router. Start adds the server and deployment layer around that app model.

URL state is first-class

Search params are parsed, validated, inherited, and written through Router APIs, so filters, tabs, pagination, and deep app state can be shared instead of synchronized by hand.

Server work stays explicit

createServerFn gives loaders, components, hooks, and handlers access to server-only work with validation, serializable boundaries, and same-origin RPC semantics.

SSR keeps the app model

Start can render the full document, stream useful UI, or opt routes into SPA/selective SSR modes while preserving the interactive client-side Router experience.

RC status

Feature-complete, still listening.

The RC API is considered stable and preparing for 1.0. For production apps, lock dependencies to a specific version and keep up with the final feedback, docs polish, and last-mile fixes.

Production RC checklist

Pin the RC Lock Start and Router packages instead of floating on broad ranges.
Track release notes Treat version bumps as planned work and re-run the routes, loaders, and server functions that matter.
Report sharp edges Small reproductions are still valuable while the final docs polish and last-mile fixes land.

Lovable

Lovable builds new projects on Start

Lovable says projects created after May 13 are server-rendered and powered by TanStack Start, with type safety and deployment flexibility as core reasons.

Inside Lovable

Thoughtworks

Thoughtworks put Start on the Radar

Technology Radar Vol. 34 lists TanStack Start in Assess and calls out compile-time safety across server functions, loaders, and routing.

Technology Radar

Bun

Bun documents Start in its ecosystem

Bun's official guide covers creating, running, hosting, and templating TanStack Start apps, including production deployment paths.

Ecosystem guide

Frontend Masters

Frontend Masters teaches the workflow

Web Dev Simplified's Frontend Masters tutorial builds a complete full-stack project with TanStack Start and compares it to Next.js.

Web Dev Simplified

Open source ecosystem

Partners and GitHub sponsors stay close to the product story.

Start is built in public, supported by maintainers, partner integrations, and sponsors who help keep the work moving.

Maintainers

Avatar of Tanner Linsley
Tanner Linsley
Avatar of Manuel Schiller
Manuel Schiller
Avatar of Florian Pellet
Florian Pellet
Avatar of Brenley Dueck
Brenley Dueck
Avatar of Sean Cassiere
Sean Cassiere
Avatar of Birk Skyum
Birk Skyum
Avatar of Christopher Horobin
Christopher Horobin
Avatar of Brooke Holmes
Brooke Holmes
View All Maintainers

Partners

Gold
CodeRabbit
Cloudflare
Railway
Silver
WorkOS
Clerk
OpenRouter
AG Grid
SerpAPI
Netlify
Bronze
Electric
Sentry
Prisma
Unkey
Start You?
We're looking for TanStack Start Partners to join our mission! Partner with us to push the boundaries of TanStack Start and build amazing things together.
Let's chat
View Previous Partners

GitHub Sponsors

Become a Sponsor
Wow, you've come a long way!
Only one thing left to do...
© 2026 TanStack LLC