Home/Platform/Release governance
Pillar 2 of 6

Every gate, owner and sign-off on the record

Most teams have governance. What they do not have is evidence. ArcRelease records every ceremony as it happens, attributes it to a named owner, escalates the ones that slip, and exports the result as something an auditor accepts.

In short

What is release governance evidence?

Release governance evidence is the timestamped, attributed record of who approved what, when, and on which release. ArcRelease captures it at the moment of the decision instead of reconstructing it from Slack scrollback before every audit.

The problem

Where governance falls apart today.

“

The governance happened. The evidence did not get recorded, so it gets rebuilt from memory before every audit.

“

My sign-off is a Slack thumbs-up. Six weeks later, in an audit, nobody can prove I ever gave it.

“

Evidence collection is screenshots pasted into a spreadsheet, and we call it a control.

Release governance

Captured at the moment of the decision.

A control you reconstruct after the fact is not a control. ArcRelease records each ceremony as it happens, names the owner, escalates the ones that slip, and turns the trail into a one-click export.

100%
release audit trail coverage, captured at decision time
Design target from product modelling. As of July 2026.
Every gate carries one named owner rather than a group or a shared mailbox.
Gates that slip auto-escalate with the owner and the overdue time attached.
Overrides are permitted and recorded with a reason and a person — because a control nobody can override becomes one everybody routes around.
One-click audit export as PDF or JSON, targeting 100% coverage captured at decision time.
The trail feeds the Gaja verdict, so an unsigned gate shows up as a cited reason before you ship.
How it works

What actually happens.

01

Define the ceremonies

QA sign-off, security review, deploy approval — whatever your gates are, each with a named owner.

02

Record as it happens

Approvals are captured with a timestamp and a person, not reconstructed from chat later.

03

Escalate the slips

A gate that goes overdue escalates automatically to the next owner up the chain.

04

Export in one click

The whole trail exports as PDF or JSON — the evidence hunt before an audit disappears.

Who this is for
Release ManagerCompliance / Audit / SecurityQA / Test Lead
Reads from
JiraGitHubSlackServiceNow

ArcRelease records governance signals from these tools. It is not a deployment engine and never writes to your code.

FAQ

Release governance, answered.

ArcRelease is built to SOC 2 controls and the Type II audit is in progress; we will not claim a report we do not hold. What ships today helps you evidence your own SOC 2 change-management controls.

Yes, and the override is recorded with a reason and a person. A control that cannot be overridden gets routed around invisibly, which is the worse outcome.

No. It records the ceremonies you already run and, if you use ServiceNow, reads change records as one signal. It adds evidence, not another workflow to maintain.

Related capabilities

Gaja AI preflight
GO, NO-GO or CONDITIONAL, with its reasons attached.
Read more →
Incident correlation
From alert to the pull request that caused it, in about ten seconds.
Read more →
Release risk analytics
DORA four keys, decomposed by service and team.
Read more →

Stop guessing at go/no-go.

Tell us about your release process. Connect your stack in ten minutes, run a Gaja preflight on a real release, and see the reasons behind the verdict.

See the platform

Free plan · ten minute setup · we reply in one to two business days