Hype Stack CLI

One command scaffolds a full-stack TypeScript app: React 19 frontend, Hono API, Postgres with Prisma and Kysely, and typed requests end to end. A second command composes features into it: auth, billing, notifications, a mobile app, a browser extension. The code lands in your repo and you own every line of it.

npx @hype-stack/cli create my-app

Built on the open-source Hype Stack template. See it in action at hype-stack.dev.

Why this instead of a boilerplate

Boilerplates hand you one frozen snapshot. Hype Stack works like shadcn/ui, but for whole features: the CLI copies real source files into your project, runs codemods, merges the Prisma schema, and wires the routes. There is no runtime dependency on us and no npm version to be locked into. Delete what you don't like, rewrite what you do.

• Typed end to end. Backend routes in Hono become a typed frontend SDK through HyperFetch. Rename a field on the server and the frontend fails to compile.
• Pick your features. Feature packs cover auth with organizations, billing on Stripe, Lemon Squeezy, or Polar, notifications, a calendar, a whiteboard, an AI workspace, a newsletter, and more. Five of them are free. compose resolves their dependencies and installs them together.
• Every platform from one codebase. Web, admin panel, mobile app on Expo, desktop, and a browser extension.
• Deploys itself. hype-stack deploy ships to Railway or Fly.io, provisions Postgres, Valkey, and a storage bucket, sets env vars, and runs migrations.

Quick start

# Scaffold a new project
npx @hype-stack/cli create my-app

# Set up env vars and get the start command
cd my-app
npx @hype-stack/cli onboard

# Add features when you need them
npx @hype-stack/cli compose

Prefer starting from a finished app? Browse the templates and install one by id with npx @hype-stack/cli template <id>.

Commands

| Command | What it does | | ---------------------------------------------- | ------------------------------------------------------------------------------------------------- | | create [name] | Scaffold a new Hype Stack project from the template, install, and boot the databases | | onboard | Set up env vars and print the start command | | compose | Pick feature packs and install them into your project | | template <id> | Install a full template, with starter, layout, and billing swaps on top | | community init / validate / add / list | Build your own packs and install them from a folder, git, npm, or your own registry | | init | Initialize stack.json in an existing project | | deploy | Deploy web apps and the server, and provision Postgres, Valkey, and a bucket | | deploy mobile | Build (and optionally submit) the Expo app through EAS | | deploy extension | Build the browser extension and publish it to the Chrome, Edge, and Firefox stores | | mcp | Run the MCP server on stdio (what the editor configs launch) | | mcp install | Pick editors, create an API key in the browser, write their MCP configs, verify the server starts | | mcp check | Launch the server from an editor's config the way the editor would, and report why it fails | | login / logout | Authenticate to install packs your organization owns |

Every command has --help, and the deploy commands take --dry-run to print every step without creating anything.

What's in the stack

React 19, TanStack Router, Tailwind CSS v4, and shadcn/ui on the frontend. Hono on the backend with Prisma migrations, Kysely queries, Postgres, Valkey caching, and an in-process cron scheduler. Better Auth or WorkOS for sessions and organizations in the starters. Expo for mobile. Vite, pnpm 12, and oxc for tooling. The full breakdown is in the docs.

MCP server for AI editors

The CLI ships a Model Context Protocol server with eleven tools, so Cursor, Claude Code, Codex, VS Code, and other MCP clients can browse packs, scaffold, compose features, and boot the databases directly from the editor:

npx @hype-stack/cli@latest mcp install

It asks which editors, opens the browser once to create an API key for them, writes their configs, and starts the server once to confirm it comes up.

Links

• Website
• Documentation
• Feature packs
• Templates
• Pricing
• Blog
• Roadmap
• Template source on GitHub
• X / Twitter

License

The template and free packs are open source. Paid packs fund maintenance of the whole stack; see pricing for what each tier includes.