Start Here

NeoBuild is an AI-assisted app builder for founders, SMEs, agencies, and product teams. You describe the app you want; NeoBuild generates a React (Vite) project, builds it in the cloud, and gives you a live preview you can click through.

You keep ownership throughout: export the code as a ZIP, push and pull with GitHub, connect a Supabase database in your own account, and publish to your own domain.

What it is good at

• Business and operations apps — inventory, quotations, approvals, client portals, CRM-lite
• Internal tools where the process is specific to how you work
• Getting a working, data-backed app in front of people quickly

What it is not

• A native iOS or Android app builder — NeoBuild generates web apps
• A drag-and-drop visual canvas; you describe changes in words
• A replacement for a developer on a large, long-lived product

1. Sign in at neobuild.dev.
2. Write a focused first prompt — one screen or one workflow, not the whole product.
3. Wait while NeoBuild generates the files, installs packages, builds, and starts the preview. The first build takes longest because packages are installed from scratch.
4. Click through the result, and check the mobile layout as well as desktop.
5. Send one follow-up prompt at a time, reviewing after each.

You do not need a database to start. Build and preview first, then connect Supabase when the app needs to store real records — see Integrations & Ownership.

Build an assistant that customers can ask about your products by voice. For example, a supplier can use its catalogue to answer specification questions and its manuals to explain installation, showing the document and page behind each answer.

Choose this example under Try a starting point in the IDE, or paste the prompt into the composer. Review it before sending. If Plan mode is available on your plan, use it to review the scope before approving the build.

Build the workflow

1. Connect Supabase. Store documents privately and save agent settings and conversations in your app’s database.
2. Add an admin upload page. Let authorized staff upload catalogues and manuals, see Processing, Ready or Failed status, and choose which documents each agent can use.
3. Make the documents searchable. Extract text, including OCR for scanned pages, and preserve document names, versions and page references. Process uploads in the background.
4. Add push-to-talk. Record a question, transcribe it, find relevant passages in the selected documents, generate an answer, then play the spoken reply. Show sources alongside the text.
5. Define memory. Keep recent conversation context for follow-up questions. If customers should resume later, add sign-in, saved conversations and a delete option. Ask before saving personal preferences.

Check the result before publishing

• Upload a short manual through the generated app’s admin page and wait for Ready. An attachment in the IDE build conversation does not automatically become agent knowledge.
• Ask a question answered on a known page. Check the reply, spoken audio and page reference.
• Ask “What about that model’s installation?” and check that the agent follows the conversation.
• Ask something the documents do not answer. The agent should say it cannot find supporting information.
• Check that users can access only their permitted documents and conversations, and that removing a document excludes it from future answers.

For larger catalogues, ask NeoBuild to index documents when they change and retrieve only relevant passages per question. Use live product records for current prices and stock. Supabase Realtime can show processing updates; simultaneous voice conversations also depend on your configured gateway and provider limits.

• Chat panel stores prompts and generated responses.
• Preview panel runs the built app.
• Version selector switches between v0, v1, v2, and repair versions.
• Tools menu handles publish, upload, download, env vars, build history, and token usage.
• GitHub panel manages push, pull, and two-way sync.

The composer has three modes. Two of them change nothing — that is the point of them. If you only remember one thing: Agent builds, Ask explains, Plan proposes.

Agent — the default. Builds.

Writes files, creates a new version and runs a preview build. Use it when you know what you want changed.

Ask — read-only. Explains.

Answers questions about how your project works, reviews code and diagnoses problems. It never drafts a plan and never edits anything. Use it when you want to understand something before touching it — "why does the login redirect twice?"

Plan — read-only. Proposes.

Drafts an implementation plan for you to approve. Nothing changes until you press Approve & Build, which runs the plan in Agent mode. Use it for anything large enough that you want to see the shape of the work first.

Ask or Plan?

They feel similar because neither one changes your app, but they answer different questions. Ask answers "how does this work / what is wrong?" and stops there. Plan answers "what would you do about it?" and ends with something you can approve. If you want to understand, use Ask. If you have decided to act and want the steps first, use Plan.