App Studio

Describe the app you need. The studio plans it with you, builds it piece by piece, tests each piece, and shows it working beside the conversation - on a copy of the data until you publish.

The eight studios About App Studio

What it is for

A plan before a build: The studio answers a description with a plan you can read and change. Building starts when you agree to it.
Built piece by piece: The work is split into items. Each one is implemented, reviewed against what you asked for, and applied as a version of its own - so nothing is ever redone, and a stopped build resumes where it stopped.
Tests are part of the app: Tests are written beside the screens and run after every change. A failure gets a repair before you see it.
Drafts never touch real data: A draft works on a staging copy with sampled rows. The shape of production data moves only when you publish.
An app is a citizen of the platform: It runs in a sandbox and asks Divan for what it declared: lists, processes, charts, flows, agents. Its access is the platform's access, not its own invention.
Your choice of engine: Builds run on Claude Code, Codex or Gemini on a runner you host, with an API key or a vendor account.

Getting started

Open App Studio and describe the app in a sentence or two. Attach a sketch or a spreadsheet if you have one.
Read the plan. Change what does not fit, then let it build.
Try the app in the preview. Publish when it does what you asked.

Tasks

Change an app that is in use

Open the app in App Studio.
Say what should change.
The change is built as a draft on staging data; people keep the published version until you publish again.

Start from a template

Open the template gallery.
Choose a ready app.
It is created with its lists, screens and tests - then it is yours to change.

Put an app in a site

Open the site.
Add the app.
Its lists, processes, reports and documents arrive with it.

Questions

Who may publish an app?

Its owner. The app's identity - name, icon, who may open it - lives with the app, and publishing is its owner's decision.

Can an app reach other systems?

Through what the platform offers: a flow in Orchestration Studio, a connector, a credential used from the Vault. The app never holds a secret.

What happens to a build when the server restarts?

It resumes. Finished items stay finished; the queue goes on with the next one.

Sites: A site is where a team's application is born.
Process Studio: Business processes: model them, run them, work them.
Data Studio: Business intelligence on governed data.
Agent Studio: AI agents that work as staff - and wait for people.
Game Studio: Games for a break, a colleague, or a whole meeting.