Welcome to Automo Build

Describe the app you want. Automo Build builds it in real code, tests it, governs every change and deploys it.

Build your first appFrom a description to a running preview in one conversation.Learn the chatThe four things that happen every time you send a message.Publish itTake the app live, on your own domain, in one click.Read the FAQShort answers about ownership, data, plans and limits.

Automo Build turns a description into working software. You explain what you want in your own words and it plans the work, writes real React, TypeScript and Supabase code, tests it, and gives you somewhere to publish it, all inside one project.

There is no stack to choose and no setup checklist. If you can explain the app to a colleague, you can build it here.

What you can build

Automo Build is happiest with software that has screens, data and people:

Internal tools, dashboards and admin panels
Customer portals, booking flows and member areas
Marketplaces, directories and community sites
Small products with accounts, payments and email
Marketing sites that later grow into an app

If your idea needs someone to sign in, save something, pay for something or get notified, it belongs here.

One governed loop

Every project moves through the same loop: describe, plan, build, test, govern, deploy and monitor. The chat drives it, and QA, Security scanning, Guardrails and Doctor keep watch along the way.

The four ideas behind everything

Almost every screen in Automo Build is one of these four things. Once they click, the rest of the product feels obvious.

Account

Your account is you: your name, your email and the workspaces you belong to. One account can work across several workspaces, such as a personal one, your company's or a client's.

Workspace

A workspace is the shared home for a team. Projects, members, billing and integrations live inside it. If you are building for a company, the workspace is usually the company. If you are building alone, it is just yours.

Project

A project is one app. It has its own code, its own database, its own preview and its own address when you publish. A workspace can hold many projects, and they do not share data unless you ask them to.

Chat

Every change starts in a chat. You describe what you want, the builder may ask a question or two, then it makes the change and shows you the result. The chat is where the work happens, not a support widget.

Who it's for

Automo Build is built for people who know what software should do, but would rather not spend a week setting up a stack:

Founders and operators who need a real tool this month, not next quarter.
Designers and product people who want to see their idea working, not just clickable.
Engineers who want a first version or an internal tool without the boilerplate.
Agencies building for clients, with a separate workspace per client.
Teams and enterprises who need roles, approvals and an audit trail.

You do not need to write code. It helps to be able to read it, and the code is yours.

How to get help

You are rarely stuck for long. In order of speed:

Ask in the chat. The builder knows your project and can explain or undo what it did.
Search these docs with the box at the top, or press ⌘K anywhere on this site.
Check the Automo status page if something feels broken rather than wrong.
Read the FAQ for the questions that come up most.
Contact your workspace owner for anything about billing, plans or access.

Changes are saved as versions, so an earlier state of the project is always within reach. See Versions and restore.

Where to go next

Start with Signing in and setting up, then build your first project.

Connecting your own tools or agents? See Developers. The Automo Build MCP server is listed in the official MCP Registry as build.automo/automo-build.

Was this page helpful?

Next stepSigning in and setting up