# ArcRelease

> ArcRelease is release governance for software teams that have to answer for what they ship. It reads the tools a team already runs, judges every release pass, warn, fail or not checked, scores risk with every point cited, and records any decision to ship past a failure as a signed statement with evidence. It is advisory by design and never sits in the deploy path. ArcRelease is a Stackaid product.

## What is live today

- Preflight: seven checks on every release (release ceremonies, risk score, open incidents, change freeze, upstream dependencies, approvals, security findings).
- Four verdicts: pass, warn, fail, and not checked. "Not checked" means no evidence was captured; it is never counted as a pass.
- A deterministic risk score (model gaja-deterministic-v1). Points come from evidence such as failed deploys, open incidents, pending ceremonies, security findings and critical dependent services, each within a fixed cap, and every point is listed with its reason.
- Signed overrides: shipping past a failing check requires an admin or release manager to sign a statement and attach at least one evidence link. The preflight is snapshotted at that moment.
- An immutable audit log: the database blocks updates and deletes.
- Evidence capture from GitHub, GitLab, Bitbucket, Jenkins, CircleCI, Argo CD, Snyk, SonarQube, PagerDuty, Datadog, Grafana, Jira, Linear, ServiceNow and Freshservice; notifications to Slack.
- DORA analytics, and a workflow builder with sandboxed code nodes.

## What is next (not live yet)

- ArcCode: start a change from a ticket in the project's tracker (Jira, Linear, GitHub Issues or Asana) with the coding tool a team already uses (for example Cursor, Claude Code or Codex; one tool for every stage, or a second for review), through human-gated stages: spec approval, coverage check, code review, and acknowledgement of every decision the agent made alone.
- Project setup: project documents (PRD, FRD, BRD), branching strategy, per-stage human gates, and release and hotfix workflows.
- Backtrack: trace an incident to its deployment, release, pull request, commit, ticket, requirement, review and ruling.
- ServiceNow change requests evaluated as a gate (they are captured today), and test and performance results as evidence.

## Principles

- Never in the deploy path: if ArcRelease is down, nothing stops.
- Absence of evidence is reported as absence.
- Neutral: it reads every tool and is owned by none.

## Links

- [Home](https://www.arcrelease.com/): what ArcRelease does, the preflight board, and FAQ.
- [Platform](https://www.arcrelease.com/platform)
- [Security](https://www.arcrelease.com/security)
- [Learn](https://www.arcrelease.com/learn)

## Getting started

Teams start with a 30-day, read-only pilot: connect the tools already in use and see the next release judged. Request one from the home page.