Compute
Configure your Compute account
Set up the smallest account that runs your first workflow, then add advanced resources only when a workflow needs them. Every change is planned, reviewed, applied and read back.
Configure only what your workflow needs
Compute does not ask you to build a workflow before you can use it. You choose a workflow that already exists, then configure the few resources it requires.
Every configuration change follows the same loop. You inspect what exists, review a plan, approve what needs approval, apply it, and read the result back. The portal reviews configuration; it is never a workflow canvas.
Start with the minimum
Most accounts need three things before their first run: an identity, a spend ceiling, and the one source the workflow reads.
- Set up a solo Compute account — one person, one scoped identity, one workflow.
- Set up a Compute organization — legal account, administrator and policy.
- Plan, apply and read back a change — the loop every change follows.
- Set spend and approvals — ceilings and who decides.
Add advanced resources when a workflow needs one
Everything below is optional. Add a resource when a workflow you have chosen actually requires it, and not before.
- Separate work with projects — isolate keys, budgets and costs.
- Run Compute for your own customers — tenant separation and delegated administration.
- Register a source — where your input is read from.
- Register a destination — where results are written.
- Build reusable workflow profiles — team defaults for quality, policy, output and limits.
- Describe your configuration as a file — secret-free desired values you keep in version control.
When something stops partway
An apply can stop on an expired plan, a changed resource version or a timeout in an external system. Verified changes stay in place, and every stopped resource carries a next action.