Ship your product.
Not the platform.

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

Get it running See what's inside

What it looks like

The Home page of a Rocketflare app, signed in as Olivia Bennett, owner of the demo organisation Acme Logistics The Home page of a Rocketflare app, signed in as Olivia Bennett, owner of the demo organisation Acme Logistics
This is the first thing you see: signed in, with a demo organisation already there.
For builders

Running in about two minutes

Run one script, ask your coding agent, or do it by hand. All three end in the same place: your browser, signed in.

  1. You

    Help me set up this project

  2. Claude Code

    Reading CLAUDE.md, then running the first-run script. Here is what it did:

    • Checked Node 24, pnpm and Docker, and installed what was missing
    • Installed the dependencies
    • Wrote the local secrets file with a fresh encryption key
    • Started Postgres in Docker
    • Created the database schema
    • Seeded a demo organisation with people, documents and activity
    • Checked the free Cloudflare login the built-in AI needs (or turned that off with --offline)
    • Signed the command-line tool in
    • Started the app on :3000 and the API on :3001
  3. Claude Code

    You're signed in as the demo owner. Try Chat, Agents, Knowledge or Analytics.

zsh 
curl -fsSL https://rocketflare.dev/install.sh | bash -s -- myapp1/9 toolchain2/9 install3/9 secrets4/9 database5/9 migrate6/9 seed7/9 cloudflare8/9 cli9/9 runready  http://localhost:3000/login?as=owner%40example.test
Opens http://localhost:3000, signed in
  1. Get a copy 10 s

    The installer clones it, makes the history yours from the first commit, and starts the bootstrap.

  2. Bootstrap 2–3 min

    Nine checked steps: toolchain, database, migrations, demo data. Or ask your agent.

  3. You're in now

    http://localhost:3000, signed in as the demo owner.

Every path, step by step

Out of the box

What it does

The parts every app needs and nobody wants to build twice — finished, tested, and already on the screen.

The People page: members with their roles and a pending invitation The People page: members with their roles and a pending invitation

People and sign-in

  • Sign in with a link in your email, or with Google, Microsoft or any other single sign-on provider.
  • Owners, admins and members — one rule decides what a page shows and what the server allows.
  • Invite people; the list updates live in every open browser.
An agent run: the timeline of steps and the finished summary An agent run: the timeline of steps and the finished summary

An assistant and agents

  • Chat that streams answers and remembers the thread.
  • Agents that run long tasks in the background and show their steps as they go.
  • Drop in PDFs and documents; search them by meaning and let the assistant cite them.
The Organisation Overview dashboard with live member and activity numbers The Organisation Overview dashboard with live member and activity numbers

Dashboards

  • An organisation overview on day one, with live numbers.
  • Build your own pages from the same data, no SQL required.
  • Every AI call is recorded with what it cost, before Cloudflare sends the bill.
your terminal 
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"…
For builders Also on the command line

A CLI your agents will love

Everything the app does in the browser it also does from the terminal — same routes, same rules, one API key.

  • Log in once from the terminal; it opens the browser, then keeps a key for your organisation.
  • List people, keys and activity. Every command takes --json, so the output pipes into jq — or straight into a coding agent's hands.
  • Add a command for your own feature in three files; the server, the browser and the CLI share one contract, so they cannot drift apart.
Behind it: the CLI concept →

Also included

Each of these has its own page among the thirteen concepts, with the reasoning behind it.

Under the hood

Boring choices, made once

One Worker, one router, one database, one contract package — and every choice written down among the thirteen concepts so you can disagree with it on purpose.

  1. BrowserReact, served by the Worker
  2. one WorkerHono · React
  3. PostgresNeon via Hyperdrive
  • Queues
  • Workflows
  • Durable Objects
  • R2
  • KV
  • Workers AI

Read the concepts

I want to ship a product

  • You have an idea and a customer, and no wish to build sign-in again.
  • You work with a coding agent and want it to know its way around from the first session.
  • You want to deploy on a Sunday and not think about it on Monday.
Start here

I want to read the design

  • You want to know how organisations stay apart in one database, and what enforces it.
  • You want to see how long work, realtime and AI fit on Cloudflare without a second service.
  • You would rather disagree with a written decision than guess at an unwritten one.
Every decision, with its reasons

More on who it's for

Before you start

Three things worth knowing, so nothing surprises you.

Everything above is already written.

Your first commit can be a feature.

Get started GitHub