TanStack Start template

Start with a strong foundation, then decide the hard product choices on purpose.

This starter gives your team a real monorepo, a working Better Auth baseline, and a checklist for tenancy, hierarchy, onboarding, and billing before implementation turns into patchwork.

Create starter accountOpen protected route

What this template does not decide for you

Tenancy

Single-tenant, multi-tenant, or hybrid stays open until the app team decides.

User hierarchy

Flat access, workspace roles, or system-plus-tenant roles are all still possible.

Billing

Per-user, flat-rate, subscription, usage-based, or custom contract can all plug in later.

Auth checklist

Tenant model

  • What is the real customer boundary in this app?
    Single tenant | Multi-tenant workspace | Hybrid or mixed model
  • Can one user belong to more than one customer, workspace, or account?
    No | Yes | Not sure yet
  • Will users need to switch context inside the product?
    No | Yes | Maybe later

User hierarchy

  • How deep should the access hierarchy be at launch?
    Flat users only | App admins and members | System admins plus workspace roles
  • Do teams, departments, or groups need to exist in version one?
    No | Yes | Maybe later
  • Do internal operators need support or impersonation access?
    No | Read-only support | Full support tools

Access and onboarding

  • Which sign-in methods are needed first?
    Email and password | Magic link | Social auth | Enterprise SSO
  • How should users get into the app?
    Self-serve signup | Invite-only | Admin-created | Sales-assisted
  • What should happen when access changes later?
    Soft disable only | Suspend and restore | Offboard with audit trail

Billing checklist

Billing subject

  • Who is actually being billed?
    Per user | Per workspace or tenant | Company account | Something custom
  • Who controls the payment relationship?
    End user | Workspace admin | Finance owner | Sales-managed contract

Pricing model

  • Which pricing model fits the product best?
    Flat rate | Per seat | Usage based | Subscription | Custom contract
  • How often should customers be billed?
    Monthly | Yearly | One-time | Manual or mixed
  • Will the product need a free tier or trial period?
    No | Free tier | Time-based trial | Not decided yet

Entitlements

  • What should billing unlock or limit?
    Features | Modules | Seat count | Usage caps | A mix of these
  • How should billing start operationally?
    Manual for now | Provider-backed self-serve | Sales-assisted invoicing | Hybrid approach