Rocketflare is a ready-made web app you copy and make your own. Out of the box it has sign-in, teams and permissions, an AI assistant that can read your documents, dashboards, a command-line tool, and a clean way to run background jobs — all on Cloudflare, over a normal Postgres database. Run it on your laptop in a couple of minutes; deploy it when you're ready.
One Cloudflare Worker · Hono · React · Postgres · MIT
Run one script, ask your coding agent, or do it by hand. All three end in the same place: your browser, signed in.
Help me set up this project
Reading CLAUDE.md, then running the first-run script. Here is what it did:
You're signed in as the demo owner. Try Chat, Agents, Knowledge or Analytics.
curl -fsSL https://rocketflare.dev/install.sh | bash -s -- myapp1/10 toolchain2/10 install3/10 secrets4/10 database5/10 migrate6/10 plugins installed analytics; tables generated and migrated7/10 seed8/10 cloudflare9/10 cli10/10 runready http://localhost:3000/login?as=owner%40example.testThe installer clones it, makes the history yours from the first commit, and starts the bootstrap.
Ten checked steps: toolchain, database, migrations, plugins, demo data. Or ask your agent.
http://localhost:3000, signed in as the demo owner.
The parts every app needs and nobody wants to build twice — finished, tested, and already on the screen.
pnpm cli login --server http://localhost:3001Opening the browser… signed in. Key stored in ~/.rocketflare/config.jsonpnpm cli whoamiuser owner@example.testtenant Acme Logistics (acme)key rocketflare_Of8D…pnpm cli members list --json | jq '.items[].email'"owner@example.test""marcus.adeyemi@acme.example"…Everything the app does in the browser it also does from the terminal — same routes, same rules, one API key.
--json, so the output pipes into jq — or straight into a coding agent's hands.Each of these has its own page among the sixteen concepts, with the reasoning behind it.
One Worker, one router, one database, one contract package — and every choice written down among the sixteen concepts so you can disagree with it on purpose.
Three things worth knowing, so nothing surprises you.
Before you spend an evening on it — what it costs, what it does not do, and who it is for.
A free, open-source web app you copy and make your own. Sign-in, organisations, teams and permissions, an AI assistant that answers from your own documents, dashboards, file uploads and background jobs are already built and tested. You add the product. It runs as one Cloudflare Worker over a normal Postgres database, under the MIT licence.
You need to be comfortable running commands in a terminal, and you will be editing code eventually — this is a codebase, not a no-code builder. You do not need to know Cloudflare, Postgres or any of the libraries beforehand. The repository is written to be driven by a coding agent such as Claude Code: open the folder, type /rf-setup, and it does the setup, the rename and the deploy for you, showing each step as it goes.
The kit is free. Running it on your laptop costs nothing at all. Deploying it costs the Cloudflare Workers Paid plan, because the database connection pool and the workflows the agents run on are paid features, plus a Postgres database — a free Neon tier is enough to start. The built-in AI is billed per call to your own Cloudflare account, with a free daily allowance, and you can switch it off or bring your own key.
Yes. It is MIT licensed: build a product on it, charge for that product, keep your changes private, and you owe nothing and need not credit anyone. Take a copy, cut it loose from the original history, and it is your codebase.
To run it on your laptop, a free one — and only because the built-in AI runs on Cloudflare, so the first start asks you to log in. Run the bootstrap with --offline and no account is needed at all; chat and agents then wait for an AI key of your own. Deploying needs a Workers Paid plan.
Both, from the same database. One setting switches between many organisations, each with its own members and roles, and a single organisation that everyone joins. You can change your mind later without touching the data or running a migration.
Billing and subscriptions are the big one — there is no Stripe integration, no plans and no metering of your customers. There is also no marketing site, no blog or CMS, and no mobile app. What is included is the platform underneath a product: tenancy, sign-in, roles, files, email, background jobs, realtime, dashboards, an AI layer and a command-line tool.
Three things. Multi-tenancy is the foundation rather than an add-on, so every row belongs to an organisation and the tests fail if one does not. The AI layer — chat, agents and search over your own documents — is built in and works on a fresh copy with no API key. And a copy keeps a link home: when the kit gains a release, one command ports it into your renamed app without recreating anything you deleted, so starting from a template does not mean falling behind it.
As many as you have ideas. Copy the kit once per product: each copy is renamed to its own app, deploys on its own, and keeps taking the kit’s releases and plugins, so the tenth product starts as current as the first. One kit and a coding agent, turning out SaaS products for as long as you keep having ideas: an infinite SaaS factory rather than a one-off template.
The kit is written to be worked on by a coding agent: a map at the root of the repository, rules that load with the files they apply to, a guide in every important folder, and one test gate that enforces them. Ask the agent to set up, rename or deploy the project and it follows the same steps a person would, showing each result as it goes.
Your first commit can be a feature — and your next product starts the same way.