HOW IT WORKS
A control point before execution.
Aegis evaluates a supported intended action against a configured rule. In an enforcement mode, the decision determines whether that action proceeds.
pip install restricted-exampleControls and record details vary by supported integration and deployment mode.
Blocked. Decision recorded for review.THE EXECUTION PATH
From intent to a reviewable decision.
- 01
Observe the intended action
A supported command, package action, tool invocation or external service request approaches execution.
- 02
Evaluate the configured rule
Aegis evaluates available action details and runtime context against the relevant explicit policy.
- 03
Allow or block
An allowed action proceeds. A blocked action does not proceed through the controlled path.
- 04
Preserve the trace
Where supported, the action, policy, decision and resulting outcome are available for review.
COMPLEMENTARY CONTROLS
A different question at every layer.
Identity asks who the agent is. Access controls determine what it can reach. Runtime policy evaluates what it is about to do.
Aegis complements identity, authorization, model, API and network controls.
A FOCUSED PRODUCT WALKTHROUGH
See the decision point.
Bring your workflow. Explore the actions Aegis supports and the evidence your team can review.