⚙ The Man Behind the Stack
There's a particular kind of developer who scratches their own itch and accidentally rewires an entire industry. Tanner Linsley is that developer. Based in Salt Lake City, Utah, he co-founded Nozzle.io - an enterprise SEO rank-tracking platform - in 2014, leaving Utah Valley University before finishing any of the three different programs he was juggling at the time. Music engineering, digital media, web development. He never stayed in one lane.
For the next several years, Nozzle was his laboratory. Every time the platform needed something - better data tables, smarter async state, a router that could actually handle type safety - and nothing on the market fit, Tanner built it himself. He then shipped it to the world. For free. Under open licenses. Maintained on nights and weekends. Supported by GitHub Sponsors and Patreon backers who recognized they were using production infrastructure that one person in Utah was holding together.
That's not a side hustle. That's a calling dressed up as a GitHub repository.
If there is a situation where there's a gap and it's going to help everyone if I just build something, that's why I build the tools that I do.- Tanner Linsley
💡 The Conversation That Started It All
React Query - the library that would eventually become TanStack Query and rack up 49,200+ GitHub stars - began with a conversation. Not a whitepaper. Not a product spec. A conversation with Kent C. Dodds about the difference between server state and client state.
The React community in 2019 was drowning in Redux. Everything went into the global store: user data, UI toggles, API responses, form drafts. It was chaos with good intentions. Tanner and Dodds talked through something that seems obvious in hindsight but wasn't widely articulated: data from a server isn't "your" state. It's a snapshot of someone else's state. It expires. It needs refreshing. It belongs in a cache, not a reducer.
React Query was born from that insight. It didn't try to replace Redux for the things Redux actually does well. It replaced the contorted patterns developers had built to make Redux do things it was never designed for. The developer community responded with an enthusiasm that suggested Tanner had named something everyone was already feeling.
Within two years, it had been renamed TanStack Query and had become the de facto standard for server state management in React applications. It now supports React, Vue, Solid, Svelte, Preact, and Angular. Because Tanner's philosophy has always been headless and framework-agnostic. The stack belongs to everyone, not just one ecosystem.
Your code is not you but an attempt at solving a problem.- Tanner Linsley
📈 The TanStack Ecosystem
The name isn't subtle. TanStack is Tanner's Stack. It started as a personal brand and became a movement. Here's what it covers as of 2026:
📝 A Philosophy, Not Just a Product Strategy
Most open source projects start with ideology and end with pragmatism. TanStack works the other way around. The libraries exist because Tanner needed them at Nozzle. The philosophy - headless, framework-agnostic, fully type-safe, dependency-light - emerged after the fact, as an articulation of what good tools feel like.
Headless means TanStack provides the logic and state but never tells you what your UI should look like. The table calculates sort order, tracks pagination, handles selection. You render whatever HTML you want. This sounds like more work for the developer. It is. It's also why TanStack Table works in React, Vue, Solid, and Angular without requiring separate forks. The hard problem is solved once. The presentation layer is your problem.
Framework-agnostic is the same principle applied upstream. Tanner watched the JavaScript ecosystem fragment into React-land and Vue-land and Svelte-land, with popular libraries rebuilt from scratch for each one. He decided his tools would cross those borders. The TanStack adapters handle the framework differences. The core logic stays shared.
Type safety is the newest pillar and the most opinionated one. TanStack Router, released in 2022, offered something genuinely new: a router where TypeScript could infer the type of route parameters, search parameters, and return values automatically. No manual type annotations. No casting. If you navigate to a route that doesn't exist, the compiler tells you before the user does.
When asked about innovation, Tanner deflects. "I prefer solving actual problems rather than wondering what I could build." TanStack DB, the embedded reactive database now in beta, is described by Tanner himself as "an extremely gratifying realization of the years-long vision I had for React Query from day 1." Not a new idea. The original idea, finally executable.
You must put forth effort, get rid of your ego, and just put your work out there.- Tanner Linsley
🆕 2026: The Year of the Full Stack
If 2019 was the year of React Query and 2022 was the year of TanStack Router, 2026 is shaping up to be the year Tanner plants a flag in every remaining corner of the frontend map. He's not building incremental updates. He's shipping categories.
TanStack Start 1.0 - his full-stack React framework - landed in 2025 after years of public development. Unlike the server-first frameworks that dominate current React discourse, Start takes a client-first position. The client isn't an afterthought. It's the starting assumption, with server capabilities layered on top through server functions and API routes. The latest addition is import protection: a Vite plugin that enforces hard boundaries between server and client code at build time, catching the kind of accidental data leaks that haunt server-component codebases.
TanStack AI launched in early 2026 with a partnership with OpenRouter, giving developers access to 300+ AI models from 60+ providers through a single, framework-agnostic API. TanStack DB entered beta simultaneously - an embedded, reactive database that sits on the client side and syncs with TanStack Query. Tanner described it as the realization of something he wanted to build into React Query from its earliest versions.
He spoke at React Conf 2026. He keeps appearing on podcasts - PodRocket, Callstack, Syntax, Software Engineering Daily. He keeps shipping. The gap between what he announces and what he delivers has always been short.
📋 Field Notes & Anecdotes
The React Query idea crystallized in a conversation with Kent C. Dodds about server state vs. client state. Tanner realized Redux was solving the wrong problem for data fetching. The insight took one conversation. The library took a weekend to prototype. The ecosystem took five years to build.
Nozzle.io is Tanner's "digital baby of 7 years." Every major TanStack library started as something Nozzle needed. He wasn't building open source tools as a business strategy. He was solving Nozzle's problems and shipping the solutions because sharing felt like the right thing to do.
When Tanner hit architectural limitations in React Router, he didn't file issues. He built TanStack Router from scratch, with TypeScript inference for route parameters baked in from day one. The community had been waiting for exactly that, they just didn't know it yet.
Between maintaining a multi-library ecosystem used by Fortune 500 companies, he woodworks. He makes music. He vacations with his wife and children. The prolific output and the quiet domesticity coexist, which says something about what sustainable work actually looks like.
💬 In His Own Words
"What's important is simply learning what is necessary in the moment to accomplish the task you have been given."
"Nozzle is my digital baby of 7 years that has directly inspired much of the OSS that I've built over that time period."
"TanStack DB is an extremely gratifying realization of the years-long vision I had for React Query from day 1."
👤 What Kind of Engineer Is He
Pragmatic. Ego-free about the work itself. Opinionated about the underlying problems. He's the kind of developer who credits his tools' shortcomings to misunderstanding the problem space, not to other people's bad decisions. He talks about open source like a craft, not a hustle.