Apps inside a project

A project is no longer one site. A single ESTAGE project can hold a Website, a Web app, and a Mobile app at the same time, and you switch between them from a switcher in the builder.

Build the marketing site, the customer portal, and the phone app once — on one set of data — without wiring three separate projects together by hand.

Each app is a real, separate build

Ask the AI to change something and it changes the app you have open. Nothing bleeds into the others.

Per app	What that means
Chat history	Each app has its own conversation with the AI
Files	Separate codebases — a Next.js app is not your website’s React build
Live preview	The preview follows the app you’re in
Pages list	Each app has its own routes and folders
Server	The Server tab shows that app’s machine, not the project’s main one
Publishing	Publish each app independently, on its own schedule

Inspector edits, version history, and settings all follow whichever app you have open.

What the apps share

The things that should be shared, are:

• The project’s CRM connection — one customer list, one product catalog, one set of orders behind all of them.
• Team members and their roles.
• The project’s domain — put each app on its own subdomain (app.mysite.com, store.mysite.com).
• The project’s cloud database — one backend, read and written by every app.

Adding an app

On the project, add the target you want — a Website, a Web app, or a Mobile app — and it appears in the switcher next to what you already have.

• Mobile apps require an account with mobile-builder access.
• Web apps are billed per app: dev hours while you build, and a dedicated machine once you publish.

Note

Creating a new project starts from a “What are you building?” chooser on the dashboard. Adding a second app to an existing project is the other route — same builder, one project.