Authentication
- Login & signup
- OAuth sign-in
- Sessions & password reset
No install, runs with npxThree ways in.
Three ways in.
All of them yours.
A bare repo, a finished template, or a stack you assemble feature by feature. Every line lands as source you own.
one command, six apps
the first minute
What actually happens when you run it.
1
You type one command
No account, no install. A short wizard with sane defaults.
$npx @hype-stack/cli create
2
It builds the workspace
One repo lands on your disk with six apps in it, already wired to each other.
3
Everything runs
One dev command starts the product, the admin and the API. Desktop, mobile and the extension build from the same code.
1commandno install, runs with npx
6apps in the repoweb, desktop, admin, api, mobile, extension
40sto first screenwired together already
How it starts
Three steps to start.
One command, a wizard you cannot answer wrong, and a running project. That is the entire learning curve.
01
Type one command
That's the entire setup surface. No dashboards, no setup lock-in.
template
$ npx @hype-stack/cli template
or
compose
$ npx @hype-stack/cli compose
works with npm, pnpm, bun
02
Answer the wizard
Arrow keys and space. Tick the features you want. It can't be done wrong.
hype-stack wizard
? Add features
space to toggle · enter to finish
- ◉Billing (Stripe)
- ◉Notifications
- ◯Collaboration
- ◯Basic Layoutfree
03
Open a running app
Frontend, backend, database, desktop, mobile, and extension builds, already talking to each other.
localhost:3000
Liveready in ~1 min
✓Frontend✓Backend✓Admin
What arrives
The command ends. Apps are running.
Real captures from a project the CLI scaffolds. Desktop, mobile and the extension land in the same repo beside them.
Your applocalhost:4200
Admin panellocalhost:4100
APIlivelocalhost:3000
methodroutestatustime
POST/auth/sign-in20014ms
GET/auth/session2003ms
GET/organizations2006ms
GET/organizations/acme/members2008ms
POST/invitations20121ms
GET/billing/plans2009ms
GET/notifications2005ms
PATCH/settings/profile20012ms
running on localhost
Deploy with one command.
Everything goes live on your own host, with the URLs, secrets, and migrations already wired between the services. No dashboards, no YAML.
Fly.ioRailwayyour account, either way
Stack progress
00 / 4 services
- ApplicationDeploying
- Admin PanelQueued
- APIQueued
- MobileQueued
my-app.com
Production/Fly.io
Deploying
Ownership
It lands on your computer. It stays yours.
App builders keep your product behind their dashboard and charge monthly to keep it alive. This puts a real codebase on your machine: no hidden costs, nothing to outgrow, and the hard engineering already done.
Like a pro
from minute one, with your AI agents
The app lands on your computer
own itReal source files in a real git repository. Open it in any editor, hand it to any developer, host it anywhere.
No rent on your own product
$0 / moBuilders charge monthly to keep your app alive. Here the core is free, packs are bought once, and running costs are whatever your hosting bills.
0
export buttons to beg for
Nothing to escape from later
walk anytimeAI no-code tools keep the code behind their dashboard. There is no cage here to export your way out of: the repo was yours from the first minute.
Do it today
already engineeredyour featuresBuilt to scale past the demo
you shipAuth, webhook retries, migrations, and CI are already engineered and tested. Your attention goes to features, not infrastructure.
1 min
From nothing to six apps
Clone, rename, install, run. All of it automated.
wiring it yourself2-3 monthshype-stack create1 min6 apps
Web, desktop, admin, API, mobile and extension
One repo, one dev command, already wired together.
createwebdesktopadminapimobileextension0 files
Written before you say yes
Compose plans the whole install and asks first.
plan · 47 fileswaits for yes
It asks, it plans, then it writes your files
A tool with write access to your codebase should be predictable. This one shows its work at every step.
you stay in control
You choose
compose
? Add features
◉ Billing (Stripe)
◉ Notifications
◯ Collaboration
◯ File uploads
Only what you tick gets installed. The bill never grows on its own.
already built
months
of engineering, already finished
auth + sessionsStripe billing + webhooksorgs + invitesadmin panelschema + migrations
Tick a pack. Weeks of engineering land as source in your repo.
nothing hidden
+47
files, every line is yours
Your team reviews it like any PR. Nothing lands outside the repo.
the math
3 min
for a feature that takes weeks to build
a developer builds billing2-3 weeks
compose installs the pack3 min
Buy the pack once instead of paying for weeks of development.
Type once.
Ship six apps.
$ npx @hype-stack/cli create
The install catalog
One command away. All of it yours.
Every card below lands in your repo as source code. Filter by category, or scan the whole list.
Billing
- Stripe checkout
- Subscriptions
- Payment webhooks
Customer portal
- Update payment cards
- Download invoices
- Cancel subscriptions
Database
- Local PostgreSQL
- Schema migrations
- Typed SQL queries
Emails & notifications
- Live notification inbox
- Emails via Resend
- Admin broadcasts
Admin panel
- Manage users
- Manage organizations
- Track revenue
Organizations
- Team workspaces
- Email invitations
- Member roles
Roles & permissions
- Role-based access
- API permission checks
- Permission-aware navigation
See it running
Templates are curated project starters built on this stack: a layout, feature packs, a custom theme, and bonus pages. The previews below are recordings of the real apps.
Questions, answered
Yes. Everything lands as plain source in your repository: frontend, backend, admin, database schema. There is no runtime dependency on us and nothing phones home.
Start with the free template. Decide later.
The core is public on GitHub and the first project costs nothing. Paid packs are a separate step, or never.
public core / free to start