AEGIS Sentinel
Home
Workspace Control
Start with one controlled workflow
AEGIS is built for one clear use case: approval and audit for AI agents and autonomous workflows before they touch production systems.
Customer Guide
How AEGIS controls agent actions
The agent sends the intended action to AEGIS before touching a real system.
AEGIS checks context, behavior, policy signals and operational risk.
Risky actions wait for approval, denial or a recurring customer rule.
Before execution, the agent confirms the approval is still valid and still matches the action.
Approvals, blocks, rules, confirmations and repeated matches remain visible in the activity trail.
Decision Preview
Waiting
No action validated yet.
Customer Portal
Billing
Sign in to load billing status.
Usage
Current Month
Plan Management
Upgrade without losing data
Upgrades keep the same workspace, memory, activity history and agent keys. Only plan limits and billing change.
Invoices
Billing History
Onboarding
Next steps
Generate one key for the first agent or automation.
Paste the validation call before sensitive actions.
Run one safe action and confirm the workspace is receiving decisions.
Support
Contact AEGIS
For onboarding, billing or security questions, contact AEGIS support.
aegis.sentinel.team@gmail.comGuided Setup
Connect in three steps
Connect is the setup workspace: create an agent key, copy one validation snippet, then send a safe test action before the automation touches a real system. Keep the workflow in human-review-first mode until you trust the pattern.
Sign in to load subscription status.
Create a key for the first agent or automation.
Run one safe validation to confirm the integration.
Agent Access
Generate agent key
Create adds a key for a new agent or automation. Rotate is available only on the current key and replaces a lost secret. Older keys remain listed for compatibility without customer actions. Secrets are copied once, never displayed again. Billing period, limits and retention stay unchanged.
Existing keys
Step 2
Copy the validation call
Place one snippet immediately before the real action. If AEGIS asks for review, the agent pauses until a human decision is recorded.
Runtime Rule
What the agent must do
Customer deployments start in review-first mode. Managed execution is reserved until explicitly enabled.
Guide
Understand how AEGIS protects a workflow
This page explains the operating model. Use Connect only when you are ready to generate an agent key and paste the validation call into a real automation.
The agent sends the intended action to AEGIS before touching a real system.
AEGIS compares the action with workspace history, policy signals, behavior and operational risk.
Risky actions wait for approval, denial, or a recurring customer rule.
Approvals, denials, expiry and rule changes remain visible without exposing internal engine logic.
Where to place AEGIS
Protect the actions that can hurt a business
Automation Recipes
Where the validation call goes
Core Concepts
What the terms mean
Activity History
Every permission change in one place
Find decisions by workflow, actor, decision type or mode.
See the decision, risk band, permission status and expiry without exposing private engine logic.
Download a customer-safe report for approvals, denials, rule changes and permission checks.
Activity Search
Find an action, approval or rule change
Inspector
No selection
Timeline
What changed
Activity Export
Customer-safe evidence
Workspace Settings
Workspace defaults
Billing, invoices and upgrades are managed from Account.
Agent API keys are generated from Connect and secrets are copied once, then hidden.
Guardian and Observer are available. Managed execution remains reserved.
Activity history is kept according to the current plan.
Notifications
Approval / action webhook
Use Review to notify a human channel. Use Action to continue a paused Make, Zapier or n8n workflow only after approval.
Safety Defaults
How this workspace runs
Billing & License
Plan Control
Billing not loaded yet.
Customer Onboarding
Account Setup
Complete a paid checkout before onboarding.
Internal Settings
Console Maintenance
Development/demo controls. In a customer workspace this stays restricted to internal operations.
Platform Intelligence
Platform Observability
Internal-only view of customers, trials, payments, abuse, usage, errors and growth. Customers do not see this layer.
Customers & Plans
Payments, Trials & Errors
Learning Signals
Platform Console
Customers, Plans & Abuse
Internal-only. Customers cannot see this panel, global learning signals, payment signals or abuse controls.
Operator Radar
What needs attention
Internal-only summary of trials, abuse, payment issues, errors and usage spikes.
Trial Control
Free Trial Policy
Internal-only. Final trial rules, expiry behavior and abuse signals are visible here before public selling.
Customers
Accounts
Open details, review usage by organization, block abusive trials or unblock trusted accounts.
Customer Detail
Usage & Recent Activity
Approval Workspace
Review risky actions without engine noise
Approval Queue
Actions waiting for review
Risk History
Recent decisions
Monitored Workflows
Known agents
Execution Gateway
Gateway Runs
Universal Agent Layer
Integration Kit
Control Maturity
Learning Gate
Learning mode is active by default.
Safety Controls
Active guardrails
Customer Controls