Aegis

Vaults / Access / Automation

Secrets for people and agents.

Save API keys, tokens, and logins in encrypted vaults. Choose who gets access, see when a vault was used, and revoke access when the work is done.

An agent can refer to a secret by name. Aegis gives the value to a trusted command and masks it in the output the agent sees.

Available today · Staging example

How vault access works.

  1. Staging vault

    Save a secret

    The client saves a deployment token in an encrypted staging vault.

  2. Release agent

    Grant access

    The client grants the agent access to the staging vault for a deployment check.

  3. Client handoff

    Review and revoke

    The client reviews vault access and revokes the grant. The next attempt is denied.

Planned Community access

Two ways to start free.

Both editions will support personal and commercial use, with multiple vaults and no project limit.

Cloud

Free One workspace per operator

Aegis hosts your workspace and manages the server, email delivery and encrypted backups.

Self-Hosted

Free One installation per operator, with no expiry

Run Aegis on your own VM. You control the keys and manage email delivery, storage and backups.

Optional donations help cover hosting and maintenance costs.

Available today

Store it. Scope it. Use it.

Organize credentials by project or environment. Give each person or agent the permissions they need in that vault. Choose end-to-end encrypted vaults when you want credentials unlocked on your device.

Store credentials

A Secret holds a single value, such as an API key. A Login keeps a username and password together with an optional website, app ID, and notes.

Grant access

Set access per vault. Login discovery shows the item key and field names. Reading Login values, searching saved websites and app IDs, and injecting credentials from server-managed vaults require Read access.

Use secrets with masked output

Aegis passes the real values to a trusted command. It masks matching values in both normal output and error output before forwarding them to the agent or terminal.

Command lineExample
aegis run --vault staging --only STAGING_TOKEN -- ./check-staging.sh
Authenticating with [REDACTED:STAGING_TOKEN]
Staging deployment healthy.
Example command with a sample token and illustrative output.

End-to-end encrypted vaults

A Use-only grant lets an enrolled agent run a command with a secret by name. Reading the value directly through Aegis requires a separate Read permission.

Server-managed vaults

Output masking also works here. Command use requires Read access, which also allows the agent to fetch the secret value directly.

Available today

The app, your terminal, and your agent.

Review vault activity in the audit trail. When version history is enabled, restore an earlier version of an item.

01 macOS
Search and copy from the menu bar. Use Aegis Studio to manage vault items, grants, and version history.
02 CLI
List vault items, manage secrets, and supply selected secrets to commands and scripts.
03 MCP
Connect a compatible AI tool to discover vault items and make HTTPS requests with secret references to origins approved by the MCP host.
04 Browser
Save logins and fill matching sites in Chrome and Edge with the Aegis extension.

Planned

More ways to manage access.

Optional add-on

Approve a single action

Let an agent request a specific read-only check. A service on the customer’s infrastructure uses the credential and returns only the status. The pilot will undergo independent security review before production credential use.

Hand control back to the client

Give the client owner a browser console to revoke agent access, verify that the next attempt is denied, and export the handoff record.