TanStack Start hosting
on Shipped.
Take your TanStack Start application from local routes to a live product, with its server and browser builds deployed together.
Give server functions somewhere to run
TanStack Start adds server rendering and server functions around its routing foundation. Deploy the production server output as a web service along with the assets the browser loads. Your application keeps its full-stack structure, while Shipped handles the public address and infrastructure needed to run it.
Keep data access behind your interface
Use server code to read from PostgreSQL or call private integrations, then return the data your interface needs. Store credentials as secrets instead of browser configuration. Separate staging values let you test new server functions and form workflows against test records before using them with customer data.
Ship the project your agent is building
Use MCP to deploy a working local application directly from your coding agent. You can also connect a GitHub repository for ongoing releases. Review both rendered pages and server responses in staging, then use deployment logs and history to follow the version running in production.
A little more detail
Questions about TanStack Start?
Is hosting TanStack Router alone the same as hosting Start?
A browser application using TanStack Router can be static. TanStack Start adds server capabilities, so applications using those capabilities need their server output deployed as well.
Do server functions make credentials safe automatically?
Keep credentials in server-only code and secrets, and control what each function returns. Do not expose private values through browser bundles, serialized responses, or logs.
From your workspace to the web