start-server-core

TanStack Start handles server-side requests and SSR by orchestrating a three-phase request flow using a core server runtime. You wire up createStartHandler in your server entry point to centralize routing, server functions, and app rendering across Node-based servers.

AsyncLocalStorage-based context maintains utility accessibility throughout the full TanStack Start request lifecycle. This mechanism ensures that request-scoped data remains available during server-side rendering and server function execution without manual prop passing.

Yes, you can manage cookies and session data directly in TanStack Start server functions. The runtime provides built-in request utilities like setCookie, getCookie, and useSession, which are accessible during the request lifecycle via AsyncLocalStorage context.

The best way to structure server routes and server functions in TanStack Start is by centralizing them using createStartHandler. This foundational runtime applies a cohesive three-phase request flow to handle routing, execute server functions, and process SSR responses.

Yes, the TanStack Start server runtime works across different Node-based server environments and framework bindings. It functions as a foundational layer, applying its three-phase request flow and utilities consistently regardless of the specific server setup.