A finding is not a verdict.
Security conclusions stay distinct from the evidence that supports them.
Trust infrastructure for software and AI agents
Security claims
need proof.
Trust cannot be another model output.
Today, Aegis independently verifies security-sensitive software changes: what was claimed, what evidence supports it, what was authorized, and whether the resulting change actually held.
code --install-extension aegis-security.aegis-security Available nowLinux x64Install details
Real Aegis product capture · Attack Graph / Data SentinelVS Code
The trust problem
Software can act.
Trust cannot be assumed.
AI can propose changes and software can increasingly act without a human writing every line. That makes a security answer less important than the chain behind it: evidence, authorization, independent verification, and an explicit decision.
A patch is not proof.
A proposed change does not get to certify that it solved the problem it addressed.
Missing proof stays missing.
Uncertainty remains visible instead of being flattened into a clean-looking answer.
How Aegis works
Claim → evidence → authorization → verification → decision.
Security-sensitive behavior identified.
Aegis keeps the security claim separate from the evidence used to support it. A finding does not become a verdict just because a scanner or model produced it.
source boundscope explicitprovenance retained
Product proof
See the record.
Not just the warning.
The shipped product keeps the security claim, supporting evidence, authorization state, remediation lifecycle, and verification outcome available for inspection instead of compressing trust into a single score.
Developer surfaces
One trust system.
Where software ships.
VS Code, the GitHub Action, and the CLI/local runtime expose the same underlying separation between analysis, evidence, authorization, verification, and decision.
01 / VS CODE
Inspect next to the code.
Review security findings, evidence, verification, policy, and remediation state inside the development loop.
Install Aegis → 02 / GITHUB ACTIONCarry verification into CI.
Use the public integration surface to preserve machine-readable verification artifacts around software changes.
Developer details → 03 / CLI + RUNTIMEKeep the workflow local-first.
Run supported deterministic workflows through the local runtime. Current packaged target: Linux x64.
Installation details →Built for trust
Confidence should come from boundaries, not branding.
Aegis separates analysis from permission, a proposed fix from post-change verification, and a billing redirect from actual paid authorization.
Security at Aegis →Local-first developer path
Supported deterministic analysis, evidence, policy, and security state can remain on the developer machine by default.
Explicit authorization
Security-sensitive execution and mutation are treated as separate capabilities rather than implied by analysis.
Independent verification
A proposed result is not trusted merely because the component that created it says it is correct.
Server-authoritative paid access
Founding Pro authorization comes from signed, server-side billing state rather than a client-controlled success screen.
Today and direction
Start with software security.
Build toward accountable autonomy.
The product and the long-term thesis are related, but they are not presented as the same thing.
TODAY
Shipping product · 0.2.4Independent security verification for software changes.
Aegis gives developers an inspectable path from security claim and evidence through authorized validation, remediation, and independent verification.
DIRECTION
Long-term product directionTrust infrastructure for increasingly autonomous software and AI agents.
As software takes more actions on its own, Aegis is being built toward the same core questions at a wider scope: what happened, was it authorized, what proves the result, and should it be trusted?
Pricing
Start free.
Scale the verification boundary.
Start with Community. Founding Pro is $19/month. Team is $49 per active contributor with direct setup, and Enterprise is scoped with the organization.
Community · available
$0
For individual developers using the local-first Aegis workflow.
- VS Code extension
- CLI + local runtime
- Local evidence workflow
- Core local verification
$19 / month
For professional developers who want the shipped paid verification and remediation capabilities.
- Attack-surface and threat-model analysis
- Task planning and deeper trusted analysis
- Authorized dynamic validation
- Secure-fix and Fix & Prove workflows
$49 / active contributor
For engineering teams that want Aegis across a shared development workflow. Team is $49 per active contributor, with setup handled directly by Aegis at launch.
- Everything in Pro
- Team onboarding and provisioning
- Shared verification workflow setup
- Pull-request and policy scope agreed before enablement
Custom
For organizations evaluating private deployment, governance, and deeper security integrations.
- Private or hybrid deployment discussion
- Organization policy and governance scope
- Security and data-boundary review
- Integration scope defined before enablement
AEGIS
Security claims
need proof.
Install Aegis, open a project, and inspect the evidence yourself.