Packs & Templates
Packs and templates are how Hype Stack ships features. This section covers what each one needs before it will run: external accounts, environment variables, and OAuth callback URLs.
Packs
A pack is a single installable feature: a starter, a layout shell, or a drop-in like billing or a calendar. You compose
them with npx @hype-stack/cli compose. Each pack has its own page here with the exact setup steps, or a note saying
there are none.
| Pack | Category | Price | Needs |
|---|---|---|---|
| Auth Starter (Better Auth) | starter | Free | Resend, optional Google OAuth |
| SaaS Starter (Better Auth) | starter | Paid | Resend, optional Google OAuth |
| SaaS Starter (WorkOS) | starter | Paid | WorkOS, Resend |
| Layouts | layout | Basic is free, the other three paid | Nothing |
| Billing (Stripe) | feature | Paid | Stripe |
| Billing (Lemon Squeezy) | feature | Paid | Lemon Squeezy |
| Billing (Polar) | feature | Paid | Polar |
| Teams | feature | Free | Nothing |
| Projects | feature | Free | Nothing |
| Notifications | feature | Paid | Optional Resend |
| Calendar | feature | Paid | Nothing |
| Whiteboard | feature | Paid | Nothing |
| AI Chat (beta) | feature | Paid | OpenAI, a billing pack |
| Newsletter | feature | Paid | Resend, with its webhook |
| CRM (beta) | feature | Paid | Nothing |
| Cookie Consent | feature | Free | Nothing |
Every feature pack depends on a starter, any of the three. Billing is one slot: pick a provider, and swap it later with a family swap if you change your mind.
The admin app has its own page. It arrives with every starter and is what billing, notifications, newsletter, and AI chat extend.
Templates
A template is a curated bundle of packs plus a theme and extra pages. When you install a template, you still configure the services its packs depend on. Each template page lists which packs it pulls in and points you to the pack setup guides for the heavy lifting.
Build your own
The pack format is public. Build your own pack covers the manifest, the file strategies, and how to install from a folder, git, or npm. Run your own registry covers hosting and selling them.
What you'll find on each page
- External services the pack or template needs (WorkOS, Stripe, Resend, OpenAI, etc.) with a link to the provider dashboard.
- Environment variables you have to fill in.
onboardprompts for the same list. - OAuth callback URLs and webhook endpoints to register in the provider's dashboard, with the exact path.
- For packs with no external integration, a note saying exactly that.
Base services
Every Hype Stack app assumes Postgres, Valkey, and RustFS are running, plus Resend for email and optionally Sentry for
error reporting. These are wired by the base template, not by individual packs. create starts them for you; by hand,
run docker compose up -d from apps/backend.