> For the complete documentation index, see [llms.txt](https://docs-launchpad.energyweb.org/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs-launchpad.energyweb.org/energy-web-verified-compute-cloud/how-the-verified-compute-cloud-works.md).

# How the Verified Compute Cloud Works

The Verified Compute Cloud is supported by four products (Launchpad, VCC Gateway, VCC Runtime, VCC Explorer) running on the Energy Web X coordination layer.

**Launchpad** is the configuration and deployment interface used by solution builders and registrars to define Verifications and deploy VCC Solution Groups. **VCC Gateway** is deployed within an enterprise's own infrastructure and acts as the secure boundary between the organisation's data systems and the VCC network. **VCC Runtime** nodes, operated by independent **VCC Operators**, execute Verifications and submit results on-chain. **VCC Explorer** provides a public read-only interface for inspecting verification outputs. **Energy Web X (EWX)** is the blockchain coordination layer that records vote submissions from VCC Runtime nodes and maintains the permanent on-chain record of every verification round.

### Verification lifecycle

**Step 1: A solution builder configures a Verification on Launchpad**

A solution builder uses Launchpad to create a VCC Solution Group (VCG) and define one or more Verifications within it. Each Verification specifies the Verification Logic (the computation to be run) and the Verification Consensus Rules (how many operators must agree, over what time period, and under what conditions). The solution builder also selects the proof mode, configures the operator participation model, and downloads the Gateway deployment package. Once the VCG is deployed, the Verification Logic and Consensus Rules are published on-chain via the Verified Compute Node Pallet on EWX.

**Step 2: The enterprise deploys VCC Gateway**

The enterprise installs VCC Gateway within their own infrastructure, connecting it to the data systems that will feed verification rounds. Raw data does not leave the Gateway.

**Step 3: The enterprise submits data for a verification round**

When a verification round is triggered, the enterprise's system pushes data to the Gateway's ingest API. The Gateway prepares the input dataset and publishes a verifiable commitment to the network: a deterministic hash of the inputs (a ComputeReceipt) in standard mode, or a zero-knowledge proof in ZK mode, along with the relevant round status on-chain. The Verification Logic itself is executed by VCC Operators, not the Gateway.

**Step 4: VCC Operators execute the Verification independently**

VCC Runtime nodes pick up the verification round. Each operator retrieves the Verification Logic, fetches the verification payload, executes the logic independently, and submits their vote to Energy Web X. Because the computation is performed by multiple independent parties simultaneously, no single node controls the outcome.

**Step 5: EWX records consensus**

The Verified Compute Node Pallet on EWX applies the configured Verification Consensus Rules. When the threshold of matching votes is reached, the agreed result is recorded on-chain as the verified output of the round.

**Step 6: The result is visible on VCC Explorer**

The round details, operator participation, vote submissions, and consensus output are visible on VCC Explorer. The level of detail visible publicly can be adjusted based on the privacy configuration of the VCG, but the existence and integrity of the verification is always recorded on-chain.