A name and a sentence or two
Give the app a name and say what it should do. It opens in the editor with the assistant ready.
New · Part of Pro Max
Describe the app you need. Get a working one.
Tell the AI assistant what the app should do, in plain English. It builds the screens, the logic, and the database tables. The preview beside the chat is the real running app, so you click through it as your users will.
Product video · 2:00
Every new app starts with sign-in, its own database, email, file uploads, and payments already built.
Inside AppBuilder
See AppBuilder in action.
The editor at work on a sample app called Home Bills: ask for a screen in chat, click a heading to change it, and look at what the app has saved.
Build by chat
Edit on canvas
Data tab
Product facts
The product facts before you begin.
- Membership
- Part of Pro Max
- You bring
- A description in plain English
- You get
- A working web application
- Built as
- A standard Next.js app you can download
- Goes live
- At its own address, hosting included
Email sending works once you add a Resend key. Stripe payments work once you add your Stripe key. Everything else is ready when the app is created.
5parts built into every new app
7tabs over the preview
2databases per app: test and live
1button to publish
From a description to a published app
Say what it should do. Use it. Publish it.
AppBuilder does not hand you a mock-up. The assistant writes a standard Next.js application, and you use the real thing while it is being built.
Screens, logic, and database tables
Ask for a screen, a form, a rule, or a report. The assistant writes the code, adds any database tables it needs, and updates the running app.
The preview is the real app
Links, forms, and sign-in all work. Sign up, add a record, and see it saved.
One button, its own address
Publishing builds the app and puts it online with hosting included. A failed publish never replaces the live app.
What every new app starts with
The parts every app needs are already built.
An application needs accounts, a place to keep data, email, uploads, and a way to get paid. Each new app has these built and tested, so the assistant spends its time on your idea.
Sign up, sign in, sign out, and forgot password.
Accounts are stored in the app’s own database. Ask for a screen that needs sign-in and the assistant uses the built-in login, so each person sees their own records.
Its own PostgreSQL database.
The assistant adds tables as the app grows. You never set up or manage a server.
Email, ready to switch on.
Apps can send email such as password resets and notices. It works once you add your Resend key in Secrets.
Uploads and downloads.
Apps can accept and serve uploaded files, so documents and pictures live in the app they belong to.
Stripe payments, ready to switch on.
Apps can take payments through Stripe once you add your Stripe key in Secrets. The money goes to your own Stripe account.
Three ways to change the app
Describe it. Click it. Open the code.
Use chat for the big steps and your own hands for the small ones. Every change, yours or the assistant’s, can be undone.
See how it worksTell it what to build.
Describe a screen, a form, a rule, or a report. Add a screenshot or a sketch to your message and the assistant uses it as a reference.
Click anything to change it.
Turn the switch on, then click any element to restyle it in the Style Editor, double-click to edit text, or send the element to the assistant. Turn it off to use the app again.
Open the code.
A file tree and a code editor. Create, rename, copy, move, and delete files, or drop files in from your computer. Download the whole app’s code as a ZIP.
Your data
Build with test data. Run on live data.
What you enter while building goes to a test database. The published app has its own live database, so your experiments never touch your customers’ records.
Two databases per app.
One for building, one for real use. Switch between them in the Data tab.
Look without touching.
See every table and its rows. The Data tab is view only, so looking can never change anything.
Find a row. Export a table.
Search a table’s rows, or download a table as a CSV file that opens in a spreadsheet.
Keys stay out of the chat.
Add keys in the Secrets tab, with separate Preview and Production values. In the Data tab, columns that hold secrets are shown as dots.
GitHub
Save it to GitHub. Bring it in from GitHub.
Connect your GitHub account once and every app you build can use it. Keep each app’s code in a private repository, or import a Next.js app you already have. Your secrets and the data people enter are never sent.
Keep the code on GitHub.
Create a private repository for the app in one click, or pick one you already have. Push sends the app’s code to its main branch as one commit.
Bring changes back in.
Pull brings changes made on GitHub into the app as one History step. Undo takes the whole step back.
Nothing is merged behind your back.
If the app and GitHub have both changed, you choose which side wins. Neither choice erases GitHub’s history.
Import an app you already have.
Pick a repository on the dashboard. A check answers in seconds: ready, needs some work (with the list), or cannot be imported (with the reason). We bring your code in and tell you what it needs to run here.
When something goes wrong
A wrong turn costs one click.
Building software means trying things. AppBuilder keeps a way back from every change, and tells you plainly when something fails.
See how it worksSend the error in one click.
When a screen errors, a bar shows the message with a Fix this button. One click sends the error to the assistant.
Step back through every change.
Undo and redo cover every change, whether you or the assistant made it.
Go back to any earlier point.
Return the app to an earlier point. The later changes are kept, so you can come forward again.
See every publish.
A list of every publish: when it happened, whether it worked and, if it failed, why.
Going live
Publish with one button. Hosting is included.
The app goes online at its own address, with its own live database. There is no hosting account or server to set up.
See how it worksOne button
Publishing builds the app and puts it online. Hosting is included.
Its own address, or your domain
Each app gets a web address when it is published. You can connect a domain you own.
A failed publish changes nothing
A failed publish never replaces the live app. The Deployments tab shows why it failed.
Pages, or an application?
PageBuilder builds pages and websites. AppBuilder builds applications people sign in to.
For a landing page, a funnel, or a company website, start with PageBuilder.gg. For a tool with accounts and saved data, such as a client portal, a booking tool, or an internal tracker, use AppBuilder.
Feature Atlas · AppBuilder
See every AppBuilder feature—and what each one gets you.
Browse every AppBuilder feature, see exactly where it lives in the app, and find the one that moves your business forward today.
Explore the AppBuilder atlas 45 features across 10 areas
Part of Scale.gg Pro Max
Describe it. Use it. Publish it.
AppBuilder gives your idea a working application with sign-in, a database, email, file uploads, and payments from the first minute. You change it by chat, by clicking, or in the code, then publish it to its own address.
Straight answers
What to know before you build in AppBuilder.
What is AppBuilder?
AppBuilder is a Scale.gg product that turns a plain-English description into a working web application. It is part of Pro Max.
What does every new app start with?
Sign-in, its own PostgreSQL database, email sending, file uploads, and Stripe payments. Email works once you add a Resend key, and payments work once you add your Stripe key.
Is the preview a mock-up?
No. The preview beside the chat is the real running app. Links, forms, and sign-in all work, so you click through it as your users will.
Will my test data reach the published app?
No. What you enter while building goes to a test database. The published app has its own live database.
Can I change things without using chat?
Yes. Turn on Edit on canvas to click any element and restyle it or edit its text, or open the Files tab and change the code.
Can I keep the code?
Yes. Each app is a standard Next.js application. You can download all of its code as a ZIP file, or keep it in a private GitHub repository and push to it from the GitHub tab.
Can I import an app I already have?
Yes, from GitHub. It needs to be one Next.js application, version 14 or newer, that uses the App Router and TypeScript, has package.json at the top level, and installs with npm, with up to 1,500 code files and none larger than 500 KB. A check tells you in seconds whether it is ready, needs some work, or cannot be imported. An app built elsewhere usually needs a few changes before everything runs here, such as its database, its sign-in, and its keys.
How is AppBuilder different from PageBuilder?
PageBuilder builds pages and websites. AppBuilder builds applications people sign in to.
Where does a published app live?
At its own address, with hosting included. You can also connect a domain you own. A failed publish never replaces the live app.