How it works
From a workflow you can describe to an application you can run.
Follow a request-approval app from first description to running software. Some steps below are still being built.
- 1
Start from the workflow
You bring the thing your team actually does — "requests come in, someone approves, the requester is told." Start with the process — the data model comes out of it.
A plain-language description, a sketched definition, or a blank canvas in the visual editor.
- 2
Shape the app
Data, screens, and automations take form — drafted by AI, composed visually, or written as text files. Every path edits the same app definition.
request data · inbox + detail screens · approve automation
- 3
Validate and preview
Validation checks connections and references before anything runs. A preview deployment gives reviewers the real running app.
Validation report · preview deployment
- 4
Review and publish
Reviewers sign off on the changes to the app definition; publish creates a versioned release. Rolling back restores a prior definition.
Reviewed release · versioned app definition
- 5
Operate
Schedules run, credentials resolve, requests flow through. Iterating means drafting the next version — the live app keeps running.
Live app · scheduled automations · audit trail
The running result
A request desk like this is an illustrative concept — the data, automation, and screens shown are what the app definition produces, not a screenshot of a released product. Whether self-hosted or on the planned managed service, the app and its definition are the same.
- · Data: typed records with managed storage
- · Logic: a resumable automation per action, inspectable end to end
- · Interface: defined screens connected to the same model
data: request
| id | type | requester | state |
|---|---|---|---|
| REQ-1042 | Equipment | a.okafor | in_review |
| REQ-1041 | Access | m.silva | approved |
| REQ-1039 | Travel | j.larsen | draft |
- 1 Validate request
- 2 Route to approver
- 3 Record decision
- 4 Notify requester
automation · resumable · schedulable
Request inbox
Request detail
Approval form
screens · connected to data and automations
Where this stands today
Running underneath
The parts that run your data, screens, automations, API endpoints, schedules, and connected services already exist and run inside the platform's own operation.
Still being built
The visual editing experience, AI drafting, the review-and-release workflow, preview deployments, and self-serve onboarding are still being built. Early access exists to shape exactly these.