Deployment Guide

License & Updates

What the commercial license covers, how lifetime updates work, and how to upgrade safely.

What the license covers

Every paid TanStack Ship template includes a commercial license:

  • Use in your own products and in client projects.
  • Modify the code freely; you own your modifications.
  • Deploy to any infrastructure (Cloudflare, Node hosts, containers).
  • Lifetime updates for the purchased template line.

Not allowed: reselling or redistributing the template itself as a competing starter/boilerplate, or removing attribution required by third-party components.

The TanStack open-source libraries underneath (Query, Router, Start, Table, Form) are MIT licensed and free for personal and commercial use regardless of template purchase.

How updates are delivered

  • Updates ship as commits to the template repository you received access to.
  • There is no runtime phone-home: your deployment never depends on TanStack Ship servers.
  • Security fixes and dependency bumps are published as soon as they are verified.
  1. Keep your customizations in the places described in the Customization Guide (brand assets, message catalogs, content, catalog data).
  2. Add the upstream repository as a git remote.
  3. Fetch and review the changelog/diff before merging.
  4. Merge upstream into a branch, run pnpm install, pnpm db:migrate:local, pnpm test, pnpm build.
  5. Deploy to a preview environment, verify auth/billing/upload flows, then promote.

Important

If you edited generated files (src/paraglide/**, routeTree.gen.ts) or applied migrations by hand, resolve those conflicts explicitly — do not blindly accept upstream versions of database migrations.

Version pinning

You can stay on a known-good commit indefinitely; nothing expires. Update when you want new features or security fixes. For agencies managing multiple client deployments, tag each client's deployed commit so upgrades are reproducible.

Refunds and support

Refund terms are on the refund policy page. Support channels and response expectations are listed on the support page.