Changelog | Approvegate — is this change approved to ship?

October 4, 2026

Start free in shadow mode

Anyone can now sign up and start without talking to us. New services start in shadow mode: Approvegate records what it would have blocked without stopping any deploys, so you can see your gaps before you enforce.

Done

✅ Self-serve sign-up
✅ Shadow-mode getting-started guide in the docs
✅ Annual billing shown by default on pricing

October 2, 2026

Audit evidence search and auditor samples

Find any deploy's evidence in seconds and answer an auditor's sample request in one step. Upload the auditor's sample list as a CSV, Approvegate matches each row to its evidence package, and you download the set as one archive.

Done

✅ Evidence search with service, environment and decision filters
✅ Evidence package view: change, approvals, separation of duties, traceability, deploy checks and audit events
✅ Auditor sample import with automatic column mapping
✅ In-app notifications for approval requests
✅ Readiness checklist on release requests before they can be approved

October 1, 2026

Protected services, freeze windows and deploy check details

Switch each protected service between Shadow and Enforcing, with 7 days of allow and block counts on every card. Switching back to Shadow requires a reason, recorded in the audit log. Deploy checks now print an aligned ALLOW or BLOCK summary in your CI logs (approvegate-cli v1.3.2).

Done

✅ Shadow / Enforcing switch per service and environment
✅ Freeze windows with a weekly view
✅ Release Records with per-check drill-in
✅ Dashboard with pending approvals, deploy and block counts

September 16, 2026

Tamper-evident audit log and evidence export

Every deploy check, override and policy change is written to a hash-chained audit log. Export a per-deploy evidence package as JSON or PDF, or a population CSV for your auditor.

Done

✅ Hash-chained audit events per workspace
✅ Evidence packages (JSON and PDF)
✅ Post-release sign-off

September 15, 2026

Change management and separation of duties

Release requests with required change details, approval workflows with minimum approvers, and a separation-of-duties policy that can stop requesters from approving their own changes.

Done

✅ Release requests and approval workflows
✅ Separation-of-duties policy (Advisory or Enforcing)
✅ Approvals bound to the commit SHA on the first passing deploy check
✅ Emergency override with a required reason