MuseMVP Flare: from your laptop to Cloudflare, with nothing in between

MuseMVP now has three ways to ship. Next.js can run on Node, or on Workers through OpenNext. Flare is the third: TanStack Start builds into a Worker through Cloudflare's Vite plugin.

One less stack to assemble

A product with sign-in, files, AI and payments usually means another database, an object store, a model account, a queue and an email provider, then several sets of keys in the environment. Flare keeps those inside one Cloudflare account:

• One Worker exports fetch, queue and scheduled
• D1 holds users, sessions, the credit ledger and payment events
• R2 holds private files, and checks ownership before a read or a delete
• Workers AI streams text and summarizes documents, without a model-provider API key
• Queues run background jobs and move exhausted retries to a dead-letter queue
• Email Sending delivers sign-in codes; local development captures them at /dev/mail

Payment gateways, and Google or GitHub sign-in, stay outside. They are your merchant accounts and identity providers.

Run it on your machine first

pnpm install --frozen-lockfile
pnpm muse:init
pnpm dev

muse:init creates a local D1 database, generates AUTH_SECRET, and seeds [email protected] and [email protected]. That step needs no Cloudflare account and no Docker. Sign in at http://localhost:3000.

Workers AI has no local emulator. Real generation needs remote bindings turned on explicitly, or a deploy to your own account.

Look at the plan before you publish

pnpm muse:doctor --target production --json
pnpm muse:deploy --target production --plan --json
pnpm muse:deploy --target production --yes --json
pnpm muse:verify --target production --json

plan only reads remote resources and says whether the database, bucket and queues will be created or reused. It creates nothing. A pending migration containing DROP, TRUNCATE, DELETE or UPDATE SET blocks the automated deploy. --yes is what checks, builds, provisions, migrates, uploads secrets and publishes. verify smoke-checks public pages. It does not certify payments or mailbox delivery.

Provisioning, real mail, inference and merchant sandbox checks depend on your Cloudflare account and payment merchants.

Where the source lives

MuseMVP and All in One include the Flare repository plus the two existing Next.js apps. The UI Templates plan does not include Flare.

The product page is /web-musemvp-flare, the guides are at /docs/web-musemvp-flare, and the live demo is flare.musemvp.com.