ReleaseOps overview.

1. Capture deployment intake, ownership, scope, dependencies, and timing.
2. Run readiness checks and surface missing permissions or evidence.
3. Create or select a versioned playbook with validation and rollback expectations.
4. Collect approval gates and enforce separation of duties.
5. Guide execution through an available adapter or an explicitly manual step.
6. Validate the observed result or assign deferred validation with an owner and deadline.
7. Collect evidence, update audit history, communicate status, and close only when exit criteria pass.

• Deployment requests and their version history
• Repositories, applications, clients, environments, and dependencies
• Playbooks, approval policies, schedules, retries, and rollback expectations
• Change records, knowledge-transfer sessions, and extracted evidence
• Validation results, deferred follow-ups, audit history, reports, and exports
• Connector configuration and actual availability state

• GitHub and AWS live paths require configured, scoped credentials and safe test accounts.
• Azure and GCP analysis remain preview until live inventory is implemented and verified.
• Terraform and CLI artifacts can be reviewed; local Terraform apply remains disabled by the desktop safety contract.
• Communication actions require configured adapters and must surface delivery failures.
• Every external operation needs resulting evidence before it is marked successful.

Use the download page for the current installer and release status.