Framework
Start begins where Router leaves off: the same typed route tree, URL state, loaders, links, and prefetching, with full-document SSR, streaming, server functions, server routes, and deployable output added around it.
Built on Router
Routes, search, loaders, links
Client-authored, server-powered
SSR, streaming, server functions
Portable output
Cloudflare, Railway, Netlify ready
Application builder
Turn a product brief into a Start-ready stack.
Lead library
Full-document SSR, server functions, streaming, deployment adapters, bundling, and conventions live here. It is the answer when the app is more than a client router with a data layer.
Foundation
Router keeps Start grounded: generated route maps, nested layouts, loaders that start before render, validated search params, and navigation APIs that carry types through every link.
Open RouterFrom the team
TanStack Start Adds First-Class Rsbuild Support
TanStack Start now supports Rsbuild 2 alongside Vite, so teams can choose the build tool that best fits their stack, preferences, and infrastructure.
Who Owns the Tree? RSC as a Protocol, Not an Architecture
RSC is usually framed as a single architecture where the server owns the tree. But it's also a protocol, and the protocol supports more than one composition model. The overlooked question is who owns the tree.
React Server Components Your Way
RSCs are genuinely exciting — smaller bundles, streaming UI, moving heavy work off the client — but existing implementations force you into a one-size-fits-all pattern. What if you could fetch, cache, and compose them on your own terms?
Solid 2.0 Beta Support in TanStack Router, Start, and Query
TanStack Router, Start, and Query now support the Solid 2.0 beta, so you can try Solid's next major release in real applications today.
