01
TanStack Start
Full-stack React application framework
Consider when
Choose it when routing, server functions, SSR, and deployment need one runtime boundary.
ECOSYSTEM · VERIFIED 2026-08-03
Understand boundaries before choosing tools
TanStack is not an all-or-nothing suite. Its tools work independently and compose along explicit boundaries. This page tracks 12 products prioritized by Atlas and distinguishes published coverage from work still on the roadmap.
- priority products
- 12
- capability domains
- 5
- reading tracks
- 2
Five composable layers
Read from the application runtime downward: each layer narrows responsibility into more specialized state, interaction, or performance capabilities. Adopt only the layers that solve today’s problem.
- AApplication architectureStart · Router
- BData and stateQuery · DB · Store · AI
- CHeadless interaction logicTable · Form · Hotkeys
- DPerformance controlVirtual · Pacer
- EEngineering toolingDevtools
Product boundaries and coverage
“Established” is an Atlas editorial category. RC, Beta, and Alpha follow upstream product labels on the verification date. Validate versions and migration cost before adopting early products.
Application architecture
Defines how an application runs, navigates, and hands code and data across client and server boundaries.
02
TanStack Router
Type-safe routing and URL state
Consider when
Choose it when route params, search params, and loading lifecycles need end-to-end inference.
Data and state
Separates remote async data, reactive data models, lightweight local state, and streamed AI interactions.
03
TanStack Query
Remote async data and caching
Consider when
Choose it when server data needs caching, freshness, retries, invalidation, and background sync.
04
TanStack DB
Reactive client data model
Consider when
Evaluate it when collections, live queries, and optimistic writes must unify multiple data sources.
Next content batchOfficial docs
05
TanStack Store
Framework-agnostic reactive state
Consider when
Evaluate it for small shared reactive client state that does not belong to remote data.
Tracking upstreamOfficial docs
06
TanStack AI
Type-safe AI and streaming protocols
Consider when
Evaluate it when providers, streamed output, and tool calls need one replaceable typed interface.
Tracking upstreamOfficial docs
Headless interaction logic
Provides state and behavior for complex UI without owning components, styling, or design language.
07
TanStack Table
Table and data-grid logic
Consider when
Choose it when sorting, filtering, pagination, and grouping must stay independent of your UI system.
08
TanStack Form
Type-safe form state
Consider when
Choose it when complex fields and sync or async validation need type safety without UI lock-in.
09
TanStack Hotkeys
Declarative keyboard shortcuts
Consider when
Evaluate it when product shortcuts need scopes, chords, conflict handling, and cross-platform modifiers.
Tracking upstreamOfficial docs
Performance control
Controls large-scale rendering and high-frequency events so expensive work happens only when needed.
10
TanStack Virtual
Long-list and grid virtualization
Consider when
Choose it when DOM volume, rather than network work, becomes the list or grid bottleneck.
Planned coverageOfficial docs
11
TanStack Pacer
High-frequency event pacing
Consider when
Evaluate it when debouncing, throttling, queuing, or rate limiting need observable composable primitives.
Tracking upstreamOfficial docs
Engineering tooling
Brings runtime state from multiple TanStack tools into one extensible debugging surface.
12
TanStack Devtools
Extensible unified debugging panel
Consider when
Evaluate it when multiple TanStack tools need one extensible runtime inspection surface.
Tracking upstreamOfficial docs
EDITORIAL ROADMAP
Editorial sequence
Start, Router, Query, Table, and Form now have dual-track coverage. DB is next, with Virtual planned behind it. For the remaining early products, Atlas will track boundaries, versions, and primary sources before publishing long-form guides.