Skip to content
Join the waitlist

Release decisions backed by evidence.

Pass/fail summary. Open defects. High-risk changes. Approval queue. Risk acceptance. Every decision signed against the mission ledger.

Watch a release candidate pass its evidence gates. When it reaches the barrier, you approve it.

Governance layer Audit trails
Capability · Release
  1. Group: Completed missions in the release group.
  2. Tests: Test results across unit, integration, E2E, accessibility. Open defects with severity and owner.
  3. Security: Security findings (SAST, dependency, secret scan). Pull requests merged into the release branch. Deployment health-checks and synthetic probes.
  4. Approve: Required approvals — present and outstanding. Approval queue · Outstanding gates with named approver.
  5. Ledger: Ready · All gates green. Release approved with hardware-token attestation. Every decision signed against the mission ledger.

capability runtime · streaming

Uptime
99.98%
Latency
14.2ms
Nodes
128/128

Evidence

412 / 418 evidence packs signed today

release readiness · evidence-backed

Delivery

3.4× velocity · 22% burn

  • playwright
  • bdd
  • api
  • a11y
  • visual

What feeds the release decision.

Seven inputs. A release decision reads all of them, including the approvals that are still outstanding.

  • Completed missions in the release group
  • Test results across unit, integration, E2E, accessibility
  • Open defects with severity and owner
  • Security findings (SAST, dependency, secret scan)
  • Pull requests merged into the release branch
  • Deployment health-checks and synthetic probes
  • Required approvals — present and outstanding

What operators see.

Five panes in one window, from suite results to the gates still waiting for a named approver. The shapes inside are samples.

Illustrative interface, fictional data. EngynQA. Release 2.4 · RC-3 runs 86 tests in 6 suites, streams its log and attaches its evidence. The release gate's checks turn green one by one and the gate changes from Blocked to Passed, then the human approver signs off.

Four states. One ledger entry.

Record a decision in any of the four states. Watch what it does to the release, and see the single entry it writes.

  1. All gates green; release approved with hardware-token attestation.

  2. Operator accepts named risk; acceptance recorded in ledger.

  3. Blocker present; release rejected with reason and remediation owner.

  4. Specific fixes required; release re-evaluated automatically when met.

Mission ledger Sample
  1. No decision recorded yet.

Keep reading.

Start a Software Factory pilot.

  1. One repository
  2. One ticketing tool
  3. One mission
  4. Evidence

Connect one repository, one ticketing tool, and one mission. See evidence in days, not quarters.

Book a pilot Join waitlist