◧ RELEASE COMMAND CENTER / gradesmatch
Release governance

Fleet release status

—
What this gate enforces

Candidates and release notes are read live from git. The gate is QA sign-off → green-light → release, order-enforced: a step cannot be skipped, and approvals bind to the exact commit they were given for. Releases touching PII or high-risk paths are auto-detected and require a second person to green-light them — the approver must not have written the sensitive changes. Every action is written to an append-only audit trail with the actor, source IP and a correlation id: the POPIA change record.

Reading release candidates from git across the fleet — first load after a restart only.

Recent prod deploys — closed loop: reality from Bitbucket + health check

…
—
◧ Release Command Center

Sign in

Checking your session…

Sign in with Google
Forgot your password?

At least 8 characters, with an uppercase letter, a lowercase letter, a number and a symbol. Not one you have used before.

✓ Check your inbox — a sign-in link is on its way to . It expires in 15 minutes.
Use an operator token instead← Back to sign in