Quick start · UPDP Docs

Start a workflow, review the generated infrastructure, and approve it through the human gates.

Start a run

A run begins with a Statement of Work and ends with a reviewed pull request. You launch it from the workflow screen in four steps.

Open a new workflow

Select New Workflow to start a delivery run. This is the entry point for turning a SOW into infrastructure.

Upload the SOW

Choose Upload and add your SOW document. The SOW Analyzer parses it into structured requirements and reuses learning from past SOWs to fill in the details.

Confirm the extracted requirements

Review what was pulled from the document: project, client, services, region, compliance target, and timeline. Add context to override or supplement anything the SOW left ambiguous.

Launch the pipeline

Select Launch. The orchestrator sequences the agents, checkpoints the run state, and opens the pipeline canvas so you can follow progress.

Watch the pipeline

The run opens on the pipeline canvas, a live map of the six delivery phases: Initiation, Analysis, Infra Generation, Deploy, Docs, and Handover. Each node on the canvas is an agent, and the orchestrator streams progress to it as work advances.

A running node shows a live thinking indicator while its agent works.
A completed node carries its duration and the output it produced.
A gate node pauses the run and waits for a human decision before the pipeline continues.
On a critical failure the run halts; you can retry without re-running the steps that already finished.

During Infra Generation you can watch the Routing Engine split the work: OneClick provisions the base infrastructure while TerraFormGen writes the additional services. The two outputs combine into one Terraform file set, which the Compliance check then scores.

Review and approve

Nothing critical is applied without a person confirming it. The pipeline pauses at each gate, shows the relevant output, and records who decided what.

Admin gate before analysis: an admin approves cross-account access and IAM role creation.
Tech Lead gate after generation: a tech lead reviews the Terraform and the compliance score before the GitHub apply. A passing score with zero critical findings is safe to proceed.
Tech Lead gate at deploy: a tech lead guards the apply itself.
Final handover gate: a project manager performs the final verification before the project closes.

Human gates are mandatory

Every critical step waits for an explicit approval, and each decision is recorded against the run. A tech lead must clear the Terraform and compliance review before apply, and a project manager signs off the handover. Your assigned role, set through Zoho OAuth and AWS Cognito, determines which gates you can act on.