Ship TanStack apps
with zero ops on Render

Yes. TanStack Start builds a Node server through Nitro, and Render runs it as a web service. Create a Render-ready app with the TanStack CLI, or add the Nitro setup from the Start hosting guide to an existing app.

Yes. Render Postgres and Render Key Value run in the same workspace as your app and reach it over automatic private networking, with no VPC to configure. Paid Postgres instances include point-in-time recovery.

Render bills three things: a flat workspace plan, compute for each service prorated to the second, and metered usage such as bandwidth. Hobby workspaces are $0/month plus compute, and free compute plans are available while you build.

Render runs the whole backend rather than the frontend alone: web services, private services, background workers, cron jobs, durable workflows, Postgres, and Key Value in one workspace. Compute is a fixed instance size prorated by the second, so the bill stays predictable as traffic grows.

Yes. Every plan includes single-service previews for pull requests. Pro workspaces and above add full-stack preview environments that spin up your entire architecture for each change.

Yes. If your app builds to a Node server or ships a Dockerfile, Render deploys it from GitHub, GitLab, or Bitbucket. Add a render.yaml Blueprint to describe the service, and set NITRO_PRESET to render-com so Nitro builds the output Render runs.