AIZOYA · GitLab Life After Code

Know what’s behind the green check.

ReleaseProof explores how teams can investigate failed pipelines and review evidence for the exact release candidate before a person makes a decision.

Explore the demo →See GitLab evidence

Prototype · Demo data only · No production release authority

Release reviewIllustrative example

Review blocked

Evidence must match the candidate under review.

Candidate identityExact commit matters

Evidence statusMissing results remain visible

Human reviewA person decides

GitLab DuoReal assisted run recorded

Interactive experience

Try an evidence check.

Explore three synthetic scenarios. This browser-only demonstration is separate from the local ReleaseProof workbench and does not collect live GitLab data.

Candidate evidence

Synthetic demo

Choose a scenario to see why a passing pipeline alone is not enough.

Release candidatea1b2c3d

Pipeline evidencef6e5d4c · passed

Blocked · commit mismatch

The green pipeline belongs to a different commit.

Pipeline evidence does not match the candidate.

Matching synthetic evidence means ready for a simulated review only. This demo does not record a human decision, verify GitLab provenance, certify compliance or authorize deployment.

01 / Investigate

Understand the failure

GitLab Duo investigated a controlled failed pipeline and suggested a targeted fix.

02 / Verify

Check the right candidate

Review commit identity and required evidence before treating a result as applicable.

03 / Decide

Keep people in control

Human approval is the intended next step; the current prototype does not persist a release decision.