ShipKit vs the T3 Stack: what $149 buys over free

TL;DR: T3 Stack is free, MIT, 29,064 GitHub stars. ShipKit is $149. They aren't competing — T3 scaffolds a typesafe Next.js app and deliberately stops, while ShipKit hands over payments, an admin panel and a deploy story already wired. The only question worth asking is whether the list further down is worth $149 of your time.

We sell ShipKit. Read this accordingly.

Everything below about T3 comes from create.t3.gg and the GitHub API, checked 1 August 2026. The section arguing for T3 is the longest one on the page, which tells you something about how this comparison actually goes.

What T3 is

A scaffolder. You run npm create t3-app@latest, answer a few prompts, and end up with Next.js + TypeScript + Tailwind, plus whichever of Prisma or Drizzle, NextAuth.js and tRPC you asked for. GitHub describes the repository as "The best way to start a full-stack, typesafe Next.js app".

Their own site is refreshingly blunt about where the job ends:

We made create-t3-app to do one thing: Streamline the setup of typesafe Next.js apps WITHOUT compromising modularity.

This is NOT an all-inclusive template.

We expect you to bring your own libraries.

Which makes this an easy comparison to write honestly. T3 isn't attempting to be ShipKit and never claimed to be. It gives you a clean typesafe floor and then leaves.

The list

Here's the argument, as a list instead of a boast. Start from a fresh T3 app, aim at something that takes money, and you'll be writing:

Payments end to end — checkout, webhook handler, subscription state in the database, and the frontend that reads it. An admin panel with its own auth: users, audit log, file browser, webhook inspector, settings. Transactional email with templates and a provider. Background jobs. Caching and rate limiting. i18n, if you need it. A component library past raw Tailwind. Then deployment: nginx, systemd, SSL, a database that comes back after a reboot.

ShipKit ships all of it. The API is a standalone Elysia server carrying 15 modules — users, admin, API keys, audit, auth providers, checkout, files, notifications, posts, projects, search, webhooks and the rest — rather than route handlers living inside the website. The admin panel is its own application behind role-based access control. 3 locales via next-intl. 68 UI components. Postgres with Drizzle underneath, plus Redis, Better Auth and Polar.

None of that is hard on T3. It's just a few weeks.

Where T3 wins

Free is a real answer. $149 against $0. More time than money, or building something you might drop in a month? T3 wins on arithmetic and nothing below changes that.

29,064 stars, 1,528 forks. Every wall you hit, somebody hit publicly first. Search a T3 error and you land on a GitHub issue; search a ShipKit error and you land on us. No feature list closes a gap that size.

MIT. The output is yours. No licence conversation, no private repo, nothing to explain to a client's lawyer. A paid boilerplate comes with terms attached; a scaffolder is just code you generated.

Modularity cuts our way. T3 asks which database and which auth you want. ShipKit already decided — Postgres, Better Auth, Polar, Elysia, Bun. Disagree with any one of those and you're not configuring, you're fighting. On T3 you'd have picked something else and moved on.

tRPC is a genuinely different bet. End-to-end typesafety with no API contract to maintain is a real pleasure, and plenty of teams want that more than they want a well-organised REST server. We don't offer it.

One more, and it deserves the same fairness we gave ShipFast: the repository's last push was 13 December 2025. For a scaffolder that means very little. It generates a project and its work is finished. Judge it on what comes out, not on commit frequency.

Where paying makes sense

One case. It's narrow.

You already know you're building something commercial, and you'd rather spend the next fortnight on the part only you can build than on a webhook handler you've written four times already.

That's the entire pitch. If the list above reads like work you enjoy, or work you'd learn from, then T3 plus your own libraries is the better road and you should take it.

The arithmetic, including the hole in it

At a loaded $75/hour, $149 buys under two hours. The list is not two hours.

But that only holds if you ship. A boilerplate bought for a project you abandon is $149 of nothing, and most projects get abandoned. Buy once you've decided, not while you're still deciding.

So, which

T3 if you want your own stack, if you're learning, if the budget is zero, or if tRPC is the thing you're after.

ShipKit if it's commercial, the decisions above are ones you'd have reached anyway, and starting from a running admin panel beats starting from a scaffolder.

FAQ

Is ShipKit built on T3?

No. Elysia on Bun for the API rather than tRPC inside Next.js, a Turborepo monorepo rather than one app, Better Auth rather than NextAuth.js.

Can I add payments and an admin panel to T3 myself?

Yes, and thousands have. That's the real decision here: a few weeks of your time against $149. Nothing technical stands in the way, only hours.

If T3 is free, why is a paid boilerplate worth anything?

For a lot of people it isn't. It's worth something when the work it removes is work you'd otherwise pay for in weeks. If that isn't your situation, T3 is the better answer and this page is telling you so.

Does ShipKit use tRPC?

No. The API is a separate Elysia server — the right shape once something other than your website needs to call it, the wrong shape if you wanted type inference flowing through a single codebase.

Sources

• Scope, philosophy and stack — create.t3.gg, read 1 August 2026
• Stars, forks, licence and last push — GitHub API for t3-oss/create-t3-app, read 1 August 2026
• ShipKit contents — the repository buyers receive, inventoried 1 August 2026