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: auth, billing, notifications, collaboration, or a layout shell. You compose them
with the npx @hype-stack/cli compose CLI. Each pack that needs a third-party service has its own page here with the
exact setup steps.
Layout packs (layout-basic, layout-native-app-shell) are frontend-only shells that depend on a starter for auth, so
they don't need their own setup guide.
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.
What you'll find on each page
- External services the pack or template needs (WorkOS, Better Auth, Stripe, Resend, etc.) with a link to the provider dashboard.
- Environment variables you have to fill in.
- OAuth callback URLs 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 and Valkey (Redis) are running, plus Sentry for error reporting. These are wired
by the base template, not by individual packs. Start them with docker compose up -d from apps/backend.
Every purchase and sponsorship funds my 8+ years of work on open source given freely to the community. It keeps the lights on, funds new packs, and keeps the ecosystem alive. Even a small tier means a lot. Thank you!