Release security for lean teams

Ship with evidence. Keep your source private.

Aegis turns code, dependency, secret, malware, container, and dynamic checks into one explainable deployment decision—self-hosted, auditable, and built for teams without a full-time security department.

Private by defaultCI-ready gatesEvidence bundles
AEGIS / RELEASE GATE● EXAMPLE POLICY
Deployment decisionBLOCKED · 3 actions

New findings are grouped by severity, owner, and remediation path before they reach production.

Findings12
Blockers3
Checks7/7
The wedge

Make the release decision obvious.

Teams do not buy another dashboard. They buy confidence that a release is safe enough—and an evidence trail when someone asks why.

01

Connect the repo

Import a GitHub project or run the CLI locally. Keep repositories and credentials inside your approved boundary.

02

Gate the release

Use quick, standard, or deep presets with deterministic exit codes and policy thresholds that fit your delivery flow.

03

Prove the outcome

Share an HTML report, SARIF, SBOM, or evidence bundle with owners, timestamps, new-finding deltas, and integrity metadata.

Simple commercial path

Start free. Pay for confidence.

Founding pricing is intentionally manual while the product proves its repeatable onboarding and support motion.

Community

$0

Self-hosted / open source

  • CLI and GitHub Action
  • Local policy gates
  • Reports and SARIF
  • Community support
Explore the repo

Security partner

Custom

Controlled private deployments

  • Private deployment architecture
  • Identity and isolation readiness plan
  • Evidence and retention workflows
  • Security program advisory
Start a conversation

Current pilots use one isolated deployment per customer. Shared public multi-tenant hosting is not part of this offer.

Have a release coming up?

Bring one repository, one policy, and one deadline. The founding pilot is designed to produce a useful security decision in the first week.

Request a pilot →