Next.jsViteReactStarter

stanza — Next.js Starter Template

By jakejarvis

Stanza is a modular monorepo template CLI that generates a TypeScript monorepo via npm init stanza by selecting framework, ORM, database, auth, and UI, and supports adding modules later with stanza-cli add.

Explore the design

Compare the page layouts and mobile experience. Open any screenshot for a closer look.

2 previews
Desktop homepage1 / 2
Desktop captureTop of page

Actual screenshot captured by the server browser.

All pages & views 2

Screenshots show visual appearance; interactive behavior may differ.

Recorded 2026-10-14View source

What stands out

A quick read of the recorded project description.

01

Generate a TypeScript monorepo via npm init stanza by selecting framework, ORM, database, auth, and UI

02

Supports running stanza-cli add in an existing project to add modules, manifest-driven and peer-dependency-aware

03

Generated files go directly into your repository; there is no Stanza runtime

04

auth, db, and orm install into separate internal workspace packages, referenced by applications via workspace:*

05

The module registry is static JSON and can point to a self-hosted address and provide custom modules

06

The README marks the project as Major work in progress

Template Details

Stanza is a modular monorepo template CLI. The README positions it as "shadcn for full-stack TypeScript projects." Usage is to run npm init stanza my-app, then cd my-app, npm install, npm run dev in sequence. During initialization you can choose the framework, ORM, database, auth provider, and UI, generating a clean monorepo with idiomatic code. The generated files go directly into your repository; there is no Stanza runtime to install or carry.

In an existing project you can run npx stanza-cli add auth better-auth at any time to add a module. The README states that add is manifest-driven and peer-dependency-aware, selects the correct adapter for the current stack, and wires dependencies, environment variables, and templates into the correct workspace package. auth, db, and orm install into their own internal workspace packages (packages/auth/, packages/db/, with package names @<your-app>/auth, @<your-app>/db), and applications use them via workspace:*. When switching auth providers, only the contents of packages/auth/ are replaced, without affecting imports in the application.

The module registry is open: modules are static JSON, and you can point the CLI at your own hosted address and provide custom modules. The repository structure includes apps/cli (the stanza-cli binary), apps/web (the stanza.tools site, using TanStack Start), packages/schema (stanza.json and module schema, contract types, category list), packages/registry (slot/peer/capability resolvers and package.json, env, template composition), packages/codemods (ts-morph helpers for region-aware patches), packages/utils (path safety and environment file helpers), packages/create-stanza (the npm init stanza template shim), registry/modules (first-party modules covering framework, orm, db, auth, ui, tooling, testing), and scripts/compile-registry.ts (builds the static registry JSON consumed by the CLI).

The README explicitly marks the project as "Major work in progress" and points to the module registry page for the roadmap. Documentation and CLI reference are at stanza.tools/docs, and the builder for visually assembling a stack is at stanza.tools. The README does not provide information on performance, production readiness, or specific framework version numbers.

Next.jsViteStarter

Is it right for your project?

Use Cases

  • Initialize from scratch a full-stack TypeScript monorepo containing a chosen framework, ORM, database, auth, and UI
  • Add modules such as auth, db, or orm on demand in an existing TypeScript monorepo
  • Switch auth providers by replacing only the contents of packages/auth/ without changing application imports
  • Self-host a module registry and provide custom modules for the CLI to use

Suitable For

  • Developers who want to build a full-stack TypeScript monorepo in a modular way
  • Teams that need to incrementally add auth, database, or ORM modules to an existing project
  • Projects that want generated code to go directly into their own repository without introducing an extra runtime
  • Teams that need a custom module registry or self-hosted module source

Getting started & customization

Use these recorded setup notes alongside the repository instructions for your chosen version.

  1. 1

    Initialization command: npm init stanza my-app, followed by cd my-app, npm install, npm run dev

  2. 2

    Example module addition command: npx stanza-cli add auth better-auth

  3. 3

    auth, db, and orm modules install into internal workspace packages such as packages/auth/ and packages/db/, referenced by applications via workspace:*

  4. 4

    The full guide and CLI reference are at stanza.tools/docs

  5. 5

    The README marks the project as Major work in progress; the module roadmap is at stanza.tools/docs/registry

Read repository instructions

License & source material

Usage conditions & limitations

Free to use · keep license notice

