TanStack Start

What does Start add to TanStack Router?

The router matches addresses to screens and loads information for them. Start adds the tools to build the app, render pages on a server and call server code from those screens.

Start 1.0 became stable in October 2026. Use the React or Solid instructions that match your project. A router example by itself does not set up the server that runs your booking code.

Where should your booking rules run?

Use a server function for the write. It can read the requested time, check what the caller can do and save the record through a database you connect.

A server function can be called by browser code. Validate what it receives and check permissions in the function where the decision is made. Keep database credentials on the server. The screen should use the function’s response to decide whether to show a confirmation.

How can you sketch the browser and server boundary?

Draw a fictional repair booking in two columns, one for the page and one for the server. The page can ask for a time. The server confirms whether that time was reserved.

1. 1
   Give the page one job

   Draw a time picker. Write down the only input it sends for this exercise, the requested repair time.
2. 2
   Give the server the final say

   Trace a request for a time that exists and one for a made-up time. The server should check both and change the paper booking table only for the valid available time.
3. 3
   Read the saved record

   Open the page again on paper. The booking is confirmed only if the shared table contains it. A new visitor who requests that time gets an unavailable response.

Which part does the host need to run?

Choose a build target that can run your server functions. The documentation describes a Node deployment as well as other provider-specific outputs.

The current React and Solid packages require Node 22.12 or newer when you use Node for setup. Other host runtimes follow their own deployment setup. A browser-only build cannot run the booking server function by itself.

The framework packages are MIT-licensed. Running the server, database and other connected services is separate.

What changes when you move to a different host?

Keep the route code, package files and server functions. Change the build and runtime settings for the destination, then connect its data services.

Back up the database separately from the code. Before moving traffic, load an isolated version on the destination and check that the same request runs on the server and reads a restored fictional record.