What you get
Every piece of the product, in plain words, so you know what is in the box before you open it.
The purchase is one folder. Everything described on this page is inside it, and none of it needs an account with anybody, because there is no service behind this product other than the ones you choose to connect.
The product, for your users
| Piece | What it is |
|---|---|
| Chat | A conversation with an assistant that can read the files in a project and write new ones. Every write is shown as a diff first |
| Code workbench | An editor, a preview, a terminal and a deploy panel beside the conversation, so a change can be read and shipped in one place |
| Projects | Folders of files with a name, a kind, a version history you can roll back, and an optional address to be published at |
| Library | Everything an account has made or uploaded: files, folders, pictures, with favourites, filters and a bin |
| Image generation | Prompt to picture, saved into the library like anything else |
| Memory | Things the assistant is asked to remember about a person, carried between conversations |
| Sharing | A public link for a picture or a file, at /i/..., that opens without signing in, with a download and a preview card |
| Teams | Seats bought with a plan, invitations, a shared view of what the team is doing |
| Credits and usage | Spend measured against the plan, as percentages rather than counters, with a weekly window |
| Billing | The plan, the upgrade path, the invoices, through whichever gateway you configure |
The marketing site, in the same app
The pages a visitor sees before they have an account are part of the same installation, not a separate project to host: landing page, pricing, enterprise, resources and legal. Their words come from the panel, so changing a headline is a form rather than a deployment.
Brand
Name, marks, colours, favicon, first-visit appearance, landing page words, email templates.
Content
Starter templates, library defaults, image rules, the legal pages, in-app notices.
Money
Plans, prices, what each plan unlocks, credits, payment gateways, invoices.
The panel
/admin is where the installation is configured. Eight groups, forty-four screens. It is protected by its
own sign-in at /admin-login, and every change made in it is written to an audit log with the name of the
person who made it.
Prop
Type
The accounts side, ready to use
Sign up and sign in with an email address and a password, optional Google and GitHub sign in, six-digit email confirmation that works once and expires in ten minutes, password reset, an onboarding questionnaire whose questions you choose, sessions you can end, and an audit log of every settings change.
The installer
Two ways in, one set of questions.
- One double-click:
setup.commandon macOS,setup.baton Windows,setup.shon Linux. A page opens in your browser and walks through it. - One command:
pnpm configure, which asks the same things in a terminal, supports--dry-run, and needs no packages installed first.
Both write only inside this folder, both keep a dated backup of the file they change, and both can leave any question for later. See Installing it.
What it is built with
Next.js 16 and React 19 on the App Router, Tailwind CSS v4, Motion for animation, shadcn/ui and Animate UI for the interface. Convex is the database, the functions and the scheduled work, with Better Auth for accounts and sessions. Models are reached through the Vercel AI SDK, so a provider is configuration rather than code. The editor is Monaco, the preview is a sandboxed frame, and the in-browser bundler is esbuild compiled to WebAssembly and run in a worker. Answers are parsed by Streamdown with KaTeX and Mermaid. Vitest is the test runner.
Why that list matters to you
Every name in it is mainstream and documented, which means you can hire for it, read about it, and get help with it. Nothing here is bespoke lock-in, and there is no framework of ours to learn.