# Tour Orbit Studio

Orbit Studio puts an app in five connected surfaces. Use each surface for one type of product work, while every surface changes the same app.

## Explore shapes the idea

Use **Explore** to keep notes, research, links, and possible product directions. Turn that material into a clear first scope before you build.

Explore helps you decide what belongs in the first version. It also keeps ideas that can wait for a later version.

## Mockup defines the pages

Use **Mockup** to see the app's pages side by side. Select a page element to change its content, size, style, or behavior.

The mockup connects interface elements to the data model. What you edit here becomes part of the app that Orbit deploys.

## Workflows define server actions

Use **Workflows** to describe what happens after an event. A workflow can run on the server when no browser tab is open.

Test a workflow step before you rely on it. Check its input, result, and any recorded error.

## Data model defines stored information

Use **Data model** to see tables, fields, rules, and links. Each Orbit app has its own Postgres database.

## Launch controls deployments

Use **Launch** to check and deploy the app. Check the deployment before you make the app available to users.

## Agent changes the same app

You can ask the Orbit Agent to make a change instead of editing each surface yourself. State the expected result. Name the relevant page, data, or workflow.

Orbit Studio is one entry point. You can also work through an MCP client such as Claude, through WhatsApp, or with the Orbit CLI.

Read the [Orbit product overview](https://orbitapps.io/) for current information about what Orbit builds, pricing, and how to start. Next, [build your first app](/get-started/build-your-first-app) or [understand the product lifecycle](/get-started/understand-the-product-lifecycle).