Hype StackHypeStack

Search

Search the packs, templates, docs, and pages

For people who ship before they hire

Vibe code it.
Then hand it over.

An agent can build your first version. The day somebody else opens it, this is a repo they read, not audit.

See what they inheritHow the agent stays in line
Shipped

A

the promise

Built by describing. Owned like code.

You describe the screen

"Plans and billing, with team seats." That sentence is the entire input.

The rails hold it

Auth, payments and the schema already exist, so the agent fills in screens instead of inventing architecture.

yourapp.com/billingShipped

It ships and holds

Real Stripe wiring, tested webhooks. Not a demo that dies the first busy week.

Handoff-ready

The day you hire, they open a repo they read, not audit: features in modules, tests beside code.

1sentence indescribe the screen
1screen shippedon a stack that holds
100%yoursrepo, database, host
The promise

Describe it once. Ship it.

Three asks from one build. Pick one to see the screen it produced.

04Yours
the packs behind these screens: 30 to 40 working days you are not building
The whiteboardShipped
The Mind Map template's board editor: sticky notes, shapes and ink on a shared canvas
The guardrails

Nothing breaks silently

A miss fails lint or typecheck in seconds, and the agent corrects itself instead of asking you what is wrong.

  • Briefed before it types

    The agent reads the house rules first, never guessing.

    Briefed by13 rule files

  • Sloppy work fails the build

    What used to be review comments are checks now.

    Enforced by4 rules at error

  • Mistakes die in seconds

    Lint, types and tests run while the agent works.

    TypeScriptViteston every edit

  • Expensive failures blocked

    The shortcuts that become outages are banned outright.

    TypeScriptno any
ninety seconds, unattended
  1. The agent rewires the billing screen0:00
  2. Typecheck fails0:04
  3. It reads the error and fixes its own change0:41
  4. Green. The change lands1:28

You were never asked. That is the point.

Four things you hold. One you never get.

We sell source code, not hosting. Stop paying us and your app keeps running.

See what they inherit
  • The code
  • The database
  • Where it runs
  • A platform bill if you leave

  • 1 day

    To a working first version

    The agent inherits auth, billing and admin instead of building them.

    the ask

    features land

    live

  • $0

    Platform bill when you ship

    An app builder bills while you build, then per user once you are live. Only ours ends.

    ai app buildermetered forever
    hype stackends at launch

  • 100%

    Of the code is yours to hand over

    The person you hire reads a normal repo, not an export.

    repo
    database
    host

Vibe code it.
Hand over a real repo.

your repoyour databaseyour host
The day you hire

Your agent writes it. A developer can read it.

When you do hire, you pay for features rather than a rewrite.

A real asset

A git repo, day one

Not an export. History, migrations and CI included.

  • apps/frontend
  • apps/backend
  • apps/admin
  • prisma/migrations
  • .github/workflows
Their first afternoon

Running in four commands

Clone it, install it, start it. Two more prove it is clean.

their first afternoon

$ git clone you/your-app

$ pnpm install

$ docker compose up -d

$ pnpm dev ✓ ready on localhost:4200

✓ pnpm lint and pnpm typecheck come back clean

Any host

Nothing to migrate off

A normal monorepo with Docker. No platform can hold it hostage.

Vercel
AWS
Fly
Your box
Familiar stack

Nothing clever to unlearn

Any React or Node developer is already qualified.

can work on this repomost of the market
can rescue an app-builder exportalmost nobody
PostgresReact 19HonoPrismaTanStackWorkOS / Better Auth
What you inherit

Built before your first prompt.

The agent inherits all of this instead of building it. It lands in your repo on day one, yours to keep.

Authentication

  • Login & signup
  • OAuth sign-in
  • Sessions & password reset
TypeScriptHono

Billing

  • Stripe checkout
  • Subscriptions
  • Payment webhooks
Stripe

Customer portal

  • Update payment cards
  • Download invoices
  • Cancel subscriptions
Stripe

Database

  • Local PostgreSQL
  • Schema migrations
  • Typed SQL queries
PostgreSQLPrismaKysely

Emails & notifications

  • Live notification inbox
  • Emails via Resend
  • Admin broadcasts
HyperFetchRedisResend

Admin panel

  • Manage users
  • Manage organizations
  • Track revenue
TypeScriptHono

Organizations

  • Team workspaces
  • Email invitations
  • Member roles
TypeScriptHono

Tenant isolation

  • Organization-scoped queries
  • Access checks on every route
HonoPrisma

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.

See all 6 templates

Two ways to install features

Same features underneath, different starting point. Either command resolves what the packs depend on, copies the source into your repository, and merges the database schema.

Ready-made

Take a template

A landing page, a design system, a themed layout, and the features already wired into it. Rebrand it, put your product in the middle, ship.

Browse templates
From scratch

$ hype-stack compose

✓ Auth✓ Billing✓ Teams✓ AI

Compose your own design

Your design and your choices, without rebuilding auth, billing, or notifications. Tick the packs you want and the CLI wires them into the open-source starter.

Browse packs

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.

Build it yourself. Keep the asset.

Build your first version on it. Hand over something a developer will thank you for.

Start buildingSee pricing

your repo / your database / your host