This entry covers the free version under the MIT license in the public repository; the free scope is the code of that version and does not mean external services or third-party assets are free.

Must comply with when using

  • Free use, modification, commercial use, and distribution of that version's code are permitted.
  • When distributing copies or substantial portions of the code, retain the original author's copyright notice and the complete MIT license notice.
  • The code is provided as is; warranties and limitations of liability are governed by the original license and applicable law.

Additional costs & items to verify

  • Demo images, fonts, icons, and other third-party assets must be checked against their respective licenses and cannot be judged solely by the code's MIT license.
  • External services such as domains, hosting, databases, payments, or AI may incur separate charges.
View Original Text Basis

Compiled by DeepSeek based on repository license and README ·2026-10-14. Results only cover the materials read; dependencies, images, fonts, and subsequent term changes are subject to their respective original texts.

Project checks & description sources

Template Information

Source platforms
GitHub
Documentation and maintenance reference score
More documented · 80 / 100
Technologies
Next.js · Vite · React
Website type
Starter
How this score is calculated

Our heuristic uses license records (up to 30), a demo link (12), a preview (10), stars (15), recorded maintenance (15), description completeness (8), feature records (5) and classification data (5). It is not a code, security or performance test, or a Google score. A link does not establish tested functionality.

What to verify for this project

Repository update recorded
2026-10-12
Screenshot last checked
2026-10-14

A demo link is listed. Check it with your own content and viewport sizes; its presence does not confirm that forms, authentication or payments work.

The catalog identifies Next.js as the primary stack. Check the actual dependency manifest and lockfile for versions and hosting requirements. These notes use recorded metadata, not a code audit or a deployment test.

Use a selection guide →

How this description was prepared

AI-assisted description based on catalog records and repository material. Repository authors are not automatically the reviewers of this description.

Review declaration: codex-user-requested-batch-review-20261015 · 2026-10-15

Inspect the recorded source material

SHA-256: 5d59525e43c50f334d16ea1358a30dc4df8951fa75b9607885280d8241f99497

2026-10-14T17:11:57.174Z

Source file / repository
# Stanza

Modular monorepo template CLI — aka shadcn for full-stack TypeScript projects.

```sh
npm init stanza my-revolutionary-app
```

Pick a framework, ORM, database, auth provider, and UI — get a clean monorepo with idiomatic code, vendored into your repo. Layer in more modules later with `stanza-cli add`.

> [!WARNING]
> **Major work in progress!** See the [module registry](https://stanza.tools/docs/registry) for the roadmap.

## Why Stanza?

- **`add` works after `init`.** Run `stanza add` on an existing project — it's manifest-driven and peer-aware, so it picks the right adapter for your stack and wires deps, env, and templates into the correct workspace package.
- **Your code, vendored.** Generated files land in your repo verbatim. There's no Stanza runtime to install or carry around.
- **Open registry.** Modules are static JSON. Point the CLI at your own host and serve custom modules.

## Quick start

```sh
npm init stanza my-app
cd my-app
npm install
npm run dev
```

Add a module to an existing project at any time:

```sh
npx stanza-cli add auth better-auth
```

`auth`, `db`, and `orm` install into their own internal workspace packages (`packages/auth/`, `packages/db/`, named `@<your-app>/auth`, `@<your-app>/db`); your app consumes them via `workspace:*`. Swapping an auth provider replaces the contents of `packages/auth/` without touching your app's imports.

## Docs

Full guides and the CLI reference live at **[stanza.tools/docs](https://stanza.tools/docs)**. Assemble a stack visually with the builder at **[stanza.tools](https://stanza.tools)**.

## What's inside

```
apps/
  cli/            # stanza-cli — the CLI binary
  web/            # https://stanza.tools (TanStack Start)
packages/
  schema/         # @withstanza/schema — stanza.json + module schema, contract types, category list
  registry/       # slot/peer/capability resolver + package.json/env/template synthesis
  codemods/       # ts-morph helpers for region-aware patching
  utils/          # shared path-safety + env-file helpers
  create-stanza/  # `npm init stanza` template shim
registry/
  modules/        # first-party modules (framework, orm, db, auth, ui, tooling, testing)
scripts/
  compile-registry.ts  # builds the static registry JSON the CLI consumes
```

## License

[MIT](./LICENSE)
Report a correction

Explore similar templates

Compare previews and descriptions within the same stack and category.