Free while in beta
Answer a few questions — framework, components, database, ORM, auth, billing, email, landing page, package manager — and the whole repo downloads, wired together, with its test suite already written and green on the first run.
Pick the tools you already trust
Generated, not forked
A template ages because you forked it: the copy in your repo stops moving the day you download it. There is no template here to fork. The repo is assembled when you ask for it, from a generator that gets fixed in one place.
What this does not claim: a starter you have already downloaded is yours and stays exactly as delivered — nothing here reaches back into it. The promise is narrower, and it is the one that matters before you start: what you are handed is current on the day you ask for it.
Every tile below is a module the generator can wire for you. No single starter contains all of them — the grid is the menu, and the questions are what pick from it.
Modularity
Every question the wizard asks maps to an adapter, not a fork. Picking Prisma over Drizzle changes the files below and nothing above them.
This is also why the list can grow. A new framework or a new database is another adapter behind the same seam, so adding one does not multiply the templates we maintain — and every combination still has to go green in CI before it is offered.
The widest choice, and why the rest are cheap: routing and rendering sit in a framework adapter, invisible above it. React + Vite is the exception — with no server to keep a secret, later questions narrow to match.
3 places change · routes, components, and business logic untouched
Where is authentication configured?
src/lib/auth.ts
One module per integration, named after the thing it integrates. Nothing else reaches for the provider.
Built for assistants
Every repo we generate has the same shape: predictable layout, typed boundaries, and a spec beside every module. An assistant can guess where something lives — and when it guesses wrong, the compiler says so before you run anything.
Every integration gets a file named after it, in the same place in every repo we generate. There is no registry to keep in sync and no indirection to trace before making a change.
strictnoUnusedLocalsnoUnusedParametersnoFallthroughCasesInSwitchnoUncheckedSideEffectImportsverbatimModuleSyntax
Each module's test file states what it must do. That is context an assistant can run, not prose it has to trust.
How it works
Every question narrows the next one, so you cannot assemble a stack that does not fit together. You see the whole repo before it is created.
Framework, components, database, ORM, auth, billing, and a name. Each answer narrows the next, so a combination that does not work is never offered in the first place.
The full file tree and the suite it ships with, laid out before anything is generated. Nothing is built until you approve it.
A zip of the whole repo, yours to unpack and push wherever you like. Install, run the suite, and it is green on the first run.
Where it deploys is the one question we do not ask. Guessing your host would only give you a config file to delete, so the repo arrives without one.
Reels
Short clips on the problem this exists to solve — and what the generator does about it.
Pricing
No tiers to compare yet — every account gets the same allowance, and it costs nothing to try.
Free
$0· free while in beta
Answer ten questions. The whole repo downloads, ready to push wherever you like, with the suite already green. Free while in beta.