Is create-t3-app free? What it actually scaffolds

What create-t3-app actually is (a CLI, not a template)

create-t3-app is a CLI, not a template repository you clone. Running npm create t3-app@latest starts an interactive setup that asks which pieces of the T3 stack you want, then generates a project containing only those choices. Next.js and TypeScript are the two constants; Tailwind CSS is almost always included alongside them. Everything past that — tRPC, Prisma, Drizzle, NextAuth — is optional and added only if you select it during setup, so the code you end up with matches what you actually asked for rather than a fixed template someone else assembled.

The project describes itself explicitly as not an all-inclusive template: the maintainers expect you to bring your own libraries for concerns like state management, and point to a separate recommendations page rather than baking opinions about them into the generator. That restraint is deliberate — create-t3-app encodes the T3 team's opinions about typesafety and modularity into the CLI itself, but leaves everything outside that scope open. You can browse the create-t3-app listing for the full breakdown of what the CLI covers and where it stops.

What's inside: tRPC, Prisma or Drizzle, Tailwind, NextAuth — à la carte

Each backend piece the CLI offers solves a specific typesafety problem. tRPC gives you typesafe API routes between client and server without a separate code-generation step. Prisma or Drizzle handle the database layer with a typesafe client — Prisma works across most SQL dialects and Mongo, while Drizzle is the lighter SQL-focused alternative. NextAuth.js adds authentication. Tailwind CSS, almost always selected, handles styling. None of these are bundled by default: each is a checkbox in the setup flow, and skipping one means the generated project simply doesn't contain any code for it.

Because the scaffold only includes what you picked, there's nothing to delete afterward — a common complaint with heavier all-in-one boilerplates. The documentation also covers deployment recipes for Vercel, Netlify, and Docker once the project exists. One detail worth checking before you run the CLI: folder structure differs depending on whether you scaffold with the App Router or the Pages Router, so confirm which one matches your current Next.js preferences before committing to a layout.

Is it really free? Licence and cost breakdown

Yes, in the plain sense: create-t3-app is listed as free and is open-source, distributed as a CLI you run with npm create t3-app@latest rather than a product you purchase. There's no license fee, no paid tier, and no gated feature set — every stack piece described above is available to every user who runs the command. The only costs you'll incur are the ones you choose yourself afterward: a hosting provider, a database, or any third-party service you wire into the generated project.

That's a real distinction from other entries in the Next.js & React category. ShipFast, for instance, is closed-source and priced from $199 one-time because you're paying for a finished Stripe-and-auth shell, not just a scaffold. create-t3-app never asks for payment because it isn't selling a finished product — it's distributing the setup step of one, for free, indefinitely.

create-t3-app vs the catalog's paid Next.js SaaS kits

ShipFast is the clearest contrast: for $199 one-time you get Stripe payments, magic-link and social auth, transactional email, and SEO helpers already wired into a working Next.js app built with Tailwind and DaisyUI. create-t3-app gives you the typesafe foundation underneath a similar stack — tRPC, Prisma or Drizzle, NextAuth — but stops at the scaffold. Stripe, email, and SEO metadata are yours to add.

Taxonomy, shadcn's App Router demo, sits in between: it's free and already wires NextAuth, Prisma, and a Stripe subscription flow together, styled with the shadcn/ui component approach. But it's explicitly a demo repository maintained at its author's discretion, not a supported CLI — you fork it and adapt the code, rather than regenerating a fresh project per app the way create-t3-app's CLI is designed to be reused.

next-forge goes the other direction in scale: a free, open-source Turborepo monorepo with separate app, web, docs, and API workspaces, plus a packages layer that keeps vendor choices like auth and payments swappable. It solves a different problem than create-t3-app — structuring a product across multiple surfaces from day one — and carries real monorepo overhead that a single create-t3-app scaffold doesn't.

When to reach for it instead of a full SaaS boilerplate

create-t3-app suits TypeScript developers starting any full-stack Next.js project who want the compiler catching integration bugs between client and server, without adopting GraphQL machinery to get there. It's also a good fit for hackathons, where a fast, typesafe starting point matters more than a finished feature set, and for teams that want end-to-end type safety as a baseline rather than a stretch goal.

It also works well as a neutral base underneath your own product code, precisely because mega-kits can feel like someone else's house once you start diverging from their assumptions. Since create-t3-app only contains what you selected, there's less to unwind later, and the T3 community around it documents and debates the same architectural questions you're likely to run into, so you're rarely working from a blank page on patterns.

Limitations: no billing, no admin, no marketing pages

create-t3-app's own documentation is explicit about the boundary: it is not for shipping a business in a weekend. There's no billing integration, no admin panel, and no marketing pages in the scaffold — the CLI hands you a typesafe foundation, not a product shell. If your project needs those pieces on day one, they're entirely additional work on top of what gets generated.

There's also an architectural tradeoff worth naming: tRPC couples client and server inside a single monorepo worldview, which fits poorly if you need to expose a public REST API to third parties. Compare that to ShipFast or Taxonomy, both of which already include a Stripe flow out of the box, or next-forge, whose packages layer isolates vendor decisions like payments behind an interface you can swap without touching the rest of the app.

FAQ

A common question is whether create-t3-app ships with a database. It doesn't — during setup you pick Prisma or Drizzle as a typesafe client, and either one still expects you to point it at a database you provision yourself, whether that's a SQL dialect Prisma or Drizzle supports or, for Prisma specifically, Mongo. The CLI's job stops at generating the typesafe access layer, not at hosting or seeding data.

Another frequent point of confusion is App Router versus Pages Router, since the two produce different folder structures once the project is generated. The documentation covers both, but it's worth deciding upfront which router you're targeting — NextAuth and tRPC wiring differs slightly between the two — rather than discovering the mismatch after you've already started adding features on top of the scaffold.

Frequently asked