What Bookbag is
You describe an app in plain language. An AI agent builds it as a real, running Next.js application that you can read, change, publish and take with you.
Bookbag builds working applications from a description. You write what you want the way you would explain it to a person; an AI agent writes the code, runs it, and shows you the result while it happens. You then keep talking to it — "make the header smaller", "add a contact form" — until the app is what you wanted.
The product lives at app.bookbag.ai.
What you actually get
Not a prototype, a wireframe or a design mock-up. A real Next.js application:
- Next.js 14 with the App Router, React 18, Tailwind CSS 3.4
- Written in JavaScript, in ordinary files with ordinary names
- Running on a real development server, in its own isolated environment
- Yours to download as a zip at any moment, with no conditions
That last point is deliberate. An app you cannot take away is not an app you own. Every project has a Download source button that gives you the whole thing; unzip it, run npm install && npm run dev, and it works on your machine with no connection to Bookbag at all.
The four things Bookbag does that matter
You can read the code. Every project has a Code tab showing the real files. The builder is not a black box; you can check what it wrote before you ship it.
You can undo anything. Every file the builder creates, edits or deletes is recorded with its contents before and after. Any build can be rolled back — and the rollback is itself recorded, so an unwanted undo can be undone. See Version history.
You can bring your own AI. Add your own provider key under Account → AI and your builds run on it, billed by the provider, spending no Bookbag credits. Credits exist for people who would rather not hold a key; they are not the only way in. See Your own AI key.
You can check it before you ship it. A security check reads the generated source for the mistakes that actually cause harm — a live API key bundled into browser code, an admin page with no access check, a paid flag stored where any visitor can set it — and hands the findings to the builder as a fix. See The security check.
How the pieces fit together
Four words cover the whole product.
An organization is who you work with. Projects live in one. Everyone in an organization can see every project in it; what they can do depends on their role. You always have at least one — Bookbag creates a personal workspace for you the first time you sign in. See Organizations.
A project is one app. It has a name, a chat, a set of files, a history and, once you publish it, a public address. See Creating a project.
A build run is one attempt by the builder to change the app. You start one every time you send a message. It has a beginning, an end, a list of everything it did, and a record of every file it touched. See What a build run is.
A sandbox is where your app runs. One per project, created on the first build, with its own development server. See The sandbox.
What one session looks like
- You sign in at app.bookbag.ai. There is no password to remember here — Bookbag uses your shared Bookbag account.
- On the dashboard you type: "A booking page for a barber shop with services, time slots and a confirmation screen."
- A project is created and the first build starts immediately. The sandbox is set up — this is the slow part, a minute or two, and it only happens once per project.
- The preview comes alive. Files appear in the step list as the builder writes them.
- The builder finishes and writes you a short summary of what it built.
- You look at it and type: "The service list should be two columns on desktop." Another run, twenty seconds, done.
- You press Publish and your app is live at
https://app.bookbag.ai/p/your-address/.
What Bookbag is not
Being clear about this saves time.
- It is not a hosting platform for a back end. Publishing produces a static export. An app that needs a database or a server API can be built and previewed, but cannot be published from here. Download it and deploy it yourself.
- It is not a code editor. The Code tab is read-only, on purpose — a pane you could type into would race the builder's own writes. Changes go through the chat.
- It does not have a plan with features behind it. There are no tiers. Builds are paid for in credits, or in nothing at all if you bring your own AI key.
Where to go next
- Signing in — how the shared Bookbag account works.
- Your first app — a walk through one project, start to finish.
- A tour of the workspace — every screen and what is on it.