Compose Your Stack

Packs are self-contained feature modules you install into an existing project. Each pack brings its own schema, routes, UI components, and migrations. The compose command lets you pick several at once and installs them in the right order.

Usage

npx @hype-stack/cli compose

This opens an interactive picker. Free packs install without an account. Paid packs you own are marked as owned; paid packs you don't own yet show their price and a lock.

For CI or scripts, pass the packs directly:

npx @hype-stack/cli compose --packs starter-saas-workos,pack-collaboration --yes

What happens during install

  1. Dependency resolution - any packs your selection depends on are pulled in and ordered automatically
  2. Validation - the whole plan is checked before a single file is written, so a bad install never leaves a half-modified project
  3. File install - schema, backend routes, and frontend pages are copied into the right places, in dependency order
  4. NPM install - every pack's dependencies are installed in one pass per workspace
  5. Codegen - you're prompted to run prisma generate and a migration for any new models
  6. Config update - stack.json records each installed pack

License keys

Paid packs need access. Log in once with your browser:

npx @hype-stack/cli login

Or pass a license key (handy for CI):

npx @hype-stack/cli compose --packs pack-billing-stripe --key <license-key>

Removing a pack

Packs are designed to be ejected. Once installed, the code lives in your project. Delete the files and revert the schema changes to remove a pack. The CLI doesn't automate removal, since most teams customize pack code after installing it.

Next

Run onboard to fill in the env vars your new packs need and set up the database.