Control every action
your AI agents take.
Put policy, approval, execution boundaries, independent verification, and evidence between AI intent and real-world impact.
Control intent
before impact.
Aegis sits in the action path. Analysis can recommend. Authority decides whether an action is allowed, blocked, or must wait for approval.
Identity. Scope. Policy. Evidence.
File, shell, git, package, secret, API, database, and deployment actions can be mediated through the same explicit trust boundary.
One place to see
who can do what.
Agents, actions, approvals, policy, incidents, and evidence come together in one operating surface. The screenshot shows the Aegis interface with demo workspace data.
Know the actor.
Identity and scope stay visible before software is trusted to act.
Gate the action.
Policy decides what the current task is actually allowed to do.
Check independently.
Verification stays distinct from the system that proposed the change.
Keep the record.
Evidence explains why an action was allowed, blocked, or escalated.
Start next to the code.
Expand when you need control.
Aegis lives in VS Code. No web signup is required to start with Community. There is no separate Aegis username and password account to create.
code --install-extension aegis-security.aegis-securityInstall details →
Aegis Snapshot
Drop one file.
See the review surface.
A browser-local preview for the first thirty seconds of evaluation. Source stays in this tab. Snapshot surfaces deterministic review signals; it does not issue a security verdict or replace full Aegis verification.
Nothing is called safe before evidence exists.
Add one source file. Snapshot will map a small set of deterministic review signals locally, then hand the full-repository decision back to Aegis.
Review surface materialized.
Snapshot can point at code. It cannot establish the repository-level security claim.
- Reachability
- UNKNOWN
- Exploitability
- NOT ESTABLISHED
- Attack path
- NOT TRACED
- Safe reproduction
- NOT RUN
- Remediation
- NOT PROVEN
- Regression proof
- NOT VERIFIED
Lexical signals can prioritize review. Full evidence, authorization, and verification remain product work.
Need the repository, attack graph, remediation, and proof? Snapshot stops before authority begins.
Don’t trust “done.”
Verify what actually held.
Aegis keeps the finding, proposed change, executed checks, and final decision separate. The result is a chain you can inspect instead of a badge you have to believe.
See the path before the verdict.
Attack Graph / Data Sentinel materializes source-to-sink paths, trust crossings, evidence, and sensitive flows before Aegis asks you to trust a conclusion.
Fixing code is not proof.
A generated patch is a proposal. Aegis keeps remediation review separate from target re-verification, regression checks, dynamic replay, rollback state, and the final decision. NOT RUN never becomes PASSED.
Incomplete evidence stays incomplete.
Trusted Analysis preserves executed tasks, policy, audit evidence, and integrity state without substituting planned work for executed proof.


Start here
One product.
Two obvious ways in.
Use Community to get into the product. Use Founding Pro when you want the paid verification and remediation path.
Install. Open a project. Inspect the evidence.
- 01Install Aegis from the VS Code Marketplace.
- 02Open a project you are authorized to inspect.
- 03Run Aegis and review the security record.
Identity. Checkout. Server-side activation. Back to Aegis.
- 01Start Founding Pro and establish your GitHub identity.
- 02Complete the secure Paddle checkout.
- 03Aegis waits for authoritative server entitlement before showing paid access.
- 04Open Aegis in VS Code with the entitled identity.