Describe a resource once. Flare writes the table, the API, the validation and the admin screens, with auth, storage and billing already wired — then ships it to Cloudflare Workers or to Vercel, from the same description.
npm create flare-framework@latest my-apppnpm create flare-framework my-appbun create flare-framework my-appcurl -fsSL https://flare-docs.codetotech.com/install.sh | bashirm https://flare-docs.codetotech.com/install.ps1 | iexPaste this into Claude, Cursor, Codex or any coding agent →
import { defineResource, field } from "@flaredev/core";
export default defineResource({
name: "Contact",
fields: {
name: field.string(),
email: field.string({ format: "email" }),
phone: field.string({ required: false }),
status: field.enum(["lead", "customer"]),
},
});Edit the descriptor and run it again: every file follows, and your own code outside the generated blocks is kept.
[ how it works ] Layers
The descriptor is the only thing you write. Each layer below is real code in your repository, generated from it and kept in step with it.
app/dashboard/contacts/*app/api/contacts/route.tsresources/contact.validators.tsdb/schema/contacts.ts[ pick one ] Stacks
Your resources, hooks, policies, seeds and every component are the same on both. What changes is the database, the ORM and where it deploys — so pick for the database, because that is the part you cannot move in an afternoon.
Cheapest to run, everywhere at once.
A Worker runs in every Cloudflare location without you arranging it, and R2 charges nothing to serve what it stores. The trade is SQLite rather than Postgres, and a runtime that is not Node.
pnpm create flare-framework my-appReal Postgres, real Node.
Extensions, window functions and ranked full-text search; any npm package that assumes Node; preview deployments. It costs more, and realtime has no equivalent here.
pnpm create flare-framework my-app -- --stack nextCompare them properly — including what each one cannot do.
[ 01 / 05 ] Create
flare create gives you a working app with sign-in, a database, an admin area and the Cloudflare bindings behind them, already connected. No choosing libraries, no glue code.
[ 02 / 05 ] Look
Pick one when you create the app, switch with flare theme mono, or set FLARE_THEME. Sign-in, dashboard, admin and home page all follow: colours, type, button shapes and even the sign-in layout.
Calm and centred, indigo accents. flare create my-app --theme default
Warm and rounded, sign-in as a card over the page. flare create my-app --theme coral
Plain and direct, boxed forms with pill buttons. flare create my-app --theme amber
Crisp blue, bold headings, social sign-in first. flare create my-app --theme sky
Black and white on a fine grid. flare create my-app --theme mono
Fresh green, sign-in beside a customer quote. flare create my-app --theme emerald
[ 03 / 05 ] Secure
flare create asks which to switch on. Each has its screens, emails and account settings, and a method you switch off is refused by the API, not just hidden.
[ 04 / 05 ] Generate
Each generator writes plain, readable files into your project. Change them, or regenerate: Flare keeps your edits and tells you when something drifted.
A table, an API, validation and admin screens for any record your app keeps.
Read the guidenpx flare gen resource Deal --fields "title:string, value:int, stage:enum(lead,won,lost), company:belongsTo(Company)"Decide who reads, creates, updates and deletes. The API and the admin both obey it.
Read the guidenpx flare gen policy Deal --roles admin,staff --delete-roles adminStripe Checkout, the customer portal, plan changes and a verified webhook.
Read the guidenpx flare gen billing --provider stripe --mode subscriptionsBans, rate limits and abuse detection in front of every request, with a dashboard.
Read the guidenpx flare gen securityAnd the code you write stays small
import { defineResource, field } from "@flaredev/core";
export default defineResource({ name: "Deal", fields: { title: field.string(), value: field.int({ min: 0 }), stage: field.radio(["lead", "won", "lost"]), contact: field.email({ required: false }), companyId: field.belongsTo("Company"), },});import { definePolicy } from "@flaredev/core";
// The API and the admin both enforce this.export default definePolicy({ resource: "Deal", read: ["*"], // any signed-in user create: ["admin", "staff"], update: ["admin", "staff"], delete: ["admin"],});import { desc, gt } from "drizzle-orm";import { getDb } from "@/db";import { deals } from "@/db/schema";
// Relations come from db/relations.ts, which flare gen keeps up to date.const recent = await getDb().query.deals.findMany({ where: gt(deals.value, 1000), with: { company: true }, orderBy: [desc(deals.createdAt)], limit: 10,});import { dealClient } from "@/resources/deal.client";
// Typed from the descriptor: stage is "lead" | "won" | "lost".const { data, meta } = await dealClient.list({ sort: "-value", filter: { stage: "won" } });
await dealClient.create({ title: "Renewal", value: 4200, stage: "lead", companyId });[ 05 / 05 ] Ship
flare deploy migrates the database first, deploys the Worker, then sets any secret you're missing — nothing to configure on the dashboard. On the Next.js stack the same command runs the Vercel CLI.
npx flare deployflare create to a deployed app that signs users up and serves its API, timed end to end on a fresh app.Put the app on your machine on a public HTTPS link. No account, DNS or open ports.
npx flare dev --tunnelSharing your local appEvery app serves an OpenAPI reference of its own API, filtered to what each role may call.
API reference (OpenAPI)Flare is at 0.x: the generators, auth, admin and deploy are tested end to end on every release, but APIs can still change between minor versions. Pin your version and read the changelog before upgrading.
No. flare dev and flare start run everything locally, D1, R2, KV and Durable Objects included. You only need an account for flare deploy.
Yes. Generated code lives inside marked blocks; everything outside them is yours and is never touched. Flare also tells you when you've edited inside a block, instead of overwriting it.
It runs vinext, Cloudflare's Next.js-compatible framework, on Workers. Flare adds what a Next.js app leaves to you: database, auth, admin, API, roles, billing and security, generated and wired together.
Any time: flare theme <name>, or FLARE_THEME in .env. Every screen follows, the admin included.