Command builder

Every choice below is a flare create flag. Pick what you want; the command updates as you do, and the defaults stay out of it — an app with default answers is one short line.

The command pins the exact version these docs describe. That is deliberate: pnpm holds new releases for 24 hours (minimumReleaseAge), so on a release day a bare pnpm create flare-framework runs an older CLI that may not know these flags. The pinned command always runs this one.

App name

Where will it run?

Next.js — Vercel, Postgres, Prisma 7 (default) Cloudflare — Workers, D1, Drizzle

Where do uploaded files go?

R2 — or any S3; MinIO locally (default) Disk — no account; one machine (Next.js only) Cloudinary — a CDN with an image pipeline UploadThing — a CDN with an uploader

Sign-in methods email & password is always on

Magic links Email codes Passkeys 2FA: authenticator app 2FA: email code

Social sign-in each needs its own credentials later

Google GitHub Apple Microsoft

Create itCopy

Then run itCopy

After it runs

The second block above is the whole setup: on Next.js it brings up Postgres, creates the tables and seeds admin@example.com / Password to sign in with; on Cloudflare there is nothing to provision at all. Then build something:

npx flare gen resource Contact --fields 'name:string, email:email!, status:enum(lead,customer)'
npx flare migrate           # create its table
npx flare seed:resource Contact 1000

Walk the same path with more explanation in the tutorials — a contact app on Next.js or on Cloudflare — or skim the quickstart. Every flag’s detail is in the CLI reference.

Nothing here is permanent except the stack: the theme, sign-in methods and storage driver are each one line to change in the app afterwards.