Choose your
components.

A different combination builds a different application. Select your services and watch the matching parts come together.

Your create command

bunx @0x0501/mystack@latest create my-app --yes --database pg-hyperdrive --deployment cloudflare --email cloudflare --payments stripe

Run this from the parent directory of your new project.

A configurable letterpress: the runtime drives it, the database sets the type, and the delivery and stamping fittings complete the workflow.

Your creation record

{
  "database": "pg-hyperdrive",
  "deployment": "cloudflare",
  "email": "cloudflare",
  "payments": [
    "stripe"
  ]
}

What connects
to what.

The website and CLI share the same catalog.
Compatibility is part of the configuration.

Supported database and runtime combinations
Database	Cloudflare	Nitro	Bun	Local development
PostgreSQL	—	Yes	Yes	Docker PostgreSQL
PostgreSQL + Hyperdrive	Yes	—	—	Docker PostgreSQL
Cloudflare D1	Yes	—	—	Wrangler local database
Turso Cloud	Yes	Yes	Yes	Local libSQL file or server
Turso Local	—	Yes	Yes	Local libSQL file
Bun SQLite	—	—	Yes	Native SQLite file

Email delivery.

Cloudflare Email requires the Cloudflare runtime. Resend works with all three runtimes. Development authentication email is logged when credentials are absent.

Payments, optional.

Select any subset of Stripe, Creem, NOWPayments and Polar. Each selected provider adds its own integration. Choose none when your application does not need payments.

Read the configuration reference

What connectsto what.

Email delivery.

Payments, optional.

What connects
to what.