Live at alpha.aios108.com
ALPHA Studio · Build
Type what to build. The agent builds it where you can see it.
ALPHA Studio is the live vibe-coding platform of the suite: you describe the app in words, the agent drafts and edits the work inside one bounded workspace, you review each change in a live preview, and you publish when it looks right. One-click publish, your approval at every consequential step.
Live now. Your workspace, your files, your approvals — nothing publishes without you.
How a build flows
Type, agent builds, one-click publish.
Three moves, same workspace throughout. Context never leaks across hidden tools, and every change waits for your review before it lands.
-
01 · Type
Describe the app in words
State the goal, the pages or flows you need, and what the app must not touch. Studio keeps that brief attached to the workspace so later edits stay in scope.
-
02 · Agent builds
Watch the work happen in the open
The agent plans, edits files, and runs the app inside your bounded workspace. You see proposed changes before they apply, and you can pause, redirect, or revert at any point.
-
03 · Publish
Preview, approve, one-click publish
Check the live preview, request revisions in plain language, then publish to your own domain when it is ready. Publishing is an explicit approval, never a side effect.
Capabilities
What Studio gives you.
One place to draft, run, review, and ship — with history that survives restarts.
-
Chat-to-app
From conversation to working app
Keep the whole build in one thread: requirements, revisions, and decisions stay attached to the workspace. Ask for a new page, a changed flow, or a simpler layout, and the agent proposes the edit for your review.
-
Live preview
See the app as it takes shape
A running preview sits beside the conversation, rebuilt from the workspace under review. What you see is what is proposed — nothing hidden, nothing simulated.
-
Your domain
Publish to your own domain
When the preview is right, publish the workspace to your own domain through an explicit approval step. Later revisions follow the same path: propose, preview, approve, publish.
-
Durable history
History that survives restarts
Conversation, file versions, previews, and publish decisions are kept with the workspace across sessions. Close the tab, come back later, and the context resumes where you left it.
Honesty note
Workspaces sleep when idle, wake on demand.
Studio workspaces rest when you step away so idle work does not consume shared capacity. Your files, conversation, and publish history are kept. When you return, the workspace wakes on demand and resumes from its kept state.
While a workspace sleeps, its public preview rests too. Publishing again after wake restores it under your control.
What stays yours
Studio never publishes, shares, or grants access on your behalf. Scope is per workspace and revocable at any time.
- File and tool access granted per workspace, revocable anytime
- Changes proposed first, applied only after your review
- Publish and domain steps held for explicit approval
- AutomationsTurn a finished Studio build into a repeatable step inside ALPHA Automations.
- ComputersEvery workspace runs on an isolated machine from ALPHA Computers — files kept, idle sleep, wake on demand.
- Research + AgentsGround decisions with ALPHA DeepResearcher and delegate scoped follow-through to ALPHA Agents.
Control commitments
Guardrails are part of the build loop.
Studio follows the same control-first rules as the whole suite. Read the philosophy for the full thesis.
-
01
Human in command
Edits are proposed before they apply. Publish, share, and domain steps wait for your explicit approval.
-
02
Contained by design
One bounded workspace per task with least-privilege access. Close the workspace and the work stops.
-
03
Auditable always
Proposals, approvals, previews, and publishes are recorded as they happen, so any outcome can be reconstructed.
Begin
Start building where it is live.
Open ALPHA Studio today, or request access to the wider suite when you are ready.