history buffer
Run a command to capture the last five entries here. Each row stays compact until you expand it.
LAB navigation
Each tab keeps one lane legible: control plane, workload, modern workloads, cloud terminals, or the microservice fabric.
Use this lane to stage and audit a federated workflow that starts on-prem, fans out across AWS, Azure, and GCP, then commits back into the VCF system of record. The current implementation is design-first with live guardrails, ledgering, and per-cloud status checks.
Multi-cloud live workflow
Expand to see the phase-by-phase operator sequence for this tab.
Confirm VCF reachability, recent on-prem ledger state, and current cloud compute counts before a federated workflow is allowed to start.
Make VCF the system of record by creating one authoritative workflow request in the on-prem note stream and audit ledger.
Model the AWS API Gateway, Lambda, SQS, SNS, and Step Functions portion of the flow while checking the current AWS runtime posture.
Represent the Azure Functions, Service Bus, and approval branch while checking Azure runtime posture and audit activity.
Represent the GCP Pub/Sub, Cloud Run, and archive branch while checking the current GCP footprint and audit stream.
Merge the three cloud branch states with the on-prem run record and decide whether the workflow is ready to commit back into VCF.
Record the final VCF-side completion event and update the on-prem workflow note stream for the current run.
Read the full workflow ledger, then remove any leftover cloud resources and return to the target one-VM-per-cloud posture.
Live route
Multi
history buffer
Run a command to capture the last five entries here. Each row stays compact until you expand it